The diagnostic service is blocked, what should I do? Fixing the "Diagnostic Policy Service is not running" error

Youtube

You can configure the operation of services in a special Windows manager. To open it, use the Windows + R key combination, enter services.msc in the line that appears and press Enter. You will see the same or similar (if you have one of the older OS versions) window:

The manager displays services in table form. Here you can view a list of available services, read their brief descriptions, and find out their current status. Of particular importance is the “Startup Type” column. It is he who shows whether a specific service is enabled and in what mode it is launched by the system.

By double-clicking on one of the services, you will open a window in which you can disable it. Just open the “Startup Type” item, select “Disabled” and click “OK”. But among other launch options there is a “Manual” value. For security reasons, select this for all services that you want to disable. This will allow the system to start services when they are really needed, and not waste time on them the rest of the time.

Do not disable services completely, but only switch them to manual mode.

The services listed below are not critical to the operation of the system, and many users can do without them. Therefore, you can set these services to manual mode. Be sure to read the summary before making changes so you don't interrupt services that matter to you.

Some services on our list may already be completely disabled on your PC or initially work in manual mode. In that case, just skip them.

Incorrect actions during the process of configuring services can lead to incorrect operation of the system. By making changes, you take responsibility.

For the changes to take effect, be sure to restart your PC after configuration.

Windows services that can be switched to manual mode

The Russian names of some services on this list may differ from those that you see on your computer. But this only applies to wording. If you cannot find the service you need by its exact name, look for options that are similar in meaning.

Windows 10

Functionality for connected users and telemetry (Connected User Experiences and Telemetry).
Diagnostic Tracking Service.
dmwappushsvc.
Downloaded Maps Manager - if you are not using the Maps application.
Touch Keyboard and Handwriting Panel Service.
Windows Defender Service.

Windows 8/8.1

Diagnostic Policy Service.
Distributed Link Tracking Client - if the computer is not connected to any network.
IP Helper - if you are not using an IPv6 connection.
Program Compatibility Assistant Service.
Print Spooler - if you don't have a printer.
Remote Registry - this service can be completely disabled.
Secondary Logon.
Security Center.
NetBIOS support module over TCP/IP (TCP/IP NetBIOS Helper).
Windows Error Reporting Service.
Windows Image Acquisition (WIA) - if you don't have a scanner.
Windows Search - if you don't use Windows Search.

Windows 7

Computer Browser - if the computer is not connected to any network.
Diagnostic Policy Service.
Distributed Link Tracking Client - if the computer is not connected to any network.
IP Helper - if you are not using an IPv6 connection.
Offline Files.
Portable Device Enumerator Service.
Print Spooler - if you don't have a printer.
Protected Storage.
Remote Registry - this service can be completely disabled.
Secondary Logon.
Security Center.
Server - if the computer is not used as a server.
NetBIOS support module over TCP/IP (TCP/IP NetBIOS Helper).
Windows Error Reporting Service.
Windows Search - if you don't use Windows Search.

Windows Vista

Computer Browser - if the computer is not connected to any network.
Desktop Window Manager Session Manager - if you are not using the Aero theme.
Diagnostic Policy Service.
Distributed Link Tracking Client - if the computer is not connected to any network.
Offline Files.
Portable Device Enumerator Service.
Print Spooler - if you don't have a printer.
ReadyBoost.
Remote Registry - this service can be completely disabled.
Secondary Logon.
Security Center.
Server - if the computer is not used as a server.
Tablet PC Input Service.
NetBIOS support module over TCP/IP (TCP/IP NetBIOS Helper).
Themes - if you are using the classic Windows theme.
Windows Error Reporting Service.
Windows Media Center Service Launcher.
Windows Search - if you don't use Windows Search.

Windows XP

Alerter.
Computer Browser - if the computer is not connected to any network.
Distributed Link Tracking Client - if the computer is not connected to any network.
Indexing Service - if you don't use Windows Search.
Internet Firewall (ICF) / Internet Connection Sharing (ICS).
Messenger service.
Remote Registry - this service can be completely disabled.
Secondary Logon.
Server - if the computer is not used as a server.
System Restore service.
NetBIOS support module over TCP/IP (TCP/IP NetBIOS Helper).
Uninterruptible Power Supply.
Upload Manager.
Wireless configuration (Wireless Zero Configuration).

In some cases, when you launch an application that works directly using a network connection, an error is displayed stating that the Windows 10 Diagnostic Policy Service is not running. This error is related to the network connection settings and it implies that you do not have enough rights to make changes to these settings. At the same time, many people mistakenly believe that they are logging in as administrators, but this is not true since some applications still have to be run as an administrator. You can fix the error using other applications that need to be run as an administrator.

Using Registry Editor

Open the Registry Editor, and to do this, press two keys on the keyboard at once WIN+R. Then enter the command in the window that opens regedit and click OK.

In the registry editor, change the Diag permission

In the registry editor that opens, expand the branch HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\VSS\Diag. Then you need to move the cursor over the last Diag item and press the right mouse button. A context menu will open in which you need to select the item Permissions.

If the Diagnostic Policy Service is not running Windows 10, then you need to allow Network Service full access

A window will open in which you find and click on the item Network Service, and below check the box Full access and click OK. After this, restart your computer.

Using services

Open services by pressing two keys on the keyboard at once WIN+R, enter the command in the window that opens services.msc and click OK.

IPSec Security Agent Service

In the window that opens, under the name Services, find the item IPSec Security Agent and open its properties.

Stopping the IPSec Security Agent service

In the window that opens, set the startup type Manually and click OK. Then in the window called Services, find the item Diagnostic Service Node and also set the startup type to manual in its properties. After that, close the Services window and restart the computer.

Using the command line

Open the command line, and to do this you need to press two keys on the keyboard at once WIN+R and enter the command in the window that opens cmd and click OK.

Command Prompt Fixes Diagnostic Policy Service Not Started Error

In the command line window that opens, enter the command pconfig /release ipconfig /renew ipconfig /flushdns netsh int ip reset c:\log1.txt netsh winsock reset c:\log2.txt shutdown -r -t 0 (reboot the terminal) and press Enter. After this, restart your computer. You can also try entering the command net localgroup Administrators /add networkservice net localgroup administrators /add localservice exit and press Enter. After this command you will also need to restart your computer.

The error often appears on computers with “pirated builds” of Windows 7,8,8.1 operating systems. I also recorded a similar error several times on licensed systems.

The main symptom is the inability to obtain network connection settings; it is impossible to connect to a computer network via LAN. A similar entry is recorded in the system logs:
The Network and Sharing Center reports that the child service could not start.
Windows Network Diagnostics reports: The Diagnostic Policy Service is not running.

There are several ways to fix the problem; I suggest some of the ones that work.

Method 1: Reset IP and DNS settings for all network connections.
The method only works if the designated services are disabled, which is quite rare.
Commands are executed on the command line (call command line Win+R, cmd Enter). At the end of entering the command, press Enter.
Resetting and getting a new IP from the DHCP server:
ipconfig /release
ipconfig /renew
Reset DNS cache:
ipconfig /flushdns
Complete reset of TCP/IP protocol pool and Winsock protocol settings:
netsh int ip reset c:\log1.txt
netsh winsock reset from:\log2.txt
After resetting the settings, you need to restart the computer; in the command line, this can be done with the command:
shutdown -r -t 0

Method 2: Starting system services
In a number of cases, the required services were unknowingly disabled by the user himself while setting up the computer through system optimizers or a third-party firewall. To run you need to call the snap-in Services in any available way.
Standard access path: Start/Control Panel/System and Security/Administration/Services
In this snap-in you need to check the status of the following services:
IPsec Policy Agent
Diagnostic Policy Service
Diagnostic Service NodeDiagnostic system unit
For the first two you need to set the launch method Automatically, for the remaining - Manually
After this, you need to restart your computer.

Method 3. Adding access rights for the network subsystem.
From here
The solution is somewhat collective farm, so I haven’t tested it myself, but according to reviews online, it sometimes works.
We open access to drive C: to LOCAL SERVICE services through the system shell, and not through the line. For this:
Launch Explorer
Right-click on Drive C and select “Properties” from the drop-down menu
In the tabs at the top, select the “Security” snap-in
Under the "Group and Users" list, click "Edit"
Next, click “Add”, in the next window “Select: “Users and Groups” click “Advanced”. Next, we look for groups of users registered in the system. In the search results we look for the service “LOCAL SERVICE”, then to all questions OK and where denied access, just continue. Then reboot the system.

Method 4: Allow network services to write to the system registry.
From here
This type of error occurs when the Network Service group is not granted full access to the Diag directory in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es\VSS registry key or the Volume Shadow Copy Service system registry value is corrupted.
To fix the problem, open the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es\VSS branch in the registry editor, right-click on the Diag folder, select "Permissions...", select the Network Service group, check the Full Control box in the "Allow" field ", click the "Apply", "OK" buttons. If the Diag branch is missing, create it manually and perform all the described manipulations.
After performing the manipulations, restart your computer.

Method 5: Add Network Services to the Administrators security group
In fact, repeating the operations from method 3, but without unnecessary body movements and wasting time waiting and applying settings. I tested the method myself and it works.

For English system:

net localgroup Administrators /add networkservice
net localgroup Administrators /add localservice
exit
Reboot the computer.

For a Russified system:
In any available way, launch cmd with Administrator rights and execute the following commands:
net localgroup Administrators /add networkservice
net localgroup administrators /add localservice
exit
Reboot the computer.

There are other ways to eliminate this error, for example, by editing local policies, but the above are enough for me. I have not yet come across any cases where at least one of them did not work.

Some users may experience problems with their PC network connection. When they try to fix this problem, they activate the troubleshooter, which displays the message “The Diagnostic Policy Service is not running.” In this material, I will tell you what the essence of this dysfunction is on Windows 7,8.1,10, what its determinants are, and how to fix the “Diagnostic Policy Service is not running” error on your PC.

English version of the error “The Diagnostic Policy Service is not running”

Typically this issue occurs when the "Diagnostic Policy Service" (eng. “Diagnostic Policy Service”), tries to start, encounters a number of errors, and then stops working.

Most often this is due to an unofficial (hacked) version of Windows OS installed on the computer, which does not always work correctly.

However, the appearance of this message may indicate problems with the network, as well as the lack of rights for the user to change system settings.

Solving the problem “Policy Service Is Not Running”

How to get rid of "Diagnostic Policy Service is not running"

To correct this dysfunction, I recommend using several methods, which I will outline below. In most cases, to restore stable functionality of the diagnostic policy service, the first method is enough to help get rid of the error on your PC.

Method number 1. Using the command line

This method is statistically recognized as the most effective in fixing the “Diagnostic Policy Service is not running”, helping the vast majority of users.

Run the command prompt as an administrator by clicking on the “Start” button, in the search bar enter cmd, but enter don't press.
The found cmd program will appear at the top, move the cursor over it and right-click ().
From the menu that appears, select “Run as administrator.”
In the command line that opens, enter the following commands sequentially, remembering to press enter after each of them:

net localgroup Administrators /add networkservice
net localgroup administrators /add localservice

If you have an English version of Windows, then these lines should look like this:

net localgroup Administrators /add networkservice
net localgroup Administrators /add localservice

After successfully executing these commands, restart your PC and the problem should go away.

Method number 2. Check the status of the Diagnostic Policy Service service

Click on the Start button, type services.msc in the search bar and press enter.
In the list of services that opens, find “Diagnostic Policy Service” and double-click on it to enter its settings.
Make sure the service is running, if necessary set the Startup Type option to Automatic and save the changes.

Method No. 3. Reset network settings

Launch the command line as an administrator (how to do this is described above), and sequentially enter the following commands into it, remembering to press enter after each of them:

ipconfig /release

ipconfig /renew

ipconfig /flushdns

netsh int ip reset c:\log1.txt

netsh winsock reset from:\log2.txt

Restart your computer.

Method number 4. Update your network card drivers

Go to Device Manager (click on the Start button, type devmgmt.msc in the search bar and press enter).
In the list of devices, double-click on “Network adapters” and find your network card in the list that opens.
Hover your cursor over it, right-click, and select “Update Driver” (stop at the automatic search for drivers).
A good option may also be to use special automated programs for updating drivers (DriverPack Solution, Driver Booster, etc.).

Method No. 5. Make changes to the system registry

Click on the Start button, type regedit in the search bar and press enter. In the Registry Editor that opens, go to the following branch: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS.
Inside VSS there will be a Diag folder, hover over it and right-click.
Select "Permissions" from the menu that appears.
In the permissions window that opens for the “Diag” group, click on “NETWORK SERVICE”, and then check the “Allow” box in the “Full Control” field.
Then click on “Ok” to save the changes.

Conclusion

The reason for the appearance of the message I am considering is the unstable operation of the mentioned service, which, in turn, may be caused by an incorrect version of Windows OS, or problems with the computer’s network connection. To solve the problem “The Diagnostic Policy Service is not running”, I recommend using the methods I have listed (paying special attention to the first of them), they will help ensure stable operation of your PC.

In contact with