Is your Windows 11 computer running slow? Are you noticing high CPU or memory usage that won’t go away? The Diagnostic Policy Service might be the culprit.
This essential Windows service helps detect and fix system problems, but sometimes it can cause issues of its own. In this complete guide, you’ll learn what the Diagnostic Policy Service does, why it might use too many resources, and exactly how to fix any problems with it.
Key Takeaways
- Diagnostic Policy Service (DPS) is a Windows service that detects and troubleshoots system problems
- High CPU or memory usage from DPS is often caused by corrupted log files or system errors
- You can fix most DPS issues by deleting the SRUDB.dat file or clearing Event Viewer logs
- It’s generally safe to disable DPS if you don’t need Windows troubleshooting features
- Windows 11 and Windows 10 handle DPS similarly, but Windows 11 has more efficient resource management
What Is Diagnostic Policy Service in Windows 11?
The Diagnostic Policy Service (DPS) is an important part of Windows 11 that works behind the scenes to keep your system healthy. Think of it as your computer’s health detective – it constantly looks for problems and either fixes them automatically or tells you what’s wrong.
This service runs automatically when you start your computer and works with other Windows components to:
- Detect hardware and software issues
- Run diagnostic tests when you use Windows troubleshooters
- Collect information about system problems
- Help Windows Update identify and fix issues
The diagnostic policy service in Windows 11 works similarly to how it does in Windows 10, but with better resource management. Microsoft has improved how Windows 11 handles system services, so DPS typically uses fewer resources than it did in previous versions.
Why Is Diagnostic Policy Service Using High CPU?
If you’ve opened Task Manager and noticed that “Service Host: Diagnostic Policy” is using a lot of CPU power, you’re not alone. This is one of the most common problems users face with this service.
The diagnostic policy service using CPU issues usually happen for these reasons:
- Large log files: DPS creates and manages log files that can grow very large over time
- System errors: When Windows has underlying problems, DPS works overtime to analyze them
- Corrupted files: Damaged system files can make DPS run in circles trying to diagnose issues
- Driver conflicts: Problematic hardware drivers can trigger constant diagnostic activity
You can identify if DPS is causing high CPU usage by:
- Opening Task Manager (Ctrl+Shift+Esc)
- Going to the “Details” tab
- Looking for “svchost.exe” processes
- Checking if any are labeled as “Diagnostic Policy Service”
Normal CPU usage for DPS should be 0-1% when idle. If it’s consistently above 5%, you have a problem that needs fixing.
How to Fix Diagnostic Policy Service High Memory Usage?
One of the most alarming issues users report is when the diagnostic policy service uses 5GB RAM or more. This can bring even powerful computers to a crawl. The diagnostic policy service high memory problem is usually related to the same issues that cause high CPU usage.
Here’s how to fix diagnostic policy service memory problems:
Method 1: Delete the SRUDB.dat File
The SRUDB.dat file stores diagnostic information and can grow to massive sizes. When this happens, DPS uses more and more memory trying to manage it.
- Press Windows+R and type services.msc, then press Enter
- Find “Diagnostic Policy Service” in the list
- Right-click it and select “Stop”
- Open File Explorer and navigate to C:\Windows\System32\sru
- Find the SRUDB.dat file and delete it (or rename it to SRUDB.old)
- Go back to Services, right-click Diagnostic Policy Service, and select “Start”
Method 2: Clear Event Viewer Logs
Windows event logs can become enormous, causing DPS to use excessive memory.
- Press Windows+R and type eventvwr.msc, then press Enter
- Expand “Windows Logs”
- Right-click on each category (Application, Security, Setup, System) and select “Clear Log”
- Restart your computer
Method 3: Run System File Checker
Corrupted system files can cause memory issues with DPS.
- Type “cmd” in the Windows search bar
- Right-click Command Prompt and select “Run as administrator”
- Type sfc /scannow and press Enter
- Wait for the scan to complete and restart your computer
How to Enable or Turn On Diagnostic Policy Service?
Sometimes the Diagnostic Policy Service stops running or gets disabled. When this happens, Windows troubleshooters won’t work properly. Here’s how to enable diagnostic policy service or turn on diagnostic policy service using different methods:
Method 1: Using Services App
- Press Windows+R and type services.msc, then press Enter
- Scroll down to find “Diagnostic Policy Service”
- Double-click it to open Properties
- Set “Startup type” to “Automatic”
- Click “Start” if the service isn’t running
- Click “Apply” and then “OK”
Method 2: Using Command Prompt
- Type “cmd” in the Windows search bar
- Right-click Command Prompt and select “Run as administrator”
- Type these commands one by one, pressing Enter after each:
- Line Wrapping
- Collapse
- Copy
- sc config DPS start=auto
- net start DPS
Method 3: Using System Configuration
- Press Windows+R and type msconfig, then press Enter
- Go to the “Services” tab
- Find “Diagnostic Policy Service” and check the box next to it
- Click “Apply” and restart your computer
If the service won’t start, you may need to fix system files or check for malware.
Should You Disable Diagnostic Policy Service?
There are times when you might want to disable diagnostic policy service, especially if it’s causing persistent performance issues. However, it’s important to understand what you’ll lose:
What You’ll Lose:
- Windows troubleshooters won’t work
- Problem detection and reporting will be disabled
- Some Windows Update features may not function properly
- System health monitoring will be limited
When to Disable:
- If DPS is consistently using 30%+ CPU or several GB of RAM
- When you’ve tried all other fixes and nothing works
- If you don’t use Windows troubleshooters anyway
- When you need maximum performance for gaming or professional work
How to Disable:
- Press Windows+R and type services.msc, then press Enter
- Find “Diagnostic Policy Service” and double-click it
- Set “Startup type” to “Disabled”
- Click “Stop” if the service is running
- Click “Apply” and then “OK”
You can always re-enable it later if you need to use Windows troubleshooters.
Advanced Troubleshooting for Diagnostic Policy Service
If the basic fixes didn’t work, here are some advanced solutions:
Run DISM Scan
DISM (Deployment Image Servicing and Management) can fix underlying Windows system issues that affect DPS.
- Type “cmd” in the Windows search bar
- Right-click Command Prompt and select “Run as administrator”
- Type these commands one by one, pressing Enter after each:
- Line Wrapping
- Collapse
- Copy
- DISM /Online /Cleanup-Image /CheckHealth
- DISM /Online /Cleanup-Image /ScanHealth
- DISM /Online /Cleanup-Image /RestoreHealth
- Restart your computer
Change Power Plan Settings
Sometimes, power settings can cause services to behave strangely.
- Type “edit power plan” in Windows search and press Enter
- Click “Change advanced power settings”
- Expand “Wireless Adapter Settings” > “Power Saving Mode”
- Set both “On battery” and “Plugged in” to “Maximum Performance”
- Click “Apply” and restart your computer
Check for Malware
Malware can sometimes disguise itself as system services.
- Run a full system scan with Windows Defender or your preferred antivirus
- Use Malwarebytes for a second opinion
- Check for unusual startup programs in Task Manager
| Normal DPS Behavior | Problematic DPS Behavior |
| CPU: 0-1% when idle | CPU: 5%+ consistently |
| Memory: 10-50MB | Memory: 500MB+ |
| Disk: Occasionally active | Disk: Constantly active |
| Starts with Windows | Fails to start or stops randomly |
Frequently Asked Questions
What exactly is Diagnostic Policy Service in Windows 11?
Diagnostic Policy Service is a Windows component that detects, troubleshoots, and helps resolve system problems. It works in the background to monitor your computer’s health and runs diagnostic tests when you use Windows troubleshooters. Think of it as your computer’s built-in health checker that constantly looks for issues and either fixes them automatically or alerts you to problems.
Why is Diagnostic Policy Service using so much CPU?
Diagnostic Policy Service typically uses high CPU when it’s trying to analyze large log files or when there are underlying system problems it’s attempting to diagnose. Common causes include corrupted system files, oversized diagnostic logs (especially the SRUDB.dat file), driver conflicts, or malware. The service gets stuck in a loop trying to diagnose the same issues over and over, consuming excessive CPU resources.
Is it safe to disable Diagnostic Policy Service?
Yes, it’s generally safe to disable Diagnostic Policy Service if you’re experiencing persistent performance issues. However, you’ll lose the ability to use Windows troubleshooters, and some automatic problem detection features won’t work. Only disable it as a last resort after trying other fixes, and remember that you can always re-enable it later if you need to run Windows diagnostics.
How do I fix Diagnostic Policy Service when it’s not running?
When Diagnostic Policy Service isn’t running, first try to manually start it through Services (press Windows+R, type services.msc, find the service, and click Start). If it won’t start, check for corrupted system files by running sfc /scannow in Command Prompt. You should also delete the SRUDB.dat file from C:\Windows\System32\sru folder after stopping the service, as a corrupted log file can prevent the service from starting.
Can Diagnostic Policy Service really use 5GB of RAM?
Yes, Diagnostic Policy Service can use up to 5GB of RAM in extreme cases, though this is not normal behavior. This usually happens when the SRUDB.dat file becomes corrupted or grows to an enormous size. The service tries to load and process this massive file, consuming huge amounts of memory. Deleting the SRUDB.dat file after stopping the service typically resolves this issue and brings memory usage back to normal levels (10-50MB).
Will deleting SRUDB.dat harm my system?
No, deleting the SRUDB.dat file will not harm your system. This file contains diagnostic data and logs that Windows can recreate when needed. When you delete it, Windows simply builds a new, clean log file the next time the Diagnostic Policy Service runs. In fact, deleting this file often fixes performance issues because it removes corrupted or oversized data that was causing the service to malfunction.
Conclusion
The Diagnostic Policy Service in Windows 11 is essential for system health but can sometimes cause performance issues. Whether you’re dealing with high CPU usage, memory problems like the diagnostic policy service using 5GB RAM, or the service not running at all, the solutions in this guide should help you get your computer back to normal.
Remember to start with the simplest fixes first – deleting the SRUDB.dat file and clearing event logs solve most problems. Only disable the service as a last resort. With these tools, you can keep your Windows 11 system running smoothly while still benefiting from Windows’ built-in diagnostic capabilities.
If you’re still having issues with system performance, check out our guide on how to fix laptop lag or learn about Windows 11 driver issues for more comprehensive troubleshooting help.
