I keep getting:
***Starting Detection Routine Phase***
Detection error for file C:\Program Files (x86)\Autopatcher\modules\Critical\KB890830_x64_glb.apm
MD5 Hashes do NOT match. Expecting A241FADDD192C32F9A5AB2612620F232, but found 5017af3226856d11ea45c2071ab3a3b6!!!
Missing file C:\Program Files (x86)\Autopatcher\modules\Critical\KB956572_vista_x64.apm
Missing file C:\Program Files (x86)\Autopatcher\modules\Critical\KB960803_vista_x64.apm
Missing file C:\Program Files (x86)\Autopatcher\modules\Critical\KB963027_vista_x64.apm
Missing file C:\Program Files (x86)\Autopatcher\modules\Critical\KB959426_vista_x64.apm
Item AutoPatcher Critical Modules is missing. Adding its download to the queue.
--Adding http://www.autopatcher.com/releases/vista_..._vista_x64.7z--
***Downloading Releases***
Files to be Downloaded: 1
Download Error: C:\Program Files (x86)\Autopatcher\temp_bin\___windows_critical_vista_x64.7z
File size does NOT match. Expecting 11931, but found 11932!!!
***Processing Cleanup Routines***
Extracting C:\Program Files (x86)\Autopatcher\temp_bin\___windows_critical_vista_x64.7z into C:\Program Files (x86)\Autopatcher\modules\Critical
Chkdsk, reboot, rerun, etc - all no avail.
Download Verification Error
Started by mylogon, May 18 2009 08:34 AM
4 replies to this topic
#1
Posted 18 May 2009 - 08:34 AM
#2
Posted 18 May 2009 - 09:59 AM
It looks like a minor script edit is needed.
___windows_critical_vista_x64.7z
Size=11932
I don't know if the script is pointing to the most recent (KB890830) update as well?
Also -> C:\Program Files (x86)\Autopatcher\modules\Critical\KB890830_x64_glb.apm
What's the logic behind putting an x64 release in an x86 folder?
Update: The uploaded critical 7z file includes the apm for 890830 v2.9 (old) but the script points to 890830 v2.10. The updated
___windows_critical_vista_x64.7z (+890830 v2.10 apm) (-890830 v2.9 apm) must be uploaded - the script info may be correct?
Mike
___windows_critical_vista_x64.7z
Size=11932
I don't know if the script is pointing to the most recent (KB890830) update as well?
Also -> C:\Program Files (x86)\Autopatcher\modules\Critical\KB890830_x64_glb.apm
What's the logic behind putting an x64 release in an x86 folder?
Update: The uploaded critical 7z file includes the apm for 890830 v2.9 (old) but the script points to 890830 v2.10. The updated
___windows_critical_vista_x64.7z (+890830 v2.10 apm) (-890830 v2.9 apm) must be uploaded - the script info may be correct?
Mike
#3
Posted 18 May 2009 - 11:07 AM
wow. i forgot about vista x64. this issue will be fixed this morning, with the inclusions of ie8 and his updates (at least, i hope).
but i'm noticing that issue about Expecting 11931, but found 11932 since some time ago. i'm not sure about why, but seems that sometimes the uploaded file becomes 1 plus than should be. i believe that it's time to move to another ftp client...
thanks for your report
[]s
but i'm noticing that issue about Expecting 11931, but found 11932 since some time ago. i'm not sure about why, but seems that sometimes the uploaded file becomes 1 plus than should be. i believe that it's time to move to another ftp client...
thanks for your report
[]s
#4
Posted 18 May 2009 - 11:14 AM
The Vista script does show size=11931 for the critical 7z file, and the file size is 11932, but the critical 7z has the wrong
890830 apm included in it v2.9 - so it must be edited, the old apm removed and the new one included.
This may have already been done by the author but the wrong critical 7z was uploaded (the old one). Until the proper
7z is on the ftp there is no need to change the script just yet.
890830 apm included in it v2.9 - so it must be edited, the old apm removed and the new one included.
This may have already been done by the author but the wrong critical 7z was uploaded (the old one). Until the proper
7z is on the ftp there is no need to change the script just yet.
#5
Posted 18 May 2009 - 12:11 PM
mIkE, i'm also holding vista_x64 release, until an proper maintainer for that join the team. i don't have any version of vista, nor an x64 capable machine, so i can update this script, but i can't test if the proper files are in there or if the detections are in there. due that, i'm relying on reports about updates and other issues. also due that, user collaboration on report/tests are imperative.
the KB890830 issue shall be solved now. i had this module done since a few days ago, but i forgot to update this release... also, ie8 is now online, with his updates: +KB969058; +KB969497
this release will keep unsigned, until properly tested
[]s
the KB890830 issue shall be solved now. i had this module done since a few days ago, but i forgot to update this release... also, ie8 is now online, with his updates: +KB969058; +KB969497
this release will keep unsigned, until properly tested
[]s
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users











