2 replies to this topic

[BlackholeForever]

The autopatcher_2k_enu.script file has been updated just recently and the hash for:

Windows2000-KB941693-x86-ENU.EXE

has been changed from 39A60D22F07CF4FB65985934F553B11D to C76DC708FD36337FEACC64059498E48D.


However, the file hasn't changed and still produces an MD5 of 39A60D22F07CF4FB65985934F553B11D.

Can anyone confirm? Thanks...

[Steve Whalen]

BlackholeForever, on Jun 7 2008, 06:28 PM, said:

The autopatcher_2k_enu.script file has been updated just recently and the hash for:

Windows2000-KB941693-x86-ENU.EXE

has been changed from 39A60D22F07CF4FB65985934F553B11D to C76DC708FD36337FEACC64059498E48D.


However, the file hasn't changed and still produces an MD5 of 39A60D22F07CF4FB65985934F553B11D.

Can anyone confirm? Thanks...

I can confirm this. Downloaded file several times and using different methods. Get the MD5 the script "found" but thinks is wrong is in fact correct. From my apup.log:

Starting detection routine for item Windows2000-KB941693-x86-ENU.EXE
Looking for file U:\software\AutopatcherWin2k\modules\Critical\KB941693_2k_enu.apm_files\Windows2000-KB941693-x86-ENU.EXE
MD5 Hashes do NOT match. Expecting C76DC708FD36337FEACC64059498E48D, but found 39a60d22f07cf4fb65985934f553b11d!!!
Item Windows2000-KB941693-x86-ENU.EXE doesn't appear to be here. Adding its downloads to queue...
Adding http://download.microsoft.com/download/8/f...693-x86-ENU.EXE.

The MD5 hash I get manually on a verified good file (verified file by testing with 7zip) is: 39a60d22f07cf4fb65985934f553b11d

Steve

[Erik Ramey]

Thanks for the heads-up. Confirmed and fixed.