KrytenAG

KB903235 was retired in August... for the two other, I can't confirm since they were showing up on a clean install under simulation... Just tested this myself, and with 905749 & 896688 installed, none of the older three items show up on windows update.

Actually, it's not. Apparently the one that was released in May wasn't the final build, but the distribution mistake wasn't caught until 9-2. If you look at the digital signatures, the rerelease has a verisign date one day (5-4-05) after the May release. If you extract the archives and compare, there are indeed differences. Looking through them, it appears that the difference is that the May release erroniously set the uninstall reg key to point to "KB893803" instead of the "KB893803v2" that it should be. While not a show-stopper, this is an important rerelease if you ever want to be able to properly uninstall the update. There is no other indication of the change, so the update probably won't show up on windows update if you already have the May release. Despite that, I'd still strongly advise everyone updating their Post-SP2 packages. [edit] Oh, and for this month's release of the malicious software removal tool, we have an exciting new Version value of "33B662A4-4514-4581-8DD7-544021441C89" .bat file: REG ADD "HKLM\Software\Microsoft\RemovalTools\MRT" /v "Version" /d "33B662A4-4514-4581-8DD7-544021441C89" /f .reg file: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RemovalTools\MRT] "Version"="33B662A4-4514-4581-8DD7-544021441C89"

Actually, I replaced it with KB896358 in my own update set (as MS05-026 says it has been replaced) and windows update showed 0 critical updates. While it may be the case that it's listed on a clean install, that seems to me to be a Windows Update error, as installing KB896358 makes KB890175 disappear from the update list (as it should). Such as for every single Windows that has Office installed. Silly Microsoft. [EDIT] On a side note, I've been using a homebrewed Auto-It-based XP Post-SP2 Updater for a few months now, and I think it's pretty stable. All it does is check for the various registry keys that each update should modify, shows you the ones that aren't yet installed, and runs each of the update packages (official MS ones, except for WMP and .NET) in silent mode, showing you the progress as it goes down the list. If anyone is interested in this, I can clean it up a bit, make it a little more user-friendly, and post it in a thread. I might also be able to add an automation switch that still shows update progress which you can use in SVCPACK on an XP CD. This would allow you to see what update is currently installing and what has yet to be done.

Ah, good to know, as I was worried about those visitors that would miss reading the later warnings to "put them in numerical order!" Yes, I'm aware of that, hence why I said "numerical, not chronological". What I should have said was they're "basically the same, except for those hotfixes that have been updated since initial release." BTW, nice job with your integratable update pack. Though I can't use it for my CD, I did give it a try and it cuts the install time waaay down.

@Joffer The answer to your question can already be found in this thread (in the 4th post, actually). The batch file doesn't have to be run from cmdlines.txt if you're not using it - you can run it from svcpack.inf instead. @straffin Heh. Yes, it is in reverse order (numerical, not chronological, though they're basically the same). I imagine that's just the way things went as items were added.

Great idea with this thread, Incroyable Hulk ! Just started browsing the msfn forums for info on making unattended/updated/etc. windows CD's, and this is the perfect thread for XP (and 2k, of course). Anyways, testing things out, I saw that KB887472 has been mentioned a couple of times, but was passed over for the list because it isn't supposed to come up with a clean install of XP. My CD is using a clean install, and that KB comes up as a critical update (the only one) on windows updates. I only have whatever windows messenger is provided with XP with SP2 slipstreamed, but maybe by "clean" you mean with messenger removed (a la nLite)? Could also be possible that the scope of the update has been increased recently. In the case that it is one for the list, here it is in your format: KB887472 -› Vulnerability in PNG Processing Could Allow Remote Code Execution XP SP2: Download -› 1056 KB (February 7, 2005) XP SP1: Download -› 1047 KB (February 8, 2005)