In some cases though, the troubleshooter itself might not run, showing error messages like: “The Diagnostics Policy Service is not running”. As the message implies, the diagnostic service necessary for the troubleshooter or some related dependencies are likely not running, which leads to this issue. As such, simply ensuring the necessary services and processes are running will resolve this issue most of the time. We’ve listed step-by-step instructions for these and more solutions in this article.
How to Fix Diagnostics Policy Service Not Running?
Also referred as DPS, the Diagnostic Policy service runs automatically in the background to investigate and log issues related to Windows components. The methods listed below will ensure a suitable environment for the Diagnostic Policy Service to run:
Check and Automate the Service
Diagnostics Policy Service is a native Windows service that can be managed through the Services utility or the Registry Editor. You might have stopped the service while trying to free up CPU usage, or accidental tweaks in the registry might have disabled it. In any case, the following steps will guide you to check the status of the service and enable it if it’s not already: Even after you run the service, if it isn’t set to automatic startup type, you will encounter the same issue after each reboot. The DPS service should be started automatically, along with Windows boot, and run in hand with svchost.exe to prepare diagnostic logs constantly. You can follow the steps mentioned below to ensure automatic startup:
Automate Logging Processes
If Diagnostics Policy Service didn’t work after starting the service, some other required services and processes required might have stopped or not started automatically. Various logger processes under Autologger and other applications are needed to be automated to make DPS function. Before moving forward, consider backing up your Registry because the process involves making changes to the registry. Follow the steps mentioned below to run the command and automate the processes: If these changes don’t work, some other changes in the registry might be the cause of the issue. Narrowing down every change isn’t feasible, especially any unknown changes. Rather, perform a system restore to any healthy point (if you have created a restore point), which will help you to restore the registry and fix the problem.
Reinstall Network Drivers
Since the DPS is not running problem prompts while troubleshooting Network related issues, corrupted network drivers may be the reason. So, reinstalling Network Drivers can sometimes fix the problem. However, you may have to reconfigure your wifi settings after the reinstall. The steps to do so have been listed below:
Provide Network Modules With Admin Access
Although in rare cases, not providing administrator access to the localservice and networkservice can cause network diagnosing issues. To fix this, you can run the following command in Command Prompt (with admin privileges):
net localgroup Administrators /add localservicenet localgroup Administrators /add networkservice
