SysinternalsSuite: removed the BlueScreen Screen Saver from the Sysinternals Suite since various 3rd party products mistakenly identify the screen saver as malware. The BlueScreen Screen Saver is still available as a download from its dedicated page here.

does pstools support Vista Bus Ed? I download the new Pstools and some fuction does not work at all when using it with Vista Bus Ed. For example when I ran pslsit \servername it returned the following error message

"Failed to take process snapshot on dc1.

Make sure that the Remote Registry service is running on the remote system, that you havefirewall p

rts allow RPC access, and your account has read access the following key on the remote system:

Yeah – this is really annoying! Lots of techs I know are having to trawl through heaps of scripts and processes just to see if they need to accept the EULA. Why not make us accept the EULA when we download the tools instead of every single time we use them?

It’s annoying that the license prompt is displayed again for each user and machine, but what really bothers me is that I can’t find the "Google Search" option in the Process Explorer context menu any more.

So it’s been a couple months and I would guess that Mark and Bryce will be focused on other areas now that they are part of Microsoft. BGInfo is a very useful tool but it becoming dated with respect to CPU and OS detection.

How do we go about requesting fixes/enhancements for these tools now? Through the forum?

1. If Mark and Bryce do not provide updates, will other developers be working on these "free" tools?

2. Any plans to add WSH support?

3. How about fixes for CPU detection, hyper-threading and core detection?

wow, I just saw the EULA deal when I grabbed a new version of HANDLE.EXE. I noticed that the size of it went up from 77k way up to 420k. When I ran it I knew why… that EULA agreement deal is taking up over 300k to the tool? wow, this is crazy… Strings.exe used to me 35k and is now almost 160k….

Microsoft, PLEASE remove the EULA from the programs themselves and make us agree to the EULA in order to download… or even make us agree to it when we unzip it?

In regard to the comment earlier on Pslist failing on Vista, that’s because Vista’s default security for the performance counters requires admin access – so run Pslist from an elevated command prompt and it works fine.

You know what? It’s not so bad that the new EULA is a bother. What burns me is that–after over two months of people complaining–nobody from Microsoft has bothered to post something in this thread to at least acknowledge that they understand the new EULA is inconvenient, but <insert PR rhetoric here>.

I was filled with dread when microsoft bought sysinternals and now I see that that dread was well founded. Is it that MS are embarrassed that the sysinternal tools are so superior to any that MS provided directly that they had to buy then break them?

Accpecting EULA is more than inconvenient, it is annoying when you use the tool in a command line one multiple systems (p.e. network path). Enter "-accepteula" is only a solution in scripts! For god’s sake I have an "old" version of pstools… (intersting, M$ has nothing done but changing the companies name and a beautiful dialog field)