3 ms·
We've had some similar problems with Windows Update on our Win7 systems in recent months as well. On a many-cored workstation it's an annoyance. On an older lap
by Silhouette 10y ago
We've had some similar problems with Windows Update on our Win7 systems in recent months as well. On a many-cored workstation it's an annoyance. On an older laptop with a dual core CPU, it's crippling.
Like others posting here, we see the service host process spinning an entire core at around 100%. That keeps the CPU clock speeds and power draw up all the time as a notable side effect.
This seems to be a separate issue from problems with Windows Update taking hours to check for and/or apply the updates themselves.
- wiredfool 10y agoGreat, looks like I have both problems.
- barrkel 10y agoGlancing at the stack traces with symbol server downloads enabled, it looks like there's a n^2 or potentially even exponential algorithm being run during the checking phase - checks are run both passively and when actively applying. There's something very wrong with the design of the algorithm - it obviously doesn't scale. Bigger, fewer patches may simply be reducing the size of n. IMO a better approach would be to offload the work to MS: upload a list of applied updates and let the cloud do the crunching. Much higher chance of memoizing and reusing work that way too. It's a sign of MS's client oriented culture still sticking around.