09-08-2015, 10:03 AM
I was hit by this issue this morning, probably something to do with the batch of updates that went in yesterday, and this was the first update scan after that. Some people get bitten by it. I think in this case it was related to something it's doing to try to automatically figure out if Windows 10 will run and whether to offer you the upgrade. It goes off into la-la land and eats up a CPU for basically forever.
Stopping the Windows Update service makes it immediately go away, so clearly that's the culprit.
I opted out of getting Microsoft software, since some folks had seen that as an issue. I installed a couple patches supposedly related to this issue but that didn't help. I set a registry flag to force it not to accept any OS version upgrades via Update, and that doesn't appear to have helped.
It's stupidly annoying. It happened to my old Vista machine a couple weeks ago, and I've not figured out how to stop it there yet because I didn't much care and just disabled updates.
I guess I should go back and remove those patches from yesterday since I'd never seen it on this machine before then.
Stopping the Windows Update service makes it immediately go away, so clearly that's the culprit.
I opted out of getting Microsoft software, since some folks had seen that as an issue. I installed a couple patches supposedly related to this issue but that didn't help. I set a registry flag to force it not to accept any OS version upgrades via Update, and that doesn't appear to have helped.
It's stupidly annoying. It happened to my old Vista machine a couple weeks ago, and I've not figured out how to stop it there yet because I didn't much care and just disabled updates.
I guess I should go back and remove those patches from yesterday since I'd never seen it on this machine before then.
Dean Roddey
Explorans limites defectum
Explorans limites defectum