WIN XP SP3, MS update and computer stuck at svchost at 100 % CPU

This thread now has over 11,000 views!!

Now that is impressive - there must still be a large number of XP users roaming these forums.

 

Doug, I just linked to this thread on another forum a moment or two ago.
No reason why we shouldn't try to help out any other poor sods that have suffered the same frustration as many of us here.

 

Microsoft thanks those that have been providing feedback on this issue, however - there is no fix at this time. When there is - it will be made widely available to those affected.

 

Doug Neal Microsoft Update (MU)

 

What's the point fixing it so close to EOL?

 

If this is a pirated/cracked version of Window XP SP3, I wouldn't trust it. It could contain backdoors written by black hat hackers, who'll steal your valuable personal info. I say it is best to buy a new operating system than torrent it for free.

 

I wonder how much of the thread that you did read?

 

What happens after Windows XP expires.

http://blogs.windows.com/windows/b/...now-support-for-windows-xp-ends-now-what.aspx

 

One NEW complication I have identified - and reported to Microsoft Tech Support
- is that one of the MS-Fix-It's that XP users are running (to try and fix Windows Update) is actually making the problem worse.

The Fix-It runs from KB971058 and is titled "How do I reset Windows Update components"
and breaks BITS (Background Intelligent Transfer Service) - and without this service Windows Update will not run.

The BITS registry is modified with Win7 / Vista format entries that are incompatible with XP
- the service gets renamed as "@%SystemRoot%\\system32\\qmgr.dll,-1000"
- plus a few other registry changes that disable the service.

Other Fix-It's for XP coded by the same idiot at MS may also exist.
So not only do you have to understand the SVCHOST problem
- but also work out how to fix the BITS registry!
Do an immediate System Restore is the only easy answer.

Happy Xmas All

 

The described MS FixIt does not address this issue.
MS will have one forthcoming shortly.
[not -http://support.microsoft.com/kb/971058-]

 

I didn't say that MS-Fix-It was supposed to fix the SVCHOST overload issue.

I said people were using it to try and fix Windows Update - which is what it is designed to do
- and ending up breaking the BITS registry because the Fix-It has a coding bug.

 

One reason would be to prevent a class action suit against MS for having broken many people's computers and then intentionally leaving them that way.

Second would be that other MS products use the Windows/Microsoft updates (think Office, MS Security Essentials, etc.), thus it's not just updates for the XP OS.

 

Well don't disable svchost, as it will need outbound access to receive Windows Updates. I've noticed WU activity on XP has been acting funny too the past couple months now. I think they're trying to encourage/nudge people to upgrade to newer OS's. And that's shady... they should honor the date they set and keep things running smooth until then.

I recently reformatted a friends PC and found out that manually getting updates wasn't working. After looking around I found a "Fix it", but I'm glad I looked further and saw a guy mention that the only thing the Fix it did was enable Automatic Updating, which I never use and always get updates manually. So I turned on automatic updating, the top option to download them automatically and install at a set time (Default: 3am)... and viola, it worked then.

So you may want to try that if you're trying to get the updates manually. After getting the first few rounds of updates it did then allow me to disable auto updating and get them manually now.

 

Did you actually read ANY of this thread?

The current SVCHOST 100% bug affects the Updates Service (WUA)
- which is used by BOTH the Automatic Updates and the Manual Windows Update options.
So it matters not - by which route you try and get your updates - the bug will get you either way.

If you have a fast multi-core CPU with plenty of RAM you may be able to just leave it searching for updates - and it will get there within 30 minutes - for slower single-core computers you need to apply the LATEST "Cumulative Security Update for Internet Explorer" or you may be stuck for 6 hours plus.

 

As was posted previously, Microsoft are patently aware of the issue and are working on a permanent fix.

Presently there are none.

Disabling Services, MSCONFIG, items, etc - will only complicate and already complex problem.

 

I came across a thread where a couple of posters claimed that manually installing the latest cumulative security update for IE resolves the problem, at least on fresh installs.
http://www.dslreports.com/forum/r28896358-Windows-XP-Always-telephone-activation-now-also-Slow-updates-

 

I think this thread is getting too long - if you just want the solution to the SVCHOST CPU overload issue
see this post from page 2 - https://www.wilderssecurity.com/showpost.php?p=2315886&postcount=50

The solutions started to appear on page 2 and developed over page 3 - go check it out if you want to understand the whole story.

 

Doug, regardless of the failure of some others to read or appreciate the info you've provided in this thread, (which, by the way, worked like a charm for me), I will always be grateful that you took the time to post it here.

 

So far disabling was the only option I've seen. Several experiences and nothing to date except for disabling which works.

 

Doug,

Thank you!

===

In case the January 2014 Patch Tuesday has again this issue and there may be another Cumulative Update for IE on XP, maybe you (or someone else) would be so kind to give the direct downloads then, if needed.
Thanks in advance!

 

Which or what exact items are you disabling ? The MS Product Team would probably want to know. There is no official fix as of yet.

 

It is simple...

 

Not that I would condone disabling the automatic service as it may hinder how Microsoft delivers software updates to your PC.

 

Look at that, today's update went smoothly without issues. Maybe because there are no Internet Explorer patches.