You try to delete, rename, or move a file and Windows hits you with:
"The action can't be completed because the file is open in another program."
You've closed everything. You're sure of it. 😤 The classic fix is "just reboot," but that kills everyone's open work and teaches you nothing. Here's how to find exactly what's holding the file in under a minute.
🔍 Step 1: Search the handles in Resource Monitor
Resource Monitor ships with Windows and can show which process has a file open.
- Press Win+R, type the command below, and press Enter:
resmon
- Go to the CPU tab.
- Expand Associated Handles and type the file name (or part of it) in the search box.
- The results list the process name and PID holding that file.
Now you know the culprit instead of guessing. 🎯
👀 Step 2: Check the usual suspects
Nine times out of ten it's one of these:
- Outlook: an attachment you previewed or opened is still locked.
- Teams: a file you opened from a chat or channel.
- Excel or Word running in the background, even with no window showing.
- File Explorer's Preview pane: just selecting a file can lock it. Toggle the pane off with Alt+P.
- OneDrive in the middle of syncing that file.
Close the app gracefully first, or pause OneDrive sync from its cloud icon in the taskbar, then try again.
⚡ Step 3: End the process (carefully)
If the app won't let go, right-click the process in Resource Monitor and choose End Process. Make sure the user has saved their work first.
Prefer PowerShell? Once you know the process name from Step 1, you can stop it like this (example uses Excel):
Get-Process -Name EXCEL
Stop-Process -Name EXCEL
⚠️ Don't end processes you don't recognize. Look them up first. And if the locking process is explorer.exe, restarting Windows Explorer from Task Manager is usually enough.
🧰 Bonus: Sysinternals tools
If you'd like more detail, Microsoft's free Sysinternals Process Explorer has Find > Find Handle or DLL (Ctrl+F) that does the same search with a richer view. Handy to keep on your toolkit USB.
🙌 Why this matters
At the help desk, "reboot it" fixes the symptom. Finding the locking process tells you the cause, so you can tell the user what happened and how to avoid it next time. That's the difference between closing a ticket and actually helping. 💪
What's the weirdest process you've caught holding a file hostage? Drop it in the comments 👇
Top comments (1)
Nice, the Resource Monitor trick is underrated. One more for the list if people have PowerToys installed: File Locksmith adds a "What's using this file?" option to the right-click menu and shows the process right there. And for the command line crowd, Sysinternals handle.exe does the same search. Saved me a lot of pointless reboots.