Fix: High CPU Usage by Service Host: Local System (Network Restricted)

Quite a number of Windows users have suffered from a problem where up to 95% of their CPU and/or Disk have been used by a process known as System Host: Local System (Network Restricted). This problem first surfaced back in the days of Windows 8 and has stuck around to haunt the brave users of Windows 10. Users affected by this issue have reported the System Host: Local System (Network Restricted) process hogging up to 95% of their CPU and up to 72 MB/s of their computer’s total capability to read data from and write data to its Hard Disk Drive. Those statistics are significant to say the least.

However, System Host: Local System (Network Restricted), in and of itself, is pretty ambiguous as it is not any one service but a guise under which a number of different Windows system services run, any of which could be causing unusually high CPU and/or Disk usage. In addition, to make things worse, this issue can also be caused by memory leak in the non-paged pool of memory. Thankfully, due to a lot of intelligent dwelling on the matter, it has been found that the most common offender that gives birth to this issue is a Windows system service known as Superfetch – a service that Microsoft claims aims to maintain and improve the performance of computers as time goes by but, in actuality, is nothing but a problem waiting to happen. If, in any case, Superfetch is not the root of the issue, it is certainly being caused by a memory leak in the non-paged pool.

The following are the two most effective solutions that you can use to try and fix this problem.

Repair Corrupt System Files

Download and run Reimage Plus Repair to scan and restore corrupt and missing files from here, once done proceed with the solutions below. It is important to ensure that all system files are intact and not corrupt before proceeding with the solutions below.

Solution 1: Disable the Superfetch service

  1. Press Windows Logo key + R to open a Run
  2. Type services.msc into the Run dialog and press Enter.
  3. Scroll down the list of services on your computer and locate the service named Superfetch.
  4. Double-click on Superfetch to edit its settings.
  5. Click on Stop to stop the service.
  6. Set the Startup type for Superfetch to Disabled.
  7. Click on Apply and then on OK.service host local system
  8. Restart your computer and check to see whether or not the problem has been fixed once it boots up.

Solution 2: Fix the memory leak in the non-paged pool of memory

If Solution 1 doesn’t work, don’t fret as you can still move onto this solution. To try and resolve this issue using this solution, you need to:

Press Windows Logo key + R to open a Run

Type regedit into the Run dialog and press Enter.

In the left pane of the Registry Editor, navigate to the following directory:


Click on Services in the left pane and then scroll down under services and chose Ndu.

In the right pane, locate and double-click on the registry value titled Start to modify it.

Change its Value data to 4. Doing so will disable it and plug the memory leak in the non-paged pool.

Click on OK.

Close the Registry Editor.

Network Restricted

Restart your computer. When your computer boots up, you should see that System Host: Local System (Network Restricted) is no longer using a massive amount of your CPU and/or Disk.

Solution 3: Running the System File Checker

  1. Open the Start menu and type ‘cmd’. Right click on the Command Prompt icon and click on ‘Run as Administrator’. Accept the UAC prompt when it comes up.
  2. In the command prompt, type the “sfc /scannow” and press enter.

Wait for the scan to successfully complete and perform a fix as well. If it’s successful, you’ll see the response ‘Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log.’

  1. Enter the command dism /Online /Cleanup-Image /RestoreHealth. After this command finishes running, monitor your CPU and Memory load and then check if the issue still exists.

Method 4: Killing SVChost

Killing the Service Host process in the Task Manager solves this issue. After this, try download your pending updates with an unmetered Wi-Fi connection.

  1. Press Ctrl + Shift + Del to launch the Windows Task Manager. You can also right-click on the taskbar and select Task Manager.
  2. Click on More details to expand the manager. This reveals all the running process.
  3. Search through the process for “Service Host: Local System”. This process hosts Windows Update and the Update Orchestrator Service. Select on this task and click End task.
  4. When the confirmation dialog shows up, check Abandon unsaved data and shut down and click the Shut down
  5. Monitor the CPU load and check if the issue has been solved.

Method 5: Performing a Clean Boot

In some cases, a third-party application or service might be causing High Cpu usage. Therfore, in this step, we will be disabling all non-essential services and applications at startup. For that:

  1. Log in to the computer with an Administrator account.
  2. Press “Windows” + “R” to open up the “RUN” prompt.
    Opening Run Prompt
  3. Type in “msconfig” and pressEnter“.
    Running MSCONFIG
  4. Click on the “Services” option and uncheck the “Hide all Microsoft Services” button.
    Clicking on the “Services” tab and Un-checking the “hide all Microsoft Services” option
  5. Click on the “Disable All” option and then on “OK“.
    Clicking on the “Disable All” option
  6. Click on the “Startup” tab and click on the “Open Task Manager” option.
    Clicking on the “Open Task Manager” option
  7. Click on the “Startup” button in the task manager.
  8. Click on any application in the list that has “Enabled” written next to it and select the “Disable” option.
    Clicking on the “Startup” tab and selecting an application listed there
  9. Repeat this process for all applications in the list and restart your computer.
  10. Now your computer has been booted in the “Clean Boot” state.
  11. Check to see if the issue goes away.
  12. If the error isn’t encountered anymore, start enabling the services one by one and identify the service by enabling which the error comes back.
  13. Either, reinstall the service or keep it disabled.


  1. The problem was because of the windows update service. Each update is around 1 GB in size that keeps downloading in the background. All those related services caused the leak. I set my WiFi as metered network and surprisingly got rid of the problem (at least temporarily). Waiting for a permanent fix.

  2. what about the high bandwidth usage. how to solve that.Also how do I shut down cortana.
    Seriously,like y microsoft y.No control at all at the user side.Again an update will come and again everything will be reset.this just gets worse n worse

  3. when I do abandon unsaved data and shutdown,the service host windows event log and many other services come up,and then again service host local system starts.Not helping.

  4. another quick way to fix.. Reset the Windows Defender Firewall to the default settings.

    To do this open
    Settings -> Update and Security -> Windows Defender -> Open Windows Defender Security Center -> Firewall and Network Protection -> Restore Firewall default settings

  5. What’s the make/model of your Lenovo? There should be an option restore to Factory settings.

  6. Perfect. Did not assume you had that in, can also happen if any of the external usb ports are utilized

  7. Good to know! I have had other sd cards and have my external hooked up all the time and never had an issue the last 4 years, took me by surprise!

Leave a Reply

Your email address will not be published.

Expert Tip

Fix: High CPU Usage by Service Host: Local System (Network Restricted)

If the issue is with your Computer or a Laptop you should try using Reimage Plus which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption. You can download Reimage by clicking the Download button below.

Download Now

I'm not interested