886 replies to this topic

[Cristiano]

no. under seven, the command changes to /extract. but isn't an good idea do that, because the extract command only extract a few files. taking Windows6.1-KB975560-x86.msu as an sample, you will have to select the whole file name (under seven, the extension is ignored by default and i didn't found an way to change this behavior back) or the extract command will not work. then, following the sample:
Windows6.1-KB975560-x86.msu /extract

you will get:
Windows6.1-KB975560-x86.cab
Windows6.1-KB975560-x86.xml
Windows6.1-KB975560-x86-pkgProperties.txt
WSUSSCAN.cab

at this point, nothing is useful. you have to extract the content of Windows6.1-KB975560-x86.cab, that will have a dozen of .cat files. from those, you have to pick the right one. one problem: there's a few with an similar name, like:
package_1_for_kb975560_bf~31bf3856ad364e35~x86~~6.1.1.0.cat
package_1_for_kb975560~31bf3856ad364e35~x86~~6.1.1.0.cat
package_for_kb975560_rtm_bf~31bf3856ad364e35~x86~~6.1.1.0.cat
package_for_kb975560_rtm~31bf3856ad364e35~x86~~6.1.1.0.cat

the current version of the module for this one asks for Package_for_KB975560~31bf3856ad364e35~x86~~6.1.1.0.cat that isn't present... i can't be sure if the detection for this one works from here, but if it is, the .cat file without that _bf is renamed

so, to make the job more easy, try 7zip with the .msu files

[]s

[click-click]

Who made the changes for the latest Feb12 XP SP3 English?

The reason I ask is that the registry detection being used for IE has changed from the previous detection method and KB2482017 is being flagged as not installed for IE8 on my system even though it is installed.

I changed IE8-WindowsXP-KB2482017-x86-ENU.apm RegistryPath=
from HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB2482017-IE8\Filelist <----- does not work
to HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB2482017-IE8 <----- this works

Previous detection did not use Filelist for IE7 or IE8. Can this be changed so I can get back my official status on AP?

Edited by click-click, 15 February 2011 - 01:39 PM.

[_def_x_]

Quote

the registry detection being used for IE has changed from the previous detection

Well, they came from Microsoft but maybe the \Filelist is supposed to be left off - it is listed in the Registry Key Verification. You only mention IE, what about the other updates, they all have \Filelist, none of them are working either? It is difficult when you only get part of the problem, I don't want to go back and do it again (and again) for the rest of the updates. I tested on 2 systems one with IE6 and one with IE8 - they worked - yes, maybe I made a mistake.

Just a side note but it's worth mentioning. The project is essentially dead, the forums are a ghost town, so you should get used to maintaining your release with what will be the perpetual Unofficial Warning Status nag screen - if you want to continue using AutoPatcher with future updates. In fact I'm not sure AutoPatcher will be as accurate once SP1 for Windows 7 is mainstream, and may be best used with XP, Vista, and Windows 7 without a service pack.

You seem to know quite a bit about how things are done, you can edit apm files, I figure you could have maintained a script had you wanted to so I would get used to having a so-called Unofficial release, one that you have created - now may be as good a time as any Edit the .apm files so they work for you, get rid of the .rti file as well. I never bother signing a release for my own use just to update a friends system, if I created the contents and I know they work signing is more effort simply to avoid looking at an interface I see for a moment anyway - and it doesn't affect AutoPatcher's ability to install an update. I do create a .md5 file for all the contents - this is a must.

I figure once Frank knows I can reach the ftp he will put a stop to it, it's only a matter of time before we're all gone for good. The forums are pretty depressing anyway, nobody logs in, if they do it is to complain, the wonderful pornographic spam hangin' around - gets old fast. I looked at a number of my last posts - few follow-up with even a kiss my butt, it makes you feel it's all a waste of time.

[click-click]

Okay, thanks for making the changes. I appreciate it. I was thinking someone new had been officially assigned to do XP. All other detections for XPSP3 and Extras were right on. IE8 was the only detection that did not work for me. I can live with unofficial

[_def_x_]

Quote

I can live with unofficial

No, I don't want you to have to with the latest release I've done, it was more a reminder - this will be the future.

What I want to figure out is why the \Filelist is giving problems with only IE8 and not the rest of the updates, there were 9 or so total this month. Maybe it is something else causing problems. Again I will fix it as soon as I get the Extras Silverlight squared away - I would install it but I don't want it on my system.

Quote

I was thinking someone new

I do consider myself a noob at this it takes me forever to finish. The script is the biggest part. I could have the new updates in AutoPatcher and signed pretty quick, it's the lines of code in the sript that start to make me dizzy, and you still have the apm files to deal with. I was amazed at how fast Cristiano could do it - don't tell him I said this Including spaces, and I added some to the latest xp script (for my eyes) there is nearly 2600 lines to sift through. Btw, Cristiano, have a look at the rti and md5 section - yes, no?

[Cristiano]

> I was amazed at how fast Cristiano could do it
at my job, i have an 100MB IC. so, everything is downloaded asap . but one tip: the modules us to be basically the same every month. so, the fastest way to do it is taking an previews one as template. take WindowsXP-KB2360937-x86-ENU.exe as an sample. forget the .exe part and replace it by .apm. opening it, just replace all the KB2360937 by the new kb number (like KB2443105). if you wish do the things even faster, forget about the FileMD5= part of the file detection and leave it as FileMD5=ANY. it works like this for seven and vista, so... if you wish do the modules for more languages, all that you have to do is replace ENU by PTB, ITA, etc and then change SystemLanguage by the target language. of course, it helps if you have free time (and as i'm working with government bidding since last year, there's days with a lot of work and days without nothing to do... the problem: it's vacations time, so i'm taking extra work load with contracts, etc...)

> have a look at the rti and md5 section - yes, no?
it's more easy to do, in fact. but as very often i did mistakes, it was more simple to fix one at a time

[]s

[lengolad]

This is all so sad... I've got a ton of machines to update (XP, Vista, and 7) and AutoPatcher has been an amazing tool. Sorry to see it fade into oblivion. I guess when the internet world assumes that everyone has a healthy broadband connection, this kind of thing is inevitable. "Just turn on Automatic Updates for all your computers--of course!" Well, that would kill my monthly download limit and would take about a week of interrupted connections... [Even to download AP updates was a hassle--many disconnections and interruptions, but at least I only had to do it once!] I was going to ask about a couple of updates that weren't getting applied to a couple of my machines, but it seems a moot point. I don't understand 'scripts' and much of the other jargon here, so I guess this is it for me. :-( I just want to say 'thanks' before I go. You've all been very helpful. Sincere best wishes to you all!

[_def_x_]

lengolad said:

I was going to ask about a couple of updates that weren't getting applied

...XP SP3 please ask away, 7 or Vista, that's Domenico and I guess he decided to leave but I do believe he updated 7x64 one last time. Still, ask, maybe someone will chime in.

click-click said:

HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP0\KB2482017-IE8\Filelist

What's strange is the .cat file isn't even being detected at your end. I updated a third machine (my XP SP3 VM) and all the updates were detected, my VM is running IE8. I emptied the .apm file of the registry detections and used only the .cat - it too worked. I'm not sure if you read my question - what about the other updates that also have \Filelist in the path, are they failing too?

Cristiano, any ideas? I've made a note to remove them but why are they breaking things at click-click's end, for me they have worked on 3 systems now - and I'm puzzled. In fact, for the 4 or so months with Windows 2000 I used them and don't recall anyone saying a detection was failing because of \Filelist in the path and again, they always worked for me which is why I kept using them, it was listed as part of the Registry Verification string.

If anyone else is having this exact problem please say so.

[Cristiano]

> Cristiano, any ideas?
i'm not sure. i guess that something may change when deploying the update or it is related to system variables. but i will take a look on it later. now, i have to fix 1 week work of my boss...

oh yes, i can't edit post #566 anymore. so, instead "just replace all the KB2360937 by the new kb number (like KB2443105)" read it like this: "just replace all the 2360937 by the new kb number (like 2443105)". without the kb, an simple replace will fix the more info link as well

[]s

[click-click]

Mike, the IE8 cat is not found because mine was named I2482017.CAT to retain 8.3 compatibility.

I always keep a previous version of APUP as a backup and also, to see what has changed between each patch Tuesday. None of the reg detections in the previous APUP .apm files used /filelist and they all end with /KBxxxxxx. I assume the other /filelist detections worked because the .CAT files matched. I don't think any of the /filelist detections would work on my system if the CAT detections were removed.

Also, the /filelist entries on my system all end with a number from 0-10. I.e /filelist/0, /filelist/10

Thanks for taking the time .....

p.s. I just ran a test with KB2393802 by removing file detection and the reg detection fails here with /filelist, but okay without it.

Edited by click-click, 16 February 2011 - 12:58 PM.

[_def_x_]

>>>the IE8 cat is not found because mine was named I2482017.CAT to retain 8.3 compatibility.
The issue is not with \Filelist, I'll explain, but why didn't the last IE8 cumulative update fail, it wasn't renamed in the apm? I'm wondering if you have a hacked XP, 'tiny' or 'nLited' to death, this is making less sense as I look into it.

First, I will admit I'm not an expert here and I don't have the ability to see every single person's system, and I can only go by what I have access to - all 3 systems have a registry \FileList for 99% of every update isnstalled, there are maybe 5 out of more than 100 updates that don't need it, usually because the update was a registry edit and no files were updated. These categories may vary system by system but an update as important as the IE8 cumulative should have many entries under \FileList, I have 38 - that's \FileList\0 - \FileList\37.

>>>I just ran a test with KB2393802 by removing file detection and the reg detection fails here with /filelist,
It shouldn't fail with it as far as I can see, this update as well, replaced files, the locations, filenames, etc are listed under these subcategories. Now, if I put \FileList\10 and it didn't exist, this may fail but, \FileList simply means there is additional info regarding this update that lies beyond the path. On my system I have 18 subcategories beyond \FileList for this update that contains critical information... here's just two entries...

\FileList\0 - FileName (ntoskrnl.exe), Location (C:\Windows\system32)
\FileList\11 - FileName (ntdll.dll), Location (C:\Windows\system32\DllCache)

Like I said there are 16 more subcategories for me, you're saying you have zero registry info listed for this update beyond \KB2393802???

It probably is a good idea to simply leave off \FileList because it isn't needed but if an update overwrites or updates files, as well, there is the qfe reference, hidden uninstaller and so on, all this info is listed beyond \KBxxxxxx, and as far as I can tell is found beyond \FileList.

I'm still scratching my head as to why you say the IE8 cumulative update dropped the IE8 part, compatability with 8.3???

Btw, I do believe you I just don't know why your cat files are being renamed and you have no info beyond the \KBxxxxxx entry. In fact, I will get a screenshot of my regsitry entry for the IE8 cumulative update and you can see the subcategories drop way down the screen - can you get me one of yours as well so at least I can see what your seeing?

Good, I had time to edit - here's a screenshot of the updates we talked about and \Filelist in the registry - updates.jpg

Edited by gUiTaR_mIkE, 16 February 2011 - 03:20 PM.

[click-click]

Mike, I have /filelist entries, but none of them contain KeyName=Type and KeyValue=Update Only the entry ending with KBxxxxxx has that KeyName and KeyValue. Using /filelist will not work for me. I was just questioning why filelist was added since it was never used in all the previous XPSP3 apms

I must add that the system I have was created with RyanVM Integrator using XP+SP3 +UpdatePack +Addons (IE8,WMP11, etc.). Every so often, I would find things not being detected by AP because I had hotfixes that had replaced the fixes AP detected. Cristiano was kind enough to add those hotfix detections for me so that AP was pretty much compatible with a system integrated with RVM. No hotfixes this time though, just business as usual.

[click-click]

>The issue is not with \Filelist, I'll explain, but why didn't the last IE8 cumulative update fail, it wasn't renamed in the apm?

The last IE8 cumulative update apm file did not use /filelist, so it did not matter if the file detection (renamed cat) failed because reg detection was successful finding the Type=Update entry. If you use /filelist, AP will not find any Type=Update entries in that subcategory on my system - only on the KBxxxxxx level.

If you are really sure filelist works for you, try removing the file detection section in one of you apm files and see if it still detects the fix only using /filelist reg detection.

Edited by click-click, 16 February 2011 - 05:36 PM.

[_def_x_]

OK, I'll fix it. I just wish that I knew why one system will write KB2482017-IE8.CAT and another KB2482017.CAT for the IE8 update (when you extract the contents of each update KB2482017.CAT is for IE6). The whole point of multiple detections is in case one doesn't work. We've dropped the md5 for the cat to make this easier (and faster) already.

Anyway, I'm geting a cold I think so I will deal with this later - you know whats going on. Btw, good catch

[click-click]

Yes, KB2482017-IE8.CAT is there when you install IE8 normally and KB2482017.CAT will be there for the IE6 component in XPSP3. The developer of the IE8 Addon which I use for building my system decided, for some reason unknown to me, to keep all of the IE8 cat files in 8.3 format. That is why my cat file was named I2482017.CAT. Even though this breaks file detection for me, reg detection works fine under the circumstances I mentioned previously. Thanks again for doing the updates for this Patch Tuesday.

Edited by click-click, 17 February 2011 - 12:07 AM.

[_def_x_]

XP SP3 (x86) English - fixed.

Please run APUP and update the release. Thanks for the feedback, much appreciated.

[click-click]

Everything looks great on my side for XPSP3. Thanks for the update.

Edited by click-click, 18 February 2011 - 10:42 PM.

[_def_x_]

XP SP3 (x86) English - Updated. See Latest Changes! for details.

Note:

Remote Desktop Client 5 is old so the update was left out, if you want the update here is the bulletin information:
... MS11-017 /// WindowsXP-KB2483618-x86-ENU.exe

If you have Remote Desktop Client 6 or 7, please report any issues with the updates.

Media Center is not directly supported so an update was left out that targeted MCE2005 only, if you want the update here is the bulletin information:
... MS11-015 /// WindowsXPMediaCenter2005-KB2502898-ENU.exe

As always, please report any issues in the Windows XP SP3 (x86) Forum

[JRosenfeld]

Thanks for that.

[_def_x_]

XP SP3 (x86) English - Updated. See Latest Changes! for details.

As always, please report any issues in the Windows XP SP3 (x86) Forum