Fix 'Diagnostics Policy Service Is Not Running' in Windows 8 or 8.1 (Historical)

The Diagnostic Policy Service, whose service name is DPS, supports Windows troubleshooting. A message saying it is not running tells you that the diagnostic process needs attention. It does not, on its own, identify why a network connection failed.

This guide is for existing Windows 8/8.1 installations, which are out of support. Record the service's current configuration before changing it. Microsoft’s newer Windows client policy documentation confirms the relationship between DPS and diagnostic execution, but its modern management settings are not a Windows 8 repair recipe.

1. Separate the diagnostic warning from the original symptom

Write down what you were trying to troubleshoot and the exact message. Can the PC open two unrelated websites, or is only the troubleshooter failing? Does another device work on the same network? A working connection with a broken diagnostic tool needs a different investigation from a shared network outage.

If this is a work or school computer, record whether an administrator, security product or previous “optimization” changed services. Do not override centrally managed settings. Keep the two questions separate: can DPS run? and does the original task work?

2. Inspect the service without changing its account

1. Press Win + R, enter services.msc and press Enter.
2. Open Diagnostic Policy Service. Confirm its service name is DPS.
3. Record its status, startup type and Log On account. Use the Dependencies tab to inspect the configuration actually present; do not assume a dependency list copied from another Windows release is correct.
4. If the service is stopped and not intentionally disabled, use an authorized administrator session to select Start once. Record the time and exact result.

For a text record of its state, open Command Prompt and run this read-only query:

sc.exe query DPS

The query reports service state and related status fields. RUNNING means the service is running at the time of the query; it does not prove that the network is fixed. Keep a dialog's start-error code separately from the query output. If access to the query itself is denied, record that rather than assuming the service has returned a startup failure.

If you know a previous local tweak disabled DPS, restore the recorded prior setting. If you do not know why it was disabled, have the administrator compare it with the intended configuration for that installation. The Windows Server service-default table formerly cited here is not sufficient evidence to reset every Windows 8 client to the same configuration.

3. Follow the actual start result

Open Event Viewer > Windows Logs > System and inspect Service Control Manager entries around the attempt. Preserve the service name, error text and time. If several services fail together, that broader pattern matters more than repeatedly starting DPS alone.

4. Check system integrity only where it fits

If the service configuration is appropriate but missing or damaged Windows files are suspected, back up important data and use Command Prompt as administrator:

sfc /scannow

Read the final result. A clean result does not validate service permissions or prove networking works. If files were repaired, restart normally and repeat the service and original-task checks. If SFC cannot finish or cannot repair files, record that outcome before adding more commands. For Windows 8/8.1 component-store evidence and repair-source limits, see the historical servicing guide.

5. Keep privilege changes out of a generic fix

If an older workaround already changed membership or permissions, give the administrator the exact commands and original configuration if known. Have them plan a scoped reversal and verify dependent applications; do not apply an unverified “reset permissions” script.

For a network complaint, change an adapter driver only when separate evidence points to that adapter—for example, a specific Device Manager error or a known incompatible driver. Reinstalling network hardware does not establish why DPS could not start.

Verify and hand over the evidence

After an authorized repair, confirm the service state, retry the same troubleshooter and retest the original task. Record these as three results. If only DPS is restored, say so; a successful service start is not a successful Internet repair.

For support, provide Windows version → original symptom → DPS status/startup setting → attempted action and time → exact error/event → integrity-check result → retest. Remove unrelated device and user identifiers before posting logs publicly.

Documentation review: 30 October 2026. Based on Microsoft service, account, error-code and integrity references. Current client documentation is used for the diagnostic relationship, not as a tested Windows 8 configuration. No DPS failure was reproduced or repaired for this revision.

Official references