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:
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.
“Installing, this may take a few minutes… WslRegisterDistribution failed with error: 0x8007019e/0x8000000d Error: 0x8007019e/0x8000000d The parameter is incorrect. Press any key to continue.”Error code 0x8007019e or 0x8000000d could be due to the absence of supporting Windows 10 features since the error does not even let one use the WSL-based command line. If you are one of the users facing this problem, then you’ve come to the right place as this post will provide you with a couple of suggestions to fix it. There are two options you can check out to fix the problem, but before you do that, you need to make sure that the Windows Subsystem for Linux feature is enabled. The two options include enabling WSL using the “Turn Windows features on or off” option and using the Windows PowerShell.
Many are upgrading their OS to Windows 10, however, it’s not always smooth sailing because users have been reportedly experiencing different bugs including Black Screen after a successful update.
One common issue in installing Windows 10 is the appearance of a black screen after installation. This usually occurs when the user restarts the computer. Initially, there will be a black screen only appearing on the monitor. There are also cases where a mouse cursor is present, while some cases have no cursor at all.
Not only that, it seemed that you’ve lost all your desktop icons when experiencing this bug.
Just like the other bugs experienced by Windows 10 users, booting to a black screen has reasons. Before you even try to look for the solution, you first have to determine the cause of the error, in this case, the error would be black screen when booting.
Before you even think of upgrading your OS to Windows 10, you need to know that there are specific system requirements and specifications to be able to successfully update your operating system.
There are more system requirements in order to use other certain Windows 10 features, but we’ll focus on solving your black screen problem in this article.
IMPORTANT NOTE: While it’s possible that you’ll be able to find the solution for your black screen during Windows 10 update, contacting the service of a professional technician or using an automated tool is advisable if you’re not confident in performing the methods to be discussed.
There’s a chance that you’ll get an error prompt saying, “installation cannot be completed in safe mode.” If this happens, simply press Shift + F10. This command will redirect you to the Command Prompt. You just open Device Manager by keying in devmgmt.msc then disable the display adapters, now check if you’ll be able to successfully boot in normal mode.
This process will normally allow you to complete the Windows 10 installation, if that’s the case you can just update the display adapter drivers from the manufacturer’s website. Restart your computer and see if this solves the problem.
Do take note, however, that the Roll Back Driver option is not available if there was no previous version installed.
Since one common cause of black screen during a Windows 10 update is the external devices you use in your computer, you might want to consider these steps as well.
Some Windows 10 users had success in solving their black screen problem by disabling the fast startup.
One of the selling points of Windows 11 was the ability to run Android apps natively in it without the need for any third-party software. It is not a big surprise that even after its release Microsoft is evolving and expanding Windows 11 and its features.
Microsoft is now rolling out an update for the Windows Subsystem for Android on the Dev Channel of the Windows Insiders program. The new version upgrades the core operating system from Android 11 to Android 12.1 (also known as Android 12L), which means the new system and app features in Android 12 and 12.1 are now available on Windows for the first time. However, not the new features in those updates apply to the modified version that runs on top of Windows. For example, one of the main improvements in 12.1 was a dual-pane notification panel for larger screens, but Android app notifications on Windows just show up in the Windows notification panel.
The upgrade also improves how Android apps integrate into Windows. The Windows taskbar will now show which Android apps are currently using the microphone, location, and other system services — similar to many native Windows applications. Toasts messages (the small popups that some apps use for temporary messages) are now displayed as Windows notifications, and the titlebar on Android apps will use the current activity name for the title.
The new update is limited to Windows Insiders for now, but once Microsoft fixes all the bugs, it should start rolling out to everyone on Windows 11 that has the Android Subsystem enabled.
Customers will most likely encounter the “We couldn’t update system reserved partition” error when upgrading to Windows 10 from Windows 7 or Windows 8.1. This error may also come with error code 0xc1900104 or error code 0x800f0922.
“We couldn’t update system reserved partition” Windows 10 upgrade error is normally caused by too little space on the System Reserved Partition (SRP). The System Reserve Partition is an additional small partition created by Windows, which stores boot files. The SRP can be filled up with security apps and third-party anti-virus. Once this partition has insufficient space, the system will not be able to upgrade to Windows 10.
Caution: The following steps are complex and need to be done by experienced users especially using the command line. Once an error is made in entering commands, there’s a chance that your device can be put in a no-boot situation, or data stored on the device can possibly get lost.
To upgrade to Windows 10, your device needs to have at least 15MB free space on the System Reserved Partition. Follow the procedure below and then try upgrading again.
NOTE: While in Admin mode, some apps like OneNote will not run.
Doing this method will make a permanent, but small increase in the free space of the device’s SRP.
a. Open the Run window by pressing the Windows key + R. Type diskmgmt.msc then hit Enter. b. Select System Reserve partition then right-click on it.
c. Choose Change Drive Letter and Paths then select Add.
d. Type Y for the drive letter then click OK.
e. Click on the Start button and search for cmd. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
f. Type Y: at the command prompt then press Enter.
g. Once you’ve switched to drive Y, type takeown /d y /r /f . then hit Enter.NOTE: Ensure that the space and period after “f” is included in order for the command to work properly
h. Type icacls Y:* /save %systemdrive%NTFSp.txt /c /t then hit Enter to back up the permission to the drive.
NOTE: Ensure that all files are marked as successful and that no files are marked as failed.
i. Type whoami then hit Enter. Record the username that appears. Afterwards, type icacls . /grant <username you got from whoami>:F /t then press Enter.NOTE: Ensure that there’s no space between the username and “:F” or the command will not work.
j. In the File Explorer, open the SRP drive and select the Boot folder. Choose the language folders you want to permanently delete. Language folders are named with four letters split with a hyphen. For example: de-DE is the German language while en-US is the U.S. English language.
2. Truncate the NTFS Log:
a. Open the Command Prompt then type chkdsk /L Y: to check the size of the NTFS Log. If the NTFS Log size is less than 5000KB, you need not truncate the file.
b. Type chkdsk /L:5000 /X /F then hit Enter to truncate the NTFS Log.
c. Return to Disk Management window. Select Action menu then select Check if the device’s SRP now has a larger amount of free space. Once there’s enough space, right click the System Reserve Partition then select Change Drive Letter and Paths. Choose Y: then select Remove.
3. If there’s still not enough available space after truncating the NTFS Log, resize the USN journal:
a. Open the command prompt then type fsutil usn queryjournal Y: to display the size in hex value. Convert the hex value to decimal then divide it by 1048576. The result you will get will be in MB. If the journal size is 30MB or more, proceed with truncating the file.
NOTE: To convert the Hex value to Decimal, open the Calculator app in Windows then choose View menu. Select Programmer then choose Hex. Type the Hex value then choose Dec.
b. Type fsutil usn deletejournal /D /N Y: then hit Enter to delete the journal. Type fsutil usn createjournal m=1500 a=1 Y: to recreate the journal having the new log size value.
a. Type icacls Y: /restore %systemdrive%NTFSp.txt /c /t in the Command Prompt. Check if the files were successfully processed before proceeding. If you see a message saying some files failed while processing, this is normal since some of the files have already been deleted before performing a backup. However, if there are no successful files indicated, the command was not properly executed.
b. Type icacls . /grant system:f /t then hit Enter to adjust the ACL back to System. Now, you can set the owner of the drive by typing icacls Y: /setowner “SYSTEM” /t /c then press Enter.
c. Check if the device’s SRP now has enough free space by going back to Disk Management and refreshing the data. If the SRP already has sufficient space, you can now remove the drive letter. Right-click on the System Reserved Partition then choose Change Drive Letter and Paths. Select the Y: drive then choose Confirm deleting the drive letter by clicking OK.
This method makes a larger, but temporary, increase in the SRP free space.1. Be sure you have an external drive having at least 250 MB free space and formatted as NFTS.
2. Open Run by pressing the Windows key + R. Type mscthen to choose the Recovery Partition. Right-click on it then choose Change Drive Letter and Paths.
3. Select Add then type Y for the drive letter, click
4. Click on the Start screen then type cmd in the search bar. In the results, right-click on Command Prompt then choose Run as administrator. The command prompt window will appear.
5. Switch to another drive by typing Y: in the command prompt. Once you’re in the drive Y, type takeown /d y /r /f .
NOTE: Ensure that space and period after “f” are included in order for the command to work properly.