WUAUCLT.exe and svchost.exe are maxing my processor on startup - h

Discussion in 'Update Services' started by Gordon, May 9, 2007.

  1. Gordon

    Gordon Guest

    I found this entry on Exchange Experts web site but couldnt see any
    resolution. My problem is identical.

    Summary:

    SVCHost.exe is maxing my processors for about 20 to 30 minutes. I know that
    wuacuclt.ext is the problem by using Microsoft's Process Explorer and this
    wuauclt.exe is under the svchost.exe with the same spid that is maxing the
    processor. I have a group policy on OU's forcing the updates on specific
    days. This is not happening on the days that the updates are due for these
    machines.
    Any help would be appreciated.

    Gordon


    I am using the WSUS 2.0 method to update the client PCs at my work. We
    have set up a WSUS server and all client machines are detected by the server
    and the appropriate updates are pushed down to each PC. Everything works
    beautifully except for one aspect... Upon startup, there is a service called
    "wuauserv" or "wuauclt.exe" (not sure what one is the culprit or if
    wuauclt.exe is a product of the wuauserv service running).

    I found this info by using "Whats Running" (application like task manager).
    This startup service runs under the svchost.exe process, the big one which
    loads/runs the sound, themes, DHCP, Automatic Updates, etc. services for
    Windows. Whats happening is random users at random times upon startup are
    experiencing extremely slow PC performance. They call the Help Desk and I
    come over to their PC to see what's going on. Sure enough, the svchost.exe
    process is running at 100%. The hard drive activity light barely comes on so
    as far as the user is concerned, everything is loaded... They click on
    Outlook, launch IE and nothing happens. They do it again and of course
    nothing loads until about 5-10 minutes later once the svchost.exe process
    dies down and finishes whatever it was doing. There is nothing that you can
    do when this happens... if you press control alt delete, the task manager
    won't show up until about 2 minutes later and even then the only thing you
    can do is kill the svchost.exe process. But the catch is, since the
    schost.exe process that the updates run under run all the main Windows
    services, you lose your xp theme, sound, internet connection, etc. Now you
    have to go to the administrative tools/services list and restart all the
    services that were shut down when you ended the svchost.exe process. The
    only time it seems to go away is if you wait for the svchost process to do
    its thing (5-10 minutes) and install the available updates, or I just set it
    so that no updates are pushed down through WSUS (which is not an option).
    This issue has happened on some of the PCs in our factory area which on one
    instance slowed production down to a halt which resulted in that assembly
    line staying an extra hour and a half at work to catch up with its units. It
    almost seems as thought the updates process doesn't download the updates or
    anything when it maxes the CPU, but rather maxes the CPU just communicating
    with the WSUS server to see what updates the PC needs. Is there any way to
    fix this and has anyone else experienced this issue??
     
    Gordon, May 9, 2007
    #1
    1. Advertisements

  2. Gordon

    Jeremy Reed Guest

    I am having the same issue this morning with a number of my laptops...
     
    Jeremy Reed, May 9, 2007
    #2
    1. Advertisements

  3. Gordon

    Gordon Guest

    I found an answer that works . Look to the third page past mine on this site
    for a thread titled.....SVCHOST Performance Problems

    Gordon
     
    Gordon, May 9, 2007
    #3
  4. Gordon

    SchoolTech Guest

    svchost is doing an automatic updates scan. It appears to me that this
    must be caused by a recent update.

    We are using WSUS SP1 and have just started to see this on multiple PCs.
    The PCs often will take 15 minutes or more to log on or even just to get
    to the logon dialog.

    Once a PC is running normally, wuauclt /detectnow will make it happen
    again by starting a new updates scan.

    There are some patches for msi.dll but so far none of these have fixed
    the problem for us.
     
    SchoolTech, May 9, 2007
    #4
  5. Gordon

    SchoolTech Guest

    Doesn't work
    As soon as wuauclt starts, svchost goes back to 99% and same heavy
    memory use.

    I have a PC at home that has 1 GB and I have machines at work that have
    256MB. They all perform the same when any app has 100MB and 90% or more
    CPU usage.

    Why does this process have to run normal priority if it consumes so much
    CPU, it should be set to a lower priority so the user can do their work
    while it runs in the background.
     
    SchoolTech, May 9, 2007
    #5
  6. Gordon

    SchoolTech Guest

    SchoolTech, May 10, 2007
    #6
  7. Sudheer GN [MSFT], May 10, 2007
    #7
  8. Gordon

    Jim Byrd Guest

    Hi Gordon dt al in thread - This appears to be the current recommended fix:


    Even if you're not still having problems, this would be a good idea:

    - The newly released 'standalone' version of Windows Update Agent 3.0, v.
    7.0.6000.374, for 32 bit machines is available here:
    http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe

    It may say "Install is not needed since Windows Update Agent is
    already installed." If so, then run the exe with the command line switch
    /wuforce , like this:

    WindowsUpdateAgent30-x86.exe /wuforce

    to force the install.

    - You will also need to install or re-install the updated KB927891, here:
    http://support.microsoft.com/?kbid=927891 for a complete fix.


    - For those using Windows Servers - Courtesy of Bobby Harter, Program
    Manager, WSUS, Microsoft, WSUS 3.0 was released on April 30th and is
    avaialble now on the Microsoft Download Center. Full information,
    documentation, samples and links to the bits can be found here:
    http://www.microsoft.com/wsus. WSUS 3.0 RC will be supported until May 31st
    2007 - WSUS 3.0 supports upgrade of WSUS 2.0 SP1 and WSUS 3.0 RC.


    - One MS recommended procedure is:

    "1. Install the Windows Update Agent (WUA) for all the client computers
    (both WSUS client and stand alone workstation)
    2. Install the Update for Windows XP (KB927891) for all the client
    computers (both WSUS client and stand alone workstation)
    3. Upgrade the WSUS Server to version 3.0"

    However, I've also seen a posting by MS which states that once the WSUS
    client has been updated with the new Agent and KB927891 and then upgraded to
    WSUS 3.0, it will then handle updating the others.


    - The MS WSUS team believes that this solves all three 'svchost' problems
    that folks have been experiencing. See here:
    http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx


    - Note that you may _still_ see high svchost usage, but with these new
    components the machine should, however, remain responsive:

    From a posting by Sudheer GN of Microsoft -

    "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 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"





    --
    Regards, Jim Byrd,
    My Blog, Defending Your Machine,
    http://defendingyourmachine2.blogspot.com/



    In Gordon <> typed:
    || I found this entry on Exchange Experts web site but couldnt see any
    || resolution. My problem is identical.
    ||
    || Summary:
    ||
    || SVCHost.exe is maxing my processors for about 20 to 30 minutes. I
    || know that wuacuclt.ext is the problem by using Microsoft's Process
    || Explorer and this wuauclt.exe is under the svchost.exe with the same
    || spid that is maxing the processor. I have a group policy on OU's
    || forcing the updates on specific days. This is not happening on the
    || days that the updates are due for these machines.
    || Any help would be appreciated.
    ||
    || Gordon
    ||
    ||
    || I am using the WSUS 2.0 method to update the client PCs at my work.
    || We have set up a WSUS server and all client machines are detected by
    || the server and the appropriate updates are pushed down to each PC.
    || Everything works beautifully except for one aspect... Upon startup,
    || there is a service called "wuauserv" or "wuauclt.exe" (not sure what
    || one is the culprit or if wuauclt.exe is a product of the wuauserv
    || service running).
    ||
    || I found this info by using "Whats Running" (application like task
    || manager). This startup service runs under the svchost.exe process,
    || the big one which loads/runs the sound, themes, DHCP, Automatic
    || Updates, etc. services for Windows. Whats happening is random users
    || at random times upon startup are experiencing extremely slow PC
    || performance. They call the Help Desk and I come over to their PC to
    || see what's going on. Sure enough, the svchost.exe process is
    || running at 100%. The hard drive activity light barely comes on so
    || as far as the user is concerned, everything is loaded... They click
    || on Outlook, launch IE and nothing happens. They do it again and of
    || course nothing loads until about 5-10 minutes later once the
    || svchost.exe process dies down and finishes whatever it was doing.
    || There is nothing that you can do when this happens... if you press
    || control alt delete, the task manager won't show up until about 2
    || minutes later and even then the only thing you can do is kill the
    || svchost.exe process. But the catch is, since the schost.exe process
    || that the updates run under run all the main Windows services, you
    || lose your xp theme, sound, internet connection, etc. Now you have
    || to go to the administrative tools/services list and restart all the
    || services that were shut down when you ended the svchost.exe process.
    || The only time it seems to go away is if you wait for the svchost
    || process to do its thing (5-10 minutes) and install the available
    || updates, or I just set it so that no updates are pushed down through
    || WSUS (which is not an option). This issue has happened on some of
    || the PCs in our factory area which on one instance slowed production
    || down to a halt which resulted in that assembly line staying an extra
    || hour and a half at work to catch up with its units. It almost seems
    || as thought the updates process doesn't download the updates or
    || anything when it maxes the CPU, but rather maxes the CPU just
    || communicating with the WSUS server to see what updates the PC needs.
    || Is there any way to fix this and has anyone else experienced this
    || issue?? H
     
    Jim Byrd, May 10, 2007
    #8
  9. Gordon

    Jim Byrd Guest

    Hi ST - The following is the recommend fix at this point:


    Even if you're not still having problems, this would be a good idea:

    - The newly released 'standalone' version of Windows Update Agent 3.0, v.
    7.0.6000.374, for 32 bit machines is available here:
    http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe

    It may say "Install is not needed since Windows Update Agent is
    already installed." If so, then run the exe with the command line switch
    /wuforce , like this:

    WindowsUpdateAgent30-x86.exe /wuforce

    to force the install.

    - You will also need to install or re-install the updated KB927891, here:
    http://support.microsoft.com/?kbid=927891 for a complete fix.


    - For those using Windows Servers - Courtesy of Bobby Harter, Program
    Manager, WSUS, Microsoft, WSUS 3.0 was released on April 30th and is
    avaialble now on the Microsoft Download Center. Full information,
    documentation, samples and links to the bits can be found here:
    http://www.microsoft.com/wsus. WSUS 3.0 RC will be supported until May 31st
    2007 - WSUS 3.0 supports upgrade of WSUS 2.0 SP1 and WSUS 3.0 RC.


    - One MS recommended procedure is:

    "1. Install the Windows Update Agent (WUA) for all the client computers
    (both WSUS client and stand alone workstation)
    2. Install the Update for Windows XP (KB927891) for all the client
    computers (both WSUS client and stand alone workstation)
    3. Upgrade the WSUS Server to version 3.0"

    However, I've also seen a posting by MS which states that once the WSUS
    client has been updated with the new Agent and KB927891 and then upgraded to
    WSUS 3.0, it will then handle updating the others.


    - The MS WSUS team believes that this solves all three 'svchost' problems
    that folks have been experiencing. See here:
    http://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx


    - Note that you may _still_ see high svchost usage, but with these new
    components the machine should, however, remain responsive:

    From a posting by Sudheer GN of Microsoft -

    "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 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"





    --
    Regards, Jim Byrd,
    My Blog, Defending Your Machine,
    http://defendingyourmachine2.blogspot.com/



    In SchoolTech <> typed:
    || Gordon wrote:
    ||| I found this entry on Exchange Experts web site but couldnt see any
    ||| resolution. My problem is identical.
    || Have a look at this thread:
    ||
    ||
    http://groups.google.com/group/micr...e6e30d61c7e/f92d6a80f92fdca6#f92d6a80f92fdca6
     
    Jim Byrd, May 10, 2007
    #9
  10. Gordon

    Malte Guest

    Hi,

    do anyone knows if MS going to release

    KB927891 and WU Agent 3.0 by WSUS 2.0 ?

    So that would be the easiest way, roll them out by WSUS 2.0, next to upgrade
    server to WSUS 3.0, isn't it ?

    BR,
    Malte
     
    Malte, May 10, 2007
    #10
  11. WUAgent will come on May, 22th with WSUS.
    Best way is to upgrade to wsus 3. ;)

    Winfried
     
    Winfried Sonntag [MVP], May 10, 2007
    #11
  12. Gordon

    Gordon Guest

    Good thing is this update just came out on Tuesday for WSUS. My server
    downloaded it for all clients and was installed on all machines.



     
    Gordon, May 25, 2007
    #12
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.