Chkdsk failing to lock volume for exclusive access despite no open user applications

Williams Noah 20 Reputation points
2026-11-18T05:34:20.4233333+00:00

Hello! chkdsk /f keeps failing to lock a secondary volume even with all users apps closed. Is it usually AV/EDR, Windows Search, or VSS holding a silent handle open, and do you guys normally track it down with handle.exe first before forcing /x? Happens to several client machines.

Windows for business | Windows Client for IT Pros | Performance | Windows desktop and shell experience
0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2026-11-18T05:35:08.17+00:00

    Identify the open handle with elevated Sysinternals Handle before using /x; closed applications do not exclude background services, filter drivers, or system processes from holding files on the volume.

    Evidence-first workflow

    1. Open Command Prompt as administrator. Both CHKDSK and Handle require administrative privileges.^1^ ^2^
    2. Ensure the command prompt’s current directory is not on the target volume:
         cd /d C:\
      
    3. Search for handles referencing the secondary drive, substituting its letter:
         handle.exe -u E:\
      
      If that returns nothing useful, broaden the searches:
         handle.exe E:
         handle.exe -a E:
      
      Handle performs a case-insensitive substring search against object names and reports the owning process, PID, hexadecimal handle value, object type, and path.^2^
    4. Stop the identified owner through its supported control path—for example, stop its Windows service, pause its backup job, unmount its application data, or exit the process normally. Then rerun:
         chkdsk E: /f
      
      Avoid handle.exe -c as the routine fix. Microsoft warns that forcibly closing an individual handle can cause application or system instability.^2^

    Process Explorer is the GUI alternative: run it elevated, use its handle search for E:\, and inspect the matching process. It is specifically designed to find processes with particular handles open.^3^

    Do not assume AV, Search, or VSS without an owner

    The lock failure establishes only that CHKDSK could not obtain exclusive volume access. An exclusive volume open is blocked when files are already open on that volume.^4^

    The available documentation does not establish AV/EDR or Windows Search as the usual owner. Treat those as candidates only if Handle identifies their process or associated service.

    VSS has one specifically documented case: a Shadow Copies for Shared Folders source volume cannot be locked while that feature is enabled. That does not establish generic VSS activity as the cause on ordinary client volumes.^1^

    For repeated incidents across clients, record the process name, PID, path, owning account, endpoint product/version, and time before stopping anything. That distinguishes a common agent from unrelated per-machine activity.

    When forcing a dismount is acceptable

    After saving work and stopping known workloads, use:

    chkdsk E: /x
    

    /x forces the volume to dismount, invalidates every open handle to it, and already includes /f; chkdsk E: /f /x is therefore redundant.^1^

    A forced dismount can produce unexpected behavior in programs whose handles are invalidated, so use it during a maintenance window rather than as the first diagnostic action.^5^

    If the owner cannot be stopped safely, schedule an offline check at restart instead of force-dismounting a live workload. CHKDSK documents that when /f cannot lock a drive, Windows can offer to check it during the next restart.^1^


    References

    1. chkdsk
    2. Handle v5.0
    3. Process Explorer v17.21
    4. Create Processing
    5. Bootsect Command-Line Options
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Marcin Policht 113.6K Reputation points MVP Volunteer Moderator
    2026-11-18T06:47:26.4433333+00:00

    Yep - in general, you should start by identifying the process holding the volume open rather than immediately forcing a dismount with /x. This can be caused by Antivirus/EDR software, Windows Search indexing, backup agents, VSS-related components, and applications with open file handles.

    You can use both Handle.exe or Process Explorer. Run Handle from an elevated command prompt and inspect references to the affected volume:

    handle.exe -a D:
    

    You can also search for the volume's device path if searching by drive letter does not identify the relevant handles:

    handle.exe -a | findstr /i "D:"
    

    Keep in mind that some processes reference volumes through device paths rather than drive letters, so a drive-letter search is not always conclusive. Process Explorer's Find Handle or DLL function can also help identify processes holding files open on the affected volume.

    Once you identify the process, determine whether it is safe to stop or temporarily disable the associated service. For example, you might investigate the Windows Search service (WSearch), an endpoint protection agent, or a backup application. Avoid terminating security or backup processes without understanding the implications.

    Regarding the switches, /f requests filesystem repairs and requires exclusive access to the volume. /x forces the volume to dismount first, invalidating open handles and interrupting access to the volume. It also implies /f. Consequently, /x is not simply another way to acquire a lock. It can disrupt applications, services, and backup operations that depend on the volume.

    For machines where this happens repeatedly, I would also check whether the secondary volume is being accessed by scheduled backup jobs, monitoring agents, indexing services, or other background processes. If the volume is used by applications or services that cannot safely be stopped, schedule the repair during a maintenance window.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.