CPU usage 100% by SVCHOST.exe after enabling WSUS

Discussion in 'Update Services' started by taylor.li, Apr 27, 2007.

  1. taylor.li

    taylor.li Guest

    We enabled WSUS service for all clients and set will run WSUS after PC has
    started for 3 minutes, but users report it is very slow after they start PCs
    in first 5 minutes. I found that the CPU usage is 100% by SVCHOST.exe for
    several minutes. I patched the hotfix 927891 and 916089 as the solution from
    Microsoft site, but it seems no more help. It still is slow and CPU 100% in
    first 5-6 minutes, how can to fix the issue?

    Thanks,
    Taylor
     
    taylor.li, Apr 27, 2007
    #1
    1. Advertisements

  2. taylor.li

    Jeff S guy Guest

    The same thing happened to me. I opened a case with Microsoft tech support,
    and ended up talking to one of their WSUS tech leads. He said the following:

    - This is a known issue with the Automatic Updates client in XP (it's not a
    problem on Vista), particularly with MS Office updates, and that his team has
    been unudated with requests for a solution. It's worse the older the PC is
    and the less robust its CPU. See Microsoft article 916089. However, patch in
    KB927891 doesn't fix the problem--maybe just makes it a little better.
    Specifically I think he said it's a bug in the file
    C:\windows\system32\msi.dll.

    - There is a new AU client created for WSUS 3.0. He said it would be
    released independent of WSUS 3 as a WSUS 2.0 update when it's available, but
    he said he didn't have it to give to me until then--might be hours or weeks,
    he didn't know.

    - As a work-around, he suggested three things, which are all not pretty:

    1. Download and install the WSUS 3.0 beta, which presumably includes the new
    beta AU client.

    2. Or decline all Office patches in WSUS and instead install these manually
    on PCs.

    3. Or disable the Automatic Updates service on clients via Group Policy
    Object, during normal business hours, but enable it during off-hours.
    The challenges with this are many. You can't schedule when the Automatic
    Update client checks in with the WSUS server (you can only specify the
    interval for when they check in), so it would be hit-or-miss if the clients
    actually check in with the WSUS server during off hours. You could get around
    that problem by changing the check-in interval to something like 1 hour and
    say to install their updates immediately. You could also concurrently set
    each client to run a job that forces the client to check in (wuauclt
    /detectnow) via an AT job or some such thing.
     
    Jeff S guy, Apr 27, 2007
    #2
    1. Advertisements

  3. taylor.li

    Jim Byrd Guest

    Hi Taylor and Jeff - How knowledgable about doing things are you? Do you
    know how to start and stop services? How to run a .cmd file? If not,
    you'll need access to someone who does to avoid problems.

    The following assumes you're on Windows XP but will probably work OK for
    Win2k as well. If you're confident about what you're doing, then try the
    following first - only if it doesn't work, then there's another level of
    stuff that can be done following:

    1. Stop and Disable Automatic Updates, Background Intelligent Transfer
    Service and the Cryptographic Service.

    2. Rename the folder %SystemRoot%\SoftwareDistribution to
    %SystemRoot%\OldSoftwareDistribution

    3. Open Notepad and create a file containing the following:

    REGSVR32 WUAPI.DLL
    REGSVR32 WUAUENG.DLL
    REGSVR32 WUAUENG1.DLL
    REGSVR32 ATL.DLL
    REGSVR32 WUCLTUI.DLL
    REGSVR32 WUPS.DLL
    REGSVR32 WUPS2.DLL
    REGSVR32 WUWEB.DLL


    Save this file as 'Wudll.cmd' (without the quotes) to any convenient
    location then exit Notepad and double click on the file you just saved. You
    should get a 'Sucess' mesage for each of the .dll's listed above.

    4. Now Re-enable to Automatic status and then Start each of the services
    you stopped before - Automatic Updates, Background Intelligent Transfer
    Service and the Cryptographic Service.

    5. Now Reboot. Now Reboot Again. (Yes, twice.)

    See if that solves it - give it a couple of days. If so, then you can
    delete 'OldSoftwareDistribution'. I would request that you post back with
    your results. _Only if the problem does re-occur_, then do the following
    _exactly_:

    1. Go to http://wiki.djlizard.net/Dial-a-fix and download Dial-a-fix
    v0.60.0.24 (2006-10-27) Here's a direct download link:
    http://djlizard.net.nyud.net:8080/software/Dial-a-fix-v0.60.0.24.zip and a
    secondary: http://djlizard.net/software/Dial-a-fix-v0.60.0.24.zip from
    that page's download section, here:
    http://wiki.djlizard.net/Dial-a-fix#Mirrors.2Fdownload_locations.2C_and_articles .

    2. Unzip it to a new folder at root with any name, e.g.
    c:\Dial-a-fix-v0.60.0.24

    3. Double click on Dial-a-fix.exe in that folder.

    4. Click on the following:
    Options/tooltips (just to get an idea of what it does in each section.
    :) )
    Both boxes under Prep
    The 'all' (top) box for Sections 2, 3 and 4 (which will automatically
    be set when you check 3)
    In Section 5, 'Programming cores/runtimes' and
    'Explorer/IE/OE/shell/WMP' only.
    Click 'Go' . (Some of the re-registrations may take what seems like a
    long time for some .dll's - Don't be impatient.)

    5. Reboot (if Dial-a-fix doesn't do it automatically at the end). Now
    Reboot Again. (Yes, twice.)


    See if that does the trick, and, again please post back with your
    experience.



    MS is well aware of the problem and has provided privately two different
    responses concerning a fix:

    "I regret to say that I was told that this known issue requires too much
    change to be implemented in a hotfix. A change will instead be implemented
    in the next Automatic Updates client, which we are planning to release in Q2
    this year."

    "According to the feedback from Product Development team, this fix will be
    published as a security update on the Windows Update site and the relevant
    KB article will also be released by us. Therefore, we just need to keep the
    system on the network up to date. In addition, the Product Development team
    also indicates that the WSUS 3.0 client may contain this patch if this fix
    can released timely. At that moment, we can also attempt to upgrade to the
    WSUS client 3.0 to test the issue."

    I'm told that the RTW (Release to Web) version of WSUS 3.0 will be published
    on 30th Apr.

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



    In taylor.li <> typed:
    || We enabled WSUS service for all clients and set will run WSUS after
    || PC has started for 3 minutes, but users report it is very slow after
    || they start PCs in first 5 minutes. I found that the CPU usage is
    || 100% by SVCHOST.exe for several minutes. I patched the hotfix 927891
    || and 916089 as the solution from Microsoft site, but it seems no more
    || help. It still is slow and CPU 100% in first 5-6 minutes, how can to
    || fix the issue?
    ||
    || Thanks,
    || Taylor
     
    Jim Byrd, Apr 27, 2007
    #3
  4. taylor.li

    taylor.li Guest

    Hi Jim,

    Thanks for your so kindly help first.

    Actually, for the first way, I had a try before since I searched out this
    kind of document, but SVCHOST.exe still has taken up 99% for 2 minutes. For
    way 2 to download and run program from the third pary (Dial-a-fix
    v0.60.0.24), I think because we have so many PCs (>1000PCs) and so important
    data in users' PCs, I didn't try. The best solution should be from
    Microsoft, hope they can publish their offical solution. But I didn't search
    it out in internet.

    I have no idea for this issue now?

    Thanks.
    Taylor
     
    taylor.li, Apr 30, 2007
    #4
    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.