Reinstalled WinXP on this laptop 4 times...Windows Update doesn't work.

[Ichinisan]

Working on a Compaq laptop for someone and I've reinstalled Windows XP at least 4 times already. I keep ending up with a system that hangs at 100% CPU usage until I kill the "Automatic Updates" service. The Windows Update web site searches for updates forever.

I've tried following steps I've found online (deleting the SoftwareDistribution folder). It does not work.

Each time, I reinstall WinXP Pro using the original "Operating System" disc and end-up with WinXP Pro SP1 installed. Then I install "Driver Recovery CD Disc 1/2" (I never put in Disc 2/2 because all required drivers are installed, according to Device Manager). It also installs some other stuff like DotNet Framework 1.1. I opted-out of stuff like Sonic burning software and an ancient version of iTunes. The Windows Update web site doesn't even start to work with IE6 now, so I install SP3 off a USB thumb drive (I downloaded it directly from Microsoft yesterday).

HALP?

 

[vailr]

Try this free program:
Tweaking.com - Windows Repair 1.9.15
http://www.majorgeeks.com/files/details/tweaking_com_windows_repair.html

 

[postmortemIA]

yep installing SP3 + offline IE8 should make it work. Also there is automatic updates in control panel, you could get patches just by enabling it and making it download updates right away.

 

[Ichinisan]

yep installing SP3 + offline IE8 should make it work. Also there is automatic updates in control panel, you could get patches just by enabling it and making it download updates right away.

Tried that. This last time, I reinstalled XP (SP1), installed *only* the WiFi driver (the Ethernet port is fried and I have to enable my guest WiFi network because the stock driver only supports WEP). Installed SP3 offline.

As I attempted to install IE8 offline, it asked if I wanted it to download updates.

30 mins later, there's still no network activity and it acts like it's downloading (no information about progress is presented). CPU is at 100% with svchost.exe using it all. I guarantee it goes down as soon as I kill the "Automatic Updates" service.

[edit]
Yup. Microsoft is KILLING ME.

 

[Via]

This is probably a dumb question, but are you sure the HD is completely clear when you begin the install?

 

[Ichinisan]

This is probably a dumb question, but are you sure the HD is completely clear when you begin the install?

I'm deleting the partition so it's one block of unpartitioned space when I press the Enter key to install. I've tried quick format and full format multiple times.


Over 8 installs now. Tried various things each time. Always ends with a system bogged-down by svchost using 100% CPU as soon as the system checks for updates (manual or automatic).

Here's where it gets strange: I still never saw anything about Windows Genuine Advantage (which this system should pass with no problem).

I tried an XP Pro SP3 disc on another throw-away system and did a clean install. That one is a dual-core CPU and it also gets stuck "Checking for updates" forever with both cores showing constant high usage while the system gets hot and the fans go full-speed. Everything calms down when I kill the Automatic Updates background service.

Did Microsoft do something to break Windows Update for all new XP Pro installs?

 

[Ichinisan]

Try this free program:
Tweaking.com - Windows Repair 1.9.15
http://www.majorgeeks.com/files/details/tweaking_com_windows_repair.html

Tried this out of desperation and deselected everything except the Windows Update repair. The problem is still there. However, it *might* have taken longer to start happening after Windows Update started scanning.

 

[mikeymikec]

There was another thread recently on this exact topic (though I can't remember whether it was XP Home or Pro). I mentioned on that thread that my VirtualBox install of XP Home SP3 did the same thing as you're describing but it eventually settled down (I can't remember how long I left it for but it wasn't a matter of multiple hours IIRC).

In both cases big-name OEM discs (either for install or 'driver recovery') had been used. My bet is that among the non-MS software installations, some dodgy registry tweaking had been done. Remember the whole XP SP3 debacle due to big-name OEMs enabling every bloody driver including the CPU power management drivers for Intel and AMD at the same time?

I would suggest using a vanilla XP install disc, preferably SP3 but not necessary, and download the drivers manually from the OEM's site (or the hardware manufacturers' sites). If anything getting the latest mature drivers for old hardware is better than some 2003-approximate-era drivers.

 

[Ichinisan]

There was another thread recently on this exact topic (though I can't remember whether it was XP Home or Pro). I mentioned on that thread that my VirtualBox install of XP Home SP3 did the same thing as you're describing but it eventually settled down (I can't remember how long I left it for but it wasn't a matter of multiple hours IIRC).

In both cases big-name OEM discs (either for install or 'driver recovery') had been used. My bet is that among the non-MS software installations, some dodgy registry tweaking had been done. Remember the whole XP SP3 debacle due to big-name OEMs enabling every bloody driver including the CPU power management drivers for Intel and AMD at the same time?

I would suggest using a vanilla XP install disc, preferably SP3 but not necessary, and download the drivers manually from the OEM's site (or the hardware manufacturers' sites). If anything getting the latest mature drivers for old hardware is better than some 2003-approximate-era drivers.

The other system I tested was a vanilla ISO and did the same thing. I left both systems for a ridiculous amount of time and both felt like they were melting down from the stress of sustained 100% CPU usage. I haven't left it alone for hours, though. I hope the computer can handle it.

 

[CZroe]

This is probably a dumb question, but are you sure the HD is completely clear when you begin the install?

I'm deleting the partition so it's one block of un partitioned space. I've tried quick format and full for,at multiple times.

I told you about the OEM restore I did that would say "Shutting Down" and then reboot as soon as I connected it online no matter how I connected it online. I did it by deleting the OS partition and then running the factory restore too. The problem was a rootkit in the MBR. Run Malware Bytes Anti-Rootkit (MBAR).

 

[Ichinisan]

I told you about the OEM restore I did that would say "Shutting Down" and then reboot as soon as I connected it online no matter how I connected it online. I did it by deleting the OS partition and then running the factory restore too. The problem was a rootkit in the MBR. Run Malware Bytes Anti-Rootkit (MBAR).

No. I'm booting directly from the CD before any rootkit would have a chance to run. The boot sector on the HDD never starts to load. The HDD is wiped and everything is copied fresh.

 

[Dahak]

Odd, the one thing that i have seen sometimes, is after yo install windows, install sp3, install ie8 (no network connected) it will skip the update check and continue provided that you have the full installer and not the small installer that goes to look online for the rest of it.

Once that is done Turn off the Automatic Updates in control panel, and then try it from the website and see what happens.

I have had it happen when a fresh install, the Automatic Updates caused delays an other odd issues when that was enabled(either on download or install automatically) and turning it off, reboot and then manually going to windows updates seems to fix it

 

[CZroe]

No. I'm booting directly from the CD before any rootkit would have a chance to run. The boot sector on the HDD never starts to load. The HDD is wiped and everything is copied fresh.

but its not wiping out the MBR. it is only imaging over that partition. the MBR is executing when the system boots normally

 

[Ketchup]

Ichinisan, I think it's interesting that you are having Automatic Update issues on Windows 8 and now on these other computers. I have never had a problem with either, and that includes computers I have serviced. Not meant to be a slam, just interesting.

When installing XP with SP1, I would recommend you run an Service Pack 2 installer, then check for updates.

Are these copies of windows activated before you try to run Automatic Updates? Could be a problem?

Also, are you running Microsoft Update, or Windows Update?

Also, in XP if you delete the partition XP is on, all traces of that installation will be gone as well. Now if there is/was an XP installation on another drive/partition, I could see some possible issues there.

 

[Mushkins]

Getting updates on XP machines has been dodgier and dodgier over the past few years, especially if your install media is pre-SP3 since it's all officially in unsupported/legacy land.

I'd try to take an XP install disk and slipstream as many updates as humanly possible into it, especially things that install Microsoft Update instead of Windows Update and later versions of IE. It might help the auto update checker not get hung up.

But yeah, here's another voice for just leaving it overnight and seeing what you get. And absolutely see if you can find the device drivers from the manufacturer website instead of that ancient restore disk. Get the wifi drivers installed and thats it, *THEN* run windows update to minimize potential conflicts, you can install the rest afterwards. Im a little surprised XP installs pre-SP3 arent just giving people a "sorry, its time to upgrade to a modern OS" splash page in Windows Update these days.

Alternatively you could configure a WSUS server on a .local domain in a VM if you have access to windows server. Then join the laptop to the dummy domain and pull the updates from your local server instead of the windows update service, then dump it from the domain back to the default workgroup. Might be a smidge more reliable and it's one more troubleshooting tool you can spin up again anytime you have to do a WinXP repair.

 

[mikeymikec]

Microsoft Update in my experience is somewhat more resource hungry than Windows Update, so I'd expect a difference there. What I was talking about was based on my experience with Windows Update though. I'd try leaving the laptop to chew it over for an hour, perhaps two tops.

 

[Ichinisan]

Microsoft Update in my experience is somewhat more resource hungry than Windows Update, so I'd expect a difference there. What I was talking about was based on my experience with Windows Update though. I'd try leaving the laptop to chew it over for an hour, perhaps two tops.

I only tried Microsoft Update the first time. Windows Update every time since.

Microsoft did something and I think this affecting any new Windows XP installation at the moment. I'm going to try a VM when I get home again.

 

[Ketchup]

... Microsoft did something and I think this affecting any new Windows XP installation at the moment....

Um, ok. The installation on my VM is about 2 months old and just did a Microsoft update. I took close to 4 minutes as there were a number of updates.

 

[Ichinisan]

Um, ok. The installation on my VM is about 2 months old and just did a Microsoft update. I took close to 4 minutes as there were a number of updates.

Yeah. I'm not suggesting that a previous install that has successfully updated would be affected.

Try a fresh install. XP Pro.

I'll try it again when I get home.

 

[Ichinisan]

Getting updates on XP machines has been dodgier and dodgier over the past few years, especially if your install media is pre-SP3 since it's all officially in unsupported/legacy land.

I'd try to take an XP install disk and slipstream as many updates as humanly possible into it, especially things that install Microsoft Update instead of Windows Update and later versions of IE. It might help the auto update checker not get hung up.

But yeah, here's another voice for just leaving it overnight and seeing what you get. And absolutely see if you can find the device drivers from the manufacturer website instead of that ancient restore disk. Get the wifi drivers installed and thats it, *THEN* run windows update to minimize potential conflicts, you can install the rest afterwards. Im a little surprised XP installs pre-SP3 arent just giving people a "sorry, its time to upgrade to a modern OS" splash page in Windows Update these days.

Alternatively you could configure a WSUS server on a .local domain in a VM if you have access to windows server. Then join the laptop to the dummy domain and pull the updates from your local server instead of the windows update service, then dump it from the domain back to the default workgroup. Might be a smidge more reliable and it's one more troubleshooting tool you can spin up again anytime you have to do a WinXP repair.

Because I thought it *might* have something to do with the SP1 install disc, I burned an "untouched" ISO of X14-73974 (originally downloaded from MSDN). I installed it on a different throw-away system. I deliberately Google-ed for a volume license key (I wanted to get a banned key and see if it would fail WGA validation).

Just like the computer with the legit / OEM disc, the throwaway test system hangs forever "checking for updates" with 100% CPU usage while the fans get really loud and it gets really hot. It never even gets to suggest WGA validation.

 

[Ketchup]

Yeah. I'm not suggesting that a previous install that has successfully updated would be affected.

Try a fresh install. XP Pro.

I'll try it again when I get home.

Cool, I'll do one if I have time (should, VMWare makes it so painless) and we can compare notes.

 

[Ichinisan]

Cool, I'll do one if I have time (should, VMWare makes it so painless) and we can compare notes.

Cool. Let me know what you find. I'm also installing in a VM.

 

[Ichinisan]

OK...after almost 2 hours, the dual-core throw-away laptop finally said that I had the latest version of Windows Update installed and prompted me to install Windows Genuine Advantage.

 

[Ichinisan]

VM is doing the same thing with 100% CPU usage (thankfully, it's a single-core VM) and taking ages with no network throughput.

So I guess I just have to be *incredibly* patient for any XP Pro system that's checking for updates for the first time.

I wonder what on earth it could actually be doing while the CPU is maxed and the PC is overheating...

 

[RampantAndroid]

Same log location as before. C:\Windows\WindowsUpdate.log

You can see what it's doing. I have a VM right now installed SP3 out of curiosity. I'll see what happens when I scan.