Word

Fix "Word Cannot Open This Document. The Document Might Be in Use"

Error message: Word cannot open this document. The document might be in use by another application

"Word cannot open this document. The document might be in use by another application" is not a corruption error and doesn’t need any repair tools to fix. It means a file lock is being held somewhere — by another instance of Word, by an Office process that crashed without cleaning up, by another user on a shared file, or by a background service. Once the lock is identified and released, the file opens normally.

This guide works through the lock sources in order, starting with the simplest checks.

Quick fix

Most of the time, the lock is held by an orphaned Word process — a previous Word session that crashed without releasing the file. Clearing it takes about thirty seconds.

  1. Save any work in other Office applications.
  2. Press Ctrl+Shift+Esc to open Task Manager.
  3. Click More details if Task Manager is in compact mode.
  4. On the Processes tab, scroll through the list and look for any Microsoft Word entries (or, on the Details tab, WINWORD.EXE).
  5. Right-click each Word process and choose End task.
  6. Try opening the file again.

If you also see entries for Excel, PowerPoint, or Outlook that you didn’t intend to have running, end those too. Office applications share components, and a hung Excel or Outlook process can sometimes hold a Word document lock.

If that didn’t work

Look for and delete the owner file

When Word opens a document, it creates a small hidden file in the same folder named with ~$ followed by part of the original filename. For report.docx, the owner file is typically ~$report.docx. This file is Word’s lock indicator. When Word closes cleanly, it deletes the owner file. When Word crashes, the file persists, and any subsequent attempt to open the document triggers the in-use error.

  1. Confirm Word is fully closed (use Task Manager to verify, as in the quick fix above).
  2. Open File Explorer and navigate to the folder containing the document.
  3. Click View > Show > Hidden items to make hidden files visible.
  4. Look for a file starting with ~$ and ending with part of your document’s name. For quarterly-report.docx, expect to see ~$quarterly-report.docx.
  5. Delete the owner file. (It’s safe to delete — Word will recreate it the next time the document opens.)
  6. Try opening the document again.

If you don’t see an owner file, the lock is being held elsewhere — proceed to the next strategy.

For shared, network, or cloud files: check who has it open

If the document is on a network share, SharePoint, or OneDrive, another user may have it open. The fix depends on the storage:

SharePoint or OneDrive (web): Open the document library in a browser. Files currently open by someone else show an indicator (initials or an icon). If you have edit rights, you can usually still open in read-only mode by clicking the dropdown next to the file and choosing Open in browser or View only.

Local network share: There’s no built-in way to see who has a file open from the file itself. If you have admin access to the file server, the Computer Management > Shared Folders > Open Files view shows who currently has files open. Otherwise, contact the colleague you suspect has it open.

OneDrive (sync client): The file may be in the middle of a sync operation. Check the OneDrive icon in the system tray — if it’s syncing, wait for the operation to complete. If sync is paused or has errors, resolve those first.

Check for OneDrive or cloud sync conflicts

Cloud-synced files can produce this error when sync is in progress and Word tries to open the file before sync completes, or when there’s an unresolved sync conflict.

  1. Click the OneDrive icon in the system tray (the cloud icon).
  2. Check the sync status. If it shows “Syncing” with an active progress indicator, wait for it to finish.
  3. If it shows a conflict warning, click into it and resolve the conflict — typically by choosing which version to keep.
  4. Once sync is fully resolved (the icon shows a green checkmark), try opening the file again.

For Google Drive, Dropbox, or Box, follow the equivalent process for that client.

Restart the computer

If none of the above identifies the lock holder, restart the computer. This forcibly releases every file lock on the system. It’s a blunt fix, but it always works for locks held locally.

Why this happens

Windows tracks file locks at the operating system level. When a process opens a file in exclusive or read-write mode, the OS records that lock, and any other process attempting to open the same file in a conflicting mode is denied access. Word uses exclusive locking on documents you open for editing — which is why two people can’t edit the same .docx on a network share without a co-authoring system in place.

Locks are released when the holding process closes the file or terminates cleanly. The problems arise when:

A process crashes without cleanup. When Word crashes (or is force-closed), Windows usually releases its file locks automatically, but the owner file (~$filename.docx) stays behind. Some Word configurations check for the owner file before opening and refuse to proceed if it exists, even when the actual OS-level lock has cleared.

A background process holds the file. Antivirus software with real-time scanning sometimes holds a transient lock on a file while scanning it. Search indexers (Windows Search) can do the same. These locks are usually milliseconds long, but on a large document, the window can be long enough to collide with a Word open attempt.

Sync clients hold locks during transfer. OneDrive, Google Drive, Dropbox, and similar clients lock files during upload and download. A document being synced to or from the cloud is unavailable to Word for the duration.

Shared file collaboration without co-authoring. Two users opening the same document on a network share without a co-authoring system (SharePoint, OneDrive co-authoring) result in the second user getting an in-use error from the first user’s lock.

Preventing this in future

A few practices significantly reduce the rate at which this error appears.

When Word crashes or freezes, take the time to fully clean up — close any remaining Word processes via Task Manager and check for owner files in the folder you were working in. Don’t just relaunch Word and hope; the orphaned lock will be there waiting next time you try to open the document.

For documents you actively share with others, use SharePoint or OneDrive co-authoring rather than a network share. Co-authoring is designed to handle simultaneous edits — multiple users can open the same document at once without lock collisions.

For OneDrive-synced documents, wait until sync completes (green checkmark in the system tray) before opening files you’ve recently saved or that have been modified by another sync source. Trying to open a file mid-sync is a reliable way to trigger this error.

Exclude your active document folders from antivirus real-time scanning if scanning interference is a recurring problem. The security trade-off is small for trusted work folders.

If the file genuinely won’t open even after every lock is cleared, the problem isn’t a lock — it’s the file itself. The page on "Word experienced an error trying to open the file" covers security-related blocks that produce a different error message but similar symptoms. The page on "The file is corrupt and cannot be opened" covers structural corruption that requires actual repair rather than lock clearing.

For broader context on Word document recovery, see the Word repair complete guide.

Last verified: April 2026