I have not been able to have the November MS updates finish, been doing this for several days, on and off ... computer is running Fast and HOT and never finishes. I wanted just to check what updates were released for XP. I just found this article a few minutes ago about an XP update problem for November.
Windows XP update locks machines with SVCHOST redlined at 100%: Fix it with KB 2879017.
Bug returns with recent patches in Windows XP's Windows Update processing, as SVCHOST pegs 100% CPU utilization.
By Woody Leonhard @InfoWorld on Nov 13, 2013
It isn't a new bug, but it's a killer, and this month's round of Automatic Updates has brought it back with a vengeance. Freshly installed Windows XP SP3 machines running Windows Update -- typically because Automatic Update is turned on -- will stall twice. First, when Windows Update accesses the Microsoft website to gather a list of available updates, the machine can lock up for five, 10, 15 minutes -- or more -- with the CPU and fan running at 100 percent. Then, if the customer waits long enough for the updates to appear, and clicks to install them, the XP machine goes racing away again for five or 10 or more minutes, with the CPU redlined at 100 percent.
If you've turned on Windows Automatic Update, your brand-new WinXP SP3 installation may just sit there and churn and churn.
Microsoft has known about the problem for months -- probably years -- but it hasn't fixed it. I first saw the problem described in a TechNet post for the June 2013 Black Tuesday patches. In September, reader warwagon on the Neowin support forum described the same problem -- and drew more than 100 comments, many of which repeated the same story. Jeff Duntemann talked about the problem in October -- and he traces its origins back to 2004. Now the November 2013 Black Tuesday patches are bringing back the same litany, and Microsoft hasn't made any moves to fix it.
The source of the problem isn't hard to track down. In every instance I've seen, wuauclt.exe -- the Windows Update Agent -- running in a SVCHOST wrapper takes over the machine. Clearly, there's a bug in wuauclt running on Windows XP and/or a bug in the way Microsoft's servers handle wuauclt on XP. Whether Microsoft will ever deign to fix it remains a sore point.
Some people advise that you turn off Automatic Update -- I do, too, for reasons painfully obvious in the 17 epic Windows Auto Update meltdowns slideshow -- but turning off Automatic Update doesn't solve the problem. As soon as you venture into Windows Update manually on a fresh Windows XP SP3 machine, the problem comes back.
The best solution appears to be a manual update to Internet Explorer. Yes, Microsoft has messed up wuauclt.exe so badly that it has to be repaired by installing an IE update -- not a Windows update -- to get it working properly. The fix is part of the October cumulative IE patch known as MS13-080/ KB2879017. If you manually download and install the October cumulative patch, then you should be able to use Windows Update with no problems.
Operative term: "should."
The precise download location varies depending on which version of IE you're using. For IE6 go here. IE7 is here. And IE8 is here.
You would think that simply upgrading to the latest version of IE would solve the problem, but it doesn't. You have to manually download and apply the patch for your version of IE.
Will Microsoft go in and fix wuauclt.exe -- or, better, fix whatever is broken in its back-end processing -- before Windows XP turns belly up next year? I wouldn't bet on it.
so there, so much for MS and the November updates ... anyone else notice this?
additional ... I only do manual updating, I get the list of updates needed and then download them to keep in a folder to burn to a CD, I install them myself, nothing actually installed by M$ ... I put the IE 8 update from October back on (as mentioned in the article) and nothing is fixed ... computer is still running very HOT and going nowhere. Thanks again to M$ for a great product, like they care! I have the updates installed through Oct 2013 and things are working good so no more crap updates for me till April / May of next year. I have been putting them on every 2 or 3 months and then doing an image backup for that stage. It's just not worth it, possibly destroying a good working XP setup in these "final days". Does M$ care, probably not at this point but I will attempt to put all final updates on in May of next year ... this frustration is too much !!!
Edited by duffy98, 17 November 2013 - 05:46 AM.
Added quote tags and missing links to the ginormous unmarked literal quote...