The only problem with this fix, is if the PC reboots; the problem reappears, ICS does NOT stay disabled. for whatever reason it comes back on and the CPU goes back to racing at 30% to 60%... so partial fix only.
I hope Microsoft will fix soon...
Sure do hope they get it fixed too. I can see no changes with the Fall Creators Update which are useful for me, yet here we are again, trying to find workarounds for Microsoft's errors.
I saw the problem return after restarting when I just killed/stopped the task using the Task Manager, but once I stopped/disabled the ICS service (via Windows Administrative Tools/Services), ICS has not run again. I'll try to attach a screen capture with
the Services status tab (via msconfig - System Configuration) and Task Manager both showing. I've restarted my computer five or six times (mostly testing this fix) and ICS still shows that it was disabled on 10/20/2017 at 4:37PM. Just did another restart
prior to replying and it's still fine.
I may just be lucky though, the problem never occurred in the first place on my wife's Dell desktop sitting a few feet to my right. This one is 64-bit Windows 10 Home and her's is 32-bit Windows 10 Home. My laptop is 32-bit Windows 10 Professional if any
of that makes any difference.
EDIT: Checked and the ICS service was NOT running on either the laptop PC or my wife's computer although I hadn't stopped it on either one after the Fall Creator's Update - guess that was the reason that neither of those computers
had the high CPU usage problem.
