http://superuser.com/questions/635837/high-cpu-load-from-sys...
In my desktop it was causing it to rev up the fan when it was idle for a few minutes.
http://www.wintips.org/how-to-fix-svchost-exe-netsvcs-memory...
I dunno what the hell Microsoft are playing at, but I'm in the process of switching all my computers to Linux.
https://news.ycombinator.com/item?id=11267019
wuaueng.dll!CUpdatesToPruneList::AddSupersedenceInfoIfNeeded
The bug is obviously in highly inefficient traversal through the existing info about the updates, which didn't degrade to being so obviously bad at the time when there was just a small number of the updates.I've used Microsoft tools to diagnose that, and I'm not the only one who has found it,
http://www.dslreports.com/forum/r30535980-WIN7-MS-updates-ta...
so the same info is available to Microsoft, but they obviously don't want to fix it.
On my machine it takes some 4 hours using 100% CPU of one core. If there are only 100 millions of such machines, and if it's just 40 Watt hours used during these 4 hours, it gives some 4 Gigawatt hours wasted every month in the world due to that particular bad code (If I calculated it right, over one year, it's a rough equivalent of the total energy use of 1500 Germans or 500 US citizens.)
However, this causes a problem in that every time you want to actually update, Windows Update may rebuild the entire "installed updates" database from scratch which can take hours on a heavily patched machine.
(The database is, fascinatingly, the whole 1 GB big).
What's worse is the automatic OS restarts that seem to also think I'm in idle mode.
But it literally rapes my HDD while updating(anytime it wants) or it's AV scanning disk(and you can't turn it off)
It makes my desktops unusable.
Doing nothing, except mabye mining a fuckton of data about you and sending it to Microsoft.
And take note of point 1 and 2.