After I log in, my system slows to a crawl. Looking at task manager I see that my computer is experiencing high CPU usage. Looking more closely I see that something called “svchost” is taking 100% of my CPU time. If I kill the process suddenly other things stop working. Is svchost a virus? How do I fix this svchost problem?
That’s actually a composite question based on several reports I’ve been getting recently.
Svchost, or more correctly “Service Host”, is a program that is designed to run other programs and “hosts” many of the system services in Windows XP. Several copies of Svchost run more than one service, which is why when you kill an instance of svchost several things on your machine might stop working.
So why is one of the Svchosts taking all your CPU?
And what can you do about it?
From what I’ve heard and have been able to tell, this is nothing more than a bug. A serious and annoying bug, but a bug nonetheless.
The bug appears to be related to the Windows Update service – the service that you’re supposed to keep running at all times so that updates will be automatically downloaded to your machine.
You can see that this copy of svchost on my machine is running not only The Windows Update service, but is actually running 29 services all totaled. So if you were to kill this instance of svchost you’d be killing all of those services and many features and functionality of your system would fail.
One Temporary Solution
One approach to this problem is to stop and then disable the Windows Automatic Update service. If you have it open in Process Explorer, as shown above, with Automatic Updates selected in the list, then just click the Stop button. If your CPU usage then drops to more normal levels, you’ve identified the problem.
To prevent the Automatic Update service from starting again, right click on My Computer and click on Manage. Expand Services and Applications, and then underneath that click on Services. In the resulting list on the right, locate Automatic Updates:
Right click on Automatic Updates and click on Properties. Change the Startup type to Disabled:
(You can also click Stop here if you didn’t stop the service earlier.)
Click OK and Automatic Update service should be disabled.
IMPORTANT: since you won’t be getting updates automatically, you should now plan on visiting the Windows Update web site periodically to make sure you keep your Windows up to date. As we’ll see shortly, this will also become important to resolve this problem “for real”.
Another Temporary Solution
Folks commenting on a previous svchost article have reported success by removing and reinstalling Windows Update.
I haven’t tried this solution since I’ve not experienced the problem, but as I said, several folks are reporting good results.
A Permanent Solution?
There isn’t a permanent solution. Not yet anyway.
There are rumors that Microsoft actually has a fix, but that you need to call up and ask for it rather than getting it through normal channels. I’m not convinced that this fix is actually for this specific problem that so many people are experiencing.
There are also rumors that Microsoft will be making the actual fix available in a future automatic update. Ironic, since it’s automatic update that you may have turned off in order to work around the problem. That’s why I recommend making certain you regularly visit Windows Update and take the latest fixes to keep your system up to date, not only for this issue but for any other issues that may crop up over time.
Also, remember, once the problem is fixed, be sure to re-enable the Automatic Updates feature. It remains an important part of keeping your system safe and up to date.
I woke to find this automatic update waiting to be installed on my machine this morning:
This is the update that’s been frequently referenced as a resolution for this problem.
It’s possible, perhaps even likely, that this issue will now get put to bed. It’s your choice at this point: you should be able to visit Windows Update to take the fix, enabling Automatic Updates again should get the fix downloaded, or you can visit the knowledgebase article to get the fix.