Some users of Windows-based systems"Seven" and higher sometimes face the problem that when you run an application that involves the use of a network connection in its work, an error is issued indicating that the diagnostic policy service is not running. Let's try to figure out what it is, and why the specified service is needed at all. Among other things, give some tips on how to fix the problem in different ways.
What does the message "Diagnostic Policy Service Not Run" mean?
First of all, it is necessary to clearly understand that such aThe error is due solely to the network and Internet settings. When a message is received that the Diagnostic Policy Service is not running, Windows 8 or 7, for example, signals that the user does not have sufficient rights to change settings related to network connections.
This is most often manifested in the case ofuse of so-called pirate assemblies, rather than official distributions used when installing the system itself. What's most sad is the appearance of a message stating that the Diagnostic Policy Service can not start, although the user has administrator rights when logging on (as he believes). In fact, in systems starting with the "seven", there is still a super administrator account. Have you noticed that sometimes programs need to be run through the right click with a choice from the menu of the corresponding type of launch? Of course, this "accounting" can be turned off in the simplest way, however, as practice shows, this does not always work.
The Diagnostic Policy Service is not running: how can I fix the situation by the simplest method?
As for the simplest method of eliminating the problem, first of all, make sure that the official Windows version is installed on the computer terminal or laptop.
Without this, you can not even try to change something, although some manual settings may work.
To begin with, after the message thatthe diagnostic policy service is not started, you can try simply to reboot the system or restore it from the control point (rollback) to the previous state (but only if there were no problems before and it worked fine). If this does not help, it is necessary, that is called, to include brains and apply cardinal methods.
Let's edit the system registry keys
In principle, the problem of how to start the serviceWindows 7 or 8 diagnostics policy, is solved by using the system registry key editing or security policy. Both editors, in general, duplicate the settings. Only, making changes in one of them, one can not cancel their preservation in another.
So, what do we need? To start, call the editor using the regedit command from the Run menu (Win + R). Next, go to the HKLM branch, where through the tree of the System folder, go down to the Diag section. In the Network Service group, you need to set the full resolution by setting the appropriate "flag" and save the changes. In theory, after rebooting the system, the problem disappears.
We use the services section for manual start
If the above option does not work, you can do otherwise. Use the same "Run" menu and enter the services.msc command.
After logging into the services editor, we check the settingsthe IPSec security agent, the diagnostic service node, and the service itself. If the start value is set to something other than automatic, it must be changed (for the first and third, the second set to "Manual"). Again, after this you need to reboot the system.
Reset network settings
Now we allow this: a message appears again that the Diagnostic Policy Service is not running. What to do in this case? It's simple. It will be necessary to reset the network settings if they are manually registered (IP and DNS server address).
To begin with, you can set them automatically.
If this does not work, you should use a command line call, where the following is written:
pconfig / release
ipconfig / renew
ipconfig / flushdns
netsh int ip reset c: log1.txt
netsh winsock reset with: log2.txt
shutdown -r -t 0 (terminal restart).
But this may not be enough. How can I start the Windows Diagnostic Policy service one more way? As easy as pie. We use editing rights to change network settings.
In the standard Explorer, right-clicking on the lettersystem disk, we call the context menu and select the properties. On the security tab, use the user groups section and go to advanced settings. Then, after searching registered users, we look for LOCAL SERVICE (the "Edit" and then "Add" buttons) and set the rights wherever the ban is.
The help comes command line
Finally, one of the fastest ways to get rid of the message that the Security Policy Service is not running is the quick input of several commands.
For Russian-speaking systems this is the sequence:
net localgroup Administrators / add networkservice
net localgroup administrators / add localservice
For English versions, all the same is prescribed, only the Russian-language word "Administrators" on the Administrators changes.
Here, in fact, and all that concerns the correctionerror and start the diagnostic service. Of course, for many users this may seem rather complicated. Nevertheless, at last I want to note that no other methods can fix the situation. So please be patient and knowledgeable.
Incidentally, the choice of the way to solve thisalthough the problem depends on the user, nevertheless, you need to clearly understand that when duplicating the system registry keys and starting the service from the corresponding editor, nothing good will come of it. Or the registry - or service. What is most sad, the service editor takes precedence. That is, if the changes are made with it, the system registry will not be able to change anything. So keep in mind for the future.
But that's not all. It is best, as it turns out, to use the command line. The fact is that Windows system services in the absence of admin rights may not always work. Moreover, it is necessary to run the command line on behalf of the administrator, otherwise nothing will work. But, in general, this is the most effective method. Although in some cases, standard methods also help.
On the other hand, if the user has installed"Cracked" version of the operating system itself, as it is not reinstalled, it will not work. The service can be blocked even at the stage of installation at the time of the introduction of the "left" license key. You understand that in this case it is better to install the official modification, and if there is a corresponding "iron", then go to the latest version in the form of "dozens". Of course, it also causes criticism for many, but it still "bugs" as much as the "eight" or its variant in the form of version 8.1. And that's why it's recommended to make a transition. And, most interestingly, you can download the "dozen" completely free of charge from the official site of Microsoft. For versions 7 and 8, you have to pay and pay a substantial amount for this, which many of our users simply can not afford.
In general, think for yourself what to do in thiscase, and which of the above methods to apply. Each of them works in its own way well, and no one can be dismissed. However, you can also get rid of the message that the diagnostic policy service is not running, and other methods. Because of their complexity, they are not considered. Here are the simplest solutions that can be used in practice for any system. In fact, it really works. These schemes were tested by many users in practice, even when using versions of XP and Vista, not to mention updated developments. But they, in spite of all their advantages, are also capable of issuing such errors. As already understood, you can fight them with the above methods.