Skip to content

In this article, learn how to fix Service Host: Diagnostic Policy Service high CPU usage problem for your Windows 10/8.1/8.

Diagnostic Policy Service is there in Windows OS to detect, troubleshoot and resolve issues with Windows Components. When this service is disabled, diagnostics will no longer be functioning. Since this is a background service and is needful for Windows, it is automatically started when you start your system and keeps running.

But sometimes you may notice high CPU usage with Diagnostic Policy Service. This is not desirable for a background service. High CPU usage from a single process makes the system slower to respond other processes and you face lagging problem. Checkout the below shown screenshot which shows high CPU usage from Diagnostic Policy Service.

FIX Service Host Diagnostic Policy Service High CPU Usage In Windows 10

If you’re also victim of this problem, this article is for you. Try below mentioned suggestions and see if they helps you to fix it:

FIX: Service Host: Diagnostic Policy Service High CPU Usage In Windows 10

FIX 1 – General Suggestions

1. First of all, try ending the task process and let it restart itself. See if high CPU usage occurs from the process now. If this continues, reboot the machine.

2. Run the System File Checker scan or run DISM commands to repair inbox corruption.

3. Try creating new user account and check if the problem persists on that.

4. Make sure you install latest Windows Updates.

5. Run System Performance troubleshooter.

6. Update your machine’s BIOS firmware to latest version.

7. Make sure you’ve latest drivers installed on the system.

FIX 2 – Via File Explorer

1. Press W8K + R and type following in Run dialog box, press Enter key:

%WinDir%\System32\sru

FIX Service Host Diagnostic Policy Service High CPU Usage In Windows 10

2. In the sru folder so open, locate the SRUDB.dat file and delete it.

FIX Service Host Diagnostic Policy Service High CPU Usage In Windows 10

Close File Explorer and restart your system.

FYI: If you’re unable to delete SRUDB.dat file due to file being used by Diagnostic Policy Service, you need to first set the Diagnostic Policy Service policy startup type as Disabled. Then you can easily delete the file. You can also delete the file from recovery mode Command Prompt.

Hope this helps!


Facebook Google+ Twitter

4 Comments

  • I made a batch file which stoppes the service and prompts the user to delete the folder. Then the service is startet again. Just create a text file and insert following code. Then save as .bat file. You need to start the bat as admin though.

    nofile.io/f/w2cdg4n8TSZ/fixDPSservice.bat

  • Kapil Arya

    ^^ Thanks for your inputs, much appreciated 😎

  • So far the problem is gone and the folder even is not created anymore :)

  • Kapil Arya

    ^^ 😊

  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    Recent Comments

    • Michele Schenk : Hello Kapil, I've tried every option I can find online to fix this, bu...

      8 hours ago

    • Kapil Arya : ^^ You can create it manually and set it to 1....

      21 hours ago

    • Mayank Date : I'm using Win 8.1. The longpathsenabled file is missing from my regist...

      21 hours ago

    • Rose McMillan : Hey Kapil, Thank you for your reply. Unfortunately, I'm not confident ...

      1 day ago

    • Kapil Arya : ^^ You're most welcome, Prashant!...

      2 days ago