SVCHOST Performance Problems
Jeff Guillet
environment. All workstation clients are Windows XP SP2. We've been living
with the 100% CPU utilization issue that occurs when clients perform update
detection with the WSUS server(s).
I was happy to read the article, "Update on svchost/msi performance issue
and 3.0 Client distribution plan" on the WSUS 3.0 blog
(http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx) and was
hopeful that it would resolve this issue, but the problem remains.
I have a test machine where I first installed KB927891 and then updated the
WSUS agent software using WindowsUpdateAgent20-x86.exe. Both wuaueng.dll and
wuauclt.exe are now version 5.8.0.2694. I continue to see 100% CPU
utilization for about 90 seconds after I run WUAUCLT /DETECTNOW, where
SVCHOST.EXE runs between 65-98%. During this time, the computer is
unresponsive.
I've been told by Sudheer [MSFT] that the fix does not require a WSUS 3.0
back end to work properly. He suggested posting my issue here. Any advice
please? Why are we continuing to have this issue?
Matt
> I have a test machine where I first installed KB927891 and then updated the
> WSUS agent software using WindowsUpdateAgent20-x86.exe. Both wuaueng.dll and
> wuauclt.exe are now version 5.8.0.2694. I continue to see 100% CPU
> utilization for about 90 seconds after I run WUAUCLT /DETECTNOW, where
> SVCHOST.EXE runs between 65-98%. During this time, the computer is
> unresponsive.
Wrong version of the WSUS agent software. You want to download and
install this file - WindowsUpdateAgent30-x86.exe.
Eric
http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe
"Jeff Guillet" <JeffG...@discussions.microsoft.com> wrote in message
news:13891ACA-A133-48FF...@microsoft.com...
Ken
about the issue again - See my post 4 down "Anyone Else Having These Issues
etc "
I just found out about the upcoming May 22 updates and I am sorry to hear
that your manual attempt to resolve the issue is not working -
This is real nuisance, I am assuming all 10,000 of your systems are not
affected right, it's seem so random with our systems -
Sudheer GN [MSFT]
The link for WSUS 3.0 client for x86 platform is
http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe
After installing, the version of wuaueng.dll should be 7.0.6000.374
--
Sudheer GN
Microsoft, WU Client
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <ws...@brechin.org> wrote in message
news:OJB%23%23FmjH...@TK2MSFTNGP02.phx.gbl...
Jeff Guillet
Jeff Guillet
I installed the WSUS 3.0 client for x86 platform and it does seem to have
fixed the problem. The SVCHOST process still runs hot and the total CPU
utilization still is at 100%, BUT the system is still reponsive. It's a
little sluggish, but at least it works. The total detection time is the same
(~90 seconds). It looks as though the SVCHOST process throttles back
automatically to accomodate other processes to run. I need to do more
testing with other clients. I'll also do some more analysis with Process
Explorer, but it looks real good so far.
Great job, guys and gals!
Jeff
Eric
worked (still pegged CPU), but then I noticed how the PC's were still very
responsive while detection was running, in comparison to how they used to be
(unbearably slow).
"Jeff Guillet" <JeffG...@discussions.microsoft.com> wrote in message
news:0EF6532F-4992-4895...@microsoft.com...
Sudheer GN [MSFT]
The biggest difference in WSUS 3.0 client (wrt performance) is that the
machines will still be responsive when WU client scans for updates. There
are also some optimization to reduce the number of update evaluations and
that will reduce the scan time in some scenarios.
It is still expected that CPU usage will be high so that the scan can
complete in lesser amount of time. But other applications can be launched
and used (they will still be a little sluggish because CPU is being shared
with WU client)
--
Sudheer GN
Microsoft, WU Client
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Eric" <you...@hotmail.com> wrote in message
news:eQY3Msm...@TK2MSFTNGP02.phx.gbl...
craig.morrison
I'm currently having the same CPU utilization problems while using the
latest version of SMS, and am now contemplating a WSUS install.
I have 2 questions though.
1) Will the files updated by WindowsUpdateAgent30-x86.exe work with
WSIS 2.0
2) Will the updated files help out SMS, and make it unnecessary to
install WSUS?
Thanks, any help would be appreciated.
Jeff
to "slip in between" the update process?
Jessica
went to Microsoft's site and manually did the updates, then restart when it
asks. My CPU performance dropped and I haven't had a problem since and those
computers are reporting fine now to WSUS. Makes me think that WSUS was
hanging an update.
Sudheer GN [MSFT]
then it will still continue to work with WSUS 2.0.
It should also work in SMS environment and remove the UI responsiveness
issue. (There will still be high CPU usage when the scan runs)
--
Sudheer GN
Microsoft, WU Client
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"craig.morrison" <cra...@canada.com> wrote in message
news:1178303038.1...@e65g2000hsc.googlegroups.com...
alle...@gmail.com
So from reading the newsgroups, this is the summary right?
1) install the hotfix 927891
2) install the WUA agent 3.0
3) upgrade the Server to 3.0 (is this optional) or can we leave it at
2.0 SP1?
For the Hotfix:
** can that be applied to machines "not" affected?
We aren't sure who's really affected as our user base is 3,000, and
I'd like to push the hotfix via SMS to XP machines to make things
simpler.
Any harm in doing that?
thanks
Allen
On May 4, 10:17 am, "Sudheer GN [MSFT]"
<sudh...@online.microsoft.com> wrote:
> Hi,
> The biggest difference in WSUS 3.0 client (wrt performance) is that the
> machines will still be responsive when WU client scans for updates. There
> are also some optimization to reduce the number of update evaluations and
> that will reduce the scan time in some scenarios.
> It is still expected thatCPUusage will be high so that the scan can
> complete in lesser amount of time. But other applications can be launched
> and used (they will still be a little sluggish becauseCPUis being shared
> with WU client)
>
> --
> Sudheer GN
> Microsoft, WU Client
>
> This posting is provided "As Is" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified athttp://www.microsoft.com/info/cpyright.htm
>
> "Eric" <youn...@hotmail.com> wrote in message
>
> news:eQY3Msm...@TK2MSFTNGP02.phx.gbl...
>
>
>
> > This is what we noticed also. At first, I didn't think the new WSUS
> > client worked (still peggedCPU), but then I noticed how the PC's were
> > still very responsive while detection was running, in comparison to how
> > they used to be (unbearably slow).
>
> > "Jeff Guillet" <JeffGuil...@discussions.microsoft.com> wrote in message
> >news:0EF6532F-4992-4895...@microsoft.com...
> >> SUCCESS!!!
>
> >> I installed the WSUS 3.0 client for x86 platform and it does seem to have
> >> fixed the problem. TheSVCHOSTprocess still runs hot and the totalCPU
> >> utilization still is at 100%, BUT the system is still reponsive. It's a
> >> little sluggish, but at least it works. The total detection time is the
> >> same
> >> (~90 seconds). It looks as though theSVCHOSTprocess throttles back
> >> automatically to accomodate other processes to run. I need to do more
> >> testing with other clients. I'll also do some more analysis with Process
> >> Explorer, but it looks real good so far.
>
> >> Great job, guys and gals!
>
> >> Jeff
>
> >> "Jeff Guillet" wrote:
>
> >>> Excellent information. I'm trying it now and will post back. Stay
> >>> tuned...
>
> >>> "Sudheer GN [MSFT]" wrote:
>
> >>> > Hi Jeff,
> >>> > The link for WSUS 3.0 client for x86 platform is
> >>> >http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/...
>
> >>> > After installing, the version of wuaueng.dll should be 7.0.6000.374
>
> >>> > --
> >>> > Sudheer GN
> >>> > Microsoft, WU Client
>
> >>> > This posting is provided "As Is" with no warranties, and confers no
> >>> > rights.
> >>> > Use of included script samples are subject to the terms specified at
> >>> >http://www.microsoft.com/info/cpyright.htm
>
> >>> > "Matt" <w...@brechin.org> wrote in message
> >>> >news:OJB%23%23FmjH...@TK2MSFTNGP02.phx.gbl...
>
> >>> > >> I have a test machine where I first installed KB927891 and then
> >>> > >> updated
> >>> > >> the WSUS agent software using WindowsUpdateAgent20-x86.exe. Both
> >>> > >> wuaueng.dll and wuauclt.exe are now version 5.8.0.2694. I continue
> >>> > >> to
> >>> > >> see 100%CPUutilization for about 90 seconds after I run WUAUCLT
> >>> > >> /DETECTNOW, whereSVCHOST.EXE runs between 65-98%. During this
> >>> > >> time, the
> >>> > >> computer is unresponsive.
>
> >>> > > Wrong version of the WSUS agent software. You want to download and
> >>> > > install
> >>> > > this file - WindowsUpdateAgent30-x86.exe.- Hide quoted text -
>
> - Show quoted text -
Sudheer GN [MSFT]
My advise is to just install WUA agent 3.0 for now. That should eliminate
the UI responsiveness issue.
KB927891 is intended to resolve memory leak and crashes, but only affect
some scenarios.
KB927891 hasn't been released to WU yet, and hence it is not advisable to
install on all machines.
--
Sudheer GN
Microsoft, WU Client
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<alle...@gmail.com> wrote in message
news:1178348068.6...@l77g2000hsb.googlegroups.com...
Sudheer GN [MSFT]
At a high level, the change was to make WU scans run in threads that are
different than that handles UI interactions in Windows explorer.
--
Sudheer GN
Microsoft, WU Client
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Jeff" <Je...@discussions.microsoft.com> wrote in message
news:CC8CDC23-9C5A-4603...@microsoft.com...
craig.morrison
wrote:
> If WU client is upgraded to 3.0 by installing WindowsUpdateAgent30-x86.exe,
> then it will still continue to work with WSUS 2.0.
> It should also work in SMS environment and remove the UI responsiveness
> issue. (There will still be high CPU usage when the scan runs)
>
> --
> Sudheer GN
> Microsoft, WU Client
>
> This posting is provided "As Is" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified athttp://www.microsoft.com/info/cpyright.htm
>
>
> - Show quoted text -
Hi, sorry, if everyone using WSUS and/or SMS is being killed by high
CPU usage during scanning for updates, and WindowsUpdateAgent30-
x86.exe is the answer, why isn't this front page news?
Why am I having to ferret out this incredibly important information?
Craig
Ken
highly noted. We have Engineering workstations that were useless when
this happened it caused a lot of problem and complaints, since it always
followed the latest update deployment .
NZSchoolTech
> SUCCESS!!!
>
> I installed the WSUS 3.0 client for x86 platform and it does seem to have
> fixed the problem. The SVCHOST process still runs hot and the total CPU
> utilization still is at 100%, BUT the system is still reponsive. It's a
> little sluggish, but at least it works. The total detection time is the same
> (~90 seconds). It looks as though the SVCHOST process throttles back
> automatically to accomodate other processes to run. I need to do more
> testing with other clients. I'll also do some more analysis with Process
> Explorer, but it looks real good so far.
>
I did this on one laptop, it failed installing the V3 update client.
After this the PC stopped working normally. Had to roll back the KB
patch install to get the PC working again.
On another machine that it installed properly on, the machine is now
100% working properly.
NZSchoolTech
> Hi,
> My advise is to just install WUA agent 3.0 for now. That should eliminate
> the UI responsiveness issue.
> KB927891 is intended to resolve memory leak and crashes, but only affect
> some scenarios.
> KB927891 hasn't been released to WU yet, and hence it is not advisable to
> install on all machines.
>
I installed both updates, KB927891 then WUA agent 3.0 but WUA update
failed with an error and the PC stopped working normally after that.
I rolled back to pre KB927891 using system restore then tried WUA agent
3.0 again, this time the PC is working. (But just to be sure I have
manually created a restore point before installing WUA Agent 3.0)
Tom S.
"Sudheer GN [MSFT]" wrote:
> Hi Jeff,
> At a high level, the change was to make WU scans run in threads that are
> different than that handles UI interactions in Windows explorer.
>
If splitting the work into UI and other threads was the biggest thing, then
Run, Don't walk over to Mark Russinovich and get his insights on the design
for Client 3.1. He works for MS now as a Technical Fellow (?) and has been
pounding the issue of doing blocking tasks in UI threads for years. I'm sure
the team and we users will benefit and we might just avoid another one of
these messes.
Respectfully,
TS