Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | ERROR_CLOUD_FILE_PROVIDER_NOT_RUNNING (0x8007016A) | Event Viewer > Application log | |
| Affected build range | Windows 11 23H2 | ||
| Registry key involved | HKLM:\SYSTEM\CurrentControlSet\Services\CldFlt | Registry Editor | -> Start=1 |
| Relevant service/endpoint URL | https://go.microsoft.com/fwlink/?linkid=2050785 | ||
| Log line signature | OneDrive: cloud file provider has stopped (Event ID 2) | Event Viewer > Application log |
Log Files to Check
%LocalAppData%\Microsoft\OneDrive\logs\SyncEngine0.odl%SystemRoot%\System32\winevt\Logs\Application.evtx
What This Error Actually Means
The error code 0x8007016A, which translates to "ERROR_CLOUD_FILE_PROVIDER_NOT_RUNNING," is raised by the OneDrive sync engine when it detects that the cloud file provider service has stopped or failed to register its file system filter. The cloud file provider is a critical component of OneDrive for Business, responsible for integrating cloud files into the local file system and managing their synchronization status. When this error occurs, users will notice red X icons or cloud overlays on affected files in Windows Explorer, indicating that these files cannot be accessed locally until the issue is resolved.Affected Versions and Scope
This error specifically impacts devices running Windows 11 build 23H2 with OneDrive for Business installed. It does not affect other versions of Windows or different cloud storage solutions like SharePoint Online or personal Microsoft accounts. The issue can occur in both standalone installations and managed environments, but it is more likely to surface in corporate settings due to the complexity introduced by additional layers such as Intune policies and conditional access rules.Where To Look First: Logs and Event IDs
To diagnose this error effectively, start by examining two primary log sources:%LocalAppData%\Microsoft\OneDrive\logs\SyncEngine0.odl: This file contains detailed logs of the OneDrive sync engine's operations. Search for lines containing "ERROR_CLOUD_FILE_PROVIDER_NOT_RUNNING" to pinpoint when and why the error occurred.%SystemRoot%\System32\winevt\Logs\Application.evtx: The Application event log is crucial as it records events from various system components, including OneDrive. Look for Event ID 2 (OneDrive: cloud file provider has stopped) to understand when the service last failed.
Root Causes
The error can stem from several distinct causes:OneDrive Background Process Not Running
If OneDrive is not running, it cannot manage its cloud file provider. Verify this by executingGet-Process OneDrive -ErrorAction SilentlyContinue in PowerShell. A null result indicates the process has exited.
CldFlt Minifilter Driver Issues
The CldFlt driver is essential for integrating cloud files into the local file system. If it's not loaded, OneDrive cannot register its file system filter properly. UsefltMC.exe to list loaded minifilters and confirm that CldFlt appears in the output.
StorageSense or Windows Storage Cleanup Service Corruption
These services can interfere with OneDrive by deleting critical files or registry entries related to the cloud file provider registration. Check for any recent changes made by these services that might have caused corruption.Fix Procedure
Follow these steps to resolve the issue:Restart OneDrive: Open the Run dialog (Win + R) and enter
%LocalAppData%\Microsoft\OneDrive\OneDrive.exe /client=Personal. Alternatively, use Task Manager > Run new task.Reset OneDrive: In the Run dialog, execute
%LocalAppData%\Microsoft\OneDrive\onedrive.exe /reset. This re-registers the cloud file provider without losing files.The reset command is a quick fix but may require additional troubleshooting if issues persist.Ensure CldFlt driver service is set to Start=1: Run
Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\CldFltin PowerShell and verify that the Start value is 1 (automatic).If CldFlt is missing from fltMC.exe output, start it manually with
sc start CldFlt. Then restart OneDrive.For persistent failures: Unlink the OneDrive for Business account in Settings > Account > Unlink this PC and re-sign in. This action forces a clean re-registration of the cloud file provider.
Error Code Variants
| Code | Description | Distinguishing Factors |
|---|---|---|
| 0x8007016A | ERROR_CLOUD_FILE_PROVIDER_NOT_RUNNING | The cloud file provider service is not running or failed to register. |
| 0x80070490 | ERROR_CLOUD_SYNC_BUSY | This code indicates that the sync engine is busy and cannot process additional requests, often due to a large number of pending changes. |
| 0x80072F15 | ERROR_FILE_NOT_FOUND | The file or directory does not exist. This error typically occurs when attempting to access a non-existent local path mapped from the cloud. |
Verification
To confirm that the issue has been resolved, monitor the following:- Check Event Viewer > Application log for Event ID 3 (provider registration error) to ensure it no longer appears after applying fixes.
- In
%LocalAppData%\Microsoft\OneDrive\logs\SyncEngine0.odl, look for lines indicating successful cloud file provider registration and synchronization activities. - Verify that files in Windows Explorer are accessible without red X icons or cloud overlays.
Prevention
To prevent recurrence of this issue, consider implementing the following measures:Regularly update OneDrive for Business to the latest version using Intune app policies. For example, download and install the latest setup from
https://go.microsoft.com/fwlink/?linkid=2050785.Configure Intune policies to enforce a consistent baseline of OneDrive settings across devices.
- Navigate to "Intune admin center > Devices > Configuration profiles" and create or update profiles for OneDrive configuration.
Avoid conflicts with StorageSense or Windows Storage cleanup services by configuring exclusions in their policies. For instance, use the OMA-URI
./Device/Vendor/MSFT/StorageSavings/ExcludePathsto prevent these services from targeting OneDrive directories.