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/WindowsUpdateAgent30-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
From: Thane Sherrington <[EMAIL PROTECTED]>
Reply-To: The Hardware List <[email protected]>
To: The Hardware List <[email protected]>
Subject: RE: [H] SVCHost survey
Date: Wed, 09 May 2007 10:43:11 -0300
At 10:37 AM 09/05/2007, Hayes Elkins wrote:
svchost is just a process that other services, including third party
drivers, utilize, it is in itself typically not the culprit when things go
crazy. HP printer driver software for instance, which is PURE GARBAGE,
will certainly cause svchost to exhibit that behavior. I've seen it myself
with their HP update component.
I would try looking at sysinternals' (now owned by MS) Process Explorer to
see what really is driving those out of place svchost threads.
On everyone of the machines I'm dealing with, it's Microsoft Update. I
know the cause - I just want a baseline so I can see when a machine is
fixed and when it isn't.
T
_________________________________________________________________
Like the way Microsoft Office Outlook works? Youll love Windows Live
Hotmail.
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_outlook_0507
