2

I have a fresh installed computer with Windows 7, 64-bit, Service Pack 1.

After a few minutes after startup, svchost.exe is consuming 100% of one cpu core.

I know there are many threads which are dealing with this problem, but none of them helped me.

I installed this updates: KB3050265 and KB3065987

I used this "Microsoft Fix it"-Tools: MicrosoftFixit50123 and MicrosoftFixit50362

I installed the current Windows Update Agent: https://support.microsoft.com/de-de/kb/949104

I tried to remove the SoftwareDistribution directory:

net stop wuauserv
net stop bits
rd /s /q %windir%\softwaredistribution
net start bits
net start wuauserv
wuauclt.exe /detectnow

And I tried to connect the computer with my home network over a usb/ethernet-adapter, and I tried to disable IPv6.

For diagnostic, I post here the WindowsUpdate.log file (after removing the SoftwareDistribution Directory, waiting until the service is hanging on 100%): http://pastebin.com/ZisR9Pft

A. Fendt
  • 75

3 Answers3

2

The CPU usage comes from Windows Updates which tries to find Updates: wuaueng.dll!CAgentUpdateManager::FindUpdates. This method calls a function wuaueng.dll!CUpdatesToPruneList::AddSupersedenceInfoIfNeeded to see if all updates are needed or if they are replaced (superseded). And this takes some time on your older Intel Core2 Duo CPU. You can't avoid the CPU usage. For a fresh Windows 7 install, use other tools that provide the current Updates.

// Update

Microsoft released a new WindowsUpdate Client Update to fix the slow Update searching/Installation.

Installing and searching for updates is slow and high CPU usage occurs in Windows 7
https://support.microsoft.com/en-us/kb/3102810

Download:
32Bit: http://www.microsoft.com/downloads/details.aspx?FamilyId=fcd6bf5d-f004-4ca3-aa7e-1de462b91dd0

64Bit: http://www.microsoft.com/downloads/details.aspx?FamilyId=4fe566bd-31b1-4413-8c4c-412b52533669

Also try if this improves your situation.

magicandre1981
  • 99,606
2

I tried everything you did as well. What finally fixed it was this answer; I installed KB3102810 which was recently released and it worked for me on 2 different machines.

Community
  • 1
aoetalks
  • 923
0

Very important: It is normal that Windows Update uses full CPU (e.g. 50%) for a very long time. I just spent many days trying everything possible, always stopping the update after giving up at ~3 hours of waiting. But in the end the solution was to simply wait for longer. I can confirm that a first time Windows Update can nowadays be stuck on the Checking for updates screen for at least 4 hours, while CPU is peaking and nothing else happens (except for the progress bar looping animation). This on a 2009 computer. On older computers it can probably something like 10 hours even. Most unbelievable thing ever. (And this has absolutely nothing to do with network problems, by the way.)

Jim Hoyle
  • 199