As Mark Russinovich decided to retire this. Here it still is. I don’t totally agree with the retirement. We, even after using MDT for deployment, would still, rarely run into some weird network issues with a machine. Putting it down to possible SID issues, running NewSID would fix it.
HASH starting with 07FA is for the zip file
MD5 Hash 07FA425D722FD5E63BFE6B1BAC26EC5B
HASH starting with 73E7 is for the newsid.exe file
MD5 Hash 73E708D1126E7AF86A4EF820C24D80E4
MD5 Hash created with Chaos MD5
http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx
http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx
UPDATE: Should point out I’ve never used MD5 HASHes before so prob cocked that up, not sure. But file is clean, do a scan to check.
UPDATE 2: Thanks to Joe for pointing out the HASH above was off. But I realise now the HASH I originally stated (which will state in the comment) is for the zip file. To show it hadn’t been tampered with since downloading it ages ago from Microsoft when it was still available. I’m going to add a HASH for the .exe as well.
Steve..
I downloaded and unzipped the sid generator but the md5 hash starts with 73e708……. not 07FA…. Did you extract the hash number yourself or did you find it on the net?
Thanks,
J
HASH was created by me at a time when I didn’t really understand HASH’s properly using a 3rd party program to create the HASH (I still don’t really) so I may have either done it wrong or mistyped it.
I’ll have a look and can re-upload it.
I’m a stranger & I’d never trust strangers but can assure you it’s not infected. You can scan it. Bit annoyed that Mark removed it from Sysinternals because he retired, but I still found it useful for odd issues at work that did appear to be SID related.
I’ve just realised the HASH I mention is of the zip file not the newsid.exe
I also remember the reason I did that, was to point out that the ZIP file hasn’t been tampered with since I originally downloaded it when it was available from Microsoft.