Updates: PsTools and SysinternalsSuite
The following Sysinternals utilities and files have been updated:
- PsTools v.2.42: all PsTools now support the switch '-accepteula' on the command-line in order to avoid breaking non-interactive scenarios (e.g. scripts and other automation)
- PsExec v1.73: for Vista the tool now supports the ability to run processes in the Local System account on the interactive desktop with the -s and -I switches.
- PsGetSid v1.43: fixes a bug where it wouldn’t correctly process multiple computers
- PsService v2.21: adds support for reporting Windows Vista delayed autostart and pre-shutdown notification services
- 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.
Comments
Anonymous
January 01, 2003
Good idea (regarding the links). I was a bit rushed getting this posted. I've added links to all the updated tools. Thanks!Anonymous
December 05, 2006
Ah, so because Microsoft wants everyone to accept the PSTools EULA even though they've been using the tools for years, we now have to change all of our scripts. Makes sense.Anonymous
December 05, 2006
Direct links to the updated tools would have been nice ;)Anonymous
December 05, 2006
Agreed, a link to the new versions would be a nice touch ;) None the less, thanks for the new versions!Anonymous
December 06, 2006
The page of SysinternalsSuite: http://www.microsoft.com/technet/sysinternals/Utilities/SysinternalsSuite.mspxAnonymous
December 06, 2006
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: HKLMSoftwareMicrosoftWindows NTCurrentVersionPerflibAnonymous
December 06, 2006
Links to the tools would realy be nice. It is a bit not of a good idea to announce something without giving the opertunity to download the updates in an easy way.Anonymous
December 07, 2006
a very fine example of how again the microsoft corporation is as removed as possible from the end-user's needs as could possibly be. did you even waste a single thought on saving initial eula-acceptance in the registry or a local file stored in the same directory so we needn't change all our scripts just because of your paranoia?Anonymous
December 09, 2006
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? Mark, please fix this...Anonymous
December 09, 2006
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. MS Live Search is a waste of my time.Anonymous
December 11, 2006
This is soo stupid and really doesn't fit the quality of the tools...Anonymous
December 12, 2006
To avoid EULA (specially when scripting) create for each products the registry key EulaAccepted (type dword) with value 1 Like this .reg file REGEDIT4 [HKEY_CURRENT_USERSoftwareSysinternalsPsList] "EulaAccepted"=dword:00000001 You can use REG.EXE to distribute EulaAccepted for each product & userAnonymous
December 18, 2006
How about fixing BgInfo so that it correctly recognizes IE7 ... ? Thanks!Anonymous
December 18, 2006
Do you plan on also providing the "-accepteula" switch for "autorunsc.exe"?Anonymous
December 27, 2006
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?
- If Mark and Bryce do not provide updates, will other developers be working on these "free" tools?
- Any plans to add WSH support?
- How about fixes for CPU detection, hyper-threading and core detection?
- Are there any planned updates for BGInfo in the near future?
Anonymous
December 30, 2006
The comment has been removedAnonymous
January 04, 2007
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.Anonymous
January 18, 2007
Wow, let me be the first to post an unqualified postive comment: Thanks much for rounding up all the tools into one download -- I used to have to click, click click to make sure I had the latest version of this awesome tool collection.Anonymous
February 20, 2007
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>.Anonymous
March 01, 2007
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?Anonymous
June 26, 2007
Preciso de alguns updates específicos.Anonymous
June 29, 2007
The comment has been removed