There are many Windows users who have reported a situation in which as much as 95% of the CPU or hard drive is being used up by System Host: Local System (Network Restricted). That situation dates as far back as Windows 8, and it pesters Windows 10 users today. As previously mentioned, this process uses up about 95% of the CPU power, and 72 mb/s of the system’s total hard drive data reading and writing ability. These are certainly alarming stats.
This problem is exacerbated by the fact that this process is not a single process, but multiple different Windows processes filed under one name. Any of these could be the root cause of the problem, so diagnostics can be difficult. Furthermore, a memory leak in the non-paged pool of memory could also cause this problem.
However, experience shows that the real cause of the problem is the same in most cases. The culprit is usually a Windows system service called Superfetch. Microsoft claims that it is supposed to make the machine’s performance better over time, but that is not usually the case. Superfetch usually causes more trouble than it’s worth. If this process is not causing the problem, then it is probably a memory leak, as previously mentioned.
Here are two of the solutions most likely to solve this problem.
Fix #1: Disable Superfetch
First, you need to hold down the Windows key and press R, which opens up the Run command. Type in ‘services.msc’ into the text box, and hit Enter. In the new window, go down the services list on your system, and find one called Superfetch.
Then, Double-click on it, so you can change its settings. Simply hit ‘Stop’ in the new menu. You should also change the type of startup to Disabled, so it doesn’t pop up anymore. Finally, hit ‘Apply’ and then ‘OK’.
Reboot your computer to check whether the problem reoccurs. If it does, move on to Fix 2.
Fix #2: Repair Memory Leak in Non-Paged Memory Pool
If you find that Fix 1 didn’t work for you, try this one.
First, hold down the Windows key, and press R. Then type in ‘regedit’ into the window that pops up, and hit Enter. In the field on the left in the Registry Editor, find this directory: HKEY_LOCAL_MACHINE > SYSTEM > ControlSet001. Hit the Services folder on the left side, and then click on ‘Ndu’. Switching to the right field, find and double-click the item named ‘Start,’ so you can modify it.
In the new menu, change the Value data to 4. By doing that, you are effectively plugging the memory leak in the non-paged pool. Afterward, click on ‘OK’ and dismiss the Registry Editor. Then reboot your system, and check whether the System Host: Local System (Network Restricted) is still using up so many resources.
Fix #3: Run the System File Checker
In the Start Menu, simply type in ‘cmd’. In the search results, right-click the icon of the Command Prompt, and select the option ‘Run as Administrator.’ A window will pop up. Simply press ‘OK’.
Once the Command Prompt is open, type in ‘sfc/scannow’ and hit Enter.
The scan will take a while to complete, and fix any errors on the way. If it is a success, the Command Prompt will write out Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log
Then type in ‘dism /Online /Cleanup-Image /RestoreHealth’
Afterward, check the CPU load as well as the memory capacity.
Fix #4: Disable SVChost
The final way to solve this issue is by ending the process called ‘Service Host’ using the Task Manager. When you have done so, download the updates required, preferably with a WiFi connection that is unmetered.
To open the Task Manager, hit Ctrl + Shift + Del. Another way to do that is to right-click the Task Bar and then Task Manager.
No matter how you choose to open it, click on ‘More’ to expand the Manager. By doing this, you are revealing all of the running processes. Find one named ‘Service Host: Local System’. It hosts the Windows Update and Update Orchestrator Service. Select this process and hit ‘End Task’. Once the confirmation window pops up, select ‘Abandon Unsaved Data and Shut Down,’ and then hit the ‘Shut Down’ button. Check the CPU performance.