I have searched the forum for my specific error but could not find any help, so sorry if I am starting a topic that has been discussed already.
I am getting a "Failed verification" error. Here is a copy of my log after the first run of autopatcher. I also tried deleting rootsupd.exe and started autopatcher again (deleted log file to) and the same error occurs.
"APUP Has Started
Operating System: English (1033) Service Pack 2
Current Locale: English - United States / Non-Unicode Default: English - United States
Starting APUP From: C:\autopatcher\apup
Date & Time: 22-Sep-2008 16:36 UTC Offset: -8
***Downloading/Processing Releases.list***
List file HTTP location: http://www.autopatch...m/releases.list
***Releases.list Processed: Waiting for User Input***
The Following Releases have been Picked:
apup.script
apengine.script
autopatcher_xp_2003_x64_enu.script
***Running Any Pre-Cleanup Routines***
***Starting Detection Routine Phase***
Missing file C:\autopatcher\apup\modules\Critical\RootCert_files\rootsupd.exe
Item rootsupd.exe is missing. Adding its download to the queue.
--Adding http://download.windowsupdate.com/msdownlo.../rootsupd.exe--
***Downloading Releases***
Files to be Downloaded: 1
Download Error: C:\autopatcher\apup\modules\Critical\RootCert_files\rootsupd.exe
File size does NOT match. Expecting 302168, but found 303232!!!
***Processing Cleanup Routines***"
Thanks
xp64 failed verification
Started by Guest_digger_*, Sep 23 2008 12:07 AM
1 reply to this topic
#1 Guest_digger_*
Posted 23 September 2008 - 12:07 AM
#2
Posted 23 September 2008 - 12:43 AM
wow. you found an new version for this one, pal
currently, we was expecting this one to be v=17,0,2195,0 and you have found v18,0,2195,0
don't worry, it's safe run this one anyway, but since the release wasn't still updated, you will see this version also "unofficial" for some time. currently, i don't have this release, so i can't sign it right now to fix this issue for you, but it will be done soon
thanks by your report
edit: this issue shall be fixed right now. but it will show also unofficial for some time
[]s
currently, we was expecting this one to be v=17,0,2195,0 and you have found v18,0,2195,0
don't worry, it's safe run this one anyway, but since the release wasn't still updated, you will see this version also "unofficial" for some time. currently, i don't have this release, so i can't sign it right now to fix this issue for you, but it will be done soon
thanks by your report
edit: this issue shall be fixed right now. but it will show also unofficial for some time
[]s
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












