3 replies to this topic

[NewmansKnight]

OK, Here's my problem:

When I install XPSP3, I use Autopatcher to install all the fixes and updates. BUT the Windows Automatic Update program will not recognize that the updates have been installed - It still wants to (re)download and (re)install the updates I just used Autopatcher to install! (If I have to do THAT, why use Autopatcher?)

How do I get Windows Automatic Update to recognize the presence of the fixes and updates (hotfixes, dot-net frameworks, etc.) that Autopatcher has installed and simply proceed from that point? It would be a HUGE, and really APPRECIATED, timesaver.

The reason I need to know is this: I do volunteer work fixing computers from time to time for a local thrift store. I know how to use Autopatcher, but most of the customers do not. (Duh!)

So I need to be able to: 1. Repair/ Restore XP on donated computers, 2. rapidly update everything (using Autopatcher), and then 3. restart/ set Automatic Updates to run as normal, from that point on, for when the customer gets it home. WithOUT it trying to reinstall everything I just installed. Annoying! For me AND the customer!

Now I will state that so far, I have been turning OFF Automatic Updates while using Autopatcher. (Actually, I have usually been setting it to "Notify me but not to download or install them unless I say so".) Does that have a bearing on it?

I hope this has not already been answered before. (If it has, please tell me where to look!) I looked through several pages of posts and read the faq to be sure I wasn't "beating a dead horse" but saw no related topics. I will also mention that I have had this problem on every computer I have redone - It seems to have no bearing on make or model or XP version.

Please help, guys, I would REALLY be grateful for a solution. Thanks.

Edited by NewmansKnight, 09 April 2010 - 09:49 AM.

[Cristiano]

> Windows Automatic Update program will not recognize that the updates have been installed
yes, it does. i work fixing computers as well and i do the updates all the times, without any issue like this one. but one thing is possible to happen: sometimes, the language from the windows interface isn't the same than the one that is installed. when this happen, then the updates that will apply will be the ones from the original windows version.

in order to have more details about your issue, we need to know the releases that you have (specific, please. the names of the rti files into your apup folder will be good enough) and also if your version shows also official or not. also, can you please run autopatcher once in any of those machines that are having this issue and then look into windows folder by an file named autopatcher.log (you can open this file with notepad or any other text editor) and then paste the entire content of that file in here?

thanks

[]s

[NewmansKnight]

Hi back,

Thanks for the diagnostic help; I guess it's obvious I'm a complete noob to Autopatcher - :-P

Here's the Log file from my home machine - don't remember when I last patched my machine, but it was in the last few weeks.

FWIW, The blurb in the upper right-hand corner reads, and has always read "Unofficial/Unsupported release" even though I download it right from the website. I don't recall modding the program.

Start of log:

AutoPatcher 5.6 loaded the filesystem.

Detected
English (1033) Windows XP Professional Service Pack 3
System Components:
Internet Explorer: 8.0.6001.18904
Windows Media Player: 9.0.0.4507
.NET Framework: 1.1.4322|1.1SP1|2.0.50727.3053|2.0SP2|3.2.30729.01|3.2SP2|3.5|3.5SP1
Windows Installer: 4.5.6001.22159
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
Microsoft Word:
Microsoft Excel:
Microsoft PowerPoint:
Microsoft Outlook:
Microsoft Access:
Microsoft Project:
Microsoft Publisher:
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath:
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:

Module 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB958215_ie7_xp_x86_enu.apm' EXPLICITLY refers to its module folder as 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB958215_xp_x86_enu.apm_files'. However, such folder does not exist!
Module 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB958215_ie7_xp_x86_enu.apm' EXPLICITLY refers to its module folder as 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB958215_xp_x86_enu.apm_files'. However, such folder does not exist!
Module 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB958215_ie7_xp_x86_enu.apm' EXPLICITLY refers to its module folder as 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB958215_xp_x86_enu.apm_files'. However, such folder does not exist!
Module 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB960714_ie7_xp_x86_enu.apm' EXPLICITLY refers to its module folder as 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB960714_xp_x86_enu.apm_files'. However, such folder does not exist!
Module 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB960714_ie7_xp_x86_enu.apm' EXPLICITLY refers to its module folder as 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB960714_xp_x86_enu.apm_files'. However, such folder does not exist!
Module 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB960714_ie7_xp_x86_enu.apm' EXPLICITLY refers to its module folder as 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB960714_xp_x86_enu.apm_files'. However, such folder does not exist!
Module 'Update for Windows Media Player 9 or 10 (KB895181)' (unique id: 'KB895181_WMP10_X86_ENU') reports 'WMP10_NONCRITICAL_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Module 'Microsoft Windows Malicious Software Removal Tool v3.5 (KB890830)' (unique id: 'KB890830_X86_ALL') cannot be loaded because it's uniqueID is duplicate (the module named 'Microsoft Windows Malicious Software Removal Tool v2.6 (KB890830)' also uses it).


End of logfile


My version always reads "Unofficial/Unsupported release", even though I download it from the main site. What am I doing incorrecly there?

I'm in the USA, so English Standard release.

It's a slipstreamed copy of XPProSP3 using NLite.

Here are the names of the files in the apup folder:


apengine.rti
directx.rti
dotnet.rti
extras.rti
xp_sp3_enu.rti


Update:

Ok, I just downloaded a 100% fresh copy of Autopatcher v1.3.0.1 from the main download page onto another computer. Downloaded ONLY the updates for XP itself (no dotnet, or anything else - ONLY the Autopatcher and XP check boxes were ticked.) Then updated XP. While patching, Autopatcher still reads "unofficial/unsupported release". Should I UNselect the Autopatcher check boxes?

Next update:

OOPS. I just thought of something: Do I need specifically to download and/or run Autopatcher from a folder on the C: drive? I normally run it from my D: drive (either a second partition or a totally seperate drive (for speed and data integrity reasons), depending on the computer I'm patching.

Attached Files

•  rti names.jpg   50.99K   8 downloads

Edited by NewmansKnight, 09 April 2010 - 01:03 PM.

[Cristiano]

well, lets see:
- the unofficial issue is due this kind of thing: Module 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB960714_ie7_xp_x86_enu.apm' EXPLICITLY refers to its module folder as 'D:\My Documents\Computer Stuff\Programs\Windows Updates\XP\Autopatcher XP\apup\modules\Critical\KB960714_xp_x86_enu.apm_files'. However, such folder does not exist!

so, for sure you have several obsolete modules in your apup folder. sometimes, certain modules don't load due uniqueID is duplicate, like happens with KB890830. there's 2 possible solutions for that:
1 - forget that you have anything and start apup from scratch (that means re-download everything again and this will be an download of almost 800MB);

2 - we need that you take an recursive md5 from your modules folder, to allow track the missing and obsolete files/folders. this may take some time, but it can be done with tools like hksfv or any other recursive md5 tool that you like. after take that md5, you need upload it to some place or attach into an post. after that, we can check with ours and point the ones that doesn't match, allowing the removal and making autopatcher official again

this also may fix the first issue, due the duplicated unique id (the duplicated module doesn't load when this happen). but please note that this option takes several hours, due several personal reasons

edit: i've forgot:
> normally run it from my D: drive
that isn't an problem, except if the drive is an remote one

[]s

Edited by Cristiano, 09 April 2010 - 01:47 PM.