I have noted of late periodically that happens here. I find that service host is hogging about 50% of cpu cycles and s l o w s everything down. The specific process ID leads to windows update, and doesn't seem to go away on its own. When I manually stop windows update service the cpu hogging ceases.
When it is acting this way manually running Windoze Update never completes - it stays in 'searching for updates' forever and ever, amen.. It seems that if I change my WindozeUpdate settings to automaticly download and install, I have no problems but when I go to 'let me decide' the issue happens. Since MS has talen the ability to decide away in WinTenTen it wouldn't surprise me if this is a 'new' featureannoyance being crammed down Win7 users throats.
I don't have the WinTenTen machine on often enough to note whether the same malady occurs there but Win10 is always set for autoupdate with no user decisions necessary. Or allowed..
Nor have I bothered to research the issue to see what the MS gurus say about it. (If anyone has dealt with this and beaten it into submission let me know. ;-)
That’s been my experience, pretty much, since getting this. If I could afford it, I would get a laptop with Win XP on it, just because I hate the fact that MS will “update” in spite of what I can do.
I’m fed up with MS and all their *ahem* machinations. I will try to learn Linux when my brain works better.