SharePoint File Locked for Editing

Encountering a “File is locked for editing”, “File in Use”, or “Locked by another user” error in SharePoint Online or Microsoft Teams blocks you from saving modifications. This happens because the cloud server assigns a temporary edit lease to a user session. If that session terminates abruptly (due to a crash, network disconnect, or sync failure), the cloud lease remains active, preventing others from modifying the file.

This guide outlines how to force release file locks administratively in the web UI, kill hung Office processes locally, and manage library checkouts.

1. What Causes SharePoint File Locks?

File locks are managed by SharePoint’s co-authoring server and local client applications:

• Orphaned Server Leases: When a user closes a document while offline or their internet drops, the server-side edit lease (which usually lasts 10 to 60 minutes) remains active.
• Mandatory Checkout Enforced: The document library configuration requires users to explicitly “Check Out” files before editing. If a user leaves the file checked out, it is locked for everyone else.
• Zombie Local App Processes: Microsoft Excel (EXCEL.EXE) or Word (WINWORD.EXE) remains running in the background of a client machine, keeping a lock file active in the local cache.

2. Force Release Locks via SharePoint Web Portal

If a user is listed as locking a file but they have closed it, you can override the lock through the web interface.

A. Override Mandatory Checkouts (For Administrators/Owners)

If the library uses checkout settings:

1. Open the SharePoint document library in your web browser.
2. Locate the locked file, click the vertical ellipsis (…) next to it, and select More → Check in.
3. Alternatively, if the changes made by the locking user are not needed, select Discard check-out to revert to the last saved version.

B. Force Close Co-authoring Session

If co-authoring is stuck:

1. Open the file in Office Online (e.g. Word or Excel for Web) rather than the desktop app.
2. Look at the top right corner to see who is currently active in the document.
3. If an inactive session is shown, the owner of the document can save a copy or wait for the auto-timeout (usually 10-15 minutes of inactivity).

A. Terminate Background Microsoft Office Tasks

A background Excel or Word thread may be holding the file handle open:

1. Press Ctrl + Shift + Escape to launch Task Manager.
2. Click on the Details tab.
3. Search the list for EXCEL.EXE, WINWORD.EXE, or POWERPNT.EXE.
4. Select the process and click End Task.
5. Alternatively, execute this in Command Prompt:

   taskkill /f /im EXCEL.EXE /im WINWORD.EXE /im POWERPNT.EXE

B. Delete Hidden Temporary Owner Files

Office apps create hidden temporary files (starting with ~$) in the sync directory:

1. Open File Explorer and navigate to your synced SharePoint folder.
2. Click on View (top menu) → Show → check Hidden items.
3. Look for files in the format ~$filename.docx or ~$filename.xlsx in the same directory as your locked document.
4. Delete these temporary lock files.

A. Force Kill Hung Office Services

1. Open Terminal (via Spotlight search).
2. Run the command to kill any running Office app processes holding files:

   killall -9 "Microsoft Excel" "Microsoft Word" "Microsoft PowerPoint"

B. Check for System Locks (lsof)

To identify which local process is locking the file:

1. Open Terminal.
2. Type lsof followed by a space, then drag-and-drop the locked file from Finder into the Terminal window (which outputs its path), then press Enter:

   lsof "/Users/username/Library/CloudStorage/OneDrive-SharePoint/Documents/LockedFile.xlsx"

3. Look at the PID column of the output. Run kill -9 <PID> using the target PID to free the file handle.

5. Summary Lock Management Reference

• Check In / Discard Checkout: Right-click the file in the SharePoint web browser interface under More to release administrative locks.
• Taskkill Office Apps: Terminate orphaned process handles on Windows using taskkill /f /im EXCEL.EXE.
• Purge Hidden Temporary Files: Delete the ~$[filename] hidden files from the local synced folder.
• Lsof Handle Scans: Use lsof [filepath] in macOS Terminal to detect which local daemon has locked the file.