Word Can't Open This Document: Locked by Another User

When This Error Actually Appears

You double-click a Word document on a network share or in OneDrive. A dialog pops up: "This file is locked for editing by another user." It gives you options to open read-only, notify, or cancel. The file hasn't been opened by anyone else for hours. The culprit is almost always a crashed Word process that didn't clean up its lock file. On Windows 10 or 11 with Office 365 or 2021, this happens when Word terminates unexpectedly — a power failure, a forced kill via Task Manager, or a plug-in crash. The lock file (with a .lck extension) sits in the same folder as your document, and Word still sees it as a live lock.

Why Word Thinks Someone Else Has It Open

Word uses a lock file system, not file-level locks. When you open a .docx file, Word creates a hidden companion file in the same directory, named like ~$document.docx or, for older formats, a .lck file. This file contains the user name, computer name, and a timestamp. On normal close, Word deletes it. If Word crashes, that file stays. Next time you open the document, Word sees the lock file, assumes the original user still has it open, and blocks write access. The lock is purely advisory — the file system itself isn't locked. So the fix is simple: delete that lock file.

The Fix: Remove the Lock File

1. Close Word completely. Not just the document — quit Word. Check Task Manager for any WINWORD.EXE processes and kill them. If those processes are stuck, the lock file regenerates immediately.
2. Browse to the folder containing your document. Use File Explorer, not Word's Open dialog.
3. Enable viewing of hidden and system files if needed. In Explorer, go to View > Show > Hidden items. Also uncheck "Hide protected operating system files" under View > Options > View. You need to see files starting with ~$.
4. Look for a file named ~$yourdocument.docx or yourdocument.docx.lck. The tilde-dollarsign prefix is the standard Word temp lock file. On network shares, you might also see a file with a .lck extension in an Office File Cache folder.
5. Delete that file. If Windows says it's in use, reboot and try again. Or use a tool like LockHunter (free) to force-delete it. The lock file has zero content worth keeping — it's just metadata.
6. Open your document normally. Word should give you full editing access now.

OneDrive-Specific Variation

If the file lives in OneDrive, the lock might be synced. Delete the local lock file, then wait 30 seconds for OneDrive to sync. If the lock persists, go to the OneDrive website, find the file, click the three dots, and select "Version history." Check if a co-author has the file checked out (SharePoint check-out, not Word's lock). If so, check it back in from the web interface.

What to Check If the Fix Doesn't Work

• Check if someone really does have it open. On a network share, remote desktop into the file server and run openfiles /query in an admin command prompt. This lists all open files and who holds them. If you see your username and the file, kill the session with openfiles /disconnect /id [session id].
• Corrupted Normal.dotm template. A bad global template can cause Word to behave oddly with locks. Rename %appdata%\Microsoft\Templates\Normal.dotm to Normal.old. Word rebuilds it fresh on next launch.
• Antivirus or backup software locking the file. Some real-time scanners hold a read lock. Temporarily disable the scanner for the folder, open the document, then re-enable. This is rare but happens with older Sophos or McAfee versions.
• File corruption in the document itself. If all else fails, try opening the file with WordPad (yes, the old Windows accessory). It ignores locks entirely because it doesn't use the same locking mechanism. Copy the content to a new Word document.

Final opinion: Microsoft's lock file system is fragile. It works fine until a crash, then it punishes you for using the product. The real fix is to always save a local copy before editing shared files. Or switch to a format that doesn't use lock files — like plain text.