The Diagnostic Policy Service (DPS) is an essential Windows service that detects, troubleshoots, and resolves issues related to Windows components, network connectivity, hardware, and system performance. It runs in the background as part of the Service Host (svchost.exe) process and usually consumes very little CPU or memory.
However, some Windows 11 and Windows 10 users notice that Service Host: Diagnostic Policy Service suddenly starts using a high percentage of CPU, causing the system to slow down. You may experience lag while opening applications, excessive fan noise, increased power consumption, or even system freezes. In Task Manager, the CPU usage may remain between 20% and 100% for extended periods, making it difficult to use your computer normally.
This problem can occur due to corrupted system files, damaged network components, excessive diagnostic logs, outdated drivers, Windows Update issues, or software conflicts. Fortunately, you don’t have to disable the service permanently, as doing so may prevent Windows from automatically detecting and repairing system problems.
In this guide, we’ll explore five proven methods to fix Service Host Diagnostic Policy Service High CPU Usage in Windows 11 and Windows 10 while keeping your system stable and fully functional.
What Is the Diagnostic Policy Service?
The Diagnostic Policy Service is responsible for monitoring Windows for hardware and software issues. It automatically detects problems and helps Windows troubleshoot them.
Some of its functions include:
- Detecting network connectivity issues.
- Monitoring Windows components.
- Running built-in troubleshooters.
- Collecting diagnostic information.
- Assisting with automatic repairs.
- Logging system health information.
Normally, the service runs quietly in the background and uses minimal system resources.
Why Does Diagnostic Policy Service Use High CPU?
Several issues can cause the service to consume excessive CPU resources.
Common causes include:
- Corrupted Windows system files.
- Damaged diagnostic logs.
- Faulty or outdated device drivers.
- Windows Update problems.
- Network adapter issues.
- Corrupted system services.
- Malware infections.
- Third-party software conflicts.
Identifying the underlying cause helps determine the most effective solution.
Method 1: Restart the Diagnostic Policy Service
Sometimes the service becomes stuck in a loop after encountering an error. Restarting it can clear temporary issues and restore normal CPU usage.
Steps to restart the service
- Press Windows + R.
- Type services.msc and press Enter.
- Locate Diagnostic Policy Service.
- Right-click the service.
- Select Restart.
- If Restart is unavailable, click Stop and then Start.
- Ensure the Startup type is set to Automatic.
- Click Apply.
- Click OK.
- Restart your computer.
After rebooting, open Task Manager and check whether the CPU usage has returned to normal.
Method 2: Repair Corrupted System Files
Corrupted Windows files are one of the most common reasons why background services consume excessive CPU resources.
Windows includes built-in repair tools that can automatically restore damaged files.
Run System File Checker
- Search for Command Prompt.
- Right-click it.
- Choose Run as administrator.
- Enter the following command:
sfc /scannow- Press Enter.
- Wait for the scan to complete.
If SFC repairs any files, restart your PC.
Run DISM
Next, repair the Windows image using DISM.
Type the following command:
DISM /Online /Cleanup-Image /RestoreHealthPress Enter.
The scan may take several minutes depending on your system.
Once finished, restart Windows and monitor CPU usage in Task Manager.
Method 3: Clear Diagnostic Event Logs
Large or corrupted diagnostic logs can sometimes cause the Diagnostic Policy Service to repeatedly process old entries, leading to high CPU usage.
Clearing these logs often resolves the issue.
Steps
- Press Windows + R.
- Type:
eventvwr.msc- Press Enter.
- Expand Applications and Services Logs.
- Expand Microsoft.
- Expand Windows.
- Locate diagnostic-related logs such as Diagnostics-Performance.
- Right-click the log.
- Select Clear Log.
- Confirm the action.
Repeat the process for other diagnostic logs if necessary.
Restart the computer afterward.
Windows will automatically recreate fresh event logs.
Method 4: Update Device Drivers
Faulty or outdated drivers can continuously trigger diagnostic checks, resulting in unusually high CPU usage.
Updating your drivers may resolve the issue.
Steps
- Right-click the Start button.
- Select Device Manager.
- Look for devices displaying warning icons.
- Expand the major hardware categories, including:
- Network adapters
- Display adapters
- Storage controllers
- System devices
- Right-click a device.
- Select Update driver.
- Choose Search automatically for drivers.
- Install any available updates.
- Restart your computer.
If the problem started after installing a new driver, consider using the Roll Back Driver option from the device’s properties.
Method 5: Perform a Clean Boot
Third-party applications or background services may interfere with Windows diagnostics, causing continuous CPU activity.
A Clean Boot starts Windows with only essential Microsoft services.
Steps
- Press Windows + R.
- Type:
msconfig- Press Enter.
- Open the Services tab.
- Check Hide all Microsoft services.
- Click Disable all.
- Open the Startup tab.
- Click Open Task Manager.
- Disable all startup applications.
- Close Task Manager.
- Click Apply.
- Click OK.
- Restart your PC.
After restarting, observe the CPU usage.
If the problem disappears, enable services one at a time until you identify the application causing the issue.
Additional Ways to Reduce High CPU Usage
If the Diagnostic Policy Service continues to consume excessive resources, these additional steps may help:
- Install the latest Windows updates.
- Scan your computer for malware using Windows Security.
- Restart the Windows Management Instrumentation service.
- Free up disk space if the system drive is nearly full.
- Disconnect unnecessary external hardware during troubleshooting.
- Update your BIOS or UEFI firmware if recommended by the manufacturer.
- Disable unused network adapters.
- Check the health of your storage drive using CHKDSK.
- Ensure your antivirus software is up to date.
- Restart the PC periodically to clear temporary processes.
These maintenance tasks can improve overall system performance and reduce unnecessary background activity.
How to Monitor CPU Usage
After applying the fixes, monitor the service to confirm that the issue has been resolved.
Using Task Manager
- Press Ctrl + Shift + Esc.
- Open the Processes tab.
- Locate Service Host: Diagnostic Policy Service.
- Observe its CPU usage for several minutes.
Under normal conditions, the service should consume very little CPU except during occasional troubleshooting tasks.
Should You Disable the Diagnostic Policy Service?
Disabling the service is generally not recommended.
Without it, Windows may be unable to:
- Detect hardware problems.
- Run automatic troubleshooters.
- Diagnose network issues.
- Identify system failures.
- Perform certain repair operations.
Instead of disabling the service, it’s better to identify and resolve the underlying cause of the high CPU usage.
Frequently Asked Questions
Why is Service Host Diagnostic Policy Service using so much CPU?
High CPU usage is typically caused by corrupted system files, problematic drivers, damaged diagnostic logs, Windows Update issues, or software conflicts that repeatedly trigger diagnostic processes.
Is it safe to end the Diagnostic Policy Service process?
You can temporarily end the process through Task Manager, but Windows may restart it automatically. Permanently disabling the service is not recommended because it plays an important role in system diagnostics.
Can malware cause Diagnostic Policy Service high CPU usage?
Yes. Certain malware can interfere with Windows services or mimic legitimate processes, leading to unusually high CPU usage. Running a full malware scan is a good troubleshooting step if the problem appears suddenly.
Will updating Windows fix the problem?
It can. Microsoft frequently releases updates that improve system stability, fix bugs, and resolve issues affecting Windows services, including the Diagnostic Policy Service.
Conclusion
The Service Host: Diagnostic Policy Service is a core Windows component designed to keep your system healthy by detecting and troubleshooting hardware, software, and network problems. While it normally runs quietly in the background, corrupted system files, faulty drivers, damaged event logs, or software conflicts can cause it to consume excessive CPU resources and slow down your computer.
Fortunately, the issue can usually be resolved by restarting the service, repairing Windows with SFC and DISM, clearing diagnostic event logs, updating device drivers, or performing a Clean Boot to identify conflicting software. Additional maintenance tasks, such as installing Windows updates and scanning for malware, can further improve system stability.
By following the five methods in this guide, you should be able to restore normal CPU usage and enjoy a smoother, more responsive Windows 10 or Windows 11 experience without disabling important system services.
