bcastner
Premium,VIP,MVM
join:2002-09-25
Chevy Chase, MD
clubs: 
 ·Verizon Online DSL
| reply to fahrenheit
Re: [XP Pro] Wuaueng.dll / Svchost.exe 100% Usage Problem.
Part of the problem is that the servers at Microsoft are incredibly busy at the moment.
If using Microsoft Update and not the older Windows Update, flip back temporarily. The Windows Updates Servers are less stessed at the moment.
================================
I note too that there is a published workaround if you are using CA Antivirus. The SVCHOST issue is related only to those using this software. The workaround from CA:
quote:
1. "Open Security Center"
2. "Open Advance Settings"
3. Clicked on the "Options" button
4. Clicked on the "Modify" link under the Exclusions list and then "Added" *.msi and *.msp to the list and clicked OK
Discussion of the CA Antivirus SVCHOST issue: »www.villagegeek.com/
--
============
MS-MVP 2004 - -2008, ASAP Member
Users Helping Users
|
|
paradigm
@net.uk
| reply to Apophis
It has nothing to do with wether or not you use Windows Update or Microsoft Update servers.
I'm behind a WSUS (3.0) server, and get the same wuaueng.dll issue.
It's happening across 4 PC's here now in the office, all 4 PC's only talk to the WSUS server. |
|
bcastner
Premium,VIP,MVM
join:2002-09-25
Chevy Chase, MD
clubs:
·Verizon Online DSL
| You misunderstood what I wrote.
In some cases the issue can be traced to busy servers. However, the "fix" suggested earlier above will likely resolve the issue in any case.
The "Fix":
From a command session, type carefully:
net stop wuauserv
rmdir c:\windows\softwaredistribution /s
net start wuauserv
You need to stop the wuauserv service (if running) to clear the softwaredistribution folder.
--
============
MS-MVP 2004 - -2008, ASAP Member
Users Helping Users
|
|
jtraynor
Loosemoose
Premium
join:2002-10-28
Carefree, AZ
1 edit | Most of these SVCHOST/wuaueng.dll problems involved both Microsoft and CA Antivirus software. Other A/V vendors may be involved, but the most prominent was CA. A temporary circumvention was to exclude .msp and .msi files from the real-time scanner - not a great solution, but it worked for many people. CA indicated the issue surfaced with engine V31.4, and a little over a week ago they released engine V31.5. The new engine seemed to resolve most of these issues. [Remove the exclusions!]
In a few isolated cases [no CA installed, or the new CA engine in place] the problem persisted. In these cases, stopping the Automatic Update service, then deleting the C:\Windows\SoftwareDistribution folder, followed by a reboot, did the trick. There may be other unique situations, but the corrections noted above resolved the predominant cases.
 |
|
Camborita
@qwest.net
| reply to paradigm
Check out this blog. It has a more detailed solution than the simple "fix" suggested earlier:
»www.stuckiniowa.com/svchostexe-1···log-257/ |
|
bcastner
Premium,VIP,MVM
join:2002-09-25
Chevy Chase, MD
clubs:
1 edit | Your detailed fix is longer than mine, but does the same thing at its core. The DLL registration is completely off-task and unrelated material for the issue being discussed in this thread.
Longer is not better, just longer. |
|
workablob
join:2004-06-09
Houston, TX
 ·Comcast
| reply to Apophis
I have been all over this particular issue and after more than a year and false hopes I disabled Automatic Updates service in the services applet.
I periodically update my Ghost image with new patches but then I also use Disk Protection in SteadyState so if I have any bad stuff get in due to a missing patch I get a new system when I reboot.
$.02
David |
|
