Fix Diagnostics Policy Service Is Not Running Error on Windows 11/10

Windows may show “Diagnostics Policy Service Is Not Running” when you try to troubleshoot an internet, network, or other system problem. You may also notice that Windows Troubleshooter cannot detect or fix the issue because the required service is stopped. The Diagnostics Policy Service (DPS) is a built-in Windows service that helps detect, troubleshoot, and resolve problems with Windows components. If for some reason the service not started or stop running, Windows diagnostics may not work correctly. In many cases, restarting the service or correcting its startup settings is enough to resolve the problem. In this guide, we’ll look at the most practical ways to fix the Diagnostics Policy Service is not running error in Windows 11.

Why Does the Diagnostics Policy Service Stop Running?

The Diagnostics Policy Service (DPS) runs in the background and allows Windows to detect and troubleshoot problems. When it is not running, Windows may be unable to diagnose certain issues correctly.

The service can stop because of several reasons, including:

• The Diagnostics Policy Service was manually disabled.
• A Windows update or system change affected its configuration.
• Required Windows services are not running.
• Corrupted or damaged system files prevent the service from starting.
• A temporary Windows service or system glitch occurs.
• Security software or other system-management tools interfere with the service.

If your internet is working normally but Windows displays this message, the problem may be limited to the diagnostic service itself. However, if you are also experiencing network problems, fixing the service can help Windows identify the underlying connection issue.

Fix 1: Restart the Diagnostics Policy Service

The first thing to try is restarting the Diagnostics Policy Service. If the service has stopped because of a temporary Windows problem, restarting it may immediately clear the error.

1. Press Windows + R to open the Run dialog.
2. Type services.msc and press Enter.
3. In the Services window, find Diagnostics Policy Service.
4. Right-click it and select Restart.
5. If Restart is unavailable, select Start.
6. Double-click the service and check that Startup type is set to Automatic.
7. Click Apply and then OK.

Now run the Windows Network Troubleshooter again and check whether the error has disappeared.

Note: If the service starts successfully but stops again after restarting Windows, continue with the next fixes. Another service, damaged system files, or a configuration problem may be preventing DPS from running normally.

2. Check the Services Required by Diagnostics Policy Service

The Diagnostics Policy Service depends on other Windows services. If one of those services is stopped, DPS may fail to start or Windows may continue showing the error.

Open Services again by pressing Windows + R, typing services.msc, and pressing Enter.

Check these services:

• Diagnostic Service Host
• Diagnostic System Host
• Remote Procedure Call (RPC)
• Windows Management Instrumentation (WMI)

For each service, double-click it and make sure it is running. If a required service is stopped, click Start.

You generally don’t need to change the startup type of every service manually. RPC and WMI are core Windows components and are normally configured automatically by Windows. Focus on services that are stopped or disabled.

Restart your PC after making any changes, then try running the troubleshooter again.

3. Reset Network Components

If the “Diagnostics Policy Service Is Not Running” error appears while diagnosing an internet or network problem, corrupted network settings may also be involved. Resetting the main Windows networking components can clear configuration problems without changing your personal files.

Open Windows Terminal (Admin) or Command Prompt (Admin) and run these commands one at a time:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart your computer after running the commands.

Once Windows starts again, reconnect to your network and check whether the problem is resolved.

Note: The ipconfig /release and ipconfig /renew commands temporarily disconnect and reconnect your network connection. This is normal.

4. Update or Reinstall the Network Adapter Driver

If the Diagnostics Policy Service error appears along with Wi-Fi or Ethernet problems, a faulty or incompatible network adapter driver could be contributing to the issue. Updating or reinstalling the driver can help if the problem started after a Windows update or driver change.

• Press Win + X and select Device Manager.
• Expand Network adapters
• Right-click your Wi-Fi or Ethernet adapter and select Update driver.
• Select Search automatically for drivers and let Windows check for an available driver.

If no updates are found, uninstall the driver:

• Right-click the network adapter and select Uninstall device.
• Restart your PC to allow Windows to reinstall the driver automatically.

If Windows didn’t install the network adapter driver automatically, then download & Install the latest driver for the network adapter from the manufacturer’s website.

5. Run SFC and DISM to Repair Windows System Files

Corrupted or missing Windows system files can sometimes prevent built-in services from working correctly. Windows includes System File Checker (SFC) and Deployment Image Servicing and Management (DISM) to repair these components.

• Open Command Prompt as Administrator.
• First, DISM /Online /Cleanup-Image /RestoreHealth
• Wait for the scan to complete. It may take several minutes.
• Then run: sfc /scannow

The sfc command, scans for and repairs corrupted or missing Windows system files, while DISM Restorehealth scans and repairs the underlying Windows image, including the component store where system files are stored

6. Use System Restore

If the “Diagnostics Policy Service Is Not Running” error started after a recent Windows update, driver installation, or software change, System Restore can help undo that change without affecting your personal files.

System Restore uses restore points to return Windows system files, drivers, registry settings, and installed programs to an earlier state.

1. Press Windows + R, type rstrui.exe, and press Enter.
2. Select Next to view the available restore points.
3. Choose a restore point created before the Diagnostics Policy Service problem started.
4. Click Next > Finish and allow Windows to restart.

If no restore points are available, this option cannot be used. Also, System Restore does not normally remove personal files such as documents, photos, or other personal data, but applications or drivers installed after the selected restore point may be removed.

What to Do If Diagnostics Policy Service Still Won’t Start

If the Diagnostics Policy Service still refuses to start after checking its settings and dependencies, the problem may be related to corrupted Windows components or a damaged system configuration.

Before making advanced changes to the registry, try these safer options:

• Restart Windows: A temporary service or system problem can sometimes be cleared by a normal restart.
• Install pending Windows updates: Open Settings > Windows Update and install any available updates, then restart your PC.
• Run System File Checker: Corrupted Windows system files can prevent services from working correctly. Open Command Prompt as administrator and run sfc /scannow.
• Run DISM: If SFC cannot repair the problem, run DISM /Online /Cleanup-Image /RestoreHealth, then restart Windows and run SFC again.

If DPS continues to fail after these steps, look at the exact error shown when you try to start the service. That message can provide a better indication of whether the problem is caused by a dependency, permissions, or damaged Windows components.

Avoid changing registry permissions or deleting service entries just to make DPS start. Incorrect changes to Windows services can create additional problems.

Frequently Asked Questions