Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Error code: 0x8007016A | Event Viewer - OneDrive Operational log | -> Event ID 6084 |
| Affected build range | Windows 11 23H2 | OS Build Information | |
| Registry key involved | HKLM\SOFTWARE\Microsoft\OneDrive\Setup | Registry Editor | -> Check for cldflt.sys status |
| Relevant service/endpoint URL | https://aka.ms/onedrive/setup | Online Documentation | |
| Log line signature | Cloud file provider is not running. | Event Viewer - OneDrive Operational log | -> Event ID 6084 |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Windows-OneDrive%4Operational.evtx
What This Error Actually Means
The error code 0x8007016A is a generic Windows system error that translates to "The specified network name is no longer available." In the context of OneDrive for Business, this error specifically indicates an issue with the Cloud File Provider (CFP) service. The CFP is responsible for managing Files On Demand functionality within OneDrive, which allows users to access their cloud files without downloading them locally until they are needed. When this error occurs, it means that the necessary components of the CFP have stopped running or failed to start correctly. The component raising this error is the Storage Sync service (StorageSync), a critical part of the Files On Demand feature in OneDrive for Business. This service interacts with cloud storage and local file systems to ensure seamless synchronization between them. When it encounters issues, such as being quarantined by antivirus software or conflicts with other services like StorSimple, it can lead to this error.Affected Versions and Scope
This issue primarily affects Windows 11 build 23H2 (OS Build 25206.1804) and later versions where Files On Demand is enabled for OneDrive for Business users. It does not affect older builds or other operating systems like Windows 10, nor does it impact non-OneDrive cloud storage providers. The error can occur in both on-premises environments and those utilizing Microsoft's cloud services. However, it is less likely to appear in scenarios where Files On Demand is disabled for users or when the affected machine is not configured with OneDrive for Business integration.Where To Look First: Logs and Event IDs
To diagnose this issue effectively, you should start by examining the Microsoft-Windows-OneDrive Operational log. This can be found atC:\Windows\System32\winevt\Logs\Microsoft-Windows-OneDrive%4Operational.evtx. The exact line to look for is:
Cloud file provider is not running.
This message will appear in the event viewer with an Event ID of 6084. Additionally, you should check if there are any related errors or warnings around this time that might provide more context about why the CFP stopped functioning.
Root Causes
The error code 0x8007016A can arise from several distinct causes:
Antivirus Quarantine of cldflt.sys
Some antivirus solutions may flag cldflt.sys, a critical system file used by the Cloud File Provider, as potentially malicious and quarantine it. This prevents the CFP from starting properly.
To identify if this is the cause, check your antivirus logs for any quarantines or detections involving cldflt.sys. You can also use PowerShell to inspect the status of the Storage Sync service:
Get-Service -Name "StorageSync"
If the service is stopped and there are no other indications of issues, this likely points towards an antivirus conflict.
Windows Update Conflicts
Sometimes, Windows updates can introduce changes that interfere with the proper functioning of OneDrive for Business. This often happens when updates modify system files or services in a way that disrupts the Files On Demand feature.
To determine if a recent update is causing this issue, review the Windows Update history and check if any problematic updates were installed around the time the error started appearing.
StorSimple Conflict
If your organization uses Microsoft StorSimple for cloud storage services alongside OneDrive for Business, there might be conflicts between these two systems. This can occur due to overlapping configurations or incompatibilities introduced by software updates.
To diagnose this issue, review the configuration settings of both OneDrive and StorSimple, ensuring that they do not conflict with each other's operations.
Fix Procedure
The following steps outline how to resolve the error code 0x8007016A:
- Restart the Storage Sync Service: Use the command prompt as an administrator and run:
net stop onedrive && net start onedrive
Warning: This step can break enrolled devices if not performed carefully. Ensure you have a backup plan in place.
- Re-register the Storage Sync Service: Open PowerShell as an administrator and run:
Get-Service -Name "FileSyncSvc" | Restart-Service
Then, check Event ID 6084 in the Microsoft-Windows-OneDrive Operational log to confirm that the service has started correctly.
- Adjust Antivirus Settings: If an antivirus solution is quarantining
cldflt.sys, adjust its settings to exclude this file. You can use PowerShell to check if the file is being blocked:
Get-FileHash -Algorithm SHA256 -Path "C:\Windows\System32\drivers\cldflt.sys"
Compare the hash value with known good values from Microsoft documentation.
- Review and Adjust Windows Update Settings: Use PowerShell to review recent updates:
Get-HotFix
Tip: If you suspect a specific update is causing the issue, use the Intune admin center > Devices > Updates & Upgrade blade to manage and rollback updates.
- Check StorSimple Configuration: Review your organization's configuration settings for both OneDrive and StorSimple. Use PowerShell cmdlets like:
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
To ensure there are no conflicting configurations.
Error Code Variants
net stop onedrive && net start onedriveWarning: This step can break enrolled devices if not performed carefully. Ensure you have a backup plan in place.
Get-Service -Name "FileSyncSvc" | Restart-Service
Then, check Event ID 6084 in the Microsoft-Windows-OneDrive Operational log to confirm that the service has started correctly.cldflt.sys, adjust its settings to exclude this file. You can use PowerShell to check if the file is being blocked:
Get-FileHash -Algorithm SHA256 -Path "C:\Windows\System32\drivers\cldflt.sys"
Compare the hash value with known good values from Microsoft documentation.Get-HotFixTip: If you suspect a specific update is causing the issue, use the Intune admin center > Devices > Updates & Upgrade blade to manage and rollback updates.
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
To ensure there are no conflicting configurations.| Error Code | Description | Distinguishing Factors |
|---|---|---|
| 0x8007016A | The specified network name is no longer available. | This error specifically relates to the Cloud File Provider not running. |
| 0x80072F8F | The system cannot find the file specified. | This error occurs when a required file is missing, often due to corruption or deletion. |
| 0x8007139F | A device attached to the system is not functioning. | This error indicates hardware issues rather than software conflicts. |
Verification
After applying the fixes, you should verify that the issue has been resolved by checking if the Storage Sync service is running correctly. Use PowerShell to check the status:Get-Service -Name "StorageSync"
Additionally, review the Microsoft-Windows-OneDrive Operational log for any new entries indicating successful operation of the Cloud File Provider.
Prevention
To prevent recurrence of this error, consider implementing policies that exclude critical system files likecldflt.sys from antivirus scans. You can use an OMA-URI such as:
.//Device/Vendor/MSFT/AVExclusionList/CldFltSysExclude
to configure exclusions in your organization's management console.
Furthermore, regularly review and test updates before deploying them to ensure compatibility with OneDrive for Business. Use PowerShell cmdlets like:
Invoke-MgGraphRequest -Method GET -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices"
to monitor device health and update status across your organization.
By following these guidelines, you can minimize the likelihood of encountering this error in future scenarios.