Find processes using a file with File Locksmith
Diagnose file-locking conflicts in File Explorer by identifying blocking processes and safely resolving handle holds.
Publication & corrections: infostoa · Editorial standards
Individual author and specialist reviewer information is not provided for this article.
Feature and Windows availability
File Locksmith is an optional Explorer shell extension supplied with Microsoft PowerToys rather than a standard Windows component. When file deletion, renaming, or directory transfers are blocked by generic file-in-use errors, File Locksmith inspects open filesystem handles and displays the specific executable names, user sessions, and Process IDs (PIDs) holding locks on the selected assets.
Setup and practical use
Enable the utility in PowerToys settings to register the command inside the File Explorer context menu. Right-click the blocked file or folder and select the Locksmith entry to run an immediate handle scan. The resulting dialog enumerates every active locking process alongside its process identifier, offering a direct command button to terminate stubborn handles. If the target handles are owned by elevated system services or another user session, an option to reload the scan under administrative permissions is available at the top of the interface.
Scope and limitations
The ability to terminate an application directly from the diagnosis dialog should not be treated as a universal remedy. Terminating cloud sync clients, relational databases, or active word processors while handles remain open can discard in-flight memory buffers and induce file corruption. Furthermore, terminating critical operating system processes or explorer instances can lead to desktop instability, requiring careful differentiation between rogue processes and vital system services.
Professional perspective
Computerworld’s practical analysis of the PowerToys suite characterizes File Locksmith as an indispensable troubleshooting aid, while cautioning that handle identification must not be confused with a blanket license for forced termination. The operational value lies in locating the blocking program so that users can save documents and close the software through conventional interfaces. Elevating to administrative credentials provides complete diagnostic visibility across system sessions, but elevation does not make arbitrary process termination inherently safe for system state.