AutoPatcher Forum

16 December XP SP3 English: Autopatcher now official, thanks.

But Windows Media Encoder 9 update 2447961 is still showing as not installed (black text, box has check in it).

Very odd, as both the registry key and the catfile that are referenced in WindowsMedia9-KB2447961-x86-ENU.apm under
[DetectionRegistry] and [DetectionFile] respectively, are present on my system.
Edited by JRosenfeld, 16 December 2010 - 01:41 PM.

can you please export the uninstall part of your registry, that is about KB2447961? that may help find the cause of the issue

thanks

[]s

Here it is (zipped as I don't know whether reg files are allowed)

now the issue looks more clear... due some reason, autopatcher isn't reaching the proper location for the .cat file. no problem, that can happen due several things, but the current registry detection doesn't look for anything that is included at that registry extract. to be more clear, it looks for:
RegistryPath=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\KB2447961_WM9L
KeyName=Type
KeyValue=Update

and this doesn't exist in that registry extract. so please, let's do an test: download the attached file and extract it under modules\Critical\__WMP_critical replacing the existent file and run autopatcher. it will state that isn't official, but don't worry about that and look for the detection only. if not works, please look for

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2447961_WM9L
KeyName=Type
KeyValue=Update

or something like that. that part of the registry can be read by the critical updates. if so, any other detection in there shall work as well

[]s

Yes that now shows it installed.

But in fact I do also have
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB2447961.cat

So why does

[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=KB2447961.CAT
FileVersion=ANY
FileMD5=ANY

not find it?

I also tried replacing windows: by the full path C:\windows\ but that did no work either.
Edited by JRosenfeld, 17 December 2010 - 12:09 AM.

How do I get Autopatcher official again with the revised WindowsMedia9-KB2447961-x86-ENU.apm file?

I tried reverting to the old one, also tried deleting all files/folders relating to KB2447961 and running apup again (which downloaded those files again), but autopatcher remains unofficial.

Quote

If there were edits that needed to be done to this .apm file, Cristiano needs to make them, sign the release and then upload the new files.

Quote

If you've run APUP again and updated the XP SP3 release and it's still unofficial, you may have a stray file somewhere. To determine this, run AutoPatcher, click About - Release Info, if the release is True you have a stray file, if it is False, update the release and/or locate the stray(s).

I removed these files,
- \__WMP_critical\WindowsMedia9-KB2447961-x86-ENU.apm
- \__WMP_critical\WindowsMedia9-KB2447961-x86-ENU.apm_files\WindowsMedia9-KB2447961-x86-ENU.exe
- md5_checksum_for_AutoPatcher_XP_ENU.md5
- xp_sp3_enu.rti

... ran APUP, updated XP SP3, the release is official once again. If you think you have a stray but can't find it, create an .md5 of the release and post the .md5 file, I (who ever gets it first) will run it against an official XP SP3 release. If the release has more than XP please mention this. Zip the .md5 file and attach it to your post.

> So why does
do you have more than one OS in your computer? i can try reproduce this issue in a vm, but to that work, it must be more close than possible to your real situation, meaning that i need to know the exact version of wmp that you have

> How do I get Autopatcher official again with the revised WindowsMedia9-KB2447961-x86-ENU.apm file?
besides the tip from mike, please look if there's any compressed file inside your modules folder. if that doesn't work, please take an recursive md5 from the entire apup folder and please say the scripts that you have mixed

[]s

Apologies to both guitarmike and Cristiano, and thanks to both for your help. It was carelessness on my part.

Using ilSFV it identified WindowsMedia9-KB2447961-x86-ENU.apm as the fiole with md5 mismatch. Looking at that file in Notepad I found that I had not, after all, replaced the new (test) WindowsMedia9-KB2447961-x86-ENU.apm with the original one after the test, and had not deleted it either when I tried running apup again after deleting the KB2447961 related files, so that apup did not replace it. Deleting those files again (this time more carefully and also deleting the XP md5 rti files) apup did download the original WindowsMedia9-KB2447961-x86-ENU.apm and all the other files, and Autopatcher was official again (though of course with that update marked as not installed).

To answer Cristiano's question: only XP pro SP3 is installed on this PC.
Edited by JRosenfeld, 21 December 2010 - 03:40 PM.

# 2011-01-12: +KB2419632; ~kb890830-v3.15

[]s

Cristiano, ran the updater this morning( my time) and came up with a file verification error on the latest update.
Ran the autopatcher to check but came up unofficial, so checked the modules folder.
It downloads the file to the folder but there is no apm file.
The file concerned is KB2419632-X86.
Bruce

First, thanks to everyone for producing some great software and for providing a great service !

I'm having the same problem, I think as reported above.

Below are entries from my apup.log file :

***Starting Detection Routine Phase***

Detection error for file F:\AutoPatcher\modules\Components\WindowsUpdateAgent_x86.apm
MD5 Hashes do NOT match. Expecting 6D3CA1DF5E1896E2BD55BEBB6256AE32, but found cc5552c855ce0c94b7d0149fdc61c4ac!!!
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.autopatch...00.229_new.7z--

Missing file F:\AutoPatcher\modules\Critical\WindowsXP-KB2419632-x86-ENU.apm
Item AutoPatcher XP SP3 Critical APMs is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://www.autopatch...l_20101214.7z--

Missing file F:\AutoPatcher\modules\Components\WindowsUpdate_x86_files\WindowsUpdateAgent30-x86.exe
Item WindowsUpdateAgent30-x86.exe - 7.4.7600.226 (KB949104) is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.wind...ent30-x86.exe--

***Downloading Releases***

Files to be Downloaded: 3
Download queue processed. Proceeding to next phase.

Download Error: F:\AutoPatcher\temp_bin\windows_xp_sp3_enu_critical.7z
File size does NOT match. Expecting 9378, but found 10850!!!


I've had the problem above with WindowsUpdateAgent_x86.apm and WindowsUpdateAgent30-x86.exe for some time. Could this be related to me disabling the WindowsUpdate service ? It doesnt appear to cause any problems and I don't use WindowsUpdate as I prefer to use AutoPatcher !

Thanks and if there is any more info you need, I can post here.

The script is pointing to the wrong .7z, the hash and size are correct - I believe the date is the problem - windows_xp_sp3_enu_critical_20101214.7z.

This should work ... /releases/english/win_xp/windows_xp_sp3_enu_critical_20110112.7z

Again, the hash and size ( ExpectedSize=9378 /// ExpectedHash=604A191EE6E67DB13C4CD28411C87817 ) seem to be correct

I've tested it, the change downloads the correct file and all is Official so no resigning needed.

fixed

[]s

Thanks very much Cristiano.

Is working fine now :

***Starting Detection Routine Phase***

Detection error for file F:\AutoPatcher\modules\Components\WindowsUpdateAgent_x86.apm
MD5 Hashes do NOT match. Expecting 6D3CA1DF5E1896E2BD55BEBB6256AE32, but found cc5552c855ce0c94b7d0149fdc61c4ac!!!
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.autopatch...00.229_new.7z--

Missing file F:\AutoPatcher\modules\Critical\WindowsXP-KB2419632-x86-ENU.apm
Item AutoPatcher XP SP3 Critical APMs is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://www.autopatch...l_20110112.7z--

Missing file F:\AutoPatcher\modules\Components\WindowsUpdate_x86_files\WindowsUpdateAgent30-x86.exe
Item WindowsUpdateAgent30-x86.exe - 7.4.7600.226 (KB949104) is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://download.wind...ent30-x86.exe--

***Downloading Releases***

Files to be Downloaded: 3
Download queue processed. Proceeding to next phase.

***Processing Cleanup Routines***

Extracting F:\AutoPatcher\temp_bin\WindowsUpdateAgent.7z into F:\AutoPatcher\modules\Components
Extracting F:\AutoPatcher\temp_bin\windows_xp_sp3_enu_critical.7z into F:\AutoPatcher\modules\Critical

Quote

It shouldn't be by looking at your log file...

Item WindowsUpdateAgent30-x86.exe - 7.4.7600.226 (KB949104) is missing or its parts are not completely downloaded

This file was updated last September (09/18 script) to 229 - #2010-09-18: ~WindowsUpdateAgent 7.4.7600.229;.

If you post a complete log file (unedited) someone could have a closer look but this looks wrong to me.

gUiTaR_mIkE, on 13 January 2011 - 08:58 PM, said:

Thanks Mike

I'll do the latest critical updates and then post the complete apup.log file. I expect that the WinUpdate issue will persist as I have had this for a number of months now. Someone else reported the same problem on another thread a few months ago, and it seemed to be a local issue for them, which is what I expect it is for me too.

If I were to leave this, do you know if it would it expose some serious vulnerabilities ? I use the same autopatcher for a number of PCs and all have the same issue.

Ok, will post back after doing the latest updates...

Thanks

FYI - I choose not to update the WindowsUpdateAgent in autopatcher and have disabled the WindowsUpdate service on all the PCs I use autopatcher on. I don't know if this could be the cause or contribute to this problem.

Quote

I'm not sure what the issue is, you don't have to install the update, but you want AutoPatcher updated and Official - is it?

You can do as you see fit, AutoPatcher is meant to be customized (and hopefully remain Official), have you thought about using an answer file? I have AutoPatcher load with nothing checked, I select the updates I want...

I uncheck everything - 0 to install / 0 to remove - click Advanced - select Save selection to answer file - give it a name, 'whatever.aaf' - and Save to \apup. I also start AutoPatcher with - autopatcher.exe /nolicense, this bypasses the two EULAs - when AutoPatcher loads I have two options, use my new answer file or not. Just an idea

Quote

Well, I agree with part of this - I don't install it either (or WGA) and have Automatic Updates disabled myself but, you want to make sure that AutoPatcher is updated with all the latest files and Official, I'm not sure how you're doing this while keeping this update out of AutoPatcher. Again, you dont' have to install an update just because it's in your release.

Not sure if anyone caught this or even cares at this point - the XP SP3 English release was updated, please report any issues.

~ / MRT v3.16; RootCerts v27
+ / KB2393802; KB2476687; KB2478960; KB2478971; KB2479628; KB2482017; KB2483185; KB2485376
- / KB978037; KB981852; KB2286198; KB2296199; KB2416400; KB2436673; KB2467659

...forgot to ask, does anyone know if the extraction method that works with Windows Installer: 4.5.6001.22159 and most of the updates in XP - kbxxxxxx /x - does this also extract the contents of the Windows 7 *.msu files, using the above version of Windows Installer - just wonderin'???