Diagnostic Policy Service High CPU Usage Error

Tech News

The Diagnostic Policy Service, or the DPS, is a troubleshooting service that detects any problem with the Windows component and tries to fix the issues it finds. The Service, when it is running, may take high CPU usage. However, it is a cause for concern if the process constantly uses high CPU resources.

You will see performance drop when the CPU uses most of its resources. This happens because once the CPU reaches high temperature due to maximum usage, the processor lowers its performance to prevent itself from any damage. This means that the CPU will start thermal throttling.

Now, without further delay, let us know more about the Diagnostic Policy Service. 

What Is Diagnostic Policy Service?

The Diagnostic Policy Service works like a troubleshooting mechanism that detects and troubleshoots problems that Windows may face. This Service runs in the background and starts detecting any issues with the PC once the system loads OS into the primary memory.

Without Diagnostic Policy Service, Windows cannot detect and fix issues with the OS or the system that may come up. 

How To Check Diagnostic Policy Service CPU usage?

When the process runs, it should take ten to fifteen megabytes of memory, and the taskbar should indicate 0% CPU usage. However, it can take more depending on whether it is running. However, you should take necessary measures to remove the DPS service if it takes extreme CPU resources, memory, or disk usage.

Follow the steps mentioned below to check the Diagnostic Policy Service resources in use.

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Click on More Details if the task manager shows tasks that are currently running.
  3. Click on the Processes tab.
  4. Under Windows processes, search for Service Host: Display Policy Service.
    diagnostic policy service task manger

Here, you can see all the resources that this process takes. If you see that the Service is taking high CPU, memory, or disk usage, you need to perform the necessary steps to lower them.

What Makes Diagnostic Policy Service Use High CPU Resources?

When the Diagnostic Policy Service tries to fix any issues, it may use high CPU resources. However, it is not a problem unless the process constantly takes an extreme amount of CPU and memory resources.

If this process is taking a lot of CPU usage, here are some possible reasons that might be causing it.

  • Corrupted System Files
  • Windows not up-to-date
  • SRUDB.dat file causing the issue
  • A problem with the Windows Update

How to Fix Diagnostic Policy Service High CPU Usage?

Before we get into the solutions, make sure you wait for a few minutes. As this is a genuine process that may use CPU resources when running, CPU resources may decrease once the process completes. 

If it does not, perform the solutions mentioned below to fix Diagnostic Service High CPU Usage.

Disable Service

You have full control over the Windows service that runs in the background. You can choose whether the application runs on startup, start, or stop its process. Therefore, disabling the Diagnostic Policy Service will release any resources that this Service uses.

Here are three different ways you can disable Diagnostic Policy Service. If one does not work, you can try the other methods.

Using Services

Follow the steps mentioned below to disable the Service using Services.

  1. Press the Windows + R key to open Run.
  2. Type services.msc to open Services.
  3. On the Right Panel, search for Diagnostic Policy Service.
  4. Double-click on it.
  5. On the General tab, under Service status, click on stop.stop diagnostic policy service
  6. Now click on Apply.
  7. If the Service automatically starts again, set Startup Type to Manual.
    manual diagnostic policy service
  8. Select Apply, then OK.

From System Configuration

If Services does not allow you to disable this process, you can try disabling it from System Configuration.

  1. Press the Windows + R key to open Run.
  2. Type msconfig to open System Configuration.
  3. Go to the Services tab.
  4. Uncheck Diagnostic Policy Service.
    disable diagnostic policy service
  5. Select Apply, then OK.
  6. Restart your PC to stop Diagnostic Policy Service from running.

From Registry Editor

The Registry in Windows holds all computer settings. And this includes settings like whether a Service starts. Follow the steps mentioned below to disable the Diagnostic Service Policy from Registry Editor.

Before making any changes, make sure to back up the registry.

  1. Press the Windows + R key to open Run.
  2. Type regeditand press Enter to open Registry Editor.
  3. Navigate to ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesDPS
  4. On the right panel, double-click on Start.
    change registry value DPS
  5. Under Value data, set the value to 4.change value data
  6. Press OK.
  7. Restart your computer to save the changed settings.

Setting the Value data to 4 will disable the process from starting automatically.

Delete SRUDB DAT File

When Diagnostic Policy Service troubleshoots your system, it creates a log file named SRUDB.dat that stores all the details about the error and fixes. This file may take a lot of disk space, and accessing them may cause high CPU usage. 

You can delete this file to see if it fixes the issue. You do not need to worry, as the Diagnostic Policy Services will automatically create this file once the Service starts.

However, the OS will not let you delete the file if you have Diagnostic Policy Service running in the background. Therefore, you need to stop the Service before you delete the file.

  1. Open File Explorer and navigate to C:WindowsSystem32sru.
    delete srudb file
  2. Permanently delete the SRUDB.dat file.

Change Power Plan

On a laptop, some services may malfunction if some devices’ power mode is not on maximum performance. Try changing this setting to see if the Diagnostic Policy Service uses fewer CPU resources.

  1. Press the Window + R key to open Run.
  2. Type powercfg.cpl to open Power Options.
  3. Under preferred plans, click on Change plan settings on the selected power plan.
  4. Click on Change advanced power settings.
  5. Expand Wireless Adapter Settings and also expand Power Saving Mode.
  6. Set both On battery and Plugged in as Maximum Performance.
    change power plan settings
  7. Click Apply, then OK.

Run SFC and DISM

The SFC (System File Checker) scans and repairs any corrupted system files, whereas the DISM (Deployment Image Servicing and Management) scans and restores the Windows image. 

As all the Services files and folders are located inside the system file, running these commands may fix any of its corrupted files that may have been causing the high CPU usage issue.

  1. Press the Window + R key to open Run.
  2. Type cmdand press Ctrl + Shift + Enter to run the command prompt as administrator.
  3. Type sfc /scannow and press Enter.
    sfc
  4. Once the process completes, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
    dism-restore-health
  5. Restart your computer and check the CPU usage.

Roll Back/Update Windows

Since the Diagnostic Policy Service is a Windows process and not a process running from a third-party application, it can be that a recent Windows update started the high usage issue. If you have recently updated Windows and you face high CPU usage, you can uninstall the recent Windows Update.

  1. Press the Windows + I key to open Settings.
  2. Go to Windows Update (Privacy & security > Windows update for Windows 10) > Update History.
  3. Scroll down and select Uninstall updates.uninstall windows updates
  4. Here you can see all the installed updates.
  5. Right-click on the latest Windows Updates and select Uninstall.uninstall-windows-updates

Clear Event Viewer Log

The event viewer logs any errors and warnings when the system runs into one. When this error log builds up, it may cause issues when the Diagnostic Policy Service tries to access the event log. To fix this, you need to clear the Event Viewer Log.

  1. Press the Windows + R key to open Run.
  2. Type eventvwr.msc to open the Event Viewer Log.
  3. On the left-most panel, expand Windows Logs and select Application
  4. On the right-most panel, click on Save All Events As…save event viewer
  5. Now choose a location and file extension to save the event log file.
  6. Again, on the right-most panel, click on Clear log.
    clear log
  7. Select Clear.

Run System Maintenance Troubleshooter

If none of the solutions works, you can try running the system maintenance troubleshooter to detect and fix any issues with the system. Even if it cannot fix the issue, it may be able to determine what’s wrong with the system.

  1. Press the Windows + R key to open Run.
  2. Type msdt.exe -id MaintenanceDiagnostic to open System Maintenance troubleshooter. 
  3. Click on Advanced and select Apply repairs automatically.
  4. Click on Next.
    run system maintenance troubleshooter
  5. Select Try troubleshooting as an administrator.
  6. Once the process completes, the troubleshooter will fix the issue or give you the reason you face the issue.

Sharing is caring!

Facebook Comments

Leave a Reply