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 guide walks through the process in clear illustrated steps, from the first preparation to a finished result. Each step has its own picture, so you can compare your progress as you go.
How to use this guide
Work through the steps in order. Method 1 of 3 covers the basics, and the later methods offer alternatives and finishing touches. If you only have a minute, skim the Quick steps box above and come back for the details.
Related guides
- How to Improve public speaking skills
- How to Make a smoothie bowl
- How to Apologize sincerely
- How to Rinse rice
- Browse all Windows Troubleshooting guides
- All 52runoob guides
Trusted external resources
- Microsoft Support — Windows Update Troubleshooter
- Microsoft Learn — Overview of Windows as a service
- Microsoft Learn — Windows Update additional resources
A note on sources
We check each guide against the official resources listed in References at the end of this article. External links open in a new tab; the related guides above stay on this site.
Quick steps
- Open Task Manager and expand Service Host: Local System (Network Restricted).
- Note which child service is using the most CPU, such as Windows Update or DHCP.
- Let an active update or scan finish before changing anything.
- Pause Windows Update or limit Delivery Optimization bandwidth if needed.
- Restart the stuck service or the PC to clear a hung network task.
- Run DISM and SFC if the high CPU keeps returning.
Things you'll need
- A Windows PC with administrator access
- Task Manager, built into Windows
- An internet connection for update and repair downloads
- About 20 minutes to let updates or scans finish
Step-by-step
Method 1 of 3: Identify the Service Using CPU
Step 1: Open Task Manager
Press Ctrl+Shift+Esc and open the Processes tab to see active programs and services.
Step 2: Sort by CPU usage
Click the CPU column header so the busiest processes rise to the top of the list.
Step 3: Expand the Service Host group
Click the arrow next to Service Host: Local System (Network Restricted) to reveal its child services.
Step 4: Find the busy child service
Read the child entries to see which service, such as Windows Update or DHCP, is using CPU.
Step 5: Check the Details tab
Switch to the Details tab and note the PID of the related svchost entry for later reference.
Step 6: Verify the file location
Right-click the process and choose Open file location to confirm the file sits in the Windows System32 folder.
Step 7: Open the related service
Right-click the busy child service in Task Manager and choose Open Services to inspect its status and description.
Step 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.
Method 2 of 3: Pause or Reconfigure the Culprit
Step 9: Let an update finish
In Windows Update settings, check whether an update is downloading or installing and let it complete.
Step 10: Pause updates briefly
Open Windows Update, choose Pause updates, and select a short interval if updates are disrupting work.
Step 11: Limit Delivery Optimization
In Windows Update advanced options, open Delivery Optimization and cap the download bandwidth.
Step 12: Restart a stuck service
In the Services window, find the named service and choose Restart to clear a hung network task.
Step 13: Disable a problematic service
If a service stays stuck, open its Properties and stop it, setting startup to Manual.
Method 3 of 3: Repair and Prevent Recurrence
Step 14: Open an administrator terminal
Right-click the Start button and open Windows Terminal or Command Prompt with administrator rights.
Step 15: Run DISM repair
Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter to repair the component store.
Step 16: Run System File Checker
Type sfc /scannow and press Enter to find and replace corrupted system files.
Step 17: Reset Windows Update components
Stop the update and transfer services, rename the SoftwareDistribution folder, then start them again.
Step 18: Check network drivers
In Device Manager, update the network adapter driver if the spike follows network activity.
Step 19: Verify CPU returns to normal
Reopen Task Manager after a reboot and confirm no Service Host group is consuming high CPU.
Step 20: Run the update troubleshooter
Open Settings, System, Troubleshoot, and run the Windows Update troubleshooter to clear stuck update errors.
Tips
- Ending the Service Host process stops every service inside the group and can break networking.
- A CPU spike while Windows Update is downloading is usually temporary and settles on its own.
- Check the child service name first; that tells you which setting to change.
Warnings
- Do not end svchost.exe or the Service Host group just to stop high CPU.
- Disabling network services like DHCP or DNS can cut off internet access.
- Back up important files before changing service startup types.
Frequently asked questions
What is Service Host: Local System (Network Restricted)?
It is a svchost.exe group that hosts Windows services needing network access, such as Windows Update, Delivery Optimization, DHCP, and DNS. Svchost.exe is only a generic host, so the high CPU comes from one of the services inside it. Expand the group in Task Manager to see which service is responsible.
Is it safe to end this process when CPU is high?
No. Each Service Host group contains several services, so ending it can shut down networking, updates, or other features and may force a restart. Instead expand the group, identify the busy service, and pause or reconfigure that service specifically.
Why does this process spike after startup?
At startup, network services such as DHCP, DNS, and Windows Update perform discovery, license checks, and update scans, which can briefly drive CPU up. The load usually drops once those tasks complete. If it stays high for hours, check for a stalled update or a corrupted component store.
Which services are commonly inside this group?
Typical members include Windows Update, Delivery Optimization, DHCP Client, DNS Client, and background network transfer services. The exact set varies by PC and by what is installed. Task Manager lists them by name when you expand the group.
References
- Microsoft Support — Windows Update Troubleshooter. https://support.microsoft.com/windows/windows-update-troubleshooter-for-windows-10-19bc41ca-ad72-ae67-af3c-89ce169755dd
- Microsoft Learn — Overview of Windows as a service. https://learn.microsoft.com/en-us/windows/deployment/update/waas-overview
- Microsoft Learn — Windows Update additional resources. https://learn.microsoft.com/en-us/troubleshoot/windows-client/installing-updates-features-roles/additional-resources-for-windows-update
- wikiHow — How to Fix Service Host Local System (Network Restricted) High CPU. https://www.wikihow.com/Reduce-CPU-Usage
Every guide is reviewed against its sources. See our editorial policy.
Reader comments
0 so farFinished this guide? Tell other readers what worked, what didn't, and what you would change.