Suddenly you might notice that your system has become slower and upon further investigation, you might find that a process named svchost.exe, linked to Diagnostic Policy Service, is taking up lots of your CPU power and memory. Other symptoms include your system heating up soon or the laptop fan becoming too loud. Nothing in the error logs, no traces of the problem creator. Worried? Don’t be! Please follow the simple methods listed below, to solve this issue super quick.
Table of Contents
Method 1: Stop the Process From Task Manager
The simplest of all the solutions is to stop the task from task manager and let it restart itself. Once it restarts, observe for a while and see if the problem is resolved or not.
1. Right click on an empty space in your taskbar and then click on the Task Manager option from the right click context menu.
2. By default, Task Manager would open up with the Processes tab. Under the processes tab, you have to scroll down and locate the section named Windows processes. Under Windows processes, you have to find the process named Service Host: Diagnostic Policy Service. Right click on it and then from the right click context menu, choose the option End task.
3. Now you will get a UAC window asking for your confirmation on shutting down the system process Service Host: Diagnostic Policy Service. Make sure to check the checkbox Abandon unsaved data and shut down to make the Shut down button active and once it comes active, click on it.
That’s it. The process will restart itself in a few seconds. Once it restarts, observe for a while and check if your problem is gone. If not, head on to the next method.
Method 2: Stop the Service from Services Manager
1. Bring up the Run window by pressing the keys WIN + R together. As next, in the Run command box, type in services.msc and then hit Enter key.
2. Now when the Services window launches, scroll down and find the service by the name Diagnostic Policy Service. Double click on this Service listing to open its Properties window.
3. We need to stop this service. For that, under the General tab, click on the Stop button as shown in the screenshot below. When you get notified that the Service has been stopped, you can press the OK button and exit.
Restart your PC and check if your problem is resolved or not.
Method 3: Delete the SRUDB.dat file from the SRU Folder
If the above 2 methods do not work, we have to delete the SRUDB.dat file from the sru folder. The SRUDB.dat file is related to Diagnostic Policy Service service. This file sometimes could grow extremely large and can cause a lot of memory consumption. When we delete this file, mostly the issue of Diagnostic Policy Service service taking up lots of CPU power goes away with it. Follow the simple steps listed below to achieve the same:
1. Launch the Run dialog box by pressing the WIN + R keys together. Once it opens up, copy paste the following and then press the Enter key.
2. You might now be notified that you do not have enough permissions to access the sru folder. In that case, just hit the Continue button.
3. You will now be able to view all the files in the System folder sru. Locate and right click on the file that is named SRUDB.dat. From the right click context menu, click on the Delete option.
4. If you by chance get the message saying that SRUDB.dat file cannot be deleted because Diagnostic Policy Service is using it, then you have to open the Diagnostic Policy Service and disable it to successfully delete the SRUDB.dat file.
For that, just like how it was done in Method 2, launch services.msc from Run window, scroll down through the services listings, locate and then double click on the service listing Diagnostic Policy Service. When its Properties window launches, click on the drop down menu associated with the option Startup type and then choose the option Disabled.
5. Now the service will be disabled. Hit Apply button first and then OK button.
6. Now you can try deleting the SRUDB.dat file again. This time it should get deleted without any problems.
7. Diagnostic Policy Service is an essential Windows service and it should restart itself with your next Windows reboot. However, just to be on the safer side, once you are done with deleting the SRUDB.dat file, you can go back to the Diagnostic Policy Service properties window again, and enable the service back. For that, click on the drop down menu associated with Startup type option and then choose Automatic from the list of options. Once you are all set, hit Apply button and then OK button.
That’s it. Restart your machine, keep it under observation for some time and check if it’s all good this time. One of the above methods should definitely fix your issue.
Someone who is in love with writing and technical tricks & tips.