If you are trying to run a Windows Service like the Diagnostic Policy Service and encounter an error instead that says, “Windows could not start the Diagnostic Policy Service”, worry not for this post will guide you on what you can do of the Diagnostic Policy Service is not running in your Windows 10 computer.
As you know, the Diagnostic Policy Service enables problem detection, troubleshooting, and resolution for Windows components on your Windows operating system. When you encounter this kind of problem, you will also see the “Access is denied” error message. This occurs when the “MpsSvc” process does not have the permissions needed for the Registry keys. This kind of problem happens when the TrustedInstaller account is missing the permissions for a Registry key and so to fix this issue, you need to take full control and ownership of the Registry keys.
You need to create a System Restore point first before you get started. This way, you can always undo the changes you’re about to make in case anything goes wrong. Once you’re done creating a System Restore point, refer to the following instructions to fix the “Windows could not start the Diagnostic Policy Service” error.
Step 1: Tap the Win + R key combination to open the Run utility.
Step 2: Type in “Regedit” in the field and tap Enter to open the Registry Editor.
Step 3: After opening the Registry Editor, navigate to this registry path:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesDPSParameters
Step 4: After that, look for the “Parameters” registry key and select Permissions.
Step 5: Now select your account under Group or user names.
Step 6: Next, make sure that the “Full Control” and “Read” boxes are both checked, and then click on the Apply and OK buttons to save the changes.
Step 7: Afterwards, navigate to this registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWDIConfig
Step 8: From there, look for the Config key and right-click on it and select Permissions and then click on Add and type “NT Service/DPS in the box and click OK.
Step 9: Now select “DPS” and check the Full control box, click OK and exit the Registry Editor.
Step 10: Reboot your computer and check if the error is now fixed.
ST0P 0X00000024 (x00190203, 0x82700550, 0xc000012, 0x00000000)Due to this error, both Safe and Normal modes become inaccessible.
‘Runtime Error! Program: C:…R6025-Pure Virtual Function Call’
“Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. If you’d like to know more, you can search online later for this error: HAL_INITIALIZATION_FAILED HAL INITIALIZATION FAILED 0x0000005C”This kind of Blue Screen error indicates that there is a hardware or device driver problem in your PC. Aside from that, it also signifies that the initialization of the Hardware Abstraction Layer or HAL has failed. This happens only during the relatively short period that the Windows operating system is being initialized, specifically during phase 4 of Windows startup. What’s worse about this kind of Stop error is that it does not just go away after a computer reboot. You may have to boot your computer into Safe mode with Networking using the Advanced startup options which you can access by tapping the F2 or F8 key. Once you’ve accessed the Advanced startup options, follow the fixes prepared below.
chkdsk /f /r