Automatic Update causes SVCHOST.exe high CPU
Symptom
SVCHOST high CPU. If stopping the Automatic Update service, the high CPU issue disappears.
You can use the following method to verify whether it is AU caused SVCHOST high CPU.
1. Run the command to find the PID of SVCHOST which is running on Automatic Update service.
Tasklist –m wuaueng.dll
2. Run the command to enforce client to Automatic Update. In certain circumstances, high CPU issue may recur after running the command.
Wuauclt /detectnow
3. Find the PID of SVCHOST which is running on Automatic Update service, monitor and verify if it causes high CPU for long time. High CPU for short time is normal and is not a problem.
Solution
If Automatic Update causes SVCHOST.exe high CPU, please refer to the following KB articles:
https://support.microsoft.com/kb/916089/en
https://support.microsoft.com//kb/927891/en
You can try the following methods to resolve the issue.
1. Install update KB927891
https://support.microsoft.com//kb/927891/en
2. If client still encounters persistent 100%CPU issue after installing update KB927891, please download and install the latest WSUS 3.0 client:
32-bit versions
https://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe
64-bit version
https://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x64.exe
https://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-ia64.exe
The 2 updates (KB927891and WUA3.0 )to resolve AU related SVCHOST high CPU issue are available on WSUS now.
KB927891 is available on WindowsUpdate /WSUS. It is listed as Critical Updates in WSUS. Please refer to:
KB936301 is listed in WSUS as Critical Updates. It is to install on WSUS 2.0 SP1 server to upgrade Selfupdate tree to “WSUS 3.0” but keep the server as WSUS 2.0, so that client can get WUA3.0 by visiting WSUS selfupdate tree. Please refer to:
https://blogs.technet.com/wsus/archive/2007/05/22/updates-for-wsus-available-today.aspx
Based on our monitoring and customers’ feedback, the above two steps are able to alleviate the Issue.
For the latest update about the issue, please refer to the following web site.
https://blogs.technet.com/wsus/archive/2007/04/28/update-on.aspx
If you have any question about the issue, please contact GCR PSS Security Support Group (shsecs@microsoft.com) to get further technical support.
[v1]Is this supposed to be here?