Find out what's locking a file
Use Microsoft's free Process Explorer to name the exact program holding a file open — the fastest answer to a capture stall, an undeletable file, or any 'in use by another process' error.
Before you begin
- Administrator access to the server (or workstation) where the file lives
In ten minutes you'll have the name of the exact program holding a file open — which turns "something is locking it" from a guess into a fix.
Windows won't tell you who has a file open; it just says "in use." Microsoft's free Process Explorer (from their Sysinternals team) will name the process, and that name is usually the whole diagnosis.
When you need this
- Capture has stalled on one file — the oldest item in a hot folder just sits there
- A file in a Content Central storage or capture folder won't delete, move, or rename
- Any error that says a file is "in use by another process" without saying which one
Get Process Explorer
Download it from Microsoft's official page: learn.microsoft.com/sysinternals/downloads/process-explorer.
There's nothing to install — unzip it and run
procexp64.exeas administrator (right-click > Run as administrator). Without admin rights it can't see other users' handles, and on a server that's usually exactly where the culprit lives.
Name the locker
In Process Explorer, press Ctrl+F (or Find > Find Handle or DLL…).
Paste the file's path — or just its name, or the folder path to catch anything holding files inside it — and click Search.
What you should see: one or more result rows, each naming a Process, its PID, and the exact handle path it has open. That process is your locker.
Double-click a result and Process Explorer highlights the process in its main window, so you can see what it is, who's running it, and when it started.
Process Explorer's Find Handle dialog with a hot-folder file path entered and one result row naming the locking process
No results while the error persists? Search again with just the file name (path forms can differ), and confirm you ran Process Explorer as administrator. A lock held over the network from another machine won't appear here — check who has the share open on the file server instead.
Release the lock the right way
Now that you know who, release the lock at the source:
- A user's application (a PDF viewer, Office, a preview pane) — have them close the document.
- A service — restart that service from services.msc, not the whole server.
- Antivirus or backup agent — these scan newly-arrived files and can hold them mid-scan. If your capture folders stall this way regularly, ask your security team to add the capture folders to the scanner's exclusions and to schedule backups away from heavy capture windows.
- The scanner or copier itself — a device still writing a large file holds it until the transfer finishes; give it a minute and search again.
Process Explorer can force a handle closed (Close Handle). Don't. Cutting a handle out from under a running program can corrupt that program's state or the file itself. Always release a lock by closing or restarting the program that owns it — the handle then closes cleanly on its own.
The command-line alternative
The same team ships Handle (learn.microsoft.com/sysinternals/downloads/handle) for terminal work — one line from an administrator prompt:
handle64.exe "C:\Scans\Incoming\invoice-2041.pdf"It prints the owning process and PID, same answer, no window.
Still stuck?
Send support:
- The full path of the locked file, and what you were trying to do with it
- A screenshot of the Find Handle results (process name and PID visible)
- What the owning process turned out to be, and what happened when you closed or restarted it
- Whether this is a one-off or the same folder keeps producing locked files