Windows Update 0x8024D001 fixed
Unbelievable.
A Google search for this returns lots of hits, however the variety of solutions seem to have mixed results.
This happened to me most recently in a shiny new Windows XP SP3 Pro virtual machine in VMware Workstation 9.x. The only item installed was, as many might expect, VMware tools.
I am a fan of stopping the windows update service, deleting the c:\windows\softwareupdates folder, and then starting the windows update service. Does that fix this? Of course not. (Actually, my usual screw-up is the clock being horribly off....)
I installed Chrome and MBSA 2.2. MBSA threw an error. Chrome worked like a charm.
Ultimately this forum, this KB article, and THIS DOWNLOAD FIXED IT. Many reboots.
Yes, XP is going EOL very soon.
You know what, that Mac Airbook with the ridiculously short screen (both models) is starting to look pretty good. (I really miss those 4:3 monitors. Stinking display manufacturers...).
This VM was originally plagued with getting an APIPA address (169.x.y.z) because the virtual network adapter hates me. Almost. Anyhow, in workstation, Edit - Virtual Network Adapter, VMNet0 needed the "Bridged" drop-down changed from automatic to the network card that was actually on the LAN. (The fact that both the wireless and wired had active connections and valid addresses seems, well, you know what--I really must stop trying to apply logic to this nonsense).
Good luck!
A Google search for this returns lots of hits, however the variety of solutions seem to have mixed results.
This happened to me most recently in a shiny new Windows XP SP3 Pro virtual machine in VMware Workstation 9.x. The only item installed was, as many might expect, VMware tools.
I am a fan of stopping the windows update service, deleting the c:\windows\softwareupdates folder, and then starting the windows update service. Does that fix this? Of course not. (Actually, my usual screw-up is the clock being horribly off....)
I installed Chrome and MBSA 2.2. MBSA threw an error. Chrome worked like a charm.
Ultimately this forum, this KB article, and THIS DOWNLOAD FIXED IT. Many reboots.
Yes, XP is going EOL very soon.
You know what, that Mac Airbook with the ridiculously short screen (both models) is starting to look pretty good. (I really miss those 4:3 monitors. Stinking display manufacturers...).
This VM was originally plagued with getting an APIPA address (169.x.y.z) because the virtual network adapter hates me. Almost. Anyhow, in workstation, Edit - Virtual Network Adapter, VMNet0 needed the "Bridged" drop-down changed from automatic to the network card that was actually on the LAN. (The fact that both the wireless and wired had active connections and valid addresses seems, well, you know what--I really must stop trying to apply logic to this nonsense).
Good luck!