MS Updates problem

abibee

I have an XP Windows Update issue (after Google'ing this), whereby when Windows checks for updates, svchost.exe uses 100% of the CPU for about 10-15 minutes. I disabled a setting and that worked for a wee while, but the problem came back, and now the only solution I have is to totally disable Auto updates.
When I then manually check for updates, the CPU goes back to 100% and everything comes to a halt again.
Now... how can I get any future critical updates? I feel I'm pretty snookered. I don't want to have to do a full re-install of Windows, I shudder at the thought. My Google'ing hasn't found any resolution. Is this the last push I need to switch to https://www.linuxliteos.com/
Anyone know of a fix for this issue?

somersethillbilly

Exactly the same situation here, XP SP3. The only workaround seems to to disable Auto Updates in services, the culprit is wuauserv. svchost peaks at 100% CPU and leaves the machine all but useless.

This has happened before, microsoft issued a fix for it, 2007 ish IIRC....Hoping that they will address this issue, conspiracy theorist may suggest it's an attempt to speed up migration away from XP.

Sooler

kill off the spoolsv.exe process

Task manager - Processes - spoolsv.exe

http://answers.microsoft.com/en-us/o...7-7303ddc4dcdf

All I had to do to fix this was run Task Manager, click the "Show processes from all users" icon, and end the "spoolsv.exe" process. Have Windows Update running so you can install the update as soon as you close the "spoolsv.exe", because this service will automatically restart itself in a short time.

Coveredinbees!!!!

I had the same thing but now it's downloading an update it seems to be happy, see what happens when it's done.


It seems to be a big update.


It's OK again now it's done the update.

danthemoneysavingman

I looked into this for a friend, it was not windows updates causing the issue but microsoft updates (e.g. for MS Office products) - you can turn this off and it solves the problem - AFAIK.

This article may help: http://support.microsoft.com/kb/901037

Then again it might not! But I hope so.

spenderdave

This issue seems caused by a rogue update to IE a couple of months ago. After disabling automatic updates (so you can use your machine) download the latest IE cumulative update from MS (https://technet.microsoft.com/en-us/security/bulletin/ms13-080) and install it. You should then find the problem cured and you can do the other updates via Windows Update per normal. Just done this on my XP machine and it fixed it.