PDF

PDF Won't Open: 'The Document Is Being Used by Another Process'

This isn’t a corruption problem. The PDF is fine; another process on your computer holds an exclusive lock on it, and the reader can’t get exclusive access to open it. The fix is to find and release the lock, not to repair anything. Most cases resolve in under a minute by closing the right background application.

Quick fix

  1. Close every PDF reader you have open. Adobe Acrobat, Acrobat Reader, Foxit, browser PDF tabs — close them all, including any that may have crashed and left a hidden background instance.
  2. Open Task Manager (Ctrl+Shift+Esc on Windows) or Activity Monitor (Cmd+Space, search “Activity Monitor” on Mac). Look for processes named Acrobat.exe, AcroRd32.exe, or Acrobat. End any that are running.
  3. Pause your cloud sync client (OneDrive, Dropbox, Google Drive, Box). Right-click the sync icon in the system tray and choose Pause. Sync clients hold locks during upload.
  4. Try opening the PDF again.

That sequence resolves the majority of cases. If it doesn’t, you need to find the specific process holding the lock.

If that didn’t work

On Windows, install Process Explorer from Microsoft Sysinternals (free, no installer required — just download and run). Then:

  1. Open Process Explorer with administrator privileges (right-click > Run as administrator).
  2. Press Ctrl+F or use Find > Find Handle or DLL.
  3. Paste the filename of the PDF (just the filename, not the full path) into the search box.
  4. Process Explorer lists every process that has a handle on the file. The culprit is usually obvious — a sync client, an antivirus, an indexer, or a forgotten editor.
  5. Note the process, close it normally if possible, or end it from Task Manager if it’s unresponsive.

On macOS, open Terminal and run:

lsof | grep "filename.pdf"

This lists every process that has the file open, with the process ID and process name. End the offending process via Activity Monitor or kill PID from Terminal.

On Linux, the same lsof command works. fuser -v filename.pdf gives a more concise output specifically about which processes have the file open.

Once you’ve identified and ended the locking process, the PDF will open normally.

Advanced recovery

If you can’t identify the locking process, or if ending it doesn’t release the lock, copy the file to a different location and open the copy. The lock applies to the original file path; a copy at a different path is unlocked.

copy "locked-file.pdf" "C:\Temp\unlocked-file.pdf"

On Mac or Linux:

cp /path/to/locked-file.pdf /tmp/unlocked-file.pdf

Open the copy. This works almost always when other approaches fail.

If the PDF is on a network share and you suspect another user has it open, you generally can’t force a release without administrator access to the server. Network file locks (SMB) typically time out automatically within 30 minutes if the holding session disconnects, but a session that’s still active will hold the lock indefinitely. Contact whoever else has access to the file, or wait.

As a last resort, restart the computer. This clears every file lock unconditionally. It’s heavyweight, but it’s reliable when nothing else works.

Why this happens

Windows, macOS, and Linux all support file locking — the operating system can grant a process exclusive access to a file, blocking other processes from opening it. PDF readers typically request exclusive access when opening a file, both to prevent simultaneous edits and to enable safe writes. When something else already holds the file open exclusively, the request fails and the reader reports the error.

Several common scenarios produce this state.

A previous PDF reader instance crashed. Adobe Acrobat in particular has a long history of leaving zombie processes behind after a crash or unexpected exit. The visible window is gone, but the process is still running with a file handle.

Cloud sync is uploading the file. OneDrive, Dropbox, Google Drive, and Box all hold the file locked during the upload phase. For large PDFs over slow connections, this can be 30 seconds or more. Files On-Demand mode in OneDrive is particularly prone to this because it may be both reading the file from cloud and writing it locally simultaneously.

Antivirus is scanning the file. Most antivirus products scan files at the moment of access. For large PDFs, the scan may take seconds, during which the file is locked. This is usually transparent but can produce the error if you try to open the file very fast after copying it to disk.

Windows Search Indexer has the file open. The indexer maintains a search index of file contents. When a PDF is being indexed, it has a read handle that, on some configurations, blocks other readers. This is rare in modern Windows but does happen.

Another user on a network share has the file open. Network file systems (SMB shares, NFS) propagate exclusive locks across the network. If a colleague has the file open in Acrobat on their machine, you can’t open it on yours.

Preventing this in future

Avoid editing PDFs directly inside cloud sync folders. Copy the file to a local location, edit it, then copy back. This eliminates the sync-lock problem entirely.

Close PDF readers when you’re done with them rather than minimizing them. This avoids the zombie-process scenario.

For files on network shares that multiple people need to access, consider whether a different workflow — a shared review tool, document management system, or simple email attachment — would avoid the contention.

If the PDF actually is damaged rather than locked, the error wording is different — see the PDF repair pillar for the broader diagnostic, or the guide to “file is damaged and cannot be repaired” if that’s the specific error you’re seeing. For PDFs that arrived from email and won’t open, transfer corruption is more likely than file locking — see PDF from email won’t open.

Last verified: April 2026