CHKDSK Says It Cannot Lock the Drive — Here Is How to Fix It

CHKDSK "cannot lock current drive" appears when Windows cannot get exclusive access to the volume it is trying to scan. The drive is being actively used by the operating system or another process, so CHKDSK refuses to proceed. This guide covers every practical fix ranked by ease of execution.

Part 1. Why CHKDSK Cannot Lock the Current Drive

CHKDSK needs exclusive write access to a volume before it can check and repair the file system. When Windows itself is running from that drive, or when another process holds a file open on it, CHKDSK cannot obtain the lock.

The most common triggers are:

💡 Tip: Run handle.exe -a from Sysinternals to see exactly which process is holding a lock on the drive before trying any fix.

The exact error message in Command Prompt reads:

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)

Pressing Y is the simplest resolution for the system drive and is covered in Part 2.

Part 2. Fix 1 — Schedule CHKDSK at Restart (Best for C: Drive)

Scheduling CHKDSK to run before Windows loads is the standard Microsoft-recommended approach for the system partition. At that stage, almost no files are locked.

Steps:

1. Open Command Prompt as Administrator (search "cmd" → right-click → Run as administrator).

2. Type the following command and press Enter:

   chkdsk C: /f /r /x
   

3. When prompted "Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)", type Y and press Enter.
4. Restart your computer. CHKDSK runs automatically during the pre-boot phase.

💡 Tip: The /r flag locates bad sectors and recovers readable data. Include it along with /f to get the most thorough scan possible.

The scan can take anywhere from 10 minutes to over an hour depending on drive size and health. Do not interrupt the process.

Part 3. Fix 2 — Use the /scan Flag for an Online Scan

Windows 8 and Windows 10/11 support an online CHKDSK mode that runs without taking an exclusive lock. It can detect and log most errors even while the drive is in use.

Command:

chkdsk C: /scan

This performs a non-destructive scan and logs issues to the Event Viewer under Application → Wininit. It will not repair errors by itself, but it confirms whether a restart-scheduled full scan is needed.

🗣️ r/techsupport user: "I ran chkdsk /scan first to confirm there were errors, then scheduled the full /f /r scan at restart. Saved me from rebooting unnecessarily just to find out the drive was clean."

Use /scan when you cannot immediately restart and want a quick health check without the lock requirement.

Part 4. Fix 3 — Run CHKDSK in Safe Mode

Safe Mode loads a minimal set of drivers and stops most third-party services, which frees many file handles. For secondary drives (not C:), Safe Mode often allows CHKDSK to run successfully without scheduling a restart.

Steps:

1. Hold Shift and click Restart in the Start menu.
2. Go to Troubleshoot → Advanced Options → Startup Settings → Restart.
3. Press 4 to boot into Safe Mode.
4. Open Command Prompt as Administrator.
5. Run: chkdsk D: /f /r (replace D: with your target drive letter).

⚠️ Important: Even in Safe Mode, CHKDSK cannot lock the C: drive if Windows is loaded from it. Safe Mode only helps for secondary volumes or external drives that have software holding them open.

If CHKDSK still reports "cannot lock" on a secondary drive in Safe Mode, a service or device driver is likely mounting it automatically. Disable suspicious startup entries in msconfig before trying again.

Part 5. Fix 4 — Use the /offlineoff Flag

The /offlineoff flag disables automatic offline repair mode, which can sometimes cause a conflict when CHKDSK is already scheduled. More usefully, running CHKDSK with volume dismount flags on a secondary drive can bypass lock conflicts.

Command for a secondary drive:

chkdsk D: /f /r /x /offlineoff

The /x flag forces the volume to dismount, which releases all open handles by force. Combined with /offlineoff, this is effective against drives that remain locked due to shadow copies or VSS activity.

🗣️ r/Windows10 user: "Adding /x to my chkdsk command finally let it run on my external SSD. Everything else had failed — the drive kept saying it was in use even though I had closed all programs."

For NVMe or SSD drives where offline repair creates risks, consider using /perf alongside /scan for a gentler approach.

Part 6. Fix 5 — Run CHKDSK from Windows Recovery Environment

The Windows Recovery Environment (WinRE) loads before the main OS and provides a command prompt where the C: drive is typically not locked. This is the most reliable method when scheduling at restart fails.

Steps:

1. Boot from a Windows installation USB or use Advanced Startup (Settings → Update & Security → Recovery → Restart now).
2. Select Troubleshoot → Advanced Options → Command Prompt.
3. Identify the correct drive letter (type dir C: — in WinRE, the system drive may be assigned a different letter such as D:).
4. Run: chkdsk C: /f /r (using the letter WinRE assigned to Windows).

This method gives CHKDSK unrestricted access because Windows is not running from that volume at the time of the scan.

Part 7. Fix 6 — Check for Drive Errors After CHKDSK

After a successful CHKDSK run, review the results to understand the drive's health.

View CHKDSK logs:

1. Open Event Viewer (Win + R → eventvwr).
2. Navigate to Windows Logs → Application.
3. Look for a source named Wininit — this contains the CHKDSK output from restart-time scans.

If CHKDSK reports bad sectors, that is a sign of physical drive deterioration. Copy all important data to another drive immediately. CHKDSK marks bad sectors so the file system avoids them, but it does not repair the physical medium.

💡 Tip: A drive with bad sectors will typically accumulate more over time. Replace the drive rather than continuing to rely on it for critical data.

Part 8. Recover Files If the Drive Has Unfixable Errors

If CHKDSK reports errors that cannot be fixed — especially on a drive with bad sectors or a corrupted file system — recovering your files should be the first priority before any further repair attempts. Ritridata can scan drives at the sector level and recover files even when the file system is damaged or CHKDSK has failed. If you suspect important data is at risk, recover files with Ritridata before attempting a full format or repair.

Download Ritridata

FAQ

Q: Why does CHKDSK say "cannot lock current drive" on my D: drive? A: A background process — such as antivirus software, a backup agent, or Windows Search indexer — likely has a file open on that drive. Boot into Safe Mode or use the /x flag to force a dismount before scanning.

Q: Can I run CHKDSK without restarting? A: Yes, for read-only detection. Use chkdsk C: /scan to perform an online scan. However, repairing errors on the system drive requires a restart-scheduled scan or running from the Recovery Environment.

Q: How long does a scheduled CHKDSK take? A: Typically 10 minutes to 2 hours depending on drive size, speed (SSD vs HDD), and the number of errors found. A 2 TB HDD with bad sectors can take significantly longer.

Q: Is it safe to interrupt a CHKDSK scan? A: You should not interrupt a scheduled CHKDSK during the pre-boot phase. Doing so can leave the file system in an inconsistent state. If it is running online (/scan), interrupting is safe.

Q: CHKDSK keeps scheduling but never completes — what is wrong? A: This usually happens when another boot-time process (a corrupted boot record, conflicting driver, or pending Windows update) aborts the scan. Run CHKDSK from the Windows Recovery Environment instead.

Q: Does CHKDSK recover deleted files? A: No. CHKDSK repairs file system structure but does not recover deleted or overwritten data. Use dedicated data recovery software such as Ritridata for that purpose.

References

• Microsoft: Check your hard disk for errors in Windows
• Microsoft: CHKDSK command reference
• Microsoft Sysinternals Handle utility
• Windows Recovery Environment overview
• Microsoft: How CHKDSK works