RyanVM

As I've already explained, I don't include hacked DLLs which don't give the user the ability to use the original functionality as well. Hence why I don't include a hacked tcpip.sys either.

My bet is that System Volume Information is protected by sfcfiles.dll. Anyway, why are you so hellbent on deleting a hidden folder with one zero byte file inside it?

Well, at least we were right about KB873377 and KB834707 not appearing anymore. My bet is KB889293 is still showing up simply due to how new KB889669 is. Give it a few days (or more realistically, a few weeks knowing how fast Microsoft works ). And I don't suppose there's any other war59312's out there with access to the full post-SP2 hotfix library? There appears to be some juicy updates in there (like a memory leak in uxtheme.dll, a fix for ntoskrnl.exe, and some others) which aren't available without contacting MS.

I've never even heard of UpdateXP 2.0, so here's some generic info: the EXEs I created are 7zip SFX archives with some scripting to run the msi files within silently. There's no reason you couldn't do it for other apps, but if they have silent switches, why bother? The three apps I made (publicly ) all had reasons for being made beyond just being switchless (ie, they add some kind of update/hacked MSI as well).

Windows Update should know obsolete hotfixes on its end. Try a fresh install with just 889669 and see what it reports. EDIT: Here's a quote directly from the KB889669 article:

What apps are you looking to make switchless?

Sounds good to me. And it's going to be a big update. OK, let me try to explain this to you (though you've pretty much got the right idea already). 889669 > 889293. 889669 appears to be 889293 with one extra fix included in the hotfix. And yes, Microsoft update rollups always postdate the older versions, so 889669 replaces 889293 which replaced 873377 which replaced 834707. I hope that clears things up for you.

You mean like this?

If there's a French full version, you should be in luck. Most likely, it's packaged the same way as the US full version, with an MST file and CAB included with the 6.0.2 files. Just make an administrative install point with MST file being called as well.

That's exactly what I made

That's the chipset, not the motherboard. Google the program CPU-Z. It can tell you your motherboard make and model.

It might help if you gave us a little bit more information, like what motherboard you're using... I for one am not psychic, anyway.

OK, I still can't track down what change the Mydoom cleaner is making which gets WindowsUpdate to think it's be run. The most promising lead was a registry key being created called "RemovalTools" to which there was a REG_SZ entry called "MydoomTool" with a value of "OK". However, I manually added it on a fresh install and WindowsUpdate still saw it as a critical update to be downloaded. If anybody else manages to track down what change needs to be made, PLEASE let me know.

Here you go.

Why not just add the one registry entry which tells Windows Update it's already installed? You shouldn't have an GDI issues with a fresh XP SP2 install anyway.

I'm including that DLL with my next update pack release.

I'm seeing the KB836528 MyDoom removal tool in WindowsUpdate on fresh installs in VirtualPC now. Anybody else seeing this? Needless to say, I'm already working on a GDItool-style fix for my next release EDIT: I'm having no luck tricking Windows into thinking the MyDoom checker already ran with registry entries. This is a tough nut to crack.

Please tell me you're not trying to install this on XP SP2... Also, this should be in the Application Switches forum.

http://unattended.msfn.org/xp/hacked_files.htm

viasraid changed to viamraid I'm pretty sure

Go to java.sun.com. The links to 5.0 are fairly prominantly featured.

Until a file is hotfixed, I presume.

Wrong. 1.5.0 is what was renamed to Java5

Very cool, jdoe

wow, very impressive list. Nice job B)