Generally, the Windows users face the error message Windows cannot run disk checking on this volume because it is write protected when the drive/volume is disabled or started to run into the Read Only mode. CHKDSK is an in-built command-line tool of Windows Operating System. It helps the users to identify the bad portions of the drive or partition. In addition, it can check the integrity of the system files saved on the drive. Furthermore, running the CHKDSK can help you to know whether the drive is damaged or is write protected.
If one of the drives of your computer is write-protected, then you are unable to edit the drive contents that includes editing of files or eliminating them from the system. To set it in a proper way, write protected shows that the volume is attributed to Read-only mode. As an example, the write protection of USB drives occurs to everyone. In this situation, you cannot copy the USB drive contents to the system or vice versa.
If you are facing the same issue, then it might be quite a difficult task for you to solve the issue yourself. But nothing to get worried about this. Here in this guide, we are going to provide you some amazing tips and tricks which can help you to fix this issue. Hence, you are advised to go through the article given below.
What Causes the Windows Cannot Run Disk Checking on This Volume Because it is Write Protected Error?
Usually, you can define write-protected status as read-only. That means, you can read the system files on write protected drive but you can’t create a new file or make any changes for the existing data. Let’s have a glance at the probable causes that accounts for why the drive get this error:
- Most of the manufacturer of the hard disk provides a write protection tab that comes included with the hard disk. Sometimes, if it switches to the Offline mode, then you can face this error.
- If the partition system file gets damaged or corrupted due to the virus or malware infection or another unknown reason, then it might be the reason behind the error.
- Sometimes, the attribute of the chosen drive is set to Read Only mode automatically and results in the Windows cannot run disk checking on this volume because it is write protected issue.
After identifying the reason why you cannot run CHKDSK on your write protected drive, let’s see how to eliminate this write protection error with different hacks.
Fix Windows Cannot Run Disk Checking on this Volume Because it is Write Protected Issue:
There are a lot of ways to troubleshoot the Windows cannot run disk checking on this volume because it is write protected issue. You need to stick to the solutions discussed below:
Procedure 1: Run CHKDSK Using Command Prompt
Before going to perform any complicated solution, you should try to resolve the Windows cannot run disk checking on this volume because it is write protected issue by running the CHKSDK. According to some users, they have fixed this issue by using several chkdsk commands. To run this, what you have to perform is:
At first, move the cursor to the bottom left corner of the screen and click on the Start menu. Then, you have to type ‘Command Prompt’ in the search field. As a result, it will show the Command Prompt option. Right-click on it. Choose the option ‘Run as Administrator’ from the list. It will open a Command Prompt window with Admin privilege.
Else if you prefer, you can also hit the X and Windows key from the keyboard to launch the Command Prompt. Then, select the ‘Command Prompt’ option from the list.
Type the command ‘chkdsk D: /f /r /x’ in the Command Prompt window. Here ‘D:’ is the default drive of the system.
The Parameters Working in the Following Way:
- /f: This parameter searches the drive of the system for any faults as well as it will try to solve them automatically.
- /r: This parameter scans the critical sectors of the drive and tries to resolve them.
- /x: This parameter dismounts the meaning of the drive if the drive is in use.
Restart the system to save the changes. After applying the above steps if you see that the error still persists, then you need to follow the other procedures discussed below.
Procedure 2: Change the Attribute Using Registry
Now, you should try to remove the write protection with the help of the Windows Registry. It can cause other complicated problems to the Operating System. Hence, you need to make sure that you perform the below steps carefully.
First, you have to open the Run Command box by pressing R and Windows key both at the same time from the keyboard. Then, type ‘regedit’ in the Run dialog box. Hit the Enter key from the keyboard. Else if you prefer, you can also tap on the OK button.
When the Windows Registry opens, you need to type the path ‘HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Control\StorageDevicePolicies’ in the location/address bar of this window. On the next window, you will see the ‘WriteProtect’ key. Click twice on it to replace the value from 1 to 0.
But, if you are still not able to find the Storage Device Policies folder from the Windows Registry, then you should perform the alternative steps provided below:
- After opening the Registry Window, you need to type the path ‘HKEY_LOCAL_ MACHINE\SYSTEM\CurrentControlSet\Control.’
- Now, you will see the New option in the middle of the next window. Choose the option ‘Key’ from the list.
- As a result, you will see a new folder. Right-click on it. Choose the ‘Rename’ option from the list. Then, type the name ‘Storage Device Policies’ and hit the Enter key from the keyboard. Now, you need to make sure that you have entered the name incorrectly.
- Then, highlight the folder that you have created recently. Move the cursor to the middle of the page and right-click on it. Choose the DWORD (32-bit) content from the list.
- Replace the name with ‘WriteProtect’ and replace the value from 1 to 0.
- Then, restart the system to save the changes.
After that, you need to check that the Windows cannot run disk checking on this volume because it is write protected issue is resolved or not. If the issue still persists, move on to the further methods.
Procedure 3: Using DiskPart Utility
DiskPart tool can help you in creating partitions on the drive. In addition, you can also use it to change the properties of a drive. To perform this, you should follow the steps given below:
At first, you have to navigate to the Start menu. Then, type ‘diskpart’ in the search bar to launch it.
After loading the Utility, you need to type ‘list volume.’
As a result, you will see a complete list of your hard disk volume. Now, you need to type the following ‘Select volume X.’ Replace the ‘X’ with the drive alphabet.
Now, type ‘attributes disk clear readonly’ and wait for a few times until the process completes. After completing the process, restart the system to save the changes.
After performing the steps, if you still face the Windows cannot run disk checking on this volume because it is write protected issue, then move on the method discussed further.
Procedure 4: Scan the Drive for Corruption
You can also fix this Windows issue by scanning the drive for any damaged files. Because it also might be the reason behind this issue. Here are the steps you should follow:
- At first, you have to navigate to the ‘This PC.’
- Then, right-click on the faulty driver. Then, choose the ‘Properties’ option.
- Navigate to the Tools tab.
- Now, you have to tap on the ‘Check’ option.
- If the windows prompt the UAC dialog box, then you need to tap on the Yes button.
- Now, wait for a few times until it completes.
After that, you need to check whether the issue has been resolved.
In the above discussion, we have provided some of the simplest solutions to fix the Windows cannot run disk checking on this volume because it is write protected issue. Hope that if you perform the above ways in their given order, then it will definitely help you to ease up your pain. After implementing the above-mentioned ways in their respective order, if you still face any kind of trouble, then you need to connect with a tech expert. In addition, you can also share your queries and valuable feedback through the comment box given at the end of this post.