This error will prevent you from scanning the drive. The scan, usually, doesn’t work when you type Y (Y for Yes) to schedule the scan for the next startup of your system. You will either see the same error or you will encounter an error “Failed to transfer logged messages to the event log with status 50” while performing the scan. The reason for this error is exactly what the error message says. The drive cannot be locked because it in use by another process. The chkdsk cannot perform the scan while your disk is in use. Sometimes, the problem might be related to a third party application causing the chkdsk to give this error. Chkdsk schedules the scan on the next restart because that is the time when your drive won’t be used by other programs. Windows will run the scan before all the programs/files load properly. So, the issue will most likely resolve on the scheduled scan. If the chkdsk gives the same error on the scheduled scan then that means your drive is still in use. This will finally be resolved by running the command prompt from the Advanced Startup Options. That solves the issue because your OS isn’t loaded at that time.

Tips

Turn off your security applications like anti-virus applications. These applications usually have a disable option that can be used to disable these applications for a short period of time. Simply right click the application icon from the system tray and select the disable option. If you can’t see the disable option then double click the security application icon and look for a disable option in that panel. Once the security application is disabled, try to run the chkdsk commands again.If you started to see the issue after a Windows Update then that might be an issue. There were cases when the Windows Update introduced a bug that would prevent people from using the chkdsk properly. These kind of bugs are fixed in the later updates. So, make sure your Windows is updated to the latest versionIf you are seeing the error “failed to transfer logged messages to the event log with status 50” while trying to run the chkdsk then you need to get in touch with your HDD manufacture’s or buy a new HDD. This error means that your HDD is badly damaged or corrupted.

Method 1: Run chkdsk /f /r /x

Running the chkdsk / f / r / x usually resolves the issue for a lot of users. If you are seeing the error on running this command then you should skip this method. Here are the steps for running this command

Once the command runs, either the scan will run successfully or your will see the message “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)” If you see this message, simply type Y and press Enter to schedule the scan. Once done, reboot and the scan will run on the startup.

Method 2: Chkdsk in Safe Mode

If method 1 didn’t work or rescheduling gives the same error or rescheduled scan doesn’t even start then try to run the chkdsk in safe mode. Here are the steps for getting into Safe Mode

Check if the chkdsk still gives the error or not. Note: You need to turn off the Safe Mode option when you are done with the chkdsk.

Method 3: Advanced Startup Options

Note: Before you proceed, make sure you have a Windows Installation Media. It can either be a CD/DVD or a Flash drive. The Installation Media should be the same as that of the version you have installed on the computer. If you don’t have one, you can borrow from a friend. This method doesn’t need you install anything. It will require you to use the Installation media to get into the Advanced Startup Options If the methods 1 and 2 didn’t solve your issue then running the chkdsk command from the Advanced Startup Options will resolve the issue for you. Here are the steps for running the command prompt from Advanced Startup Options menu

Close the command prompt and click Continue on the Advanced Startup options to reboot.

Important Note

If you are seeing different errors on different methods e.g. you are seeing the “failed to transfer logged messages to the event log with status 50” error when running chkdsk from Advanced Startup Options and you are seeing the “volume bitmap errors” when you run chkdsk in Safe Mode then there might not be a problem. If you keep seeing the same errors in these situations then you don’t have to do anything. The “failed to transfer…” error you are seeing in Advanced Startup Option might be because the log can’t simply be written to an installation disk. The point is, if you aren’t seeing any other big problems and your system is running fine without any BSODs or other issues then you should be fine. These errors might simply be because of the various different situations you are running the chkdsk into. However, if you notice any weird behavior or corrupt files then take your HDD to a computer repair shop and make sure it isn’t damaged or have any issues. If your HDD really is damaged then you might lose a lot of your personal data.

chkdsk /f /r vs chkdsk /r /fFix: Could not open lock file /var/lib/dpkg/lockFix: The Current Mail Client Cannot Fulfill the Messaging RequestFix: CHKDSK cannot continue in read-only mode Fix  chkdsk cannot lock current drive error - 46Fix  chkdsk cannot lock current drive error - 21Fix  chkdsk cannot lock current drive error - 56Fix  chkdsk cannot lock current drive error - 12Fix  chkdsk cannot lock current drive error - 16Fix  chkdsk cannot lock current drive error - 87Fix  chkdsk cannot lock current drive error - 7Fix  chkdsk cannot lock current drive error - 29Fix  chkdsk cannot lock current drive error - 79Fix  chkdsk cannot lock current drive error - 69Fix  chkdsk cannot lock current drive error - 40Fix  chkdsk cannot lock current drive error - 86Fix  chkdsk cannot lock current drive error - 34Fix  chkdsk cannot lock current drive error - 9