How to Fix Service Host Local System (Network Restricted) High CPU
Service Host: Local System (Network Restricted) is a svchost.exe group that runs Windows services needing network access, so a high CPU spike means one of those services is working hard. Common culprits include Windows Update, Delivery Optimization, DHCP, and DNS. Expand the group in Task Manager to find the specific service, then let it finish or adjust its settings instead of ending the process. This illustrated guide covers 3 methods and 20 steps, with a separate picture for every step.
-
1. Open Task Manager
Press Ctrl+Shift+Esc and open the Processes tab to see active programs and services.
-
2. Sort by CPU usage
Click the CPU column header so the busiest processes rise to the top of the list.
-
3. Expand the Service Host group
Click the arrow next to Service Host: Local System (Network Restricted) to reveal its child services.
-
4. Find the busy child service
Read the child entries to see which service, such as Windows Update or DHCP, is using CPU.
-
5. Check the Details tab
Switch to the Details tab and note the PID of the related svchost entry for later reference.
-
6. Verify the file location
Right-click the process and choose Open file location to confirm the file sits in the Windows System32 folder.
-
7. Open the related service
Right-click the busy child service in Task Manager and choose Open Services to inspect its status and description.
-
8. Note the exact service name
Write down the service name so you can target it precisely instead of ending the whole Service Host group.
-
9. Let an update finish
In Windows Update settings, check whether an update is downloading or installing and let it complete.
-
10. Pause updates briefly
Open Windows Update, choose Pause updates, and select a short interval if updates are disrupting work.
-
11. Limit Delivery Optimization
In Windows Update advanced options, open Delivery Optimization and cap the download bandwidth.
-
12. Restart a stuck service
In the Services window, find the named service and choose Restart to clear a hung network task.
-
13. Disable a problematic service
If a service stays stuck, open its Properties and stop it, setting startup to Manual.
-
14. Open an administrator terminal
Right-click the Start button and open Windows Terminal or Command Prompt with administrator rights.
-
15. Run DISM repair
Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter to repair the component store.
-
16. Run System File Checker
Type sfc /scannow and press Enter to find and replace corrupted system files.
-
17. Reset Windows Update components
Stop the update and transfer services, rename the SoftwareDistribution folder, then start them again.
-
18. Check network drivers
In Device Manager, update the network adapter driver if the spike follows network activity.
-
19. Verify CPU returns to normal
Reopen Task Manager after a reboot and confirm no Service Host group is consuming high CPU.
-
20. Run the update troubleshooter
Open Settings, System, Troubleshoot, and run the Windows Update troubleshooter to clear stuck update errors.