The File Is Locked for Shared Use Error: What Site Owners Should Check

When a user opens a file in a SharePoint document library, they see the error “The file is locked for shared use by” followed by a person’s name. This error prevents editing and often appears without a clear reason. The cause is a temporary lock that Office applications place on a file while it is open. This article explains why this lock occurs and shows site owners the exact settings and steps to check when users cannot access a file.

Why the File Lock Error Occurs in SharePoint

SharePoint uses file locks to prevent two people from editing the same document at the same time and overwriting each other’s work. When a user opens a file in an Office application such as Word, Excel, or PowerPoint, SharePoint creates a temporary lock. The lock is tied to the user’s session and the application that opened the file. The error message “The file is locked for shared use by [user name]” means that SharePoint still sees that user as having the file open, even if the user believes they closed it.

How Co-Authoring Affects File Locks

SharePoint co-authoring allows multiple users to edit a file at the same time. When co-authoring is active, the file lock is shared — each user gets a read-write lock that allows simultaneous edits. But if the library has the “Require Check Out” setting enabled, only one user can lock the file at a time. This setting forces a user to check out a file before editing, which creates an exclusive lock. No other user can edit until the file is checked back in.

When Locks Do Not Release Automatically

A file lock should release when the user closes the file or navigates away from the SharePoint page. However, locks can persist in these situations:

• The user’s browser tab or Office app crashed while the file was open.
• The user closed the file but the Office background process (such as Excel.exe or WINWORD.exe) is still running on their computer.
• The user opened the file from a SharePoint sync folder and the sync client has not updated the lock status.
• The library has “Require Check Out” enabled, and the user never checked the file back in.

Steps to Check Who Locked the File and Release the Lock

Site owners can check the lock status and release it without requiring the original user to take action. Follow these steps in order.

1. Identify the user who holds the lock
   Open the document library and locate the file. Hover over the file name and click the check mark to select it. On the toolbar, click the three dots (ellipsis) and select Details. In the Details pane, look for the Locked By field. If the field shows a user name, that person has the file locked. If the field is empty, the lock may be temporary and will release soon.
2. Ask the user to close the file properly
   Contact the user shown in the Locked By field. Ask them to close the file in all Office applications and close any browser tabs that have the SharePoint library or file open. On Windows, they should check for background processes: press Ctrl+Shift+Escape to open Task Manager, look for Excel, Word, or PowerPoint processes, and end them if the file does not close.
3. Use the Manage Check Out option to force a check-in
   If the library has Require Check Out enabled, the file will show as checked out. Select the file in the library, click the three dots, and choose Advanced > Manage Check Out. On the Manage Check Out dialog, select Discard Check Out to release the lock. The file will revert to the last saved version before the check-out.
4. Check the library setting for Require Check Out
   Go to the library settings. Click the gear icon in the top right, select Library settings, then click Versioning settings. Under Require Check Out, select No if you want to allow multiple users to edit the file simultaneously. This change applies to all files in the library and prevents exclusive locks from occurring.
5. Clear the lock from SharePoint admin center if the user is unavailable
   If the user who locked the file has left the organization or is unreachable, site owners can ask a SharePoint admin to break the lock. The admin can go to SharePoint admin center > Active sites > select the site > Site contents > find the library > find the file. The admin can use the Manage Check Out option to discard the check-out. Only site collection admins and above can force-check in a file.

If the File Lock Error Still Appears After Releasing the Lock

SharePoint Library Sync Client Keeps the Lock Active

If users sync the library with OneDrive sync client, the sync client may hold a lock on the file even after the user closes it. To fix this, ask the user to pause sync: right-click the OneDrive icon in the system tray, select Pause syncing, wait 30 seconds, then resume sync. The lock should release after the sync status refreshes.

Office File Is Stuck Open in the Browser

When a user opens a file in the browser using Office Online, the lock is tied to the browser tab. If the tab crashes or the user closes the browser without closing the file first, the lock may persist for up to 10 minutes. The user should open the file again in the browser and close it using File > Close. Alternatively, the user can wait 10 minutes for the lock to time out automatically.

File Locked by an Anonymous User or System Account

In rare cases, the Locked By field shows a system account name such as “SharePoint System Account” or “NT AUTHORITY\SYSTEM.” This usually indicates that a background process, such as a Power Automate flow or a third-party sync tool, has the file open. Check the library for any running flows or scheduled jobs. Disable the flow temporarily, then use Manage Check Out to discard the check-out.

Require Check Out vs Co-Authoring: When Each Lock Type Applies

Item	Require Check Out Enabled	Require Check Out Disabled
Lock type	Exclusive (one user at a time)	Shared (multiple users can edit)
Lock release	Only when user checks in or admin discards check-out	Automatically when user closes file or after 10 minutes
Version control	Major versions only, one per check-in	Major and minor versions, auto-saved every few minutes
Best for	Files that need approval before others see changes	Files where real-time collaboration is needed

Site owners should match the lock setting to how the team works. If the error appears frequently, disable Require Check Out and enable co-authoring. If the file contains sensitive data that must be reviewed before sharing, keep Require Check Out and train users to check in files when they finish editing.

Now you can identify the user who holds the lock and release it using the Manage Check Out option or by adjusting the Require Check Out setting. Next, review the library versioning settings to decide if Require Check Out is necessary for your team. A concrete tip: if users frequently edit files from the browser, disable Require Check Out to prevent orphaned locks that require admin intervention.