svchost.exe using 100% CPU because of Windows Update (wuauclt) in XP
Recently I had a Windows XP machine where CPU usage stayed at 100% for approx. 10-15 Minutes after startup. So I used process analyzer to check which thread was using the CPU and (as usual) it turned out to be Windows Update.
It seems that some recent Windows XP updates broke the system once again (after already having issues with an update ruining DOS high memory last year). The solution to the problem is to install the updates KB2879017 and KB2870699 manually. After installing these and a reboot, CPU usage of svchost.exe went back to normal.
Edit: Here is an explanation from Microsoft why this is happening.
System programmer
Comments
I had three different PC’s, all different makes, but all were single core, with IE6 and the updates are set to ‘notify only’.
During early October 2013, all three machines exhibited the same problem with wuauclt causing svchost.exe to run at 100%, resulting in disabling the autoupdate service.
I guess that m$ made a change to the Update Server, without ensuring that client had had plenty of time to update their code ! (the machines are updated regularly).
However, after weeks of searching and trying mostly out of date advice.
I found and then tried your solution and it worked, first time on all three PC’s.
I downloaded the two KB updates (Select the ‘IT professionals’ link and then the correct link for the IE/OS in use).
I installed KB2879017 (without resetting) and then KB2870699, then reset the computer.
Then restarted the Autoupdate service and all was well, with CPU usage at it usual low levels.
I then updated the OS, as per normal.
Many thanks dose for your excellent work in discovering how to fix this problem.
Spoke a bit too soon …. Tuesday the 12th November 2013 updates once again broke wuauclt.
Again all three PC’s (Single Core, XP SP3, IE6, Update setting – Notify before download) After an update notification, again had wuauclt, causing svchost to run the CPU at 100%. Curious, how machines of the same spec., are being significantly effected by the update notification only – assuming m$ haven’t updated something against the users wishes.
However, the answer was in the update notification – KB2888505 an update to IE, which, says it replaces KB2879017. Downloading this update separately and installing manually. Rebooting, restarting the update service, brought the machines back to normal.
Trackbacks