Resolve High CPU usage by Local Service (No Network) on Windows Server 2016

Share on linkedin
LinkedIn
Share on twitter
Twitter
Share on facebook
Facebook

Service Host Local Service High CPU Usage

If your server is running unresponsive with high CPU usage attributed to something called ‘Local Service (No Network)’, then it is probably an issue with Windows Firewall.

High CPU Symptoms include:

  • Applications & Windows Services not starting
  • Windows Service Distributed Transaction Coordinator stuck in “Starting” state
  • Attempts to go into Control Panel > Windows Firewall result in nothing happening and/or the explorer process hanging

Steps to resolve:

You can try to correct this by resetting the Firewall:

  1. Run CMD.exe as Administrator
  2. Use the command:
    netsh advfirewall reset

If this process also hangs then try:

  1. Using regedit go to path:
    HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy
  2. Rename Key FirewallRules to something else such as FirewallRulesBak
  3. Create a new FirewallRules key
  4. Go to the DomainProfile key and change the REG_DWORD Value EnableFirewall to 0 (zero)
  5. Do this for PublicProfile and StandardProfile as well.Use Regedit to change FirewallPolicy
  6. Reboot your server.

Try the “netsh advfirewall reset” (from CMD.exe as Administrator) again.

Run netsh command from elevated command line shell

Reboot again and if all goes well, CPU usage will return to normal and you should also be able to open Windows Firewall from the Control Panel.

Follow us on LinkedInFacebook or Twitter to be notified when we post new content or sign up to our newsletter using the form at the bottom of the page.