Fall Creators Update Resulting in High CPU Use By Service Host

Anonymous
2017-10-18T03:41:50+00:00

Hi,

After updating to the new version, I am seeing high CPU use from two processes:

Any ideas on how to make them not use a lot of CPU so that my laptop cools down and the fan stops blowing?

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2017-11-01T23:47:18+00:00

Hi all, 

Had the same problem myself and found the solution which is quite simple :

Go to settings -> update & security -> Windows Defender -> Open Windows Defender -> Firewall & Network protection

Then you need to disable the firewall for all the types of networks

once that's done click on restore settings

That should do the trick and you're cpu usage should return to normal.

Hope it helps, it did for me.

Was this answer helpful?

400+ people found this answer helpful.
0 comments No comments

82 additional answers

Sort by: Oldest
  1. Anonymous
    2017-11-19T07:10:54+00:00

    Apperently they don't.

    In the last month I have seen a high CPU usage on 2 services (Service Host: Local Service (No Network) and Service Host: Local System. Now I know this is because of my WiFi hotspot creator program (Connectify), but I didn't have any of the problems on Windows 10 with this program installed in the last 2 years, until this guys launched Windows 10 1709 Fall Creators Update and last updates on 1703. I have tried to switch the program, but it doesn't mater what wifi hatspot program i install, the problem appears again and again. Windows 10 works normal again only if I fully uninstall all this type of programs for creating wifi hotspots. 

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-11-19T07:50:31+00:00

    Marius - -  I continued to scout arund and found MY solution on another thread.

    Solution #1 worked for me. 

    #1]  Go to settings –

    > update & security –

    > Windows Defender –

    > Open Windows Defender –

    > Firewall & Network protection

    Disable the firewall for ALL networks

    Once that's done click on restore settings

    Then – turn on the firewalls again!

    That should do the trick and you're cpu usage should return to normal.

     #2}  Another trick, but only if you don't use Ethernet.

    1. Right-click on Network icon on taskbar > Open Network & Internet Settings
    2. Click "Change adapter settings"
    3. Disable everything that is not Wi-Fi
    4. Search "Services" from Start Menu/Cortana
    5. Find and double-click on "Internet Connection Sharing (ICS)"
    6. In "General" tab, change Startup type to "Manual", then click OK
    7. Restart computer
    8. If it fails, try to shut down the ICS service on Task Manager, then restart again

    Turn the firewalls back on afterwards!

    Good luck!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-11-19T07:58:14+00:00

    Just for the record, I installed v1709 fresh on a laptop and this issue did not appear. On the upgrade from v1703 on another laptop and on my main PC, this issue did appear.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-11-19T08:26:03+00:00

    Just for the record, I installed v1709 fresh on a laptop and this issue did not appear. On the upgrade from v1703 on another laptop and on my main PC, this issue did appear.

    So do I, actually I installed this 3 times fresh and the problems still show up again and again, after I have installed my Connectify. The only solution for me is to remove it completely but I don't want that. It sucks because Microsoft doesn't do anything to fix this, because it's their fault, not the guys that did Connectify. The Windows 10 worked just fine with this program installed until this Fall Creators Update. They edited something in the OS which cause this problem but I don't know what.

    Was this answer helpful?

    0 comments No comments