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

Leave a Reply

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

Recent Comments

  • Kapil Arya : ^^ Glad to help Alex 😎...

    3 hours ago

  • Alex : You actually are a lifesaver. All the different tutorials I saw never...

    3 hours ago

  • Madiha : I am getting the same issue while updating app version. First time it ...

    6 hours ago

  • Kapil Arya : ^^ You're most welcome Helekesite 😊...

    9 hours ago

  • Helekesite Vui : thank you very much. you're one of the best....

    11 hours ago

  • Kapil Arya : ^^ Try Network Reset first: https://www.kapilarya.com/how-to-reset-net...

    1 day ago

  • Kapil Arya : ^^ Make sure you're admin and running Command Prompt as administrator....

    1 day ago