You open a Word document, start editing, and then see the message “File is locked for editing by another user” — even though you are the only person with the file open. This error usually occurs because Word detects a stale lock file left behind after a crash, a network disconnect, or a previous unsaved session. This article explains the technical reasons behind the false lock warning and provides three reliable methods to regain access to your document without losing work.
Key Takeaways: Why Word Shows a False Lock Error
- Close Word and delete the hidden .tmp or .lck file: Removes the orphaned lock that Word created during a previous session.
- File > Info > Manage Document > Recover Unsaved Documents: Recovers the last autosaved version if the lock file is tied to an unsaved copy.
- Use Windows Task Manager to kill all WinWord.exe processes: Forces Word to release all file handles, including the stale lock.
Why Word Incorrectly Reports a File as Locked
When you open a Word document, the application creates a hidden lock file — typically named ~$filename.docx — in the same folder as the original document. This lock file tells Word and other users that the file is in use. If Word closes normally, it deletes the lock file. If Word crashes, the computer loses power, or the network disconnects while the file is open, the lock file remains on disk. On the next launch, Word sees the orphaned lock file and assumes another user or another instance of Word is still editing the document.
The lock file is a zero-byte or tiny file with a tilde and dollar sign prefix. It contains no user data — only a pointer indicating which user name locked the file. Because Windows file permissions allow any user on the same machine to see this file, Word can mistake a leftover lock for an active session. The problem is most common with documents stored on network drives, SharePoint, or OneDrive, where file synchronization delays can also create temporary lock artifacts.
A second cause involves the Word Normal.dotm template. If Normal.dotm is corrupted or held open by a background add-in, Word may fail to release the lock on any document that depends on that template. In rare cases, antivirus software that scans .docx files in real time may hold a file handle, preventing Word from clearing the lock.
Steps to Remove the Stale Lock and Open the Document
Use the methods below in order. Start with Method 1 because it is the fastest and safest. If the lock persists, move to Method 2 or 3.
Method 1: Delete the Hidden Lock File Manually
- Close Word completely
Exit Word by clicking File > Exit or pressing Alt+F4. Do not simply close the document window — close the entire application. - Open the folder where the document is stored
Use File Explorer to navigate to the exact folder that contains the locked .docx file. If the file is on OneDrive or SharePoint, open the local synced folder. - Show hidden files
In File Explorer, click the View tab and check the box labeled Hidden items. This makes the lock file visible. - Locate the lock file
Look for a file named ~$ followed by your document’s name. For example, if your document is Report.docx, the lock file is ~$Report.docx. - Delete the lock file
Right-click the ~$ file and choose Delete. Confirm if prompted by User Account Control. If the file is in use, proceed to Method 2. - Open the document
Double-click the original .docx file. Word should now open it for editing without the locked message.
Method 2: Kill All Word Processes via Task Manager
- Open Task Manager
Press Ctrl+Shift+Escape. If Task Manager opens in compact mode, click More details. - End all Word processes
In the Processes tab, scroll to Microsoft Word. You may see multiple entries labeled Microsoft Word. Right-click each one and select End task. Repeat until no Word processes remain. - Delete the lock file
With Word completely closed, repeat steps 2 through 6 from Method 1. - Restart Word
Open Word from the Start menu or taskbar. Then open the document via File > Open.
Method 3: Recover the Unsaved Copy and Save As
- Close the locked document
If the document is open in read-only mode, close it without saving. - Open a blank document
In Word, press Ctrl+N to create a new blank document. - Go to File > Info > Manage Document
Click Manage Document and then select Recover Unsaved Documents from the dropdown. - Open the most recent unsaved version
In the dialog, locate the .asd file that matches your document name and time. Click Open. - Save the recovered document
Press F12 to open Save As. Give the file a new name, such as Report_v2.docx, and save it to a different folder. Do not overwrite the original locked file until you confirm it is no longer locked. - Delete the original lock file
Follow Method 1 to remove the orphaned lock file from the original folder.
Other Symptoms That Indicate a Stale Lock File
Word Prompts “File in Use” but No One Else Has It Open
This is the exact scenario described in this article. The root cause is almost always an orphaned lock file. Use Method 1 first. If the lock file cannot be deleted because it is in use, restart the computer to release all file handles, then delete the lock file before opening the document again.
Word Shows “Read-Only” on a Local File
A local .docx file that opens as read-only may have its lock file intact but the original file marked as read-only in Windows file properties. Right-click the .docx file, choose Properties, and uncheck the Read-only box under General. Then delete the ~$ file as described in Method 1.
Lock Message Appears After OneDrive Sync Conflict
If the file is stored on OneDrive and a sync conflict occurs, OneDrive may create a copy named Filename-ComputerName.docx. The original file may remain locked. Open the conflict copy, save it with a new name, and then delete both the original lock file and the conflict copy from the OneDrive folder.
Local File Lock vs Network File Lock: Key Differences
| Item | Local file lock (orphaned) | Network file lock (active) |
|---|---|---|
| Lock file location | Same folder as the .docx | On the network server or SharePoint |
| Lock file name | ~$filename.docx | .lck file or database entry |
| Cause | Crash, power loss, improper shutdown | Another user has the file open |
| Fix method | Delete the ~$ file or restart Word | Wait for the other user to close or force disconnect |
| Persistence after reboot | Lock file may survive reboot if not deleted | Lock is released when network session ends |
After following the steps in this article, you can now open a Word document that falsely reports as locked even when you are the only user. Always delete the hidden ~$ lock file first before trying more complex recovery methods. If the problem recurs frequently with the same file, check whether an add-in or antivirus program is holding a file handle. As an advanced tip, you can prevent future orphaned locks by enabling Word’s AutoRecover setting at File > Options > Save and setting the AutoRecover save interval to every 1 minute — this ensures you lose minimal work if Word crashes and leaves a lock file behind.