Word: "The document is locked for editing by another user"

Hi, it's BlueByte. You go to open a Word file and instead of the document you get a dialog: the file is locked for editing by another user, offering only a read-only copy. Nothing is corrupted — Word found a lock for the document (an "owner file") and assumed someone else has it open. Often no one does. We'll walk through the exact message and its variants, the three reasons Word believes the file is in use, how to tell a real conflict from a stale lock, how to clear it safely, and how to keep it from sticking.

What "locked for editing by another user" actually says

The dialog names the file and the supposed owner:

The document "Budget.docx" is locked for editing by another user.
To open a read-only copy of this document, click Read Only.

Variants you may see instead: File in use — <filename> is locked for editing by <user>, an Upload blocked badge on OneDrive or SharePoint, or on a mapped network drive simply This file is in use. They all mean the same thing — Word (or the sync client) sees a lock and won't let you edit until it's released. It is not a permissions error and not file corruption.

The three reasons Word thinks the file is in use

Microsoft's guidance lists three causes, and every case is one of them:

• A leftover owner file. Word creates a temporary owner file whenever you open a saved document, holding the name of whoever opened it. If Word crashed or was force-quit, it never deleted that file, so the lock outlives the session.
• A hidden second instance of Word is still running in the background with the document open — a WINWORD.EXE process that didn't exit after you closed the window.
• Someone genuinely has it open — the file is on a network share, OneDrive, or SharePoint and another person is editing it right now.

Only the third is a real conflict. The first two are stale locks: nothing is actually editing the file.

Tell a real conflict from a leftover lock

Don't kill processes blindly — check first. The owner file is a hidden file next to the document, named with a ~$ prefix. Microsoft's example: the owner file for Document.doc is ~$cument.doc — Word keeps the ~$ and trims the leading characters of the name, so match on the ~$ prefix rather than the exact spelling:

dir /a "C:\Users\you\Documents\~$*.doc*"

If that lists a ~$… file while nobody is editing the document, the lock is stale. Next, check for a lingering Word process:

tasklist | findstr /i winword

A WINWORD.EXE line with no visible Word window is a hidden instance. If both come back empty and a colleague confirms the file is open on their machine, it's a real conflict — open read-only and wait rather than forcing anything.

Close every hidden Word process first

If the lock is stale, quit Word completely so nothing holds the file, then end any orphaned process:

taskkill /IM WINWORD.EXE /F

SUCCESS: The process "WINWORD.EXE" with PID 8124 has been terminated.

SUCCESS (or not found, meaning it was already gone) means no Word process is holding the document. Save any other open documents first — /F forces the process to close without prompting.

Delete the leftover owner file (~$)

With Word closed, remove the stale owner file by its ~$ name:

del "C:\Users\you\Documents\~$dget.docx"

The command returns silently on success. Owner files are hidden, so if File Explorer doesn't show it, enable View ▸ Show ▸ Hidden items or use the del command above. Deleting the owner file is safe — it holds only the lock and the opener's name, never your document's contents.

A real case: Word crashed and left its lock behind

You're editing Budget.docx on a shared drive when Word freezes and you end it from Task Manager. You reopen the file and get locked for editing by another user — naming yourself. That's the tell: you are the "other user," from the crashed session. You run tasklist | findstr /i winword, see one stray WINWORD.EXE, and end it with taskkill /IM WINWORD.EXE /F. Then dir /a shows ~$dget.docx; you delete it with del. Reopening Budget.docx now goes straight to an editable document — the crash's lock is gone, and nothing was lost.

Check the document opens for editing again

Reopen the file. It should open editable, with no read-only banner and no lock dialog. Confirm the owner file is really gone:

dir /a "C:\Users\you\Documents\~$*.doc*"

File Not Found

File Not Found means the lock is cleared. If a fresh ~$ file appears the moment you open the document, that's expected — Word creates a new owner file for your session and deletes it when you close cleanly.

Keep the lock from sticking

Quit Word with File ▸ Close or by closing the window, not by killing it, so Word deletes its own owner file. For files several people touch, store them in OneDrive or SharePoint and turn on AutoSave — real co-authoring lets everyone edit at once instead of trading a single lock, which is what the "another user" message is really about on a plain file share. If Word crashes often, install the current updates; a repaired install stops leaving orphaned locks behind.

How this differs from "read-only" and "marked as final"

Locked for editing is an external lock — another session or a leftover owner file. That's different from a file whose read-only attribute is set (clear it with attrib -r file.docx), from Marked as Final (a property inside the document you clear under File ▸ Info ▸ Protect Document), and from Protected View, the yellow bar on files downloaded from the internet that you clear with Enable Editing. If there's no lock dialog and no owner file but you still can't type, you're looking at one of those, not a lock.