A thing with apup.exe
OmYcroN
21 Mar 2010
Why after i download XP sp3 list the Unofficial/Unsupported Release appears and after I re-download the list the unofficial/Unsupported Release dissappears ?!
_def_x_
21 Mar 2010
Hmm, assuming you are telling us everything we need to know, and that the second run was in the same folder...
During the first run, there was a hiccup during the download process and a file was incomplete or missing altogether. I
would expect APUP to give off a warning - "one or more files failed verification".
The second time the incomplete (or missing) file was downloaded properly, the release is now complete and Official.
If a second or third run of APUP does not fix the problem, it could be a script or server issue, maybe software (software
can produce errors), so a report of these conditions is the only way to get them fixed. The issue here is not related to
software - I'm simply mentioning it as a possibility for an error, or failed download.
...Just a bit of FYI
Links go bad, servers can be erratic or go offline for a moment, tired eyes update scripts and can make mistakes. Let's not
overlook it very well could be a glitch at the user's end also - were talking electricity, 1s and 0s here
the best remedy
is to try a second, maybe third time and if nothing changes report the problem to the appropriate forum - with details.
During the first run, there was a hiccup during the download process and a file was incomplete or missing altogether. I
would expect APUP to give off a warning - "one or more files failed verification".
The second time the incomplete (or missing) file was downloaded properly, the release is now complete and Official.
If a second or third run of APUP does not fix the problem, it could be a script or server issue, maybe software (software
can produce errors), so a report of these conditions is the only way to get them fixed. The issue here is not related to
software - I'm simply mentioning it as a possibility for an error, or failed download.
...Just a bit of FYI
Links go bad, servers can be erratic or go offline for a moment, tired eyes update scripts and can make mistakes. Let's not
overlook it very well could be a glitch at the user's end also - were talking electricity, 1s and 0s here
the best remedyis to try a second, maybe third time and if nothing changes report the problem to the appropriate forum - with details.
OmYcroN
21 Mar 2010
No download errors because the second time I run apup.exe, it did the download part almost instantly (so everything it's OK no?). Just wondering about the thing, because every single time I have to do this (start a second time apup.exe) and I'm not sure it's a sever problem.
_def_x_
21 Mar 2010
OmYcroN said:
No download errors because the second time I run apup.exe
-> "one or more files failed verification" - but you're saying no error message appears, I don't know why not.
OmYcroN said:
it did the download part almost instantly (so everything it's OK no?)
OmYcroN said:
Just wondering about the thing, because every single time I have to do this (start a second time apup.exe)
that would allow for a positive answer. If by chance you're downloading more scripts and the download size is getting close to the 4GB range,
you may want to download fewer scripts at one time. Again, I'm only supposing what is going on at your end. The important part is the release
is Official, this is what you want to see.
Ignotus
08 May 2010
I just ran apup.exe for the first time tonight. I too was downloading the XP SP3 files. I did not receive any error messages during or after the download, but it said that it was an unofficial or unsupported version in red letters. I then ran apup.exe again from the same directory. It didn't appear to download anything additional and it completed almost instantly. It now says Official Release in the AutoPatcher window. It seems odd that this happened to me too and there was no indication of there being any problems with the download the first time I did it. I'm busy working on my system at the moment, but I may try it again from a different directory and see if it says "unofficial" the first time. I'll see if I can get a log if it does. Then I'll run it again and get another log for comparison. If anyone has any tips regarding the information I can supply to troubleshoot the issue, just reply and I'll check back here.
The RTI files are: apengine.rti and xp_sp3_enu.rti.
I tried loading md5_checksum_for_AutoPatcher_XP_ENU.md5 into HkSFV but HkSFV crashes every time while it's loading.
EDIT: I have rerun apup.exe from a different directory. I'm not exactly sure how HkSFV works as I just installed it today, but I finally got it to run to completion after trying to load md5_checksum_for_AutoPatcher_XP_ENU.md5 several times. It reports everything with a green check mark except for modules\Components\WindowsUpdateAgent_x86.apm, which is reported as FILE NOT FOUND. AutoPatcher is again saying Unofficial/Unsupported Release. I ran apup.exe a 2nd time and it says "Fetched 1.2 KiB". However, I forgot to capture a log the 2nd time I ran it. Perhaps it should create a log by default? Anyway, after several attempts, I was finally able to load the MD5 file into HkSFV and it now reports a check mark for everything, including WindowsUpdateAgent_x86.apm. That file is being reported as 2,134 bytes. It appears to me that WindowsUpdateAgent_x86.apm is not being retrieved the first time that I run apup.exe, which is causing it to be marked as unofficial/unsupported. Running apup.exe a 2nd time retrieves the missing file and then marks it as "official". I saw a different thread that discusses an issue with the checksum of WindowsUpdateAgent_x86.apm. Perhaps it is related.
EDIT2: I do see the following in the log file that was created the first time that I ran apup.exe.
EDIT3: I decided to delete WindowsUpdateAgent_x86.apm to see what would happen. After I deleted the file, I opened AutoPatcher and it again said unofficial/unsupported. I then ran apup WITH logging and it said that it downloaded 1.2 KiB again, just like before. I then checked the log and it says:
Edited by Ignotus, 08 May 2010 - 08:16 AM.
The RTI files are: apengine.rti and xp_sp3_enu.rti.
I tried loading md5_checksum_for_AutoPatcher_XP_ENU.md5 into HkSFV but HkSFV crashes every time while it's loading.
EDIT: I have rerun apup.exe from a different directory. I'm not exactly sure how HkSFV works as I just installed it today, but I finally got it to run to completion after trying to load md5_checksum_for_AutoPatcher_XP_ENU.md5 several times. It reports everything with a green check mark except for modules\Components\WindowsUpdateAgent_x86.apm, which is reported as FILE NOT FOUND. AutoPatcher is again saying Unofficial/Unsupported Release. I ran apup.exe a 2nd time and it says "Fetched 1.2 KiB". However, I forgot to capture a log the 2nd time I ran it.
Perhaps it should create a log by default? Anyway, after several attempts, I was finally able to load the MD5 file into HkSFV and it now reports a check mark for everything, including WindowsUpdateAgent_x86.apm. That file is being reported as 2,134 bytes. It appears to me that WindowsUpdateAgent_x86.apm is not being retrieved the first time that I run apup.exe, which is causing it to be marked as unofficial/unsupported. Running apup.exe a 2nd time retrieves the missing file and then marks it as "official". I saw a different thread that discusses an issue with the checksum of WindowsUpdateAgent_x86.apm. Perhaps it is related.EDIT2: I do see the following in the log file that was created the first time that I ran apup.exe.
Missing file C:\Documents and Settings\crib\Desktop\apup2\modules\Components\WindowsUpdateAgent_x86.apm Item AutoPatcher WUAgent module is missing or its parts are not completely downloaded. Adding whole download for this item to the queue. --Adding http://www.autopatcher.com/releases/common/WindowsUpdateAgent_x86.7.4.7600.226_new.7z--
EDIT3: I decided to delete WindowsUpdateAgent_x86.apm to see what would happen. After I deleted the file, I opened AutoPatcher and it again said unofficial/unsupported. I then ran apup WITH logging and it said that it downloaded 1.2 KiB again, just like before. I then checked the log and it says:
***Starting Detection Routine Phase*** Missing file C:\Documents and Settings\crib\Desktop\apup2\modules\Components\WindowsUpdateAgent_x86.apm Item AutoPatcher WUAgent module is missing or its parts are not completely downloaded. Adding whole download for this item to the queue. --Adding http://www.autopatcher.com/releases/common/WindowsUpdateAgent_x86.7.4.7600.226_new.7z-- ***Downloading Releases*** Files to be Downloaded: 1 Download queue processed. Proceeding to next phase. ***Processing Cleanup Routines*** Extracting C:\Documents and Settings\crib\Desktop\apup2\temp_bin\WindowsUpdateAgent_x86.7z into C:\Documents and Settings\crib\Desktop\apup2\modules\ComponentsI don't know why, but it appears to me that WindowsUpdateAgent_x86.apm isn't being downloaded the first time you run apup, or something is happening to the file that causes it to show unofficial/unsupported in AutoPatcher. Running apup a 2nd time appears to download the missing file and resolves the issue. I just now saw another thread titled Download Error causes Unofficial/Unsupported status. I apologize if this was addressed in that thread. The last post in that thread is dated March 20 and this thread here was started March 21, so not sure that it was addressed in the other thread.
Edited by Ignotus, 08 May 2010 - 08:16 AM.
Cristiano
08 May 2010
you are the 2nd one to report this issue. i did an partial download test another day and i didn't found any problem in the download process, but surely i'm missing something. i will look for it again
edit: i've forgot: at my girlfriend pc, the same issue with hksfv happens. i didn't found an solution for it, except change the software. this one shall work too
edit2: partial download test done again. no issues found. i will do an full download test, but due my download speed, this will take time. in meantime, can you please try one thing? you are running apup from a folder that contain spaces in the name and is an long patch. can you please move apup2 to c:\ just to check if the long patch is the cause of the issue? there's one know issue with long patch, but i'm unsure if this affects even those that have an patch with only english letters, but...
thanks
[]s
Edited by Cristiano, 08 May 2010 - 10:00 PM.
edit: i've forgot: at my girlfriend pc, the same issue with hksfv happens. i didn't found an solution for it, except change the software. this one shall work too
edit2: partial download test done again. no issues found. i will do an full download test, but due my download speed, this will take time. in meantime, can you please try one thing? you are running apup from a folder that contain spaces in the name and is an long patch. can you please move apup2 to c:\ just to check if the long patch is the cause of the issue? there's one know issue with long patch, but i'm unsure if this affects even those that have an patch with only english letters, but...
thanks
[]s
Edited by Cristiano, 08 May 2010 - 10:00 PM.
Ignotus
09 May 2010
I reinstalled XP SP3 today. I have not applied any updates or fixes yet. I ran apup from the root of the drive and received the same error. It's marked as unofficial and the file is missing.
modules\Components\WindowsUpdateAgent_x86.apm does not exist
I ran it again and it fetched 1.2 KiB. The MD5 checks OK, however, it still says that it's unofficial for some reason.
Here's the output of the 2nd run where it fetched the missing file:
I just ran it a 3rd time and it said it downloaded 0 files and it's still showing unofficial in red letters, but going ABOUT>RELEASE INFO shows OFFICIAL TRUE TRUE. As I said, this is a new install without any patches applied. I don't know if that's related or not. Here's a pic of the ABOUT>RELEASE INFO:
This one really has me stumped as to why it won't say OFFICIAL RELEASE.
Edited by Ignotus, 09 May 2010 - 02:43 AM.
modules\Components\WindowsUpdateAgent_x86.apm does not exist
I ran it again and it fetched 1.2 KiB. The MD5 checks OK, however, it still says that it's unofficial for some reason.
Here's the output of the 2nd run where it fetched the missing file:
Spoiler
I just ran it a 3rd time and it said it downloaded 0 files and it's still showing unofficial in red letters, but going ABOUT>RELEASE INFO shows OFFICIAL TRUE TRUE. As I said, this is a new install without any patches applied. I don't know if that's related or not. Here's a pic of the ABOUT>RELEASE INFO:
This one really has me stumped as to why it won't say OFFICIAL RELEASE.
Edited by Ignotus, 09 May 2010 - 02:43 AM.
Cristiano
10 May 2010
well, one issue i've found: an rogue version WindowsUpdateAgent_x86.apm was forgot inside components.7z. due this issue, then in a first run the old version was making the release unofficial. in a 2nd run, then apup was downloading the right version and fixing the issue. the script is now fixed to this issue
as for the releases showing as official and yet autopatcher saying that is unofficial, this us to happen when there's an extra file present. hksfv has an issue: when an file doesn't match, then an .bad file is created and this extra file makes the release unofficial. so please, check the entire modules folder for .bad files and remove all. if this doesn't fix the issue, please take an recursive md5 from the modules folder and attach it into an post or upload it so some place, that i can check for rogue files
thanks
[]s
as for the releases showing as official and yet autopatcher saying that is unofficial, this us to happen when there's an extra file present. hksfv has an issue: when an file doesn't match, then an .bad file is created and this extra file makes the release unofficial. so please, check the entire modules folder for .bad files and remove all. if this doesn't fix the issue, please take an recursive md5 from the modules folder and attach it into an post or upload it so some place, that i can check for rogue files
thanks
[]s
