This is in Brian Livingston's newsletter:
Finally, a real 'svchost.exe' fix 

For those of you who've suffered from svchost.exe, which is used by
Microsoft Update, going wild and taking 100% of your workstation's CPU
resources, help is at hand.

Redmond plans to offer up some long-awaited patches to updaters in the
foreseeable future. But you can get the needed fixes to solve this problem
and get your computer back now — without having to disable Microsoft Update
and reverting back to Windows Update, or disabling Automatic Updates
altogether.

The fix is two-fold. Both of the following patches are needed to fix the
issue:

• Step 1: KB 927891. Download the fix from Knowledge Base article 927891
(this link is for Windows XP machines) and install it first.

• Step 2: WSUS 3.0 client. Next, install the WSUS 3.0 client update. An MSDN
article on this update is available in Microsoft's MSDN library. A link to
the executable is contained near the very bottom of that article, or you can
download the executable using this link. (There is no easy download page at
Microsoft yet, because this fix has just come out.)

You need this download to install the new Automatic Updates program, which
is technically the new WSUS 3.0 client. Even though you may not be using
Windows Software Update Services, this download provides you with the new
engine that's used by workstations that run Microsoft Update.

You may still see your system spike up to 100% CPU usage every now and then.
But we should soon get from Microsoft the much needed, permanent fix to this
very vexing issue, which many of us have been fighting for months. The
promised patches will be deployed to all customers in the coming months, as
discussed in the official WSUS blog.

These are the links embedded:
<http://www.microsoft.com/downloads/details.aspx?familyid=7A81B0CD-A0B9-497E
-8A89-404327772E5A&displaylang=en>
MSDN article: http://msdn2.microsoft.com/en-us/library/aa387285.aspx



Mark

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thane Sherrington
Sent: Thursday, May 10, 2007 11:13 AM
To: The Hardware List
Subject: RE: [H] SVCHost survey

At 12:22 PM 09/05/2007, Hayes Elkins wrote:
>That it is most likely wuauclt that is the culprit.
>
>Try updating the WU update agent to v3.0
>
>http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/Window
sUpdateAgent30-x86.exe
>I've read of good results from a thread here @ arstechnica and there 
>are other interesting suggestions to try as well (no need to read 
>the previous 6 pages): 
>http://episteme.arstechnica.com/eve/forums/a/tpc/f/12009443/m/786004271831/
p/7

This sometimes works, but switching to Windows Update seems to work 
all the time.

T 

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.467 / Virus Database: 269.6.6/795 - Release Date: 5/9/2007 3:07
PM
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.467 / Virus Database: 269.6.6/795 - Release Date: 5/9/2007 3:07
PM
 


Reply via email to