Upcoming comic book movies with release dates

As you know, the CHKDSK utility is proven to be one of the useful tools to fix any issues that concerns file system, storage, and disk. However, as useful as it may be, it is still not immune to issues as you could encounter errors when running it. One of these errors is the “One such error is the CHKDSK cannot continue in read-only mode” error. If you receive such an error message while running CHKDSK, then you’ve come to the right place as this post will help you sort the problem out. It is possible that the drive is read-only or that the Write Protection is enabled. It could also be that the drive is already being used and scanned by a different program or utility. To get rid of this error, there are a couple of suggestions you need to check out. You can try to run the CHKDSK utility from Recovery or run it on Boot. You could also try to disable Write Protection. For more detailed steps, follow the given instructions below.

Option 1 – Try to run the CHKDSK utility from Recovery

The first thing you can do to resolve the error in CHKDSK is to run the CHKDSK utility from Recovery. How? Follow these steps:

• First, boot into the installation environment for Windows 10 from a Windows installation media.
• Next, click on the “Repair your computer” option.
• After that, select Troubleshoot > Advanced options > Command Prompt.
• After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /r /f
• Wait until the disk error checking process is completed.
• Once it’s done, exit the Command Prompt window and restart your computer and then see if the error is fixed.

Option 2 – Try running the CHKDSK utility on Boot

On the other hand, you can also try to run the CHKDSK utility on Boot so you can fix the error and recover any damaged segments of the drive.

• Open an elevated Command Prompt and enter this command: chkdsk /r
• After that, you will a message that says, “Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)”
• Type Y and tap Enter to schedule a CHKDSK scan once your computer reboots next time.

Option 3 – Try to remove the Write Protection from the drive

As mentioned, removing the Write-Protection on the concerned drive could also help you fix the problem and there are two ways to get rid of the write protection – you can either use the Diskpart utility or the Registry Editor. How? Refer to the following steps.

Via Diskpart utility:

• Open Command Prompt with admin privileges and then type the “diskpart” command and tap Enter to execute it.
• Next, type “list disk” and tap Enter to get the list of all the Disk connects or all the partitions that are formed on those disks.
• After that, you need to choose one command depending on the list of commands you entered. Type “select disk #” and tap Enter to select the disk or partition you want to select.
• Then type “attribute disk clear readonly” and tap Enter to Disable the Write Protection on the selected disk or partition.

Via Registry Editor:

• Tap the Win + R keys to open the Run utility and type “Regedit” in the field and then tap Enter to open the Registry Editor.
• Next, navigate to the following registry key:

ComputerHKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlStorageDevicePolicies

• After that, look for the DWORD named “WriteProtect” and double click on it, and then set its Value Data to “0”.
• Now restart your computer and see if the problem is now fixed or not.

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.

If you are typing inside the Search bar, Cortana, Taskbar, Windows 10 apps, etc., and then everything seems invisible then read on as this post will guide you in fixing this issue. At first, you might think that something is wrong with your keyboard but it really has nothing to do with it. The problem actually lies with the apps from Microsoft Store. Thus, if you can’t type anything in any of the apps from Microsoft Store in Windows 10, refer to the options given below to fix them.

Option 1 – Ensure that ctfmon.exe is running

Ctfmon.exe is a Microsoft process in Windows 10 that controls the Alternative User Input as well as the Office Language bar. In other words, it enables end-users to control the computer using on-screen keyboard inputs, speech, and even pen for various languages. It would be better if you launch the program once by going to the C:/Windows/system32 folder. Doing so will ensure that whatever API is needed for the keyboard typing to work properly again. You also have to make sure that its startup status is not disabled. In addition, you can also try the following steps, alternatively.

• Open the Task Scheduler.
• Then go to Microsoft > Windows > TextServicesFramework.
• And on the MsCtfMonitor, right-click and enable the task.
• Now restart your computer.

This will ensure that all the text boxes will start to work again. And if the task MsCtfMonitor is missing from the list of tasks, you can import it with the XML file from basics.net. Then download and create a task to run it each time you log in to your PC.

Option 2 – Use the Windows Store Apps Troubleshooter

You might also try running the Windows Store Apps Troubleshooter as it can help in resolving issues with the Windows Store apps. This built-in tool can resolve most of the app-related problems. To use it, go to Settings > Update & Security > Troubleshooting > Windows Store Apps and from there, click the start the troubleshooter button. The Windows Store Apps Troubleshooter will scan the computer for any issues with the Windows store apps and will automatically fix them if it finds any.

Option 3 – Re-register all the Windows 10 UWP apps using PowerShell

• First, make sure to close all the running applications on your computer.
• Next, in the Start search, type in PowerShell and right click on the result, and select the “Run as administrator” option.
• After that, type the following commands to re-register the Windows 10 apps. Make sure to hit Enter on each line:
  • reg delete "HKCUSoftwareMicrosoftWindows NTCurrentVersionTileDataModelMigrationTileStore" /va /f
  • get-appxpackage -packageType bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + "appxmetadataappxbundlemanifest.xml")}
  • $bundlefamilies = (get-appxpackage -packagetype Bundle).packagefamilyname
  • get-appxpackage -packagetype main |? {-not ($bundlefamilies -contains $_.packagefamilyname)} |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + "appxmanifest.xml")}

Option 4 – Try to run the DISM tool

You can also run the DISM Tool as it helps in repairing the Windows System Image as well as the Windows Component Store in Windows 10. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth” which could help in fixing the problem.

• Open the Command Prompt with admin privileges.
• Then type in the following commands and make sure to hit Enter right after you type each one of them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • exe /Online /Cleanup-image /Restorehealth
• Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 5 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Restart your PC.

Windows 10 users a set of rules or standards called Network Protocols in communicating over the internet. These protocols are the ones that made sure that the data is correctly sent between computers. However, if any of the Network Protocol is missing in your Windows 10 computer, then you will most likely encounter a problem like not being able to browse the internet, or share files. For this, you can try to run the Incoming Connections troubleshooter: As you were not able to connect to your internet connection using your PC, you can try to run the Incoming Connections troubleshooter as it might resolve the problem. Refer to the following steps to run this troubleshooter:

• Tap the Win + I keys to open Settings.
• After opening Settings, go to Update and Security.
• Next, navigate to the Troubleshoot pane and select the Incoming Connections section and click the Run Troubleshooter button to get started.
• Wait until the troubleshooter is finished doing its job and then try connecting to your network again.

If after running the Incoming Connections troubleshooter you receive an error message instead that says, “Network Protocol is missing”, then here are some suggestions you need to check out to fix it. Take note that you must have admin privileges before you start troubleshooting the problem.

Option 1 – Try to update or rollback or uninstall the Network drivers

You might also want to update, roll back, or disable your Network drivers to fix the “This operation failed as no adapter is in the state permissible for this operation” error.

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
• Then right-click on each one of the Network drivers and depending on your preference, you can either select “Update driver”, “Disable device” or “Uninstall device”.
• After that, restart your PC and see if it helped in fixing the netio.sys Blue Screen error.

Option 2 – Try to reset Winsock, TCP/IP & Flush DNS

You might also want to try resetting Winsock, TCP/IP, and flushing DNS might help you resolve errors. To do so, follow these steps:

• Right-click on the Start button and click on Command Prompt (administrator) so you can pull up an elevated Command Prompt.
• After that, execute each one of the commands listed below. And after you typed in one after the other, you have to hit Enter.

1. netsh winsock reset – type in this command to reset Winsock
2. netsh int ip reset resettcpip.txt – type in this command to reset TCP/IP
3. ipconfig /flushdns – type in this command to flush the DNS cache

• Next, restart your PC and check if the problem’s fixed.

Option 3 – Diagnose the Network Adapter

To diagnose the Network Adapter, go to Control Panel > All Control Panel Items > Network Connections, and from there, look for the network adapter that could be causing the error. Note that if you are using a Wi-Fi connection, then it’s probably your Wi-Fi adapter, otherwise it has something to do with your Ethernet adapter. Just right-click on the problematic network adapter and select diagnose to troubleshoot.

Option 4 – 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.

Option 5 – Try importing Winsock settings from another computer

If resetting Winsock or the Network didn’t fix the problem, then you can try to import settings from a computer that’s in good condition. You need to have access to the registry to get this done and then export and import a couple of settings. Refer to these steps to get started:

• Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, go to this registry path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
• Next, look for two registry keys named “Winsock” and “Winsock2” and then right-click on each one of them and select the Export option.
• Now copy the registry keys to a USB drive and then copy the keys on the PC in excellent condition.
• Then double click on each one of them and it will install the WINSOCK keys.

It is common knowledge that when you open a file that contains viruses, it will automatically infect the operating system. This is why most antivirus programs like Windows Defender won’t allow the opening of a file or execution of any associated program if they detected that the file or program could potentially harm the computer. In situations like this, you may get an error stating, “Operation did not complete successfully because the file contains a virus”. In addition, it is also possible that this error message can pop up even for known programs. To open the program or file that triggered the error, you will be given a couple of options in this post but make sure that the program or file is really safe to open and does not contain any virus. You can open the file or execute the program by disabling the Windows Defender or any antivirus program temporarily. You could also try to add an exclusion in your antivirus program or repair File Explorer or run the Disk Cleanup tool. For more details, refer to each one of the options provided below.

Option 1 – Try to temporarily disable the Windows Defender program

Although you could encounter this error with any antivirus program, it is more common in Windows Defender. Thus, you can try to disable it for a while when you open the file or execute the program. To do so, follow these steps:

• First, click on the Start button and go to Settings > Update and Security > Windows Security.
• Here, select the “Open Windows Security” option located in the right pane.
• After that, click on the “Virus and threat protection” option.
• Next, click on Manage settings under the Virus and threat protection settings.
• Then turn off the switch for both Real-time protection and Cloud-delivered protection.
• Now restart your computer and try to open the file or execute the program again and see if it works.
• Note: Do not forget to enable the Real-time protection and Cloud-delivered protection back in Windows Defender.

Option 2 – Try adding an exclusion in the Windows Defender program

• Open the Windows Defender Security Center from the system tray area.
• Next, click the “Virus & threat protection” option and then open the “Virus and threat protection settings”.
• After that, scroll down until you find the “Exclusions” and click on the “Add or remove exclusions” option.
• Then click the plus button and select the type of exclusion you want to add and from the drop-down list, select Folder.
• Next, navigate to the path where the file or program is located.
• When a User Account Control or UAC prompt, just click on Yes to proceed.
• Now try to run the program or file again and see if it worked. If it did, then make sure to turn on your antivirus. However, if it didn’t work, proceed to the next given options below.

Option 3 – Try to run a System File Checker scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be the cause why you’re getting the errors 0x8024a11a and 0x8024a112. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Now restart your computer and see if the problem is fixed or not.

Option 4 – Run the Disk Cleanup tool

You can also try using the Disk Cleanup tool. To use it, refer to these steps:

• Tap the Win + R keys to open the Run dialog box and then type “cleanmgr” in the field and hit Enter to open the Disk Cleanup window.
• After that, select the drive you want to clean.
• Now click OK to clean the disk and restart your computer.

When you upgrade or update your Windows 10 computer but you suddenly got Error 0x8024a206 while trying to install the updates, it is due to a rouge update that was downloaded or because of some corrupted component in Windows. In case you don’t know, any file downloaded by Windows is verified for its integrity and if the files don’t pass the integrity test, then Error 0x8024a206 will most likely pop up during the Windows update or upgrade.

Option 1 – Reset the Windows Update components to the default

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the contents in the SoftwareDistribution folder. The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 2 – Re-register DLLs related to Windows Update

DLL files, also known as Dynamic Link Library, are parts of applications that are separated from the core program so that they can be used again as well as independently be updated. The DLL files are loaded into memory and then used. Note that they have to be registered with Windows so they can be loaded. So if they’re not, the main program will fail. And this is the same with the DLL files related to the Windows Update. Thus, you need to register them in order to resolve Error 0x8024a206.

• In the Cortana search box, type “command prompt”.
• From the search results that appear, right-click on Command Prompt and select the “Run as administrator” option.
• After that execute the commands listed below one after the other and don’t forget to hit Enter right after you key in each one of them.
  • regsvr32 JSCRIPT.DLL
  • regsvr32 MSXML3.DLL
  • regsvr32 WUPS2.DLL
  • regsvr32 WUPS.DLL
  • regsvr32 WUAUENG.DLL
  • regsvr32 WUAPI.DLL
  • regsvr32 WUCLTUX.DLL
  • regsvr32 WUWEBV.DLL

Note: You also have the option to run the commands together via a batch file. Simply create a batch file by copying all the commands in a notepad and then save it as “WURegisterDLL.bat”. After that, run the batch file and it will execute the commands all at the same time. Then you have to restart your computer and see if it has fixed the Error 0x8024a206.

Option 3 – Run the System File Checker

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the Error 0x8024a206. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow and hit Enter.

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 4 – Run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update Error 0x8024a206. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Running the Windows Update service does not always go well as from time to time, you could encounter some errors when using it. One of these errors is the Windows Update Error 0xc1900403. In such cases, you will see the following error message under the Windows Update section:

“There were problems installing some updates, but we’ll try again later, If you keep seeing this and want to search the web or contact support for information, this may help – 0xc1900403”

The log files displayed in the error message may include, “0XC1900403 – MOSETUP_E_UA_CORRUPT_PAYLOAD_FILES”. This indicates that the payload files are corrupted which is why you’re getting the Windows Update Error 0xc1900403 and to fix it, you can try to restart your computer and install the updates again or reset the Windows Update-related folders. You could also run the Windows Update troubleshooter or use either the Standalone Installer or the Media Creation tool. For more details, refer to each one of the options provided below.

Option 1 – Restart your computer and try installing the Updates again

Restarting your computer can also help in fixing the Windows Update failed to install error 0x80240034. There are cases where the issue resolves on its own as it could just be some simple network or PC error.

Option 2 – Delete the contents in the Software Distribution folder and Catroot2 folder

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:/Windows/SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 3 – Try running the Windows Update troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing Windows Update Error 0xc1900403. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Option 4 – Try to use the Media Creation tool

The Media Creation tool in Windows allows you to use the ISO installation file to make a bootable device that you can use to install Windows on your PC. Note that this is kind of different from the usual installation process as it could erase your computer’s current settings and data on the primary drive. Thus, before you proceed, you need to backup all your data into some removable drive and then use the Media Creation Tool to make a bootable drive.

• After making the bootable drive, you need to plug it into your computer and then reboot.
• Next, tap the F10 or Esc key to open the boot options.
• Now set the boot priority of the removable drive the highest. Once the setup comes forth, follow the next onscreen instructions and install Windows without any problems.

If you suddenly encounter a PNP_DETECTED_FATAL_ERROR Blue Screen error, then this post can help you out. The PNP_DETECTED_FATAL_ERROR BSOD usually occurs when any new hardware that is mostly the Plug and Play type is attached. In such cases, when the device is plugged, and the driver for that device crashes or isn’t found or is not compatible, you will most likely encounter this particular BSOD error. There are several error codes that come under this category, some of them are 0x000000CA (0x01681690, 0xEA96A7BE, 0x938A81AD, 0xF8362881. This BSOD error can also occur at any time. However, the only constant thing here is when you plug a PNP device like earphones, microphones, USB drives, and many more. The PNP_DETECTED_FATAL_ERROR bug check has a value of 0x000000CA which indicates that the Plug and Play Manager encountered some severe error which is most likely have something to do with a problematic Plug and Play driver. To fix this error, here are some possible solutions that could help.

Option 1 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like PNP_DETECTED_FATAL_ERROR Blue Screen error. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 2 – Try disabling or removing newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the PNP_DETECTED_FATAL_ERROR Blue Screen error.

Option 3 – Try disabling BIOS Memory options namely Caching Shadowing

Disabling the BIOS Memory options such as Caching and Shadowing can help you in fixing the PNP_DETECTED_FATAL_ERROR Blue Screen error. All you have to do is enter the BIOS first and then use the Arrow and Enter keys to select your choices. And if you can’t seem to find it, look for specific instructions from your OEM or you could also look out for instructions from the manufacturer of your motherboard.

Option 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the PNP_DETECTED_FATAL_ERROR Blue Screen error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 5 – Try to uninstall programs you’ve installed recently

Chances are, some programs that you just installed might be the one that’s causing the BSOD error. Thus, you need to uninstall the program to resolve the problem.

• In the search box, type in “control” and then click on Control Panel (desktop app) among the search results.
• After that, select Programs and Features from the list which will give you a list of all the programs installed on your computer.
• From there, look for the concerned program and select it and then uninstall it.

Option 6 – Update the Device drivers

• Tap the Win + R keys to launch Run.
• Type in devmgmt.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 device driver you and then select either “Update driver” or “Uninstall device”. And if you find any “Unknown device”, you need to update it as well.
• Select the “Search automatically for updated driver software” option and then follow the instructions to complete the process.
• If you have chosen to uninstall the driver, follow the screen options to complete the process and then restart your PC.
• Connect the device and Scan for hardware changes – you can see this option under Device Manager > Action.

Option 7 – Perform a System Restore

Performing System Restore might help you in fixing the PNP_DETECTED_FATAL_ERROR Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

The Windows 10 system allows users to change the default location of the User folders to another drive. This is probably to make sure that the files stay safe in case the system suddenly crashes. However, in some cases, while changing the path to another drive, for instance, the D drive or any folder, the Windows system recognized it as a hard drive as well so even though the files will be saved on that folder, it will appear as a hard drive in the Windows Explorer or look merged with another folder. It could also be that you had dragged and dropped a user folder to another user folder by accident. So if you’re wondering how you can unmerge the User folders, read on as this post will guide you on how exactly you can do that. Take note that even if you try to use the File History to restore the User folders, it still won’t work and you won’t be able to move them back to their previous locations nor restore the folders back to their previous versions and it would only state that they are not available. In the instructions given below, we are using the Downloads folder as an example.

• Step 1: Tap the Win + R keys to open the Run dialog box.
• Step 2: Next, type “Regedit” in the field and hit Enter to open the Registry Editor.
• Step 3: After opening the Registry Editor, navigate to the following registry key:

ComputerHKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders

• Step 4: Then double-click on the multi-string value {374DE290-123F-4565-9164-39C4925E467B} located in the right hand pane. And in the Value Data, copy and paste the following value:

%USERPROFILE%Downloads

• Step 5: Now click OK and close the Registry Editor.

Note: Look close enough and you’ll see that the multi-string values belong to each one of the folders. From there, you have a Desktop, Favorites, Skydrive, Music, Pictures, and many more.

• Step 6: Restart your computer. After that, the operating system will pick up the new folder location during the startup. Here are the values for the other folders:

Music – {1CF1260C-4DD0-4ebb-811F-33C572699FDE} Pictures – {3ADD1653-EB32-4cb0-BBD7-DFA0ABB5ACCA} Videos – {A0953C92-50DC-43bf-BE83-3742FED03C9C} Documents – {A8CDFF1C-4878-43be-B5FD-F8091C1C60D0} Desktop – {B4BFCC3A-DB2C-424C-B029-7FE99A87C641}

• Step 7: Now all you have to do is to change the location correctly. Start by tapping the Win + E keys to open the Windows File Explorer.
• Step 8: After that, right-click on the Downloads folder located in the right-hand pane.
• Step 9: Then click on Properties and go to the Location tab then type “D:\Downloads” in the location box.
• Step 10: Click the Apply button and then the OK button to save the changes made. Doing so would ensure that not only the Downloads folder is restored but also that it does not stay merged to another folder or appear as a drive.

Microsoft has released Windows 11 as a public beta release for all the people that are not willing to be in the insider program. Beta release as of this moment is identical to Insider Preview build 22000.100. and updates will not roll so fast as in insider preview and it is marked as unstable release, same as insider build. I would not install Windows 11 beta on the main PC since some drivers still have issues and may lead to some blue screens. Be aware that the beta build will have all Windows 11 system requirements including TPM 2.0. This is a big difference from insider build which can be installed on systems lacking official requirements. So basically if you have a spare PC that could run Windows 11 install it so you can see what it brings and feel it so you can make a decision will upgrade once it is released later this year.