Curing Windows Update after a hardware change

· by Steve · Read in about 2 min · (265 Words)

I mentioned in my previous post that I’d managed to avoid performing a complete XP reinstall when changing my motherboard by following the steps in this MS Knowledge Base Article. However I noticed that I wasn’t getting the surge of windows updates that I’d expected since I assumed the process would replace a bunch of files from the original XP SP2 CD.

It turned out that Windows Update was bottlenecked on the Microsoft Installer 3.1 update, which was refusing to install correctly. I fixed that by manually downloading the Windows Installer 3.1 redist package and installing it, after which I got the expected 80-odd update queue. I shut the machine down and left it to it - but on getting back to the machine the next time I noticed I still had a 79-item queue. Hmm.

Trying to apply the updates manually failed with no indication of why, but digging into the c:\windows\windowsupdate.log I found the message: “Error: 0x80004002. wuauclt handler: failed to spawn COM server” which appeared to be the root of the problem. Some hunting online indicated that a bunch of COM DLLs might have somehow become unregistered through the process of running the upgrade install, so I had to manually REGSVR32 the following DLLs:

WUAPI.DLL
WUAUENG.DLL
WUAUENG1.DLL
ATL.DLL
WUCLTUI.DLL
WUPS.DLL
WUPS2.DLL
WUWEB.DLL

Fun huh? That seems to have done the trick, it’s now chewing through all 80-odd updates in a much happier fashion. Just posting this here in case anyone else follows that KB article and wonders why their updates are broken. It’s a shame the KB article doesn’t deal with this.