OneDrive “File in Use” Error (Even when the file is closed)

The OneDrive “File in Use” error occurs when Windows or Microsoft 365 maintains an active lock handle on a document even after you close the editing window. This problem is usually caused by an orphaned background process (such as EXCEL.EXE or WINWORD.EXE), the Windows File Explorer preview pane (prevhost.exe), or a stuck Office File Cache sync thread. To fix it immediately, force-close remaining application processes in Task Manager or pause and resume OneDrive synchronization to release the stuck lock handle.

Fast-Fix: The 45-Second Solution

An unreleased read/write lock handle held by an orphaned background process or Windows File Explorer preview handler causes this low-risk error. To resolve the temporary file lock, open Task Manager, end tasks for WINWORD.EXE, EXCEL.EXE, POWERPNT.EXE, and prevhost.exe, then pause and resume OneDrive syncing via the tray icon.

Diagnostic Snapshot

• Severity Tier: Low to Moderate (blocks local sync updates; existing cloud data remains safe).
• Data Safety Risk: Low (unsaved local changes stay cached locally, but cloud versions remain unaffected).
• Common Cause: Orphaned background executable holding a file handle, Windows File Explorer Preview Pane lock, or stalled Office File Cache background thread.
• Admin Requirement: None for standard workstation locks; Global or SharePoint Administrator required only if a server-side lock persists longer than 24 hours on a shared cloud folder.

Condition: Low Risk vs. High Risk

Understanding whether your lock issue is local or server-bound determines how aggressively you need to troubleshoot:

• Low Risk Condition: The error appears on a single file stored on a local workstation, disappears after closing File Explorer or restarting the application, and does not interfere with other files syncing across your OneDrive directory.
• High Risk Condition: The error persists across full system reboots, impacts multiple users working in a shared SharePoint or OneDrive document library, or triggers recurring merge conflicts and credential failure alerts across your Microsoft 365 apps.

The System Break (What This Means)

Windows manages file access using system lock handles (FILE_SHARE_READ and FILE_SHARE_WRITE). When you open a document in Word or Excel, the operating system applies a lock handle to prevent other programs from altering the underlying binary stream at the same time.

Think of this file lock like a mechanical C-clamp placed on a pipe during repairs to keep water from flowing. When an application closes normally, it sends a release signal that removes the clamp. However, if Word crashes, an add-in hangs, or File Explorer previews the document, the application exits without removing the clamp. OneDrive detects that Windows still has an active, open handle on the file and halts sync operations to prevent data corruption, throwing the “File in Use” error.

Root Cause Probability

When a closed file reports that it is still open, the underlying cause typically falls into one of three weighted categories:

[====================] 60% Orphaned Background Process / Preview Pane
[==========          ] 30% Stalled Office File Cache / Telemetry Lock
[===                 ] 10% Stale Server-Side Co-Authoring Lock

• Likely (60%): An orphaned background application (WINWORD.EXE, EXCEL.EXE, or prevhost.exe) or the File Explorer preview pane is maintaining an open file handle.
• Possible (30%): A corrupted entry in the local Microsoft Office File Cache (%LocalAppData%\Microsoft\Office\16.0\OfficeFileCache) is maintaining a locked state between local storage and cloud endpoint handlers.
• Rare (10%): A stale server-side co-authoring lock on SharePoint or OneDrive Web triggered by an abrupt network disconnect during an active collaborative session.

Conflict Escalators

Specific workstation configurations and background tools increase the frequency of unreleased file handles:

• File Explorer Preview Pane: Keeping the Preview Pane enabled forces Windows to invoke prevhost.exe whenever you select a file. This places a continuous read-lock on the document even if no office app is open.
• Third-Party Antivirus & Indexing Tools: Backup utilities or security agents scanning changed files can hold temporary lock handles right as OneDrive attempts to upload the updated byte stream.
• Office AutoSave/Co-Authoring Webhook Delays: Momentary Wi-Fi drops while AutoSave is sending delta patches can leave the local Office sync engine waiting for an acknowledgment token that never arrives.
• New Outlook & Teams Attachment Previews: Previewing an attached document inside Microsoft Teams or Outlook opens a hidden temporary background thread that locks the target document in your sync folder.

Progression: 1 Hour → 24 Hours → 1 Week

Ignoring an unreleased file lock leads to incremental sync breakdown and file isolation:

• 1 Hour: Local edits fail to push to OneDrive Cloud. A red “X” or yellow warning badge appears over the file icon in File Explorer, but local changes remain cached safely in memory or temporary files.
• 24 Hours: Version divergence begins. If other team members edit the document via OneDrive Web or mobile devices, their updates apply to the cloud master copy while your workstation remains isolated on a stale local copy.
• 1 Week: Office File Cache corruption escalates. OneDrive flags the document for a forced “Save a Copy” resolution, increasing the risk of orphaned file versions and lost team changes.

Common Misdiagnoses

It is easy to confuse a local lock handle issue with other Microsoft 365 sync failures. Here is how to distinguish them:

• Merge Conflicts: A merge conflict occurs when two users submit different edits to the cloud at the same time. “File in Use” prevents your edits from leaving your computer in the first place because Windows refuses to hand the file to OneDrive. If you are dealing with conflicting revisions rather than locked handles, see How to Resolve OneDrive “Merge Conflict” without Losing Data.
• Upload Blocked / Sign-In Required: An upload block stems from expired OAuth identity tokens or multi-factor authentication loops. “File in Use” is strictly an OS-level file handle collision. If your sync status reports authentication errors, see OneDrive “Upload Blocked” – Sign in to resolve this issue.
• Access Denied / Permissions Errors: Access denied errors occur when security ACLs prohibit file modifications. “File in Use” allows file reads and writes under normal conditions but is temporarily blocked by an active process handle.

Immediate Action Steps

Follow these sequential steps to release the lock handle and resume normal OneDrive synchronization.

Step 1: Terminate Orphaned Processes via Task Manager

1. Press Ctrl + Shift + Esc to launch Task Manager.
2. Select the Details tab on the left menu (or top navigation depending on your Windows version).
3. Sort processes by Name and search for any of the following executables:
   • WINWORD.EXE
   • EXCEL.EXE
   • POWERPNT.EXE
   • prevhost.exe
4. Select each process and click End Task.

Step 2: Turn Off the Windows File Explorer Preview Pane

1. Press Win + E to open File Explorer.
2. Click the View tab in the top ribbon menu.
3. In the Show submenu, uncheck Preview pane (or press Alt + P to toggle it off).
4. Refresh your folder view by pressing F5.

Step 3: Pause and Resume OneDrive Sync

1. Click the OneDrive icon (cloud symbol) in your Windows system tray.
2. Click the Gear icon (Settings) in the top right corner of the popup menu.
3. Select Pause syncing and choose 2 hours.
4. Wait 10 to 15 seconds for OneDrive to drop all active socket connections.
5. Click the OneDrive tray icon again and click Resume syncing.

Step 4: Clear the Local Office File Cache

1. Open any working Microsoft 365 application (such as Word or Excel).
2. Click File > Options in the top left corner.
3. Select Save from the left navigation menu.
4. Scroll down to Cache Settings.
5. Click Delete cached files and confirm by clicking Delete cached information.

Step 5: Perform a Soft Reset of the OneDrive Client

If the sync engine remains stuck after releasing file handles, reset the OneDrive client executable:

1. Press Win + R to open the Run dialog box.
2. Copy and paste the following command, then press Enter:DOS %localappdata%\Microsoft\OneDrive\onedrive.exe /reset
3. If OneDrive does not restart automatically after 2 minutes, run this command:DOS %localappdata%\Microsoft\OneDrive\onedrive.exe

If OneDrive remains in an unyielding “Processing Changes” loop after executing a reset, refer to OneDrive Stuck on “Processing Changes” for Hours.

Hard-Stop Red Flags

Escalate the issue to your enterprise IT support desk if you encounter any of the following symptoms:

• Persistent Server Lock: File Explorer reports the file is “Locked for editing by Unknown User” continuously for over 24 hours across multiple system reboots and network changes.
• Mass Lock Failure: Every file within a specific folder or shared library throws “File in Use” errors simultaneously.
• Corrupted Encryption / Access Denial: Opening the file yields system alerts stating “Access Denied,” “Tenant Security Block,” or corrupt file header notifications.

What the IT Admin Will Check

When escalated, an IT Administrator will use server-side tools and administrative portals to clear persistent locks:

1. SharePoint Online / OneDrive Admin Center Verification: Admins will inspect active co-authoring sessions on the target document library to identify hung user sessions.
2. Forced User Session Termination: Admins will execute PowerShell commands using the SharePoint Online Management Shell to terminate ghost web sessions:PowerShell # Revoke active user sessions across cloud endpoints Revoke-SPOUserSession -User principaluser@yourdomain.com
3. PnP PowerShell Lock Release: If a server-side lock handle remains orphaned on a document, admins can clear the lock directly via PnP PowerShell:PowerShell # Connect to tenant and unlock file handle Connect-PnPOnline -Url "<https://yourdomain.sharepoint.com/sites/sitecollection>" -Interactive Unlock-PnPFile -ServerRelativeUrl "/sites/sitecollection/Shared Documents/filename.docx"

Resolution Complexity

Metric	Level	Details
User Self-Service Fix	Low Complexity (85% of cases)	Resolved in under 2 minutes by ending background tasks in Task Manager or toggling off the File Explorer Preview Pane.
Client / Cache Reset	Moderate Complexity (12% of cases)	Requires purging the Office File Cache or executing a onedrive.exe /reset command.
IT Admin Escalation	High Complexity (3% of cases)	Requires server-side PowerShell session revocation (Revoke-SPOUserSession or Unlock-PnPFile).

Related Error Escalators

If resolving the “File in Use” error triggers secondary sync issues, consult these targeted diagnostic guides:

• Sync Client Unresponsiveness: If OneDrive remains frozen after releasing local file handles, see OneDrive Stuck on “Processing Changes” for Hours.
• File Overwrite Warnings: If clearing the lock handle forces OneDrive to identify divergent copies, follow How to Resolve OneDrive “Merge Conflict” without Losing Data.
• Identity and Authentication Failures: If your sync status changes from “File in Use” to credential warning prompts, see OneDrive “Upload Blocked” – Sign in to resolve this issue.

Ticket Closed

The OneDrive “File in Use” error is almost always a client-side operating system artifact, a lock handle left behind by an ungracefully terminated application process or an aggressive preview pane handler. By ending orphaned tasks in Task Manager, disabling the File Explorer preview pane, and cycling OneDrive synchronization, you clear the held handle and allow OneDrive to resume syncing your file.