Diagnostic policy service

Diagnostic policy service DEFAULT

How to FIX: Diagnostic Policy Service Cannot Start. Access is Denied – Error 5. (Solved)

The Diagnostic Policy service (DPS) enables problem detection, troubleshooting, and resolution for Windows services and components. If this service cannot start and you receive an "Access Denied" error 5, when you try to start the service manually then read this tutorial to fix the issue.

The Diagnostic Policy Service is required to diagnose Windows problems using the troubleshooting tools that are offered in Windows 7, 8 or 10 OS. If the DPS service is stopped then you won't be able to diagnose and fix several system issues that affect Windows' operation (e.g. Networking or Internet Access problems).

How to FIX: Diagnostic Policy Service Cannot Start: Access is Denied (Windows10/8/7)

Step 1. Scan for Viruses/Malware.

Viruses or malicious programs can cause your PC to work abnormally.  So, before you continue to troubleshoot your problems, use this Malware Scan and Removal Guide to check and remove viruses or/and malicious programs that may be running on your computer.

Step 2. Modify Diagnostic Policy Service Registry Permissions.

1. Simultaneously press the Windows image+ R keys to open run command box.
2. Type regedit and press Enter.


3. At the left pane, navigate to this key:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DPS\Parameters

4. Right click on the Parameters key and select Permissions.

Diagnostic Policy Service Cannot Start

5. Click Add, type your account name/username in the search box and click OK.


6. Select your username and check the Full control box to grant to your account full control permissions on the 'Parameters' key and click OK.

fix Diagnostic Policy Service Cannot Start

7. Then navigate to this key:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WDI\Config

8. Right click on the Config key and select Permissions.

fix Diagnostic Policy stopped

9. Click Add, type NT Service\DPS in the search box and click OK.

fix Diagnostic Policy error 5

10. Select the 'DPS' and check the Full control box.

Diagnostic Policy access denied

11. Click OK and then close the registry editor.
12.Restart your computer.
13. After the restart, check if the "Diagnostic Policy Service Cannot Start" issue, was resolved. If not, then continue to next step.

Step 3. Add 'NETWORK SERVICE' & 'LOCAL SERVICE' to Administrators group.

The next step to resolve the "Diagnostic Policy Service Cannot Start: Access is Denied" issue, is to add the 'Network Service' & 'LOCAL SERVICE' objects to Administrators group. To do that:

1. Open Command Prompt as Administrator. To do that:

a. In the Search box type: cmd or command prompt
b. Right click on the command prompt (result) and select Run as Administrator.

fix Diagnostic Policy stopped

2. In command prompt type the command below and press Enter:

  • net localgroup Administrators /add networkservice

fix Diagnostic Policy service error 5

4. Then type the following command and press Enter:

  • net localgroup Administrators /add localservice

fix Diagnostic Policy service error 5

5. Reboot your computer.

That it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.

If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for usin our effort to continue to help others while keeping this site free:
If you want to stay constantly protectedfrom malware threats, existing and future ones, we recommend that you install Malwarebytes Anti-Malware PROby clicking below (we do earn a commision from sales generated from this link, but at no additional cost to you. We have experience with this software and we recommend it because it is helpful and useful):

Full household PC Protection - Protect up to 3 PCs with NEW Malwarebytes Anti-Malware Premium!

Sours: https://www.wintips.org/fix-diagnostic-policy-service-cannot-start-access-is-denied-error-5/

Diagnostic Policy Service - high CPU

the file "C:\Windows\System32\sru\SRUDB.dat"

is about 61MB on my system, but doesn’t show any updates in the last ~22 hours.

 I could not seem to stop the service, the stop request timed out, and it’s status is now just “stopping”. Because of that, I could not delete the SRUDB.dat file.

 Not sure where/how to find all of the ESENT events, but under administrative events, tons of these, looks like one about every minute or so, from various sources { General, …}, but almost all from “Database corruption”.

 Here is one:

Log Name:      Application

Source:        ESENT

Date:          3/29/2018 6:25:00 AM

Event ID:      447

Task Category: Database Corruption

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      grglap


svchost (4204,D,21) SRUJet: A bad page link (error -338) has been detected in a B-Tree (ObjectId: 31, PgnoRoot: 7633) of database C:\WINDOWS\system32\SRU\SRUDB.dat (2400 => 12609, 31).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">


    <Provider Name="ESENT" />

    <EventID Qualifiers="0">447</EventID>




    <TimeCreated SystemTime="2018-03-29T11:25:00.023206500Z" />




    <Security />





    <Data>SRUJet: </Data>










 But here is one from General:

 Log Name:      Application

Source:        ESENT

Date:          4/4/2018 4:34:49 PM

Event ID:      522

Task Category: General

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      grglap


ShellExperienceHost (1940,P,0) TILEREPOSITORYS-1-5-21-2554618691-1091664963-2105190305-1006: An attempt to open the device with name "\\.\C:" containing "C:\" failed with system error 5 (0x00000005): "Access is denied. ". The operation will fail with error -1032 (0xfffffbf8).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">


    <Provider Name="ESENT" />

    <EventID Qualifiers="0">522</EventID>




    <TimeCreated SystemTime="2018-04-04T21:34:49.006341300Z" />




    <Security />





    <Data>TILEREPOSITORYS-1-5-21-2554618691-1091664963-2105190305-1006: </Data>



    <Data>-1032 (0xfffffbf8)</Data>

    <Data>5 (0x00000005)</Data>

    <Data>Access is denied. </Data>




Sours: https://social.technet.microsoft.com/Forums/en-US/cf6ceadd-4bb4-4668-b8fb-8ccf7d067e31/diagnostic-policy-service-high-cpu?forum=win10itprogeneral
  1. Pisces daily horoscope ganeshaspeaks
  2. Glype proxy alternative
  3. Husqvarna mower parts
  4. Skywalker square trampoline instructions

What Is Diagnostic Policy Service & How to Enable/Disable It [Partition Manager]

Summary :

Diagnostic Policy Service

In this article, MiniTool Partition Wizard gives a detailed introduction on Diagnostic Policy Service and provides 4 commonly used methods to enable and disable Diagnostic Policy Service.

What Is Diagnostic Policy Service

Diagnostic Policy Service (DPS) is an essential service installed by default in your Windows. This service aims to detect and troubleshoot the potential problems for the components of your Windows. It will initiate automatic corrective action or log the appropriate diagnostic information for the cause analysis of the problems, and then notify the user of the potential problem.

Commonly, this service runs automatically with your system in the shared process of svchost.exe (Service Host) to keep finding issues for the components. If Diagnostic Policy Service is not running, you will be unable to know the causes of issues in your system.

Diagnostic Policy Service

How to Enable or Disable Diagnostic Policy Service

Although Diagnostic Policy Service starts automatically, it might be disabled due to various reasons including manual misoperation, virus infections, and etc. So, you might wonder how to enable Diagnostic Policy Service.

Here are 4 methods to enable the service in Windows 10, and you can also use these methods to disable it when needed.

Option 1: Via Services App

The easiest way to enable Diagnostic Policy Service and disable it is to manage it in Services app. The detailed steps are listed below.

Step 1: Press Windows + R to open Run window.

Step 2: Input services.msc and click OK to open Services app.

Step 3: Find Diagnostic Policy Service and double-click it to open its Properties.

Step 4: Choose Automatic or Manual from the drop-down list of Startup type. Then, click Start button in Service status section to enable the service, or click Stop button to disable it.

enable Diagnostic Policy Service in Services app

Step 5: Click Apply and OK to save changes.

Option 2: Via System Configuration

You can also enable or disable Diagnostic Policy Service in System Configuration. It is very easy to operation. Just follow the instructions below:

Step 1: Invoke Run dialog, type msconfig and click OK to open System Configuration.

Step 2: Switch to Services tab and locate Diagnostic Policy Service. Then, check the service (or uncheck it if you want to disable it) and click Apply and OK button.

enable Diagnostic Policy Service in System Configuration

Step 3: A notification window will pop up, requiring a restart for the changes to take effect. Just save your tasks and click Restart button to restart your system.

Option 3: Via Registry Editor

If you are familiar with Registry Editor, you can also choose to enable or disable Diagnostic Policy Service by modifying Windows registry. You are recommended to back up registry in advance before you make any changes. Here’s how to do enable or disable the service in this way.

Step 1: Input regedit in the Run window and click OK to open Registry Editor.

Step 2: Copy and paste the following path to the address bar and press Enter to locate the registry key of DPS: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DPS

Step 3: In the right pane, double-click Start to edit the DWORD. Input your preferred value in the box under Value date and Click OK button to save changes. The startup types of the service and the corresponding value data are listed below:

  • Automatic: 2
  • Automatic (Delayed Start): 2
  • Manual: 3
  • Disabled: 4

Note: If you change to Automatic (Delayed Start), a new key DelayedAutoStart will be created with value 1. When you change to Automatic startup type, the value of the new key will be changed to 0.

enable Diagnostic Policy Service in Registry Editor

Option 4: Via Command Prompt

Alternatively, you can also execute certain commands to manage the Diagnostic Policy Service. To enable the service in Command Prompt, you can refer to the steps displayed below.

Step 1: Open Run window, input cmd and press Ctrl + Shift + Enter to run Command Prompt as administrator.

Step 2: Set the startup type of DPS to Automatic or Manual as your needs. Just type either of the following commands and press Enter:

  • Automatic: REG add “HKLM\SYSTEM\CurrentControlSet\services\DPS” /v Start /t REG_DWORD /d 2 /f
  • Manual: REG add “HKLM\SYSTEM\CurrentControlSet\services\DPS” /v Start /t REG_DWORD /d 3 /f

Step 3: Now, input the command net start DPS to enable Diagnostic Policy Service.

Note: If you want to disable DPS service, you can execute the command REG add “HKLM\SYSTEM\CurrentControlSet\services\DPS” /v Start /t REG_DWORD /d 4 /f in Command Prompt as well.



AmandaFollow us

Position: Columnist

Amanda has been working as English editor for the MiniTool team since she was graduated from university. She enjoys sharing effective solutions and her own experience to help readers fix various issues with computers, dedicated to make their tech life easier and more enjoyable.

She has published many articles, covering fields of data recovery, partition management, disk backup, and etc. In order to provide more useful tips and information, she is still committed to expand her technical knowledge.

Sours: https://www.partitionwizard.com/partitionmanager/diagnostic-policy-service.html

Diagnostics Policy Service Is Not Running [Solved]

It seems that the network connection is not good on your Windows computer. So probably you to troubleshoot the network through the Windows Network Diagnostics. But unluckily, you are seeing this error saying before it tells you any network problem as before:

The Diagnostics Policy Service is not running

Rest assured. You’re not alone. Many Windows users have this problem as you. More importantly, we’ve found the answer for you.

Read on this small guide and follow to solve the problem on your Windows.

What is Diagnostics Policy Service?

The Diagnostic Policy Service enables problem detection, troubleshooting and resolution for Windows components on your Windows operating system. If this service is not running, diagnostics will no longer function.

How do I fix the Diagnostics Policy Service is not running issue?

Here’re 3 easy and helpful solutions you can try. You may not have to try them all; Just start from the top and work your way down the list until your problem is solved.

  1. Check the Diagnostics Policy Service in the Services window
  2. Give the network service and local service administrator privilege on your Windows
  3. Reinstall your all network adapters

Solution 1: Check the Diagnostics Policy Service in the Services window

Since the error message tells you that the service is not running, the first quick solution is to check the service status in the Services window.

Follow these steps:

1) On your keyboard, press the Windows logo key  and R (at the same time) to invoke the Run command.

2) Type services.msc and click OK.

3) Locate Diagnostics Policy Service, right-click on it to select Start, if Start grayed out, click Restart instead.

4) Right-click on Diagnostics Policy Service again and this time select Properties.

5) Set its Startup type to Automatic. Then click Apply > OK.

6) Run the Network Diagnostics and see if it goes well.

Solution 2: Give the network service and local service administrator privilege on your Windows

This problem could happen due to the service doesn’t have access to run properly. You can easily fix it by giving the services administrator privilege.

1) Type cmd in the search box from the Start menu. Then right-click on Command Prompt or cmd.exe to select Run as administrator.

2) Type the following commands and press Enter after each.

net localgroup Administrators /add networkservice

net localgroup Administrators /add localservice

If you’re on Windows 8, you’ll need to add a space before “service”. So, the commands for you to type would be:
net localgroup Administrators /add network service
net localgroup Administrators /add local service

You should see a message saying The command completed successfully after each.

3) Close the Command Prompt window, and run the Network Diagnostics to see if it goes well.

Solution 3: Reinstall your network adapters

This error could be also caused by your malfunctioned network adapters. You can try to reinstall your network adapters to solve it.

1) On your keyboard, press the Windows logo key and R (at the same time) to invoke the Run command.

2) Type devmgmt.msc and click OK.

3) Double-click Network adapters and right-click on your network adapters one by one(if there’re more than one) to select Uninstall device.

4) Click Action > Scan for hardware changes. Microsoft should then reload the network adapter driver automatically.

5) Run the Network Diagnostics to see if it goes well. If it keeps giving you the error, install the latest driver for your network adapter then.

You can update your network adapter driver manually by going to your motherboard or computer manufacturer’s website, searching for the most recent correct driver for your network adapter. Be sure to choose only drivers that are compatible with your variant of Windows system.

Note: If you can get access to the Internet on your computer, then download the driver file from another working computer and save it to the USB flash drive. Then you can install the driver on your target computer through the USB drive.

Alternatively, If you don’t have the time, patience or computer skills to update your network adapter driver manually, you can, instead, do it automatically with Driver Easy. Driver Easy will automatically recognize your system and find the correct drivers for your exact network adapter, and your variant of Windows system, and it will download and install them correctly:

1) Download and install Driver Easy.

2) Run Driver Easy and click the Scan Now button. Driver Easy will then scan your computer and detect any problem drivers.

3) Click the Update button next to a flagged network adapter driver to automatically download and install the correct version of this driver (you can do this with the FREE version). 

Or click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system (this requires the Pro version – you’ll be prompted to upgrade when you click Update All).

Driver Easy requires network connection to update drivers. If your windows can’t access the Internet, please use the Offline Scan feature of Driver Easy to help you.

4) After updating your network adapter driver, please restart your computer.

5) Run the Network Diagnostics to see if it goes well.


66 people found this helpful

Sours: https://www.drivereasy.com/knowledge/diagnostics-policy-service-not-running-solved/

Policy service diagnostic

She looked at me sadly and said. You can leave immediately, you can spend the night in the hall. As you want".

How To Fix The Diagnostic Policy Service is not running on Windows 10/8/7

Oleg had already attacked Alin's vagina with his penis in full, when Alex, on a pull-out sofa standing half a meter from their bed, gently with kisses, finished. Undressing Tatyana, leaving her in stockings alone. Having passed through the mouth, breasts, navel, Alex's lips went down to where, already pouring out the nectar of desire, a small purple bud of Tatiana's flower swelled.

Unlike Alina, Tanya's crotch was not shaved clean, but a thin, light strip of hair that went down the pubis to the.

You will also be interested:

Somehow I got to bed, and unable to undress I flopped onto the bed. There were two days left before leaving. To be continued… This story is almost real, it happened in 2000. With this story, we all started. They invited us to a restaurant for a birthday party.

43925 43926 43927 43928 43929