Windows Update / SvcHost.exe 100% Cpu in task manager

When the updates began streaming for me last month it was the same, like the floodgates were opened and the files were streaming at a blur of speed on parallel paths through both the automatic updates silent channel where the tray icon was showing updates ready to install, and also got the more than 125 updates through the open browser at Microsoft Update.  It ran amazingly fast when the files began streaming.  I remember chuckling for thinking at the time there wasn't much sharing of bandwidth for the few people who were getting any downloads from Windows Update. 

30% of the computers on earth are running Windows XP and it is embedded in some equipment that can't be just "upgraded" in an unplanned sudden OS transition......so it is a huge problem.  I have 3 new desktops sitting in crates nearby with Windows 7 and 2 more machines still on XP to be upgraded, so this issue is more psychological aggravation than "mission critical" for me.  Windows XP at the IE7 level was always rock stable and desktops would be left on 24/7 sometimes 2 months without a maintenance cycle and a reboot.  Behind a firewall zero viruses or exploits in 10 years, you can't do better than 100% rock solid secure. The only issues I ever had were hardware issues like drive failures and power supplies or a memory stick or motherboard or video card, probably due to thunderstorm and lightning caused line surges that got through the surge protectors.  XP SP3 has been every bit as much of a truly outstanding operating system as has IE8 been a real stinker as a crippled bloated toolbar "browser" too soon incompatible with most websites.  The idea of a web browser is ability to view and interact with most websites. So what is the real purpose for IE8 ?  Did IE8 ever really do that well except for a short time?  What ever was the true purpose for IE8 ?

Firefox exposes what Microsoft did to XP crippling XP functionality via IE8.  Many websites will not even function when attempted to be viewed using IE8 so for that to be the case then de facto support for XP was already effectively ended with IE8.  Microsoft will not openly declare that support for XP has already ended, but will gradually make it impossible to use XP so that the clingers on gradually figure it out themselves that XP has been obsoleted and how it was done was through the browser IE8.  Any supported Microsoft OS will or should always have a supported Internet Explorer to go with it and should have a reliable e-mail client also, not just a Web Mail, but an actual standalone e-mail client with local storage like the old Outlook Express or Windows Live Mail.  If not, then MS should include Office Outlook with the OS.

Gentlemen - OUTSTANDING, absolutely Outstanding!!!

The recommendations by Xircal apparently worked as I did nothing else!

However - allow a bit of guidance... I nearly chose NOT to apply the routine as I am very big on interpretations of English though I do not declare myself to be a major at English. A single word changes the meaning of a sentence.

**It read : '**Does svchost still consume 100% CPU cycles? If it does, do the following.'

Since my CPU was not at 100% - I interpreted it to read - then the routine is not necessary!

But like a science fiction movie or recalls from the past - when you want to get something stubborn to work - you 'hit it on the side'! I looked upon the recommended routine as  - a hit it on the side remedy.

Nothing changed with RUN with the items stated YET I would NOT discount this as a part of the formula for the remedy.

Windows update began to show signs of coming back to life - but the initial two updates: the update to windows update itself and the GWA Tool failed twice to install - the error code is all about BITS not working.

Went back to BITS - it was STOPPED - changed it to STARTED without restarting the computer as I suspected it may go back to STOP which I did note does exactly that. If BITS is supposed to 'turn on' when a process requires it but it fails to do so - this is now on record here!

Windows update while active in processes (not during an attempt to download updates) did NOT go beyond 4% of CPU at any time AFTER the routine was applied!

Went back (after starting BITS) and activated Windows update - and had 127 updates downloaded and installed in 26 minutes!!!!!!!!!!!!!! With CPU usage during the download/install process at 8-72% mostly in the lower (30%) range!!!

Thank you - so much!

Have a Great Thanksgiving a Joyous Holiday Season to You and your Family(s)

Been reading of the plight of so many for so long - I hope this remedy can be prominently displayed/posted for Folks to easily find.

The CPU spike is still going to occur at Windows Update and it will occur whether automatic updates is on or off, but the difference is that when BITS is running and working the CPU spike will be a transient event lasting only a brief time while the needed updates list compiler is running and the CPU load will then decrease to a more normal loaded range instead of hanging there at 100% for hours to test your CPU heatsink and maybe fry the core.

BTW I have both SP2 and SP3 install disks and have tried both and no activation or WGA issues seem to be related to the cluster eff people are experiencing with Windows Update and the trashed BITS functionality.  The cumulative security updates to IE are the suspect number 1, since just installing that as a standalone update done offline seems to fix most peoples problem with the endlessly spiking CPU at windows update.  That holds for the automatic and the manual use of the site.

Format drive then OS, then system drivers then OSSP2 then OSSP3 during this have nonessential devices unplugged such as audio - just video and keyboard/mouse. May also be advisable to disconnect other hard drives as during install may go to a D drive instead of the C drive.

Before clicking next to install SP2 and also SP3 - take note that there is a lot of hard drive activity indicated by the yellow light - this is large files being unzipped. It is a good idea to WAIT until the light goes out - about 60 seconds then click next - it relieves the pressure and assures a stable install.

Do not ACTIVATE windows until you have installed all other hardware along with its drivers (get latest drivers from device sites as drivers on discs may be outdated). If you activate windows prematurely - windows will think it is a different computer - grief WILL follow!

It is far in the past when an operating system was assigned only to a motherboard!