Error downloading updates
Started by Sa7elli7e, Mar 07 2011 10:29 PM
6 replies to this topic
#1
Posted 07 March 2011 - 10:29 PM
I'm running apup for the first time, get to the end of a long download session, and it doesn't like the last four little files it has to download. Attached is my log. Thanks in advance for any tips or help!
#2
Posted 08 March 2011 - 03:02 AM
Welcome Sa7elli7e
We're trying to get away from accepting log files as an attachment, just not safe anymore - I hope you understand. If you could put the log file (unedited) and only the release you're having trouble with in Spoiler it would be much easier (and safer) to read.
If you're unsure how to do this read Log File Reference & Log File How-To.
We're trying to get away from accepting log files as an attachment, just not safe anymore - I hope you understand. If you could put the log file (unedited) and only the release you're having trouble with in Spoiler it would be much easier (and safer) to read.
If you're unsure how to do this read Log File Reference & Log File How-To.
#3
Posted 08 March 2011 - 05:31 PM
My apologies. I'd considered pastebin; is that also an acceptable way to post logs?
Spoiler
#4
Posted 08 March 2011 - 06:54 PM
>>> I'd considered pastebin; is that also an acceptable way to post logs?
It's better than trusting a zip file but Spoiler is the easiest - no links to follow, click Show and walla
OK, I downloaded from all 3 links and they work, the files checked. I'm guessing you have an issue at your end. You can try manually downloading the files and drop them in the appropriate folders. There's a caveat though, you'll need to rename 2 of the files. Btw, always run APUP again when done to confirm your work.
Let's start with the easiest. rootsupd.exe
... If you can download manually, delete the partial file if one exists and drop the complete file in \modules\Critical\RootCert_files
-> http://download.wind...en/rootsupd.exe
These 2 are really easy, just get the names correct and drop them in the appropriate folders - look at your log file
Like I said, the names are kinda long, your log has the correct names - copy and paste - use the kbxxxxxx and rename the correct files.
... windowsxp-kb892130-enu-x86_72e487d115be77f49f64053893a23ecb58bc59cb.exe - rename to WindowsXP-KB892130-ENU-x86.exe, drop in \modules\wga\wga_files
-> http://www.download....ecb58bc59cb.exe
... windowsxp-kb898461-x86-enu_e8e139341e1a6c535ddf2db57052c71d19fc7249.exe - rename to WindowsXP-KB898461-x86-ENU.exe, drop in \modules\NonCritical\KB898461_xp_x86_enu.apm_files
-> http://www.download....71d19fc7249.exe
Use your log file for exact names, locations, and md5sums, don't forget to run APUP again, you want the files to pass. Post back if you get stuck.
It's better than trusting a zip file but Spoiler is the easiest - no links to follow, click Show and walla
OK, I downloaded from all 3 links and they work, the files checked. I'm guessing you have an issue at your end. You can try manually downloading the files and drop them in the appropriate folders. There's a caveat though, you'll need to rename 2 of the files. Btw, always run APUP again when done to confirm your work.
Let's start with the easiest. rootsupd.exe
... If you can download manually, delete the partial file if one exists and drop the complete file in \modules\Critical\RootCert_files
-> http://download.wind...en/rootsupd.exe
These 2 are really easy, just get the names correct and drop them in the appropriate folders - look at your log file
... windowsxp-kb892130-enu-x86_72e487d115be77f49f64053893a23ecb58bc59cb.exe - rename to WindowsXP-KB892130-ENU-x86.exe, drop in \modules\wga\wga_files
-> http://www.download....ecb58bc59cb.exe
... windowsxp-kb898461-x86-enu_e8e139341e1a6c535ddf2db57052c71d19fc7249.exe - rename to WindowsXP-KB898461-x86-ENU.exe, drop in \modules\NonCritical\KB898461_xp_x86_enu.apm_files
-> http://www.download....71d19fc7249.exe
Use your log file for exact names, locations, and md5sums, don't forget to run APUP again, you want the files to pass. Post back if you get stuck.
#5
Posted 08 March 2011 - 10:02 PM
OK, I found the problem. My first clue was that when I looked at the three indicated files, they were all ~2KB, which is the size you get when a download is broken. When I attempted to download those files manually with the links you provided me, the corporate proxy blocked me. Apparently, even though the corporate proxy was just fine with almost 800MB of download.microsoft.com content, the last ~3MB worth of small files were unattainable. I used my cell phone tethered as a modem, and everything finished up brilliantly. Thank you for your suggestions and help, without which I may never have come across the real cause of the problem.
Cheers!
Cheers!
#6
Posted 08 March 2011 - 10:35 PM
>>>the corporate proxy blocked me.
Have mercy, it might have helped knowing this up front
Try using the proxy settings in APUP 'Options'. If it works please let us know.
If you try updating a system within a network using AutoPatcher (not APUP) - good luck, AutoPatcher hasn't been very cooperative. If you find a way please post the details.
Have mercy, it might have helped knowing this up front
If you try updating a system within a network using AutoPatcher (not APUP) - good luck, AutoPatcher hasn't been very cooperative. If you find a way please post the details.
#7
Posted 14 March 2011 - 02:16 PM
I had meant to post a response a while back but didn't have time.
In response to the corporate proxy not being mentioned, I hadn't assumed it was the problem simply because 99% of the downloads finished through that exact same proxy without a single problem. Only two individual files failed to download; I have no idea why. Such is life.
Also, I have had very good luck updating a few of our systems with the autopatcher system, including Windows and Office updates and Adobe Reader. I have enough privileges to install and remove most software while the PC is on the domain, though. If I encounter further problems (and overcome them), I'll come back to share my experiences.
In response to the corporate proxy not being mentioned, I hadn't assumed it was the problem simply because 99% of the downloads finished through that exact same proxy without a single problem. Only two individual files failed to download; I have no idea why. Such is life.
Also, I have had very good luck updating a few of our systems with the autopatcher system, including Windows and Office updates and Adobe Reader. I have enough privileges to install and remove most software while the PC is on the domain, though. If I encounter further problems (and overcome them), I'll come back to share my experiences.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












