17 replies to this topic

[WilliamAnthony]

Just downloaded autopatcher yesterday, and got verification failed error.

Here is the log:

***Starting Detection Routine Phase***

Detection error for file C:\Documents and Settings\user\Desktop\apup\modules\Components\UserProfileHiveCleanup_files\UPHClean.msi
    MD5 Hashes do NOT match. Expecting 4a451d2ad168e092874997dec6c5dd40, but found 4b18d1395599e85a1007aaf433c7e4c5!!!
  Item UPHClean.msi failed detection or its parts. Adding whole download for this item to the queue.
  --Adding http://download.microsoft.com/download/a/8/7/a87b3d05-cd04-4743-a23b-b16645e075ac/UPHClean-Setup.msi--

Edited by WilliamAnthony, 16 September 2010 - 02:01 AM.

[_def_x_]

@WilliamAnthony - please don't edit the log files - Log Files - More Info

This is from the XPSP3 English script right? Anyway, using the XPSP3 link it looks as if this file has been updated - this is what I'm getting.

Name: UPHClean-Setup.msi
Size: 430080
MD5: 4B18D1395599E85A1007AAF433C7E4C5

[Cristiano]

oh boy... true. the sad thing is that this kind of issue just shows when doing an full download test. this will be fixed in about 7h

thanks

[]s

[Cristiano]

done. issue fixed. but i've found one possible issue to those that deploy it manually: the old version isn't removed when installing the new one. the removal of the old version worked after the deployment of the new one, but to be on safe side, i've added the removal of the old version in the install command of the new version. so, if the module is selected, autopatcher will first remove the old one, then install the new one

[]s

Edited by Cristiano, 16 September 2010 - 05:32 PM.

[rigar]

I had a strange error with this file as well, but it happened after Cristiano's last post (about two hours ago). The file "UPHClean-Setup.msi" as downloaded by apup.exe failed verification. Looking at it, the downloaded file was also too small, and it had an MD5 that matched an old version of the file according to a web search.

I downloaded and looked directly at the script, and tried downloading the file directly from MS using that URL with a standalone downloader that doesn't rely on IE or anything else. It was identical to the file apup.exe had downloaded. But checking HTTP headers as I downloaded the file showed the last modified date of the file as 2006.

I tried again a few minutes ago and the correct file was downloaded both separately and by apup.exe (right size, matching MD5, HTTP last modified date of September 14).

Since as far as I know, there are no proxies between me and the ISP, I'm led to believe that Microsoft may have been serving the wrong file, at least for a while.

[_def_x_]

I'm sure the old way was technically just as functional but it seemed unnecessary to change the name. The download functions much cleaner the way you have it now - the script expects to find UPHClean-Setup.msi and downloads UPHClean-Setup.msi good job!

Spoiler

...Old

Item=UPHClean.msi

DetectFile=autopatcher:\modules\Components\UserProfileHiveCleanup_files\UPHClean.msi
DetectHash=4a451d2ad168e092874997dec6c5dd40
DownloadFrom=http://download.microsoft.com/download/a/8/7/a87b3d05-cd04-4743-a23b-b16645e075ac/UPHClean-Setup.msi
DownloadTo=autopatcher:\modules\Components\UserProfileHiveCleanup_files\UPHClean.msi
ExpectedSize=336896
ExpectedHash=4a451d2ad168e092874997dec6c5dd40

...New

Item=UPHClean-Setup.msi

DetectFile=autopatcher:\modules\Components\UserProfileHiveCleanup_files\UPHClean-Setup.msi
DetectHash=4B18D1395599E85A1007AAF433C7E4C5
DownloadFrom=http://download.microsoft.com/download/a/8/7/a87b3d05-cd04-4743-a23b-b16645e075ac/UPHClean-Setup.msi
DownloadTo=autopatcher:\modules\Components\UserProfileHiveCleanup_files\UPHClean-Setup.msi
ExpectedSize=430080
ExpectedHash=4B18D1395599E85A1007AAF433C7E4C5

[Cristiano]

> but it seemed unnecessary to change the name
true. long ago, someone had the idea about made short names, renaming files/folders/updates as kb123456 instead the real names that the kbs have. in fact, that way is more elegant, but it also creates an huge window to mistakes. just as a sample, take a look at this:
WindowsXP-KB952954-x86-ENU.exe

in the old fashion way of naming the updates and modules, it should be something like KB952954_sp3_x86_ENU.exe or something like that. just imagine if the release manager is with tired eyes and instead _ forgets an - in place. the module could not work, issues could be reported in the logs and also a lot of unneeded issues. so, instead create more job to me, i've just did the simplest thing that i know about it: leave the original name and name the modules with the same name than the update. that way is far more easy to do and generates 0 errors related to _ and -

> last modified date of September 14
the enu script was updated today, September 16, at 2:26pm (at my time zone, gmt -3). given that, the script was updated something like 6h ago. to reach the old version, it's possible that some cache between you and our server is in place (possibly an transparent one). but there's an easy way to clean the cache: reaching the releases.list file and the target script with an browser http://www.autopatch...m/releases.list

but still, ms has a lot of mirrors. some time ago, the rootcerts was updated. after several days, the new version was reached only by an alternate link (that currently is at the script), but the static one (that should be the first one to be updated) was updated just some days ago

[]s

[WilliamAnthony]

Hi, I got another ones this morning...

Thanks

APUP Has Started
Version: 1.3

Operating System: English (1033) Windows XP Professional Service Pack 3
Current Locale: English - United States / Non-Unicode Default: English - United States
Starting APUP From: Z:\apup
Date & Time: 17-Sep-2010 10:51 UTC Offset: 7

***Downloading/Processing Releases.list***

List file HTTP location: http://www.autopatcher.com/releases.list
Download queue processed. Proceeding to next phase.

***Releases.list Processed: Waiting for User Input***

The Following Releases have been Picked:
apup.script
apengine.script
english/win_xp/autopatcher_xp_sp3_enu_20100916.script
dotnet/autopatcher_dotnet_20100811.script
mssecurity_enu/autopatcher_ms_security_en_us.script

***Running Any Pre-Cleanup Routines***

Download queue processed. Proceeding to next phase.
Executing shell command: del "Z:\apup\apup_bin\uz.exe"
Executing shell command: rmdir /S /Q  "Z:\apup\win9xnt"
Executing shell command: del "Z:\apup\modules\Components\UserProfileHiveCleanup_files\UPHClean.msi"
Executing shell command: del "Z:\apup\modules\Critical\KB970238_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB970238_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB973039_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB973039_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.10.exe"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Components\WindowsDefender_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Components\WindowsDefender_x86_enu.apm"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\IE8-WindowsXP-KB981332-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\IE8-WindowsXP-KB981332-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\IE8-WindowsXP-KB982381-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\IE8-WindowsXP-KB982381-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\IE7-WindowsXP-KB982381-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\IE7-WindowsXP-KB982381-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\WindowsXP-KB982381-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\WindowsXP-KB982381-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB971468_xp_sp3_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB971468_xp_sp3_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\WindowsXP-KB979683-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\WindowsXP-KB979683-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\WindowsXP-KB979559-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\WindowsXP-KB979559-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB975561_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB975561_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\NonCritical\IE8-WindowsXP-KB982632-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\NonCritical\IE8-WindowsXP-KB982632-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.9.exe"
Executing shell command: del "Z:\apup\modules\NonCritical\__WMP_noncritical\__WMP11_noncritical.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\NonCritical\__WMP_noncritical\wmp11"
Executing shell command: del "Z:\apup\modules\Critical\__WMP_critical\KB941569_xp_wmp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__WMP_critical\KB941569_xp_wmp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.8.exe"
Executing shell command: del "Z:\apup\modules\NonCritical\KB925168_DN11SP1_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\NonCritical\KB925168_DN11SP1_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__WMP_critical\KB968816_xp_x86_enu.apm"
Executing shell command: del "Z:\apup\modules\Critical\KB969947_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB969947_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB978262_xp_sp3_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB978262_xp_sp3_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB978262_xp_sp3_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB978262_xp_sp3_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\IE8-WindowsXP-KB980182-x86-ENU.apm"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\IE7-WindowsXP-KB980182-x86-ENU.apm"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\WindowsXP-KB980182-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\WindowsXP-KB980182-x86-ENU.apm_files"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\IE7-WindowsXP-KB980182-x86-ENU.apm_files"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\IE8-WindowsXP-KB980182-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.7.exe"
Executing shell command: del "Z:\apup\modules\NonCritical\KB979306_xp_sp3_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\NonCritical\KB979306_xp_sp3_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\NonCritical\IE8-WindowsXP-KB980302-x86-ENU.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\NonCritical\IE8-WindowsXP-KB980302-x86-ENU.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.6.exe"
Executing shell command: del "Z:\apup\modules\Critical\KB951066_xp_x86_enu.apm"
Executing shell command: del "Z:\apup\modules\Critical\KB973354_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB951066_xp_x86_enu.apm_files"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB973354_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.5.exe"
Executing shell command: del "Z:\apup\modules\Critical\KB978251_xp_sp3_x86_enu.apm"
Executing shell command: del "Z:\apup\modules\Critical\KB977165_xp_sp3_x86_enu.apm"
Executing shell command: del "Z:\apup\modules\NonCritical\KB978506_ie8_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB978251_xp_sp3_x86_enu.apm_files"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB977165_xp_sp3_x86_enu.apm_files"
Executing shell command: rmdir /S /Q "Z:\apup\modules\NonCritical\KB978506_ie8_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\KB978207_IE7_xp_x86_enu.apm"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\KB978207_IE8_xp_x86_enu.apm"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\KB978207_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\KB978207_xp_x86_enu.apm_files"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\KB978207_IE7_xp_x86_enu.apm_files"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\KB978207_IE8_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\wga\KB905474_wga_xp_x86.apm"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.4.exe"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\KB971961_IE8_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\KB971961_IE8_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB976098_xp_sp3_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB976098_xp_sp3_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.3.exe"
Executing shell command: del "Z:\apup\modules\Critical\KB958687_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB958687_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB971633_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB971633_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB971486_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB971486_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB971557_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB971557_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB973525_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB973525_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\NonCritical\KB975364_ie8_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\NonCritical\KB975364_ie8_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\KB976325_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\KB976325_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\KB976325_IE7_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\KB976325_IE7_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\__MSIE_critical\KB976325_IE8_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\__MSIE_critical\KB976325_IE8_xp_x86_enu.apm_files"
Executing shell command: del "Z:\apup\modules\Critical\KB890830_files\windows-kb890830-v3.2.exe"
Executing shell command: del "Z:\apup\modules\Critical\KB961371_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "Z:\apup\modules\Critical\KB961371_xp_x86_enu.apm_files"
Executing shell command: ren "Z:\apup\modules\Components\__dotnet\NDP1.1sp1-KB953297_files" NDP1.1sp1-KB953297.apm_files
Executing shell command: del "Z:\apup\modules\Components\__dotnet\NDP35SP1-KB976126.apm_files\NDP35SP1-KB976126-x86.exe"

***Starting Detection Routine Phase***

Detection error for file Z:\apup\modules\NonCritical\__WMP_noncritical.apm
    MD5 Hashes do NOT match. Expecting 73B77A6DB3A4B83C8C878827BBC6B963, but found fc9925ec58b934ba0ef5a4263e168777!!!
  Item WMP NonCritical Parent Module failed detection or its parts. Adding whole download for this item to the queue.
  --Adding http://www.autopatcher.com/releases/modules/__WMP_noncritical.apm--

Detection error for file Z:\apup\modules\NonCritical\__WMP_noncritical\__WMP10_noncritical.apm
    MD5 Hashes do NOT match. Expecting 7758F547C3D1C334981C09F4E2388469, but found 3f9cca8672d21800c444fd7de6caaaed!!!
  Item WMP 10 NonCritical Parent Module failed detection or its parts. Adding whole download for this item to the queue.
  --Adding http://www.autopatcher.com/releases/modules/__WMP10_noncritical.apm--

Detection error for file Z:\apup\modules\Critical\__WMP_critical.apm
    MD5 Hashes do NOT match. Expecting C03317D76519E7AFF487DDCE520A857E, but found bd619293c3bad940c4ac82a74651b295!!!
  Item WMP Critical Parent Module failed detection or its parts. Adding whole download for this item to the queue.
  --Adding http://www.autopatcher.com/releases/modules/__WMP_critical.apm--

***Downloading Releases***

Files to be Downloaded: 3
Download queue processed. Proceeding to next phase.

Download Error: Z:\apup\modules\NonCritical\__WMP_noncritical.apm
    File size does NOT match. Expecting 1754, but found 1752!!!

Download Error: Z:\apup\modules\NonCritical\__WMP_noncritical\__WMP10_noncritical.apm
    File size does NOT match. Expecting 1791, but found 1858!!!

Download Error: Z:\apup\modules\Critical\__WMP_critical.apm
    File size does NOT match. Expecting 1816, but found 1885!!!

***Processing Cleanup Routines***

[_def_x_]

@WilliamAnthony

I tested the script and it seems OK, the files are downloading fine and the numbers square.

I copied the latest XP SP3 release (updated moments ago) to a test folder, removed the 3 .apm files you are having troubles with - __WMP_noncritical.apm, __WMP10_noncritical.apm, __WMP_critical.apm - the script redownloaded the 3 files, size and hash are a match, the release is again Official.

Maybe someone else can test and see what they get - at my end it all checks out.

If removing the files and attempting redownload them is producing the same thing - the wrong files - this is strange.

[Cristiano]

i've just did an full download test in here and an download test restricted to the .apm files. no issues at all. but one hint: at september 06:
Item=WMP NonCritical Parent Module

DetectFile=autopatcher:\modules\NonCritical\__WMP_noncritical.apm
DetectHash=FC9925EC58B934BA0EF5A4263E168777
DownloadFrom=http://www.autopatcher.com/releases/modules/__WMP_noncritical.apm
DownloadTo=autopatcher:\modules\NonCritical\__WMP_noncritical.apm
ExpectedSize=1752
ExpectedHash=FC9925EC58B934BA0EF5A4263E168777

Item=WMP 10 NonCritical Parent Module

DetectFile=autopatcher:\modules\NonCritical\__WMP_noncritical\__WMP10_noncritical.apm
DetectHash=3F9CCA8672D21800C444FD7DE6CAAAED
DownloadFrom=http://www.autopatcher.com/releases/modules/__WMP10_noncritical.apm
DownloadTo=autopatcher:\modules\NonCritical\__WMP_noncritical\__WMP10_noncritical.apm
ExpectedSize=1858
ExpectedHash=3F9CCA8672D21800C444FD7DE6CAAAED

Item=WMP Critical Parent Module

DetectFile=autopatcher:\modules\Critical\__WMP_critical.apm
DetectHash=BD619293C3BAD940C4AC82A74651B295
DownloadFrom=http://www.autopatcher.com/releases/modules/__WMP_critical.apm
DownloadTo=autopatcher:\modules\Critical\__WMP_critical.apm
ExpectedSize=1885
ExpectedHash=BD619293C3BAD940C4AC82A74651B295

given that, i'm sorry to say that, but WilliamAnthony is behind an webcache (hidden, perhaps?) that is reaching the old version of those files. the fix for it is easy, but requires an action from the user side. first, open your browser and reach those links:
http://www.autopatch...noncritical.apm
http://www.autopatch...noncritical.apm
http://www.autopatch...noncritical.apm

after do that, reload the page that you have reached. 1-2 times us to be enough. then, run apup again that the proper files shall be reached by now

[]s

[iknowledge]

I am getting the following error:

"One or more files has failed verification. Please re-run AutoPatcher Updater.
If this problem persists, please report to the forums at AutoPatcher.com."

The following is seen in the AutoPatcher Updater window when this error occurs:
"Fetching windows-kb890830-v3.10.exe from download.microsoft.com..."

Fetched 13.76 MiB / 13.76 MiB (100.0%)

I have been trying since the last 3 days and the download is failing... Please Help....

[Cristiano]

> kb890830
this one is v3.11 since a few days ago. can you state the script that you are downloading?

thanks

[]s

[iknowledge]

How do I state the script? I just downloaded the latest version of autopatcher from the download section and have selected Win Xp SP3, Win 7, Win2K3, Office XP, Office 2003, Office 2007, SP1 Addon, SP2 Addon, DirectX, .Net Package, Adobe Package.

I have attached a screenshot for your reference.

http://img413.images.../autoupdate.jpg

[Cristiano]

ouch. that image worked as an description of the scripts that you are downloading. basically, you are downloading almost all the scripts at once. that is in deed possible, but not advisable, because the scripts aren't updated at the same time. by instance, vista wasn't updated yet and it has the link for malicious software removal tool. every single time that a new version of this one arrives, the old one is removed from ms servers, breaking the scripts. but it may be something else as well. one idea: at apup main folder, there's an "hit this..." that file loads apup in logging mode and it helps a lot to track download issues. can you please try that and host the content of apup.log in some place? that log us to be too large to be CP in a post, but it may be attached in the board, compressed, in "use full editor"

thanks

[]s

[iknowledge]

Now I am getting a new error:

Verification Failed

"Fetching WindowsUpdateAgent_7.4.7600.229.7z from www.autopatcher.com"

[iknowledge]

Can i select each script one at a time and download all the scripts? Is there any special procedure to do so or should I launch apup.exe each time and select one script and download that script and then when the download is completed re-run apup.exe and unselect the previous script and select the other script for download?

[_def_x_]

@iknowledge

You will need to take extra precautions now that you have placed all the releases in one '\modules' folder. A few suggestions, these will make it easier to find problems.

...Always run apup.exe with logging - double-click 'hit_this...cmd' or create a shortcut to apup.exe adding /log - 'apup.exe /log'
...Don't select more than 2 or 3 main scripts at one time (not counting AutoPatcher Updater & AutoPatcher Engine)
...If you're having troubles with a script run apup and select only that script, post your issue in the correct forum and include the log - Log Files Help
...Get used to using AutoPatcher to determine what releases are failing - start AutoPatcher - click 'About' - click 'Release Info', the release 'Title' in RED is failing, this release needs fixing, usually just updating it will work but not always.
...There are a few 'common' updates - 890830 is one, as Cristiano has mentioned, if XP downloads file (v11) and Vista SP2 (v10), the scripts will cancel each other out - check the log file, the release that has the newer file use this release to update, or you could wait for the other script to catch up. It wouldn't hurt to mention - "Vista SP2 is downloading v10 of 890830 and XP SP3 is downloading v11" - the release maintainer will understand and probably already knows.

Bottom line here, you have many releases all piled into one folder, you will need to isolate your issues by running each script and posting with log files, simply stating you're having troubles with WindowsUpdateAgent doesn't help since you have so many releases together - the problematic script needs to be identified - not just the update

[_def_x_]

iknowledge said:

Can i select each script one at a time and download all the scripts?

I addressed this above but I will restate it this way - the issue seems to be a 4GB download limit before errors occur in APUP.

A good rule of thumb might be to select no more than 2 or 3 main scripts at a time, download, check for errors, if you get an error, run APUP again, select only the problem script, if you get an error again, post the issue along with the log in the proper forum.

You want to have APUP provide the 'Finish' tab, you may also get an 'Exit' tab, either way always check the log file, run the .md5 against the release (if it has one), and check the 'Release Info' in AutoPatcher. These 3 steps help keep your release Official.

Btw, I forgot to mention - the 'True' status is key here, you can have an Unofficial AutoPatcher but all the releases are 'True' as seen in 'Release Info' - this means you have a stray (extra) file somewhere, remove it - the Title in RED, well, this release is incomplete - update it.