Configure and troubleshoot Automatic Updates
28 August 2007 by Snakefoot | Comment » | Trackback OffAutomatic Updates uses 100% CPU
Automatic Updates (AU) can become corrupted, so svchost.exe starts using 100% CPU when contacting Microsoft to check for updates. This can be tested by running this command:To fix the high CPU usage apply the following updates to Automatic Updates. More Info MS KB932494:wuauclt /detectnow
- Download and apply MS KB927891 hotfix.
- Download and apply WindowsUpdateAgent30-x86.exe client update for Windows Update Server 3.0 using the /wuforce command line switch.
Automatic Updates crashes when checking for updates
Automatic Updates can also enter a state where it crashes by just checking for updates:To repair the Automatic Updates service try the following steps:Generic Host Process for Win32 Services encountered a problem and needed to close.
- Press the Start-button and Run... this command to stop the service:
net stop wuauserv
- Check the root for all drives (including network drives) and delete the folder called WuTemp:
drive:\WuTemp
- Delete the following folder containing the Cryptographic Service database:
%systemroot%\system32\catroot2
- Rename the following folder to SoftwareDistributionOLD:
%systemroot%\SoftwareDistribution
- Rename the following system files used by Automatic Updates, so Windows File Protection is activated and restores them again:
- Cdm.dll
- Iuengine.dll
- Wuapi.dll
- Wuauclt.exe
- Wuauclt1.exe
- Wuaucpl.cpl
- Wuaueng.dll
- Wuaueng1.dll
- Wuauserv.dll
- Wucltui.dll
- Wups.dll
- Wups2.dll
- Wuweb.dll
- Restart Windows
- Reinstall Windows Update Client by launching the install with the parameter /wuforce
More Info MS KB 931852
Automatic Updates fails to start
Automatic Updates might fail to start with the following error even if the service is not disabled:This can be caused by the service being disabled with group policies or registry NoAutoUpdate. It can also be caused by DLL's required by Automatic Updates needs to be registered:Error 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Event ID: 10005
DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service wuauserv with arguments "" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334}
- REGSVR32 %windir%\system32\wuapi.dll
- REGSVR32 %windir%\system32\wuaueng1.dll
- REGSVR32 %windir%\system32\wuaueng.dll
- REGSVR32 %windir%\system32\wucltui.dll
- REGSVR32 %windir%\system32\wups.dll
- REGSVR32 %windir%\system32\Wuauserv.dll
Tags:
Category:
Updated: 23 October 2007