Files not marked as installed
Posted 05 September 2010 - 07:05 AM
Recently I have noticed that two updates are never marked as installed no matter how many times I install them. They are:
Cumulative Time Zone Update for Windows XP (KB955839)
Windows Update Agent v7.2.6001.788
I deleted the install files and redownloaded them using apup but nothing changed.
I should mention that even before this for some months Autopatcher for Windows XP SP3 (x86) has been listed as not official, but I don't know why. I have never edited the contents of the apup folder before today.
Any help is appreciated.
Posted 05 September 2010 - 08:46 AM
Just for kicks, fire up AutoPatcher first, click 'About' - click 'Release Info', what is the 'Date' of your AutoPatcher XP x86 release, the latest Official release is August 26, 2010? Btw, are there other releases in with the XP package? The release 'Title' in RED needs attention.
It sounds as if you haven't updated your XP x86 release in a while, it is a good idea to update at least twice a month, you run APUP to collect new files and get rid of old ones - it looks as if you have a couple.
Windows Update Agent is at 7.4.7600.226 (KB949104) /// (KB955839) looks to have been removed ages ago, I can't find KB955839 in any script, going as far back as May 2010.
What I would do:
...Windows Update Agent - delete the executable (WindowsUpdateAgent30-x86.exe) in the folder and delete the associated .apm file (WindowsUpdateAgent_x86.apm) from the '\Components' directory.
...Cumulative Time Zone Update (KB955839) - delete the folder and the associated .apm file for Time Zone Update KB955839.
...Run APUP, select the 'XP_SP3_x86' script to update your release. I would run APUP a few times, the second time to clean the log file. If you still have an Unofficial release, run the .md5 file and scan your folder - please report what the log file shows and any errors the .md5 discovers.
Also, what is the date of the script you are retrieving, the latest is autopatcher_xp_sp3_enu_20100826.script? I know you stated you have done the deleting and redownloading but you should be getting a newer version WUA???
Edited by gUiTaR_mIkE, 05 September 2010 - 08:52 AM.
Posted 05 September 2010 - 09:37 AM
I've run apup a few times and am still unofficial. I don't have that .script file you mentioned, although the log file shows "english/win_xp/autopatcher_xp_sp3_enu_20100826.script" as having been picked.
The closest thing I have is autopatcher_xp_x86_enu.script, created 2008/08/07 and modified 2008/09/03. The Release Info tab in autopatcher gives September 10, 2008 as the date for Autopatcher for Windows XP.
Posted 05 September 2010 - 10:22 AM
About the script, I didn't mean you had it locally on your computer, rather, what was APUP retrieving when getting the 'releases.list' file - it looks like you are getting the latest script -> August 26, 2010. What exaclty do you mean by - The closest thing I have is autopatcher_xp_x86_enu.script, created 2008/08/07 and modified 2008/09/03 - and what exactly are you doing with these scripts, they are extremely old, why are you saving them? You can save them (no big deal) just wondering what you're plans are for them?
You failed to answer a few important questions...
...Are there other releases in with the XP package?
...What is the 'Date' of your AutoPatcher XP x86 release - not AutoPatcher Engine?
...Please report what the log file shows and any errors the .md5 discovers.
See the attached image for an example of what I'm looking for in questions 1 and 2 - the 'Release Info' screen. Also, what is the version of AutoPatcher you are using, it can be seen from the same window listed as 'Program version:'?
Also, did you run the .md5 file located in the root folder (with apup.exe), what did the md5sum file report, if nothing (no errors), your Unofficial status is likely due to more stray files in your release.
Posted 05 September 2010 - 11:44 AM
I've never manually downloaded any script files, they have just been in the folder. I've also attached a screenshot of the release info window.
I used a program called md5summer on the file md5_checksum_for_AutoPatcher_XP_ENU.md5 and it had no errors. The apup log also had no errors.
Edited by drspangle, 05 September 2010 - 11:49 AM.
Posted 05 September 2010 - 12:11 PM
If you look closely at your screenshot you will see 2 instances of XP SP3 x86, including Erik Ramey's, I think you may simply have to remove the .rti file from the root folder (the folder where apup.exe is). Everything else seems OK.
So, you need to find the .rti file that Erik Ramey used to make his release (XP from 2008) Official and remove it. You don't need to remove any of the other .rti files only the one that has xp_sp3_x86 (or some derivation of) in the name. Cristiano's .rti file is named like this -> xp_sp3_enu.rti. Don't worry if you remove Cristiano's file as well, when you delete the offender rerun APUP and select the XP SP3 x86 script to clean up the release. Then check to see if things are Official.
There is the distinct possibility you will still be Unofficial because there may be other files left behind from this old release.
Btw, you have many releases in one folder so keep them updated and always check the 'Release Info' window if you aren't sure what release is making the whole package Unofficial.
OK, find and delete that .rti file and report back, I'll be waiting
Posted 05 September 2010 - 01:12 PM
If you continue to have problems, you will need to create a .md5sum of your whole AutoPatcher release, we will then run it against a release with the same packages. What this will do is flag files missing at our end which will be the extras at your end - these will be the files causing the release to become Unofficial.
If you do create the .md5, put it in a .zip archive and attach it to your post.
Posted 05 September 2010 - 01:17 PM
How do you suggest I go about finding them? How does the program determine which files are supposed to be there? I tried removing and redownloading (using apup) all .apm files, but this didn't help.
Edit: oops, started my reply before your last post. wait just a minute
Edited by drspangle, 05 September 2010 - 01:20 PM.
Posted 05 September 2010 - 01:39 PM
Posted 05 September 2010 - 01:39 PM
If the above isn't practical, create the .md5 like I mentioned above, scanning all of the '\modules' folder, zip it up, we will try to create the exact package and then run your .md5 file. The files should be flagged as missing at our end - these are your extras (strays) - they need to be removed. It is tedious but works.
The .rti file is a md5sum if you will, it expects to find only the files present when the file was created for that particular release. If the 'Title' is True but AutoPatcher displays Unofficial, you have extras somewhere. If the 'Title' is RED, you are missing files in that particular release, in this case usually running APUP and updating the problem release works.
Posted 05 September 2010 - 01:42 PM
Posted 05 September 2010 - 02:57 PM
from those, this ones must be removed:
after that, this issue shall be solved, but this must be checked
Posted 05 September 2010 - 03:45 PM
It's sort of funny, for a long time I thought there was no official release yet and that everyone's was "unofficial/unsupported".
Posted 05 September 2010 - 03:48 PM
Edited by gUiTaR_mIkE, 05 September 2010 - 03:50 PM.
Posted 05 September 2010 - 07:08 PM
Posted 06 September 2010 - 04:42 AM
Also, if it was me I would get rid of - \APUP_BIN_old - not exactly sure what renamed this folder either There's more crap in the \root folder but if the OP don't mind, who am I to say differently
Posted 06 September 2010 - 01:30 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users