The Diagnostics Policy Service is a Windows background service responsible for detecting and troubleshooting network-related issues. If for some reason the service not started or stop running you may experience problems with internet connectivity, network diagnostics, and troubleshooting tools. Usually, you may get error message “Diagnostics Policy Service is not running” when attempting to diagnose a network issue through Windows Troubleshooter. Well, this error can occur due to several reasons, including corrupted system files, misconfigured service settings, missing permissions, or conflicts with third-party software. This article explores a few appropriate fixes that can help fix the problem and restore normal network functionality.
Post Contents :-
Restart the Diagnostics Policy Service
If the service is stopped or not functioning properly, restarting it can help restore normal operation.
- Press Win + R, type
services.msc, and press Enter to open the Services window. - Locate Diagnostics Policy Service in the list.
- Right-click on it and select Restart.
- If the service is stopped, right-click and select Start.
- Double-click the service, set the Startup type to Automatic, then click Apply and OK.
- Restart your computer and check if the issue is resolved.
Grant Administrator Permissions to the Service
If the service lacks the necessary permissions, it may not start properly. Manually granting it administrative privileges can help.
Open Command Prompt as Administrator (Press Win + X, then select Windows Terminal (Admin)). Type the following commands one by one and press Enter after each:
net localgroup Administrators /add networkservice
net localgroup Administrators /add localservice
Close the Command Prompt and restart your computer. This method ensures that the Diagnostics Policy Service has the necessary permissions to run correctly.
Reset Network Components
Again Corrupt network settings can interfere with the Diagnostics Policy Service. Resetting network components clear any incorrect configurations that may be preventing network services from functioning properly.
Open Command Prompt as Administrator, Type the following commands one by one and press Enter:
netsh winsock reset
netsh int ip reset
Close the command prompt, Restart your computer and check if the service is running.
Update or Reinstall Network Drivers
Outdated or faulty network drivers can interfere with network services, including the Diagnostics Policy Service. If both the above solutions don’t work, reinstalling the network adapters might fix the problem instantly.
- Press Win + X and select Device Manager.
- Expand Network adapters and right-click your active network adapter.
- Select Update driver and choose Search automatically for drivers.
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.
Disable Third-Party Antivirus or Firewall
Some third-party security software can interfere with Windows services. Temporarily disabling them can help determine if they are the cause.
- Open your third-party antivirus or firewall software.
- Disable real-time protection and any firewall settings.
- Restart your computer and check if the Diagnostics Policy Service is running.
- If disabling the software resolves the issue, consider adjusting security settings or switching to Windows Defender.
Perform a System File Check (SFC) and DISM Scan
If the Diagnostics Policy Service is failing due to corrupt system files, running SFC and DISM scans can help repair Windows components.
- Open Command Prompt as Administrator.
- First, run sfc /scannow command then DISM /Online /Cleanup-Image /RestoreHealth
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
Perform a System Restore
Again if the issue started after a recent update or software change, restoring Windows to a previous working state can help fix the problem.
- Press Win + R, type
rstrui, and press Enter. - Select Next and choose a restore point before the issue occurs.
- Click Next and then Finish to restore your system.
- Wait for Windows to restart and check if the error is resolved.
