Unofficial/Unsupported Release (Win XP SP3...
dreamerman
22 Jun 2010
Hi all. I am new to autopatcher & hope for your patience. After downloading 1.3GB worth (had to leave my laptop overnight at work!), I got the Unofficial/Unsupported Release on autopatcher.exe. I ran hit_this_to_generate_a_log_file_for_apup.cmd several times to try to flush out any broken files but no joy. I looked at the log file but can't seems to detect anything wrong. Can anyone please help me out? Sorry to sound like an idiot, I am an accountant & have very limited knowledge on this type of subject matter. Thanks.
Edited by dreamerman, 22 June 2010 - 02:10 AM.
Spoiler
Attached Files
-
Unsupported.jpg (72.63K)
downloads: 11 -
autopatcher.jpg (63.96K)
downloads: 8
Edited by dreamerman, 22 June 2010 - 02:10 AM.
_def_x_
22 Jun 2010
No problem dreamerman, let's see what we have here...
According to your screenshot the issue is with XP SP3, this is the release that is causing the Unofficial status. When the Release Info window shows True under Official that means that these releases are good to go. When you see False under Official that means there are file(s) missing, it is strange that your log shows 0 (zero) files to download. If by chance you see True for all the releases but the release as a whole is Unofficial - this means a stray file is lurking somewhere. Again, your issue is that XP SP3 is missing something.
What you want to do is run the xp_sp3_...md5 file in your APUP / AutoPatcher directory and see if it detects anything missing, you will need an .md5 verification tool, there are many but here are a few - ExactFile or ilSFV. Please report the verification tool's findings.
After you run the verification tool, run APUP again and select only XP SP3 (you can keep the first 2 selections 'Updater' and 'Engine') but none of the other releases - lets see what this does. Again please report your findings from your log.
The hit_this...cmd file only runs APUP with logging, it wont clean anything up, the script (the selection you make in the APUP selections window) is supposed to do this but for some reason we are not getting all the files it looks like but let's try again and only with one script (XP SP3) this time.
So, test the supplied .md5 file on the XP SP3 release, also re run APUP only selecting the failing script, see what this does, and post your findings.
BTW, when you are having issues, it is a good idea to check the window like you did in AutoPatcher, run APUP again, and when you post a log file, have only the problem release listed in the log, it is much easier to read. Also, don't bother this time but next time, determine the problem release (the red title for XP and False statement = PROBLEMS), post the question and relevant log in the given forum ie XP issues in the XP forums etc. Again, for next time.
According to your screenshot the issue is with XP SP3, this is the release that is causing the Unofficial status. When the Release Info window shows True under Official that means that these releases are good to go. When you see False under Official that means there are file(s) missing, it is strange that your log shows 0 (zero) files to download. If by chance you see True for all the releases but the release as a whole is Unofficial - this means a stray file is lurking somewhere. Again, your issue is that XP SP3 is missing something.
What you want to do is run the xp_sp3_...md5 file in your APUP / AutoPatcher directory and see if it detects anything missing, you will need an .md5 verification tool, there are many but here are a few - ExactFile or ilSFV. Please report the verification tool's findings.
After you run the verification tool, run APUP again and select only XP SP3 (you can keep the first 2 selections 'Updater' and 'Engine') but none of the other releases - lets see what this does. Again please report your findings from your log.
The hit_this...cmd file only runs APUP with logging, it wont clean anything up, the script (the selection you make in the APUP selections window) is supposed to do this but for some reason we are not getting all the files it looks like but let's try again and only with one script (XP SP3) this time.
So, test the supplied .md5 file on the XP SP3 release, also re run APUP only selecting the failing script, see what this does, and post your findings.
BTW, when you are having issues, it is a good idea to check the window like you did in AutoPatcher, run APUP again, and when you post a log file, have only the problem release listed in the log, it is much easier to read. Also, don't bother this time but next time, determine the problem release (the red title for XP and False statement = PROBLEMS), post the question and relevant log in the given forum ie XP issues in the XP forums etc. Again, for next time.
dreamerman
22 Jun 2010
Mike, thanks for your speedy reply. Under apup folder, I only have the following md5 files. I don't have the xp_sp3_...md5 you mentioned. Can this be the issue? Many thanks.
md5_checksum_for_AutoPatcher_XP_ENU.md5
md5_checksum_for_DirectX_Addon_Pack.md5
md5_checksum_for_DotNet_Addon_Pack.md5
md5_checksum_for_Extras_Addon_Pack.md5
md5_checksum_for_office2003_ENU.md5
md5_checksum_for_Office_Addon_Pack.md5
md5_checksum_for_AutoPatcher_XP_ENU.md5
md5_checksum_for_DirectX_Addon_Pack.md5
md5_checksum_for_DotNet_Addon_Pack.md5
md5_checksum_for_Extras_Addon_Pack.md5
md5_checksum_for_office2003_ENU.md5
md5_checksum_for_Office_Addon_Pack.md5
_def_x_
22 Jun 2010
Well now, my bad, the .md5 you want to run against the XP release is well -> md5_checksum_for_AutoPatcher_XP_ENU.md5 
dreamerman
22 Jun 2010
gUiTaR_mIkE, on 22 June 2010 - 02:52 AM, said:
Well now, my bad, the .md5 you want to run against the XP release is well -> md5_checksum_for_AutoPatcher_XP_ENU.md5
Edited by dreamerman, 22 June 2010 - 04:03 AM.
dreamerman
22 Jun 2010
OK, these 2 files are missing per ilSFV. Will do this now - "After you run the verification tool, run APUP again and select only XP SP3 (you can keep the first 2 selections 'Updater' and 'Engine') but none of the other releases - lets see what this does. Again please report your findings from your log".
IE8-WindowsXP-KB980302-x86-ENU.exe
IE8-WindowsXP-KB976662-x86-ENU.exe
IE8-WindowsXP-KB980302-x86-ENU.exe
IE8-WindowsXP-KB976662-x86-ENU.exe
dreamerman
22 Jun 2010
Mike, I ran hit_this_to_generate_a_log_file_for_apup.cmd twice & selected Updater, Engine & Win Xp SP3. Results shown below. Log still shows zero file downloaded. Maybe I can manually download it from MS website?
Spoiler
dreamerman
22 Jun 2010
YEAH, I SOLVED IT THANKS TO YOUR HELP MIKE!!
OK, this is what I did.
1. Ran ilSFV against md5_checksum_for_AutoPatcher_XP_ENU.md5 & discovered I am missing 2 files - IE8-WindowsXP-KB980302-x86-ENU.exe & IE8-WindowsXP-KB976662-x86-ENU.exe
2. Re-run apup.exe & only selected XP SP3, Updater & Engine
3. Log file says zero files downloaded so it is not picking up both missing files.
4. I went to http://www.vorck.com...otfixes_xp.html & downloaded both missing files from MS via links provided by the said website.
5. I moved both downloaded files into where it should be per ilSFV
6. Re-run again apup.exe & only selected XP SP3, Updater & Engine. Log still shows zero files downloaded.
7. Re-run again ilSFV against md5_checksum_for_AutoPatcher_XP_ENU.md5 & result show all ok
8. Run autopatcher.exe & confirm all OFFICIAL & all TRUE.
Happy :-) Many thanks Mike.
OK, this is what I did.
1. Ran ilSFV against md5_checksum_for_AutoPatcher_XP_ENU.md5 & discovered I am missing 2 files - IE8-WindowsXP-KB980302-x86-ENU.exe & IE8-WindowsXP-KB976662-x86-ENU.exe
2. Re-run apup.exe & only selected XP SP3, Updater & Engine
3. Log file says zero files downloaded so it is not picking up both missing files.
4. I went to http://www.vorck.com...otfixes_xp.html & downloaded both missing files from MS via links provided by the said website.
5. I moved both downloaded files into where it should be per ilSFV
6. Re-run again apup.exe & only selected XP SP3, Updater & Engine. Log still shows zero files downloaded.
7. Re-run again ilSFV against md5_checksum_for_AutoPatcher_XP_ENU.md5 & result show all ok
8. Run autopatcher.exe & confirm all OFFICIAL & all TRUE.
Happy :-) Many thanks Mike.
_def_x_
22 Jun 2010
Excellent news - this is how it gets done sometimes - down and dirty. I'm impressed, nice job!
The bad news is the script has issues - thanks to you the issue was discovered. Let me explain one file at a time.
Looking at the script with reference to file IE8-WindowsXP-KB976662-x86-ENU.exe. For some unknown reason the download link for the executable was removed from the script starting with the XP script dated 20100526 and including the latest 20100616. The last script to have the download link was 20100512 - as far as I can tell. The .apm was left in place and there was no 'delete' command for the file or folder. I'm gonna guess if you for the first time ran APUP and using the latest script, you should have been minus the folder -> \modules\NonCritical\KB976662_ie8_xp_x86_enu.apm_files\ which you needed to create?
So, if the file is supposed to be there (I say this because the link for the executable was removed for some reason) the link for the executable needs to be added once again...These are the details...
OK, one down, and one to go. I'll be back.
The bad news is the script has issues - thanks to you the issue was discovered. Let me explain one file at a time.
Looking at the script with reference to file IE8-WindowsXP-KB976662-x86-ENU.exe. For some unknown reason the download link for the executable was removed from the script starting with the XP script dated 20100526 and including the latest 20100616. The last script to have the download link was 20100512 - as far as I can tell. The .apm was left in place and there was no 'delete' command for the file or folder. I'm gonna guess if you for the first time ran APUP and using the latest script, you should have been minus the folder -> \modules\NonCritical\KB976662_ie8_xp_x86_enu.apm_files\ which you needed to create?
So, if the file is supposed to be there (I say this because the link for the executable was removed for some reason) the link for the executable needs to be added once again...These are the details...
Spoiler
...otherwise a 'delete' command for both the .apm file and the folder (and file) for the executable will need to be added to get rid of these files.OK, one down, and one to go. I'll be back.
dreamerman
22 Jun 2010
Mike, yes I needed to create both folders to contain both files. I found that out from ilSFV (which is a super tool). I am sold on autopatcher & million thanks for your help.
_def_x_
22 Jun 2010
dreamerman, I hope you read this post - Do Not Install These Updates just yet! There is contradictory information in the last 3 scripts and I can't tell if one, or both, or neither of these updates should be in this release. Cristiano will know, he looked at the MS bulletin and he does the script. I would hold off until this gets sorted out. Let me have one last look at the last 3 scripts regarding 980302, I'll post my findings, and then you can create a new post letting Cristiano know there may be an issue with these 2 updates.
Let me look again, and in the mean time make sure these 2 are not selected for installation.
Let me look again, and in the mean time make sure these 2 are not selected for installation.
dreamerman
22 Jun 2010
gUiTaR_mIkE, on 22 June 2010 - 05:26 AM, said:
dreamerman, I hope you read this post - Do Not Install These Updates just yet!
_def_x_
22 Jun 2010
The bottom line for these 2 files is - Cristiano needs to determine should they stay or should they go. The script is all over the place with the commands and it looks as if one of the 'delete' commands is not working on the executable for IE8-WindowsXP-KB980302-x86-ENU.exe. The 20100526 script even has a loop for this file that 'deletes' it then turns around and 'downloads' it again. For me, I have the folder with the executable but no .apm, and you were missing the executable (and the folder). If you look, I bet you are missing the .apm file that goes with KB980302 - look and see.
I have both the .apm file and executable for IE8-WindowsXP-KB976662-x86-ENU.exe even though the script has removed the download link, and the .apm is still in the .7z. I bet you have both as well - double check.
This is a simple fix but Cristiano will have to make the corrections including fixing the 'PreAction=rmdir' command that seems to not work all the time and maybe replace it with 'PreAction=del'. He will get it fixed, in the mean time hold off on KB976662, KB980302 wont install without an .apm file, if you do have one - don't install this one yet either.
I have both the .apm file and executable for IE8-WindowsXP-KB976662-x86-ENU.exe even though the script has removed the download link, and the .apm is still in the .7z. I bet you have both as well - double check.
This is a simple fix but Cristiano will have to make the corrections including fixing the 'PreAction=rmdir' command that seems to not work all the time and maybe replace it with 'PreAction=del'. He will get it fixed, in the mean time hold off on KB976662, KB980302 wont install without an .apm file, if you do have one - don't install this one yet either.
_def_x_
22 Jun 2010
If I was a gamblin' man I would say that IE8-WindowsXP-KB976662-x86-ENU.exe needs to stay, so all that needs to be done here is add the download link to the executable - see post #9 spoiler for the link info.
It does appear that IE8-WindowsXP-KB980302-x86-ENU.exe needs to go so a better 'delete' command may do the trick - I would use...
PreAction=del "autopatcher:\modules\NonCritical\IE8-WindowsXP-KB980302-x86-ENU.apm"
PreAction=del "autopatcher:\modules\NonCritical\IE8-WindowsXP-KB980302-x86-ENU.apm_files"
...but I don't gamble
It does appear that IE8-WindowsXP-KB980302-x86-ENU.exe needs to go so a better 'delete' command may do the trick - I would use...
PreAction=del "autopatcher:\modules\NonCritical\IE8-WindowsXP-KB980302-x86-ENU.apm"
PreAction=del "autopatcher:\modules\NonCritical\IE8-WindowsXP-KB980302-x86-ENU.apm_files"
...but I don't gamble
dreamerman
22 Jun 2010
Thanks Mike, perhaps I better wait for fix by Cristiano? Not really comfortable fiddling with inner workings. I have time so I better wait.
click-click
22 Jun 2010
KB982632 replaced KB980302 (Compat View). I mentioned it here, but it looks like Cristiano forgot to remove it.
_def_x_
22 Jun 2010
No, Cristiano didn't forget to remove KB980302, the command isn't working for some reason - the command appears twice, you can see it in the log and script.
Spoiler
Cristiano
23 Jun 2010
right now, i don't know why the download link for IE8-WindowsXP-KB976662-x86-ENU.exe has vanished from this script. it may be an overlap when pasting the new downloads, i don't know. but the removal for this one isn't listed in the log, so surely the removal of the download link was an mistake. i've re-added this and for one of the double removal for IE8-WindowsXP-KB980302-x86-ENU.apm_files, i've replaced the last command by PreAction.FolderDelete=autopatcher:\modules\NonCritical\IE8-WindowsXP-KB980302-x86-ENU.apm_files . it may do the job, i don't know for sure because i can't test it from this location
one issue: ms has updated wmp11. the download is about 24.5 MB and the script is waiting for the old md5. the new one shall be this one: 5A8299FEC0ED0F7B6F50E1DABD76FF93 but i have to confirm it downloading it from at least 1 another location and i will be able to do it only tonight
[]s
one issue: ms has updated wmp11. the download is about 24.5 MB and the script is waiting for the old md5. the new one shall be this one: 5A8299FEC0ED0F7B6F50E1DABD76FF93 but i have to confirm it downloading it from at least 1 another location and i will be able to do it only tonight
[]s
Cristiano
23 Jun 2010
done. KB980302 issue solved. in my local folder, this one was missing .apm. due that, in my local folder this one wasn't being removed. probably this issue happened when testing the script, i'm not sure. but it shall be fixed by now and also the issue with wmp11
[]s
[]s
