What is USB Kill Kit

If you encounter an error message that states, “Your computer has lost the lease to its IP Address <IP ADDRESS> on the Network Card with network address <NETWORK ADDRESS>”, then this post might be of help to you. This kind of error due to the timeout caused by the DHCPv6 address which is used to connect the client to the user network as an independent client or a part of a domain. There are a lot of potential fixes you can try to fix this error and we will be discussing each one of them below. You can try to reboot your router, flush the DNS cache, reset the Network adapter, toggle the DHCPv6 Lease time or disable IPv6 in the Network Center. For more details, refer to the following options.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try to flush the DNS configuration

You could also try to flush the DNS configuration in your computer to fix the error. How? Refer to these steps:

• Tap the Win + X key combination and click on the Command Prompt (Admin) option or you could also search “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
• After opening Command Prompt with admin privileges, enter each one of the commands given below sequentially in order to flush the DNS cache.
  • ipconfig/release
  • ipconfig/renew
  • ipconfig/flushdns
• Now type the exit command to close Command Prompt and then restart your computer and see if the problem is fixed.

One the other hand, you could also try to reset Winsock as well as the TCP/IP. Once done, just exit the Command Prompt and check if that fixes your issue. You may want to reset Winsock & reset TCP/IP as well.

Option 3 – Try to toggle the DHCPv6 Lease time

• First, you need to log in to the Admin panel of your router.
• Next, navigate to the DHCPv6 settings inside it and look for a field for Lease Time.
• After you’ve found it, increase the Lease Time value to something greater than what is already entered depending on your preference.
• Now apply the configuration and reboot your router to apply the modified settings. Just remember that if things didn’t work out, you can just change back the Lease Time value to what it was before.

Option 4 – Try disabling the IPv6 in the Network Center

• Tap the Win + X key combination and click on Network Connections.
• This will open the Settings app on a specific page. Now on the right-side panel, click on the Network and Sharing Center link.
• After that, it will open the Control Panel and from there, click on the network that your computer is connected to and then click on Properties.
• Next, uncheck the entry that says, “Internet Protocol Version 6 (TCP/IPv6)” in the list that populates.
• Now click on OK and close all other windows and see if the error is fixed.

Option 5 – Run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:

• Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
• Next, scroll down and select the “Network Adapter” option from the right pane.
• Then click on the Run Troubleshooter” button.
• After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
• Restart your computer.

Option 6 – Try to perform Network Reset

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:

• Tap the Win + I keys to open Settings.
• From there, go to the Network and Internet section.
• Next, scroll down and look for “Network Reset” under the status pane.
• After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.

Error code 0x8007007b - What is it?

Error code 0x8007007b will present itself when Windows users are trying to activate Windows. You may try to activate it through the update and security option, but it is likely that you will receive the same error code. Error code 0x8007007b may be presented when Windows 7 and Windows 8.1 users try to upgrade and activate Windows 10 on their computer.

Common symptoms include:

• An error message will display that says Windows cannot be activated. The KMS host cannot be located in the DNS, please have the system administrator verify that the KMS is published correctly in DNS.
• Error 0x8007007b will be displayed, stating that the file or directory name or the volume label syntax is not correct.

Solution

Error Causes

There are multiple causes for the user to see this error code, including if a user is using volume-licensed media while installing a number of various Windows operating systems. This error may also be caused because the activation wizard cannot connect to a KMS host computer. It is likely that if the user has a volume-licensed form of media, they were likely given a MAK (multiple activation keys).

Further Information and Manual Repair

There are several ways to go about repairing error code 0x8007007b. It is important to try all of the methods, but if it is too difficult or you do not know what you are doing, please do contact a Windows repair technician. They will likely be able to fix the problem with ease.

Method One: Instead of KMS activation, use a Multiple Key Activation

When KMS activation is not used, and when there is not a KMS server, the product key type should then be changed to a MAK. For MSDN (Microsoft Developer Network) or TechNet, the SKUs that are listed on the media are generally volume-licensed media, and that means that the product key that is supplied is a Multiple Activation Key.

To change the KMS to a MAK, click Start, All Programs, Accessories, and then right-click on Command Prompt. Click Run as Administrator. If prompted for a password or confirmation, enter it now.

When the command prompt opens, type in the following command, and press enter after:

slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx (these x's are representative of the MAK product key).

Method Two

While on the desktop, press the Windows key and R. The Run window should appear, and then you should enter the following command: Slui 3. Press Enter and then wait for the window to appear. This window will ask for the operating system activation product key. Enter the product key and then press the Activate button. Reboot the computer. Now the Error Code 0x8007007b should be gone.

Method Three

Open the Command Prompt with access as administrator as mentioned previously. Enter the following command: sfc /scannow. The command will then complete its task. This will take a good bit of time, so leave the computer to do its work. The sfc must finish the scan. When the scan has finished, reboot the computer. Now you can check for activation. The error code should be gone.

Method Four: When the client can't locate a KMS host on the network to complete activation

This method for correction should be used when the network does have a KMS host computer setup, and the client is not able to locate the KMS host on the network to complete activation.

To verify that the computer does in fact have the KMS host installed. Click Start, All Programs, Accessories, and then right-click on Command Prompt. Run as administrator. If you are now prompted to enter a password or confirmation, do so. When the command prompt box comes up, type in the following command, and then press Enter: nxlookup -type=all_vlmcs._tcp>kms.txt

The command will generate a file, open this KMS file. The file will contain one or more entries. As a default, the KMS host server will dynamically register a DNS SRV server evidence once every 24 hours. In order to check the registry to ensure that this is happening, follow these steps:

• Click Start, type in regedit, and then press Enter.
• Locate the key HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSL and then click on it.
• The DisableDnsPublishing subkey should be present and have a value of 1. If it is missing, create a DWORD value by right clicking DisableDnsPublishing, click Modify, in the Value Data box type in 0, and then click Okay.

Method Five: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

If you encounter the “Diskpart failed to clear disk attributes” error when you try to change the read-only state of a storage device using the Diskpart application and the request is denied, worry not for this post will give you a couple of fixes to resolve the problem. As you know, Diskpart is used for resolving read-only storage devices by changing their attribute via the command line. So if it is not able to change the attribute of the storage device, then you will most likely encounter an error such as this one. This kind of error is not uncommon and as long as there are no damaged physical attributes, you can resolve it right away. There are tons of reasons why you’re getting this error while using Diskpart, it could be that the storage device has a physical write-protected switch or the disk is hidden or has bad sectors. It could also be because the storage drive might be in RAW format or that you are running the Diskpart application without admin privileges. Whatever the cause may be, here are some options you can try to fix the problem but before you proceed, make sure that you log on to your PC as an administrator.

Option 1 – Check if there is a physical switch on the storage device

There are some USB devices and SD card readers that have a write-protected physical switch that disables all the writable options on the storage device and so if it is turned on, Diskpart won’t be able to change the disk attribute to writable. To check, simply look for the physical switch on both sides of the device and once you found it, make sure that it is toggled off and then plug the storage device back in then try running Diskpart once again.

Option 2 – Modify the WriteProtected key in the Registry Editor

Before you proceed, you have to create a System Restore Point first.

• Tap the Win + R keys to open Run and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to the following path:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlStorageDevicePolicies

• After that, look for the “WriteProtect” registry entry which is located on the left side of the window, and then double click on it.
• Change its value to “0” and click OK to save the changes made and exit the Registry Editor.

Option 3 – Run CHKDSK to check the drive for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system including the “Diskpart failed to clear disk attributes” error.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]

Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.

• Now if you are prompted to run CHKDSK after your reboot your PC, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.

Option 4 – Clear the attributes on RAW

• Tap the Win + S keys then type “diskpart” in the field.
• Click the Diskpart application and if a User Account Control dialog box pops up, click Yes to proceed.
• After opening an elevated Command Prompt, type in the commands listed below and make sure to tap Enter right after you key in one command after the other.
  • list volume
  • select volume ‘n’ (In this command, you have to replace ‘n’ with the volume number of the drive)
  • format fs=fat32 quick (In this command you also have the flexibility to change the format to ‘ntfs’ or ‘exfat’)
• After executing the commands given, unplug the removable storage device and wait for a couple of seconds and then plug it back in.
• Now try any normal write operations and see if the error no longer appears.

Option 5 – Try checking the hardware components

On the other hand, it is also possible that the issue has something to do with a hardware problem and so you need to check the hardware components on your computer to determine that.

The Windows Subsystem for Linus, also known as WSL, is a useful and excellent tool for developers. However, it isn’t without flaws as users can still encounter some errors when using it. One of these errors is the error code WslRegisterDistribution, 0x8007019e,0x8000000d. Although it seems like the error is have something to do with the installation of WSL, it could be a false positive since some users who’ve installed WSL still encountered the same problem. Here’s the context of the error:

“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.

Option 1 – Try to enable the WSL using the “Turn Windows features on or off” option

• To get started, search for “Turn Windows Features on or off” in the Start Search and click on the appropriate result to open a dialog box.
• After that, you will see a populated list in the dialog box and from there, look for the “Windows Subsystem for Linux” option.
• Once you find it, select OK. This will search and install the system files needed and ask you to restart your computer.
• Restart your computer. The Linux distro should now work without any trouble.

Option 2 – Try to use Windows PowerShell

The next thing you can do to fix the error code 0x8007019e or 0x8000000d is to use Windows PowerShell.

• Tap the Win + X keys and click on the “Windows PowerShell (Admin)” option to open Windows PowerShell as admin.
• After that, execute this command to enable the Windows Subsystem for Linux feature: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
• The command you entered will start to search for the required system files and install them.
• If prompted, type “Y” to restart your computer. This should fix the problem.

As you know, Excel sheet is frequently acclaimed as one of the most useful software that allows users to create spreadsheets, crunch numbers as well as prepare a business report. Usually, tapping the arrow keys to move from one cell to another. However, there are times when you might experience trouble in tapping them – for instance, they won’t work when you tap them. This kind of problem can be quite frustrating since no matter what you do, especially when you tap the arrow keys, instead of a single cell, it moves the entire spreadsheet. If you are one of the users who experience this problem, worry no more for this post will guide you on what you can do to fix it. When arrow keys won’t function as intended in Excel spreadsheets, it could be due to unintended behavior of the Scroll key or it could be related to some issues with the keyboard driver. Whatever the cause is, here are some suggestions you can check out to fix it.

Option 1 – Try to disable the Scroll Lock

The first thing you can do to fix this problem with arrow keys is to disable the Scroll Lock. Although doing this is easy, newer laptops don’t actually come with it so if your keyboard does not come with a scroll key, all you have to do is tap the Fn key and disable Scroll Lock. Aside from that, you could also use the on-screen keyboard to turn off the Scroll Lock. You will see its status on the Excel sheet which will help you to double-check. Moreover, you could also tap the Shift + F14 keys to toggle off the Scroll Lock. To use the on-screen keyboard to turn off Scroll Lock, follow the steps below.

• Tap the Windows key and type “on-screen keyboard” and then tap Enter.
• Once the on-screen keyboard is opened, you should see that the Scroll Lock is on the “On” position since the ScrLk keys are in blue.
• Like pointed out earlier, you can utilize the Scroll Lock indicator located in the status bar as well as disable or enable the scroll key by using this feature on Microsoft Excel.

Option 2 – Try turning on the Sticky key

If disabling the Scroll Lock did not fix the problem, you can try turning on the Sticky Key instead. A lot of users reported that this option fixed the problem for them. So you should try to turn on the Sticky key and to do that, follow the steps below.

• First, type “control panel” in the Start Search and click on Control Panel from the search results.
• Next, select the “Turn On Sticky Keys” option and click on OK.
• After that, go back and uncheck the “Turn On Sticky Keys” option. This should fix the malfunctioning arrow keys on Excel.

Option 3 – Try running the Hardware and Devices Troubleshooter

The first thing you can do to fix the problem is by running the Hardware Troubleshooter. Although it won’t make much of a difference, there’s still a possibility that it could automatically fix the problem with these function keys. To use it, refer to these steps:

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 4 – Update the keyboard driver

You can also update the keyboard driver to fix the problem. There are cases when an outdated or corrupted driver can fix the problem. To do so, follow the steps below.

• Tap the Win + R keys to open the Run dialog box.
• Then type “devmgmt.msc” in the field and hit Enter to open the Device Manager.
• From there, look for the keyboard driver and click on it.
• Next, right-click on the keyboard driver and select the Update driver option.
• After that, click the “Search automatically for updated driver software” option to proceed.

Option 5 – Reinstall the keyboard driver

If updating the keyboard driver didn’t help, then you might want to reinstall it. How? Follow the steps below.

• Tap the Win + R keys to launch Run.
• Type in MSC into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. Look for the keyboard driver, right-click on it and then select “Uninstall device”.
• After that, unplug the device and restart your PC.
• Then plug your device back in. Assuming your device is connected to your PC, open the Device Manager again.
• Next, click on the Action button and click the Scan for hardware changes button. That should fix the problem

Note: You could also completely uninstall the driver and go directly to the manufacturer’s website and download the latest driver for your hardware and then install it.

A lot of users lately reported getting an error that says, “The application has failed to start because its side-by-side configuration is incorrect”. This kind of error can pop up when you try to open a number of programs, regardless of their origin, the developer, and compatibility. Here’s the full context of the error message:

“<PATH OF THE EXECUTABLE FILE>, This application has failed to start because its side-by0side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail”.

This kind of problem has something to do with the C++ runtime package in the background. It could also be related to an error for a registry value. Whatever the cause is, you can fix this error with the help of some suggestions provided in this post. You can try to reinstall the application or check the registry setting or reinstall the suitable Visual C++ Runtimes or re-enable the Microsoft .NET Framework. For more details, refer to the instructions given below.

Option 1 – Try to reinstall the application

There are times when some supporting module for your application under the hood could have messed up the application. And so to fix that, you need to uninstall the concerned application and then try reinstalling it again. Once you’re done, check if it fixed the problem or not.

Option 2 – Try to change the Registry setting

• Tap the Win + R key combination to open the Run dialog box.
• Then type “Regedit” in the fields and tap Enter to open the Registry Editor.
• Next, navigate to this registry key: Computer HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion SideBySide Winners x86_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_none_02d0010672fd8219 9.0
• From there, look for a String value named “default” and double click on it.
• After that, change its Value data to match the one as the third value in BINARY.
• Now restart your computer to successfully apply the changes made.

Option 3 – Try reinstalling the appropriate Visual C++ Runtime

• You need to open the Event Viewer first by searching for it in the Windows Search box.
• After opening Event Viewer, look for the error events that are sourced by SideBySide.
• Next, look for the actual Visual C++ Runtime module that’s causing the error.
• Now download the module from the official website of Microsoft Support and then install it and see if it fixed the problem.

Option 4 – Re-enable the Microsoft .NET Framework

You could also try to disable the Microsoft .NET Framework then enable the latest version of the .NET Framework on your PC and check if the error is fixed.

The feature that was originally planned for now scrapped Windows 10X is included in Windows 11. You will be able to customize your Virtual desktop with different wallpapers for each screen. In order to fully customize your virtual desktops with different wallpapers follow this easy step-by-step guide.

1. Click on the Task View button in the taskbar
2. When the Task View opens, select the desktop on which you want to set wallpaper
3. The view will switch to the selected desktop. Right-click anywhere on the desktop and select personalize
4. In personalization settings, click on the background
5. Select wallpaper which you would like to have on the desktop by clicking on browse and navigating to the desired one
6. Close the settings
7. Repeat for each virtual desktop you would like to customize

One of the most critical processes in the Windows 10 operating system is the Explorer.exe. And there are times when you might encounter an error that says, “System call failed”. You can encounter this error when you try to launch File Explorer, and in such case when the File Explorer does not work, it could cause issues in accessing folders and files on your computer. This kind of error pops up when the explorer.exe system file has become corrupted or if there is some process that interferes with its smooth functioning. To fix this error, you can try to restart the explorer.exe process, run both the System File Checker scan and DISM tool. You could also put your computer in a Clean Boot State or uninstall any programs you’ve installed recently. For more details, follow each one of the given suggestions below.

Option 1 – Try to restart the Explorer.exe process

The first thing you can do is try to restart the Explorer.exe process. To do so, refer to these steps:

• First, right-click on the Taskbar and select the Task Manager.
• Next, expand the Task Manager window to see all the active processes.
• From there, look for the Windows Explorer process, right-click on it and select Restart.
• After that, check if the error is now fixed.

Option 2 – Run System File Checker scan

If restarting the explorer.exe process didn’t work, you can also try running the System File Checker or SFC scan to fix the error. System File Checker is a command utility built into your computer that helps restore corrupted files and missing files. Refer to the following steps to run it:

• Hit the Win + R keys to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in this command: sfc /SCANFILE=c:windowsexplorer.exe

Note: If you are using a 64-bit Windows operating system, enter the “sfc /SCANFILE=C:WindowsSysWow64explorer.exe” command instead.

• Wait until the process is completed and then restart your computer.

Option 3 – Run the DISM tool

You might also want to run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like the “System call failed” error. To repair these corrupted system files, you can run the DISM commands:

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the problem is now fixed.

Option 4 – Try running the Check Disk utility

• In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
• After opening Command Prompt, type this command and tap Enter: chkdsk c: /f /r
• The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
• Tap the Y key to schedule Disk Check the next time your computer restarts.

Option 5 – Put your computer in a Clean Boot State

As pointed out, there are some instances that some conflicting programs installed in your computer might be the one that triggers the “System call failed” error to appear when you try to open File Explorer. To identify which program is causing the problem, you need to put your computer in a Clean Boot State. To do so, follow the steps below.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Once your computer has restarted in a Clean Boot State, perform your scan again and see if it now works, and then start to isolate the problem by checking which one of the programs you installed recently is the root cause of the problem.

Option 6 – Try to uninstall the programs you’ve installed recently

In case you don’t know, freeware software packages aren’t always free as some of them could contain malicious software that can cause serious damage to your computer. Thus, if you have installed a program recently prior to getting the “System call failed” error, then you have to uninstall that program.

• Tap the Win + R keys to open the Run dialog box.
• Then type “appwiz.cpl” in the field and tap Enter to open the Programs and Features in Control Panel.
• Next, arrange the list of installed programs in the order of the installation date.
• After that, look for the problematic program and right-click on it, and then select Uninstall.
• Once the process is done, restart your computer and see if the error is fixed.

In an operating system, it is ideal for an administrator to have permission to access all the folders and files. However, there are times when you try to access the security settings or attempt to view the properties of a file, you could encounter an error saying, “You do not have permission to view this object’s security properties, even as an administrative user”. This kind of error may be caused by several reasons. For one, if your computer is infected with a virus or malware which might have caused some changes to the concerned folder or file. It could also occur if a program or service is using the folder or file simultaneously which explains why you’re not able to access the system. It could also be that the folder or file might have been owned by a user account that no longer exists or you might not have the permissions to view the targeted folder or file even though you’re logged in as administrator. To fix the “You do not have permission to view this object’s security properties, even as an administrative user” error, here are some options that might help.

Option 1 – Put your computer in a Clean Boot State

You can also troubleshoot the problem in a Clean Boot state. It could be that there are some third-party applications in your computer that’re preventing you from accessing security settings or properties of a file and to isolate this possibility, you need to boot your computer in a Clean Boot State and then try installing the program again. Putting your computer in this state can help you identify which program is the culprit and thus isolates the problem. In a Clean Boot state, your computer will start using only the pre-selected minimal set of drivers and startup programs. Note that you have to disable and enable one process at a time.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After you’ve set your computer into a Clean Boot State, try to check if the error is now fixed and that you can now view the Properties.

Option 2 – Try booting your computer into Safe Mode and delete inactive users

Aside from the Clean Boot State, you can also reboot your computer in Safe Mode and then delete all the inactive users. There are instances when the folder was created or owned by a user account that’s either deleted or inactive now and so you need to get rid of these inactive user accounts to resolve the error.

• First, boot your computer in Safe Mode.
• Then right-click on the concerned folder or file and select Properties.
• Next, select Advanced in the Security tab and click on Add.
• A new window will appear and from there, click on “Select a principal”.
• And then type the name of the user to who you wish to give permissions in the “Enter the object name to select” box.
• Now select Check Names and this would resolve the user name.
• After that, click OK to save the settings. This will close the window and take you back to the previous one.
• Next, from the drop-down menu, change the Type to Allow and select the Full Control checkbox.
• Click OK to save the changes made and then restart your computer in a normal mode.

Option 3 – Try to take ownership of the folder or file

Another thing you can do to fix the problem is to take ownership and force the system into giving permissions to the Administrator. How? Refer to these steps:

• Type “command prompt” in the Windows Search bar and then right-click on the relevant search result and select “Run as administrator”.
• After that, if a User Account Control or UAC prompt appears, just click on Yes to proceed.
• Next, type and enter this command: TAKEOWN /F <path>
• Note that the <path> is the location of the folder or file in File Explorer.
• Now type and enter this second command: ICACLS <path> /grant administrators:F
• Finally, once the command has been executed, restart your computer and then see if you can now access the folder or file.

Option 4 – Try scanning your computer using Windows Defender

As mentioned, the error when accessing the security settings or properties of a folder or file might be due to a virus or malware. It could be that it had made some modifications that prevents you from accessing security settings or properties. To eliminate it, you have to scan your computer using security programs like Windows Defender.

• Tap the Win + I keys to open Update & Security.
• Then click on the Windows Security option and open Windows Defender Security Center.
• Next, click on Virus & threat protection > Run a new advanced scan.
• Now make sure that Full Scan is selected from the menu and then click the Scan Now button to get started.

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.