Home › Knowledgebase › KB-1252

How to fix word document locked for editing on network drive

Summary

This guide helps you troubleshoot and resolve: How to fix word document locked for editing on network drive. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

How to fix word document locked for editing on network drive

Small businesses often rely on local network drives or NAS devices for shared file access. When multiple staff members need to edit the same Microsoft Word document, file locking conflicts can prevent collaboration. This guide explains how to resolve locked Word documents on network drives and NAS storage, including advanced steps for Windows servers and NAS devices.

Understanding file locking on network drives

When a Microsoft Word document is stored on a network drive or NAS, Word creates a temporary owner file while the document is open. This file usually begins with a tilde and dollar sign, such as ~$document.docx, and is typically hidden. If a second user attempts to open the same file, Word detects this temporary file and reports that the document is locked for editing by another user.

Unlike cloud-based platforms, traditional network drives do not support real-time co-authoring. Only one person can edit a file at a time. If Word closes unexpectedly or a VPN connection drops, the temporary lock file may remain behind, causing the document to appear locked even when no one is actively editing it.

Immediate troubleshooting steps

  1. Confirm who has the file open. Ask colleagues if they currently have the document open in Word. If they do, request that they save their changes and close the file completely.
  2. Check for orphaned temporary files. If no one has the document open, the lock file may be stuck. Browse to the network folder in File Explorer and look for a hidden file beginning with ~$. If present and no one is editing the document, delete it.
  3. Open as read-only. If you only need to view the content, select "Open as Read-Only" when prompted. This allows you to read the document without waiting for the lock to clear.
  4. Save a local copy. Use "Save As" to save the document to your desktop or local Documents folder, make your edits, then copy the updated version back to the network drive once the original is unlocked.
  5. Restart the computer holding the lock. If the user who had the file open has logged off but the lock persists, restarting their machine can release the file handle held by the server or NAS.

Check open files on a Windows server

If your network drive is hosted on a Windows server, you can use Computer Management to see who has the file open and close the connection.

  1. Log on to the file server with an account that has administrative privileges.
  2. Right-click the Start button and select Computer Management.
  3. In the left pane, expand Shared Folders, then select Open Files.
  4. Look through the list for the locked Word document or its associated ~$ temporary file.
  5. Right-click the entry and select Close Open File to release the lock.
  6. Ask the affected user to try opening the document again.

If you do not see the file listed, the lock may be held by a NAS device or a workstation rather than the server itself.

Handling NAS admin access

If your files are stored on a network-attached storage (NAS) device, the procedure differs from a Windows server.

  1. Log in to the NAS administration interface using a web browser. You will need administrator credentials for the device.
  2. Navigate to the file manager, shared folders, or session monitoring section. The exact menu name varies by manufacturer (for example, Synology DSM uses File Station and Storage Manager, while QNAP uses File Station and System Monitoring).
  3. Locate the locked document or the ~$ temporary file associated with it.
  4. Check for active user sessions or open file locks. Disconnect the session or close the file handle through the NAS interface.
  5. If the interface does not provide an option to release individual file locks, restarting the NAS service or the device may clear stale locks.

Always ensure you have a recent backup before making changes to shared storage through the NAS administration interface.

If the lock file cannot be deleted

Sometimes the ~$ temporary file cannot be deleted because it is still in use or because you lack the necessary permissions.

  • File is in use: Confirm that no user has the document open. Check Computer Management on the server or the session list on the NAS. Close any open handles before attempting deletion again.
  • Access denied: Ensure you are logged in with an account that has modify or full control permissions on the folder. On a Windows server, you may need to take ownership of the file or grant your account full control through the Security tab in file properties.
  • File reappears: If the temporary file returns immediately after deletion, a user or application still has the document open. Identify the source and close the file properly before retrying.
  • Do not force-delete during active editing: Never delete a ~$ file while a user is actively working in the document. Doing so can cause data loss or corruption.

Preventing future locking issues

While network drives are suitable for simple file sharing, they do not support simultaneous editing. Consider the following strategies to reduce locking conflicts:

  • Split large documents. Break lengthy reports or spreadsheets into smaller sections so different team members can work on separate files at the same time.
  • Use check-out procedures. Establish a team rule where the person editing a file notifies others, or use any check-out feature available in your document management system.
  • Save local copies for editing. Copy the file to a local workstation, make changes, then copy it back to the network drive when finished. This reduces the time the network copy remains locked.
  • Schedule editing times. For documents that require frequent updates, agree on editing windows so staff do not attempt to modify the same file simultaneously.

Migration as a long-term alternative

If locked documents are a recurring problem, migrating shared folders from a local network drive or NAS to SharePoint Online is a non-sales alternative worth considering. SharePoint Online supports real-time co-authoring, allowing multiple users to edit the same Word document at the same time. It also provides automatic version history and secure remote access without requiring a VPN.

This migration removes the root cause of network drive locking rather than managing the symptoms. If your business is ready to move away from traditional file shares, Open a Ticket to discuss your options.

Before deleting any ~$ temporary files, ensure no one has the document open. Deleting a lock file while a user is actively editing can cause data loss.

Do not attempt to force-delete files on a NAS or server unless you have administrative access and a recent backup. Incorrect changes to shared storage can affect all users.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket