Interactive Troubleshooter

Published: Oct 11, 2026

SharePoint Sync Error 0x80070194: OneDrive Cloud Files Diagnostic

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

This guide resolves SharePoint and OneDrive sync error 0x80070194 (ERROR_CLOUD_FILE_UNAVAILABLE). It fixes broken cloud file placeholders, Windows Cloud Files Filter (CldFlt) driver faults, re-authentication locks, and corrupted local synchronization databases.

Full Diagnostic Tree & Step-by-Step Overview

How does error 0x80070194 manifest during SharePoint or OneDrive file operations?

Error appears when double-clicking a 'Cloud Only' (blue cloud icon) file placeholder in File Explorer.
Error occurs on an entire synced SharePoint document library or 'Shortcut to OneDrive' folder.
The OneDrive client status shows 'Processing changes' indefinitely with 0x80070194 in sync logs.
Error occurs following a user account migration, password change, or Entra ID conditional access update.

What is the state of the specific file placeholder throwing the 0x80070194 error?

File placeholder points to an item deleted or moved directly on SharePoint web, breaking the local reparse point.
Windows Cloud Files Filter driver (`cldflt.sys`) is stopped or failing to hydrate the file.
Local NTFS reparse point attribute on the file is corrupted or locked by security software.
File path length exceeds 260 characters or contains unsupported characters on the local file system.

Clearing Broken Reparse Points and Restoring Deleted SharePoint Items

Solution:

Root Cause: Broken NTFS Reparse Point Linkage

Error 0xC000038E (ERROR_CLOUD_FILE_UNAVAILABLE / 0x80070194) occurs when File Explorer requests hydration of a Cloud-Only file whose server-side object was moved, deleted, or unlinked on SharePoint. The local NTFS reparse point points to an invalid server GUID.

# Diagnostic Verification:

Check the file on SharePoint Web (https://yourtenant.sharepoint.com). If missing, it was moved or deleted.

Check OneDrive sync status (%localappdata%\Microsoft\OneDrive\logs).

# Step-by-Step Fix:

Check SharePoint Recycle Bin:

Open the SharePoint library in a browser > click Recycle bin > select item > click Restore.

Delete Broken Local Placeholder:

If permanently deleted on web, remove the local placeholder in PowerShell:

Remove-Item -Path "C:\Users\Username\Tenant\Library\BrokenFile.docx" -Force

Force OneDrive Sync Pause and Resume:

Right-click OneDrive cloud icon > Pause syncing (2 hours) > wait 10 seconds > Resume syncing.

# Prevention & Long-Term Monitoring:

Advise users to delete items inside synced folders rather than web interface to keep local reparse tables aligned.

Repairing Windows Cloud Files Filter Driver (`cldflt.sys`)

Solution:

Root Cause: Cloud Files Filter Driver (`cldflt.sys`) Failure

OneDrive Files On-Demand relies on cldflt.sys to manage file hydration. If the service fails or its registry startup flags are modified, Windows cannot convert cloud placeholders into local files, throwing 0x80070194.

# Diagnostic Verification:

Open PowerShell as Admin:

Get-Service cldflt

If status is Stopped, the filter driver is inactive.

# Step-by-Step Fix:

Verify Driver Registry Flags:

Open regedit and go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CldFlt

Ensure Start DWORD value is set to 2 (Automatic).

Start Driver in PowerShell:

Run:

sc.exe start cldflt

Restart Computer and test hydration.

# Prevention & Long-Term Monitoring:

Ensure OS debloating scripts do not disable core filter driver services (cldflt).

Removing Local Reparse Attributes and Forcing Offline Cache Hydration

Solution:

Root Cause: NTFS Reparse Attribute Corruption

Third-party backup tools or antivirus software can lock NTFS reparse tags (IO_REPARSE_TAG_CLOUD). This corrupts the local metadata header, preventing OneDrive from reading the file's cloud pin state.

# Diagnostic Verification:

In Command Prompt, run:

fsutil reparsepoint query "C:\Path\To\File.docx"

Check for tag mismatch or file access locks.

# Step-by-Step Fix:

Force Hydration in PowerShell:

Run:

Expand-Archive or Clear-RecycleBin commands, or force hydration via attrib:
attrib -P +A "C:\Path\To\File.docx"

Copy File out of Sync Root:

Copy the affected file to C:\Temp. If successful, delete the item in the sync folder and move the copy back.

Reset File Pin State:

Right-click file > click Always keep on this device.

# Prevention & Long-Term Monitoring:

Exclude active sync root folders from aggressive real-time file system modification agents.

Resolving MAX_PATH Character Limit Violations in Sync Paths

Solution:

Root Cause: Win32 File Path Length Limit (260 Characters)

Combining deep SharePoint site names, library structures, subfolders, and long filenames can exceed the Win32 MAX_PATH 260-character limit, blocking file hydration calls.

# Diagnostic Verification:

Run in PowerShell:

Get-ChildItem -Path "C:\SyncRoot" -Recurse | Where-Object {$_.FullName.Length -gt 240} | Select-Object FullName

# Step-by-Step Fix:

Enable Win32 Long Paths in Registry:

Open regedit > go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

Set LongPathsEnabled DWORD to 1.

Shorten Library or Folder Names:

Rename top-level folders on SharePoint Web to reduce total path string lengths.

Force Sync Pass:

Restart OneDrive to apply updated path targets.

# Prevention & Long-Term Monitoring:

Use concise naming conventions for SharePoint document libraries and high-level folders.

What is the scope and setup of the affected SharePoint library sync?

The error affects a folder linked via 'Add shortcut to OneDrive' rather than standard library sync.
The entire synced SharePoint library fails to update and displays a red 'X' overlay.
SharePoint site permissions were recently modified or user account was moved to a new group.
Information Rights Management (IRM) or Sensitivity Labels were applied to the library.

Fixing Conflicts Between 'Add Shortcut to OneDrive' and Direct Library Sync

Solution:

Root Cause: Sync Engine Protocol Conflict

Using both Add shortcut to OneDrive and Sync on the same SharePoint library creates manifest mapping collisions, resulting in error 0x80070194.

# Diagnostic Verification:

Inspect OneDrive web interface for a folder icon containing a small link graphic alongside a directly synced SharePoint folder in File Explorer.

# Step-by-Step Fix:

Remove Web Shortcut:

Open OneDrive web (https://onedrive.live.com).

Locate the shortcut folder > click three dots (...) > select Remove shortcut.

Unlink Direct Sync in Client:

Click OneDrive tray icon > Gear icon > Settings > Account.

Locate the SharePoint library > click Stop sync.

Re-establish Direct Sync:

Open the SharePoint web library > click the Sync button in the top toolbar.

# Prevention & Long-Term Monitoring:

Standardize on either 'Add shortcut to OneDrive' or 'Sync' across your organization.

Completely Resetting the OneDrive Sync Engine (`onedrive.exe /reset`)

Solution:

Root Cause: Local Sync Database Corruption (`ClientFirst.sqlite`)

Unexpected shutdowns or network drops can corrupt OneDrive's SQLite database (ClientFirst.sqlite), severing local file mapping to SharePoint object IDs.

# Diagnostic Verification:

All files in the synced folder display error 0x80070194 and status icons fail to update.

# Step-by-Step Fix:

Run Reset Command:

Press Win + R, enter:

%localappdata%\Microsoft\OneDrive\onedrive.exe /reset

Re-launch OneDrive (if it does not restart automatically after 2 minutes):

Press Win + R, enter:

%localappdata%\Microsoft\OneDrive\onedrive.exe

Allow Background Manifest Rebuild:

Wait for OneDrive to re-index all local placeholders.

# Prevention & Long-Term Monitoring:

Avoid force-killing onedrive.exe processes during active sync cycles.

Re-authenticating Identity and Re-evaluating SharePoint Permissions

Solution:

Root Cause: Stale Entitlement Tokens and ACL Changes

If SharePoint site permissions change or a user password is updated, local sync tokens become invalid. OneDrive fails to hydrate placeholders, returning 0x80070194 due to access denial.

# Diagnostic Verification:

Opening the document library directly on SharePoint Web prompts for authentication or shows 'Access Denied'.

# Step-by-Step Fix:

Unlink Account in OneDrive:

Click OneDrive tray icon > Settings > Account > Unlink this PC.

Clear Stale Office Credentials:

Open control /name Microsoft.CredentialManager > select Windows Credentials.

Remove generic credentials starting with MicrosoftOffice16_Data: and OneDrive.

Open OneDrive, authenticate, and select your library locations.

# Prevention & Long-Term Monitoring:

For detailed endpoint guidance, consult the Microsoft Official Support Guide.

Resolving Information Rights Management (IRM) and Sensitivity Label Blockades

Solution:

Root Cause: IRM Encryption Key Retrieval Failure

When Information Rights Management (IRM) or MIP Sensitivity Labels are enforced, OneDrive must fetch RMS decryption keys before hydrating files. Network blocks on RMS endpoints trigger error 0x80070194.

# Diagnostic Verification:

Files open correctly in web apps (Word Online), but desktop apps fail to hydrate placeholders.

# Step-by-Step Fix:

Clear Local RMS Template Cache:

In PowerShell, run:

Remove-Item -Path "$env:LOCALAPPDATA\Microsoft\MSIPC\*" -Recurse -Force -ErrorAction SilentlyContinue

Open File in Office Web App First:

Open the file on SharePoint Web to confirm account rights.

Use 'Open in Desktop App':

Click Editing > Open in Desktop App to trigger RMS key generation.

# Prevention & Long-Term Monitoring:

Ensure corporate firewalls whitelist RMS endpoints (*.aadrm.com and *.rms.ms).

What operational state is the OneDrive client reporting during the sync failure?

Sync engine reports 'Files On-Demand failed to start' or 'Error 0x80070194'.
OneDrive local storage path resides on an unsupported non-NTFS formatted drive (e.g., FAT32, exFAT, ReFS).
Third-party Antivirus / Security agent locks OneDrive cache folders in AppData.
Windows Storage Sense is forcefully removing hydrated files under low disk space conditions.

Performing Clean Reinstallation of OneDrive Client Software

Solution:

Root Cause: Corrupted Sync Engine Binaries

Corrupted onedrive.exe application binaries can prevent the Files On-Demand API from parsing reparse points properly, leading to hydration failures.

# Diagnostic Verification:

System Event Viewer logs show Event ID 1000 referencing OneDrive.exe or SyncEngine.dll.

# Step-by-Step Fix:

Uninstall OneDrive:

Open Command Prompt as Admin:

%SystemRoot%\SysWOW64\OneDriveSetup.exe /uninstall

Clear Leftover Application Data:

Run:

Remove-Item -Path "$env:LOCALAPPDATA\Microsoft\OneDrive" -Recurse -Force -ErrorAction SilentlyContinue

Install Latest Standalone Version:

Download and run the standalone installer from Microsoft's production channel.

# Prevention & Long-Term Monitoring:

Use Production or Enterprise ring updates for higher sync engine stability.

Converting Sync Volume File System to NTFS Architecture

Solution:

Root Cause: Non-NTFS File System Incompatibility

OneDrive Files On-Demand requires NTFS reparse points and sparse file features. Syncing to exFAT, FAT32, or network shares triggers error 0x80070194.

# Diagnostic Verification:

Open PowerShell:

Get-Volume

Check if the drive hosting your sync folder uses a file system other than NTFS.

# Step-by-Step Fix:

Unlink OneDrive Account:

Go to OneDrive Settings > Account > Unlink this PC.

Convert Drive to NTFS (if using FAT32):

Run in Command Prompt:

convert X: /fs:ntfs *(replace X: with target drive letter)*

Relocate Sync Folder:

# Prevention & Long-Term Monitoring:

Only host OneDrive sync roots on native, fixed NTFS partitions.

Excluding OneDrive Cache Directories from Antivirus Real-Time Scanning

Solution:

Root Cause: Antivirus File Lock Race Conditions

Antivirus engines scanning temporary hydration files can hold exclusive handles on local cache directories, breaking placeholder instantiation.

# Diagnostic Verification:

Temporarily disabling real-time antivirus protection allows cloud placeholders to hydrate without error.

# Step-by-Step Fix:

Add Antivirus Path Exclusions:

Exclude the following paths in your security software:

%localappdata%\Microsoft\OneDrive\
C:\Users\<Username>\<TenantName>\

Add Process Exclusion:

Add an exclusion for %localappdata%\Microsoft\OneDrive\onedrive.exe.

Test file hydration.

# Prevention & Long-Term Monitoring:

Configure enterprise EDR solutions to respect cloud file hydration handles.

Configuring Storage Sense Policies to Prevent Dehydration Conflicts

Solution:

Root Cause: Aggressive Storage Sense Dehydration

When disk space is low, Windows Storage Sense automatically dehydrates local files back to cloud placeholders. If this occurs during active file read operations, the local file handle breaks, throwing 0x80070194.

# Diagnostic Verification:

Windows notification area displays 'Storage Sense freed up space' right before the sync error occurs.

# Step-by-Step Fix:

Adjust Storage Sense Settings:

Go to Settings > System > Storage > Storage Sense.

Change Content Dehydration Thresholds:

Under *OneDrive*, change Content will become online-only if not opened for more than: to Never or 60 days.

Pin Essential Folders:

Right-click critical folders > select Always keep on this device.

# Prevention & Long-Term Monitoring:

Maintain at least 15% free disk space on volumes hosting cloud sync folders.

What enterprise identity or group policy state is affecting the sync client?

Entra ID Conditional Access Policy blocks unmanaged or non-compliant device access.
Group Policy disables sync for specific tenant IDs or forces silent account configuration.
Primary Refresh Token (PRT) is missing or invalid on a Hybrid Entra ID Joined PC.
Web Account Manager (WAM) broker authentication package is corrupt.

Validating Entra ID Device Compliance and Conditional Access Policies

Solution:

Root Cause: Conditional Access Device Compliance Rejection

If Entra ID Conditional Access requires compliant or hybrid-joined devices, non-compliant endpoints will have their file hydration calls blocked by the API, resulting in 0x80070194.

# Diagnostic Verification:

Open Command Prompt and check join status:

dsregcmd /status

Confirm AzureAdJoined : YES and IsDeviceJoined : YES.

# Step-by-Step Fix:

Check Intune Compliance:

Open Settings > Accounts > Access work or school > click account > Info > click Sync.

Review Entra Sign-In Logs (Admin):

Inspect Entra ID portal sign-in logs for Error 53000 (Device non-compliant).

Re-register Device:

If compliance state is broken, run dsregcmd /leave and re-join the domain.

# Prevention & Long-Term Monitoring:

Implement grace periods in Conditional Access policies during OS updates.

Audit Administrative Template GPO Settings for OneDrive

Solution:

Root Cause: Group Policy Sync Restrictions

Administrative GPOs (such as *Allow syncing OneDrive accounts for only specific organizations*) can block background hydration calls if tenant GUIDs are misconfigured.

# Diagnostic Verification:

Check active GPO keys in Registry Editor:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive

# Step-by-Step Fix:

Review Tenant Restrictions Key:

Go to HKLM\SOFTWARE\Policies\Microsoft\OneDrive\AllowTenantList.

Verify your tenant ID GUID is correctly listed.

Force GPO Update:

Open Command Prompt as Admin:

gpupdate /force

Restart OneDrive client.

# Prevention & Long-Term Monitoring:

Test GPO updates in an isolated OU before tenant-wide deployment.

Refreshing Entra ID Primary Refresh Token (PRT)

Solution:

Root Cause: Invalid Primary Refresh Token (PRT)

On Hybrid Entra ID Joined machines, OneDrive relies on a Primary Refresh Token (PRT) for single sign-on. If the PRT expires or invalidates, placeholder hydration fails.

# Diagnostic Verification:

Run dsregcmd /status in Command Prompt and check if AzureAdPrt : YES.

# Step-by-Step Fix:

Lock and Unlock Session:

Press Win + L to lock Windows, then unlock to request a fresh PRT.

Force Re-authentication:

Open Command Prompt as Admin:

dsregcmd /debug /join

Restart OneDrive client and test file access.

# Prevention & Long-Term Monitoring:

Ensure domain controllers sync password hashes reliably with Entra Connect.

Re-registering Web Account Manager (WAM) Broker Plugin

Solution:

Root Cause: WAM Broker AppX Corruption

Windows Web Account Manager (Microsoft.AAD.BrokerPlugin) handles cloud token requests. If the AppX package breaks, authentication calls silently fail.

# Diagnostic Verification:

Attempting to sign in to OneDrive results in a blank white box or immediate crash.

# Step-by-Step Fix:

Re-register AAD Broker Plugin in PowerShell (Admin):

Run:

Add-AppxPackage -Register "C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

Re-register Accounts Control Package:

Run:

Get-AppxPackage -AllUsers *AccountsControl* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Restart PC and launch OneDrive.

# Prevention & Long-Term Monitoring:

Avoid manually modifying or cleaning SystemApps directories.

Related Diagnostic Guides

Fix Copy text (Ctrl-C or context menu) not working on browsers

Windows Credential Guard Blocking App Exclusions: How to Fix It

WordPress Redirecting to Spam Websites: How to Fix It

Malicious Browser Extensions: How to Detect and Remove Them

Unreal Engine Shader Compilation Stuttering: How to Fix It

Subscribe to StepDiag

Embed Guide on Your Website