← All Documentation
The problem it solves
You've probably seen this Windows dialog: "The action can't be completed because the file is open in another program." Sometimes it's obvious what's using it — a Word document you still have open. Other times Windows refuses to tell you. Maybe a background service is locking it. Maybe you closed the program but it's still hanging around. File Unlocker asks Windows directly which processes have handles on a specific file or folder and offers to close them for you.
How it works
Every open file or folder in Windows has one or more "handles" pointing to it. File Unlocker uses Windows' own Restart Manager and handle-enumeration APIs to list every process holding a handle on the path you selected. You can then pick which ones to terminate.
How to use it
- Go to Fix → File Unlocker.
- Type or paste the full path of the locked file or folder into the text box. Or click Browse File / Browse Folder.
- Click Scan.
- The list shows every process currently holding the file or folder open — name, PID (process ID), and how many handles it has.
- Select the processes you want to close (usually all of them).
- Click Unlock. TuneBit first asks each program politely to close the file; if that fails, it will terminate the process.
- Try your original action again — the file should now move, rename, or delete without complaint.
Typical offenders
- explorer.exe — showing the file in a preview pane. Close the preview pane or the folder window.
- Search Indexer — indexing your documents in the background. Give it a minute, or ask Unlocker to close it.
- Antivirus — scanning a file you just downloaded. Almost always releases within a few seconds.
- OneDrive/Dropbox — syncing. Pause sync, or use Unlocker.
Before unlocking, try closing politely. If the list includes an editor like Word or Notepad++, save your work and close the app normally — that's safer than forcing the process to quit and potentially losing unsaved changes.
Do not unlock system processes blindly. If File Unlocker lists something like svchost.exe or System, be cautious: terminating those can cause instability. In most cases, closing the specific user program (Chrome, Word, explorer) is enough — leave low-level system processes alone unless you know what you're doing.