Interactive Troubleshooter

Published: Sep 10, 2026

Dropbox Smart Sync Not Working: Complete Diagnostic & Fix Guide

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Exhaustive root-cause diagnostic tree for fixing Dropbox Smart Sync failures, online-only file download errors, and sync driver stalls. Resolves macOS File Provider framework deadlocks, Windows NTFS reparse point corruption, File Explorer integration crashes, and local database lock states.

Full Diagnostic Tree & Step-by-Step Overview

What specific Smart Sync behavior or error message are you encountering?

Online-only files fail to hydrate or download when double-clicked, returning an OS file system or I/O error.
Right-clicking files does not show the 'Make online-only' or 'Make available offline' context menu options.
Files marked as 'Online-only' still consume full physical hard drive space or continuously re-download.
Dropbox app hangs indefinitely on 'Syncing...' or 'Connecting...' while Smart Sync status icons disappear.

What operating system environment and underlying driver subsystem is reporting the file hydration failure?

Windows environment failing with 'Error 0x80070185: The cloud sync provider failed the operation' or raw file lock error.
macOS environment failing with File Provider extension domain errors or infinite hydration spinner on macOS Monterey/Ventura/Sonoma.
Network security app or endpoint security tool blocking high-bandwidth chunked hydration streams.

Repairing Windows Cloud Files Filter Driver and Reparse Points

Solution:

Root Cause: Windows Cloud Files Filter Driver (cldflt.sys) Unbind or Reparse Tag Corruption

Dropbox Smart Sync on Windows uses the Windows Cloud Files Filter Driver (cldflt.sys) alongside NTFS reparse points (IO_REPARSE_TAG_CLOUD_DROPBOX) to present virtual placeholders. When cldflt.sys becomes detached from the NTFS volume or reparse tags become corrupt, double-clicking an online-only placeholder fails to trigger file hydration. The OS throws ERROR_CLOUD_SYNC_PROVIDER_FAILED (0x80070185) because the filesystem filter driver cannot route the I/O request back to the Dropbox daemon.

Diagnostic Verification:

Open PowerShell as Administrator and verify if the Cloud Files Filter Driver is active and attached to your OS volume:

fltmc filters

Check if cldflt is listed under filter drivers and verify volume attachment:

fltmc instances -m cldflt

Step-by-Step Fix:

1Re-enable and Start Cloud Files Filter Service:

Run PowerShell as Administrator to ensure the driver startup type is set to system boot:

Set-Service -Name "cldflt" -StartupType System
Start-Service -Name "cldflt"

2Re-attach Driver Filter to the Target Volume:

Attach cldflt to your primary volume (replace C: with your Dropbox volume letter if non-standard):

fltmc attach cldflt C:

3Reset NTFS Reparse Point Flags on Corrupt Placeholders:

Force Dropbox to audit local reparse tags by running the built-in Dropbox fix commands:

Open Dropbox Preferences > Account.

Hold Space + Option (macOS) or Alt + H (Windows) and click Fix Hardlinks and Fix Permissions.

4Restart System Shell:

Restart Explorer to re-initialize shell namespace extension hooks:

Stop-Process -Name explorer -Force; Start-Process explorer.exe

Prevention & Long-Term Monitoring:

Avoid running registry cleaners or aggressive disk defragmenters that modify NTFS reparse tags or unmount filesystem filter drivers.

Resetting macOS File Provider Framework Domain State

Solution:

Root Cause: macOS File Provider Daemon (`fileproviderd`) Domain Lock

On modern macOS releases, Apple mandated the migration of cloud storage sync engines from kernel extensions (KEXTs) to the native File Provider framework. When macOS experiences unexpected crashes, kernel updates, or daemon panics, the fileproviderd subsystem loses track of the Dropbox extension domain mapping located inside ~/Library/CloudStorage. The local virtual filesystem becomes read-only or fails to process hydration callbacks.

Diagnostic Verification:

Open macOS Terminal and check the status of active File Provider domains:

fileproviderctl list

Look for domain entries associated with com.getdropbox.dropbox and verify if the status reports [Error] or [Disconnected].

Step-by-Step Fix:

1Kill Orphaned File Provider and Dropbox Processes:

Execute process terminations in Terminal:

killall fileproviderd
killall Dropbox

2Reset File Provider Domain for Dropbox:

Remove and re-register the file provider domain via command line:

fileproviderctl domain remove com.getdropbox.dropbox.fileprovider

3Force Re-indexing of macOS Cloud Storage Location:

Reset Spotlight metadata indexing for the CloudStorage folder:

mdutil -i off ~/Library/CloudStorage
mdutil -i on ~/Library/CloudStorage

4Relaunch Dropbox App:

Launch Dropbox from Finder or Terminal (open /Applications/Dropbox.app). Allow macOS to prompt for File Provider permission authorization.

Prevention & Long-Term Monitoring:

Refer to Official Apple Support Documentation regarding macOS file provider migration limits, ensuring system software updates do not interrupt active sync migrations.

Resolving Encrypted Socket Inspection and Endpoint Security Blocks

Solution:

Root Cause: Transport Layer Security (TLS) Inspection & Endpoint Filter Locks

Dropbox Smart Sync streams file hydration payload chunks via HTTPS over high-concurrency TCP sockets. Endpoint Detection and Response (EDR) software, third-party firewalls, or corporate Web Proxies enforcing SSL/TLS deep packet inspection break chunked HTTP/2 streams. The Dropbox client drops socket handles while waiting for payload bytes, leaving the local file stuck in a zero-byte placeholder state indefinitely.

Diagnostic Verification:

Inspect the Dropbox debug log file for network transport errors:

Windows: %LOCALAPPDATA%\Dropbox\logs\

macOS: ~/Library/Logs/Dropbox/

Search for log entries containing SSLHandshakeFailed, CERT_UNTRUSTED, or Connection reset by peer.

Step-by-Step Fix:

1Bypass Proxy and SSL Inspection for Dropbox Endpoints:

Configure network firewalls and local security software to bypass SSL inspection for *.dropbox.com, *.dropboxapi.com, and *.dropboxstatic.com.

2Configure Dropbox App Proxy Parameters:

Open Dropbox Preferences > Network.

Under Proxy Settings, explicitly change from *Auto-detect* to No proxy (if operating outside a mandatory corporate proxy network).

3Re-bind Local CA Certificate Stores:

On Windows, flush invalid certificate revocation lists in PowerShell as Administrator:

certutil -urlcache * delete

4Restart Sync Engine:

Quit Dropbox completely and relaunch the application to establish clean, uninspected socket tunnels.

Prevention & Long-Term Monitoring:

Maintain explicit enterprise firewall exceptions for Dropbox client binaries (Dropbox.exe or /Applications/Dropbox.app).

Which operating system shell environment is missing the Smart Sync context menu controls?

Windows Explorer context menu missing Smart Sync options or limited by Windows 11 sparse package menu limits.
macOS Finder context menu missing Smart Sync options due to disabled Finder Extensions or system policy.

Re-registering Windows Shell Extensions and COM Handler Artifacts

Solution:

Root Cause: Windows Shell Extension DLL Unregistration or Sparse Package Drop

Dropbox context menu items ('Make online-only' and 'Make available offline') are injected into File Explorer using COM shell extension DLLs (DropboxExt64.dll). In Windows 11, new context menus require a packaged Appx manifest (Sparse Package). If Windows updates overwrite COM registration keys or if third-party shell extensions exceed OS slot allocation limits (Windows limits context menu overlay handlers to 15 slots), Dropbox extensions fail to register.

Diagnostic Verification:

Inspect registered Shell Overlay Handlers in the Windows Registry using PowerShell:

Get-ChildItem -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers"

If the Dropbox entries are numbered lower than 15 or missing entirely, overlay context integration is broken.

Step-by-Step Fix:

1Re-register Core Shell Extension DLLs:

Open PowerShell as Administrator, navigate to the Dropbox binaries directory, and re-register DLL handlers:

Set-Location "C:\Program Files (x86)\Dropbox\Client"
regsvr32 /s DropboxExt64.dll

2Priority-Prefix Dropbox Registry Identifiers:

Navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers in Registry Editor (regedit).

Ensure Dropbox keys are prefixed with spaces or low numbers (e.g., 1DropboxExt1) so they occupy the top 15 slots recognized by Windows Explorer.

3Restore Classic Context Menu on Windows 11 (Optional Troubleshooting Step):

Force Windows 11 to display the legacy full context menu via PowerShell:

reg add "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32" /f /ve

4Restart File Explorer:

Apply registry changes immediately:

Stop-Process -Name explorer -Force; Start-Process explorer.exe

Prevention & Long-Term Monitoring:

Limit installation of excessive cloud storage apps (e.g., OneDrive, Box, Google Drive) that compete for limited Windows shell overlay slots.

Re-authorizing macOS Finder Integration Extensions

Solution:

Root Cause: macOS Finder Extension Sandboxing Revocation

macOS enforces strict sandboxing rules on extensions that inject UI elements into Finder. If the macOS system database (pluginkit) marks the Dropbox Finder extension as disabled, or if privacy permissions under Accessibility or Full Disk Access are revoked during a macOS security update, Finder will suppress all Smart Sync options from the right-click menu.

Diagnostic Verification:

Check the active status of the Dropbox Finder plugin via Terminal:

pluginkit -m -i com.getdropbox.dropbox.garcon

Look for a + sign indicating the plugin is enabled. A - sign indicates the plugin is disabled by macOS.

Step-by-Step Fix:

1Force-Enable Finder Extension via PlugInKit:

Run the explicit plugin activation command in Terminal:

pluginkit -e use -i com.getdropbox.dropbox.garcon

2Grant Full Disk Access and Accessibility Permissions:

Open System Settings > Privacy & Security > Full Disk Access.

Toggle the switch for Dropbox to ON.

Repeat under System Settings > Privacy & Security > Accessibility.

3Restart Finder Process:

Flush and relaunch Finder to load context extension bundles:

killall Finder

Prevention & Long-Term Monitoring:

Verify that system administration profiles (MDM) do not restrict user extension approvals for macOS Finder integrations.

What disk allocation anomaly or download behavior is occurring with your Online-only files?

Files marked as 'Online-only' report full size-on-disk due to application background reads or indexing engines.
Online-only files automatically re-download and switch back to 'Local' status without user intervention.

Disabling Automated File Scanners and Indexing Engine Hydration Triggers

Solution:

Root Cause: Unintentional Hydration via Background File System Scanners

An 'Online-only' file is a sparse placeholder containing metadata (file name, size, structure) but zero physical data blocks allocated on the hard drive. If a local application (such as Windows Search Indexer, macOS Spotlight, antivirus real-time scanners, or automated backup tools) opens the file handle to read header signatures or generate thumbnails, the OS interprets this as a user request and automatically downloads the entire file payload back to disk.

Diagnostic Verification:

On Windows, monitor process handle activity against your Dropbox folder using PowerShell:

Get-WinEvent -ListProvider Microsoft-Windows-Kernel-Process

Alternatively, check Resource Monitor (resmon.exe) under Disk Activity to identify which .exe process is actively reading files in the Dropbox path.

Step-by-Step Fix:

1Exclude Dropbox Directory from Windows Search Indexer:

Open Settings > Privacy & security > Searching Windows.

Under Excluded Folders, click Add an excluded folder and select your primary Dropbox directory.

2Exclude Dropbox Directory from macOS Spotlight:

Open System Settings > Siri & Spotlight > Spotlight Privacy.

Drag the Dropbox folder into the privacy exclusion list.

3Exclude Dropbox Directory from Antivirus Real-Time Scans:

Configure your antivirus software (e.g., Windows Defender) to exclude raw read scans on the Dropbox folder using PowerShell as Administrator:

Add-MpPreference -ExclusionPath "$env:USERPROFILE\Dropbox"

4Re-apply Online-Only Attribute:

Right-click the bloated folder in File Explorer or Finder and select Make online-only.

Prevention & Long-Term Monitoring:

Configure automated backup solutions (such as Backblaze or Acronis) to exclude virtual cloud storage drives to prevent massive background file hydration.

Configuring Smart Sync Default Preferences and Resolving Sync Conflicts

Solution:

Root Cause: Sync Engine Preference Mismatch and Conflict Loop

If the primary setting under your Dropbox account preferences is configured to set newly added files to 'Local' by default, or if multiple workstations linked to the same account are overriding file states, the server state will continuously push full file payloads back to your machine. Additionally, corrupted local sync databases can cause the sync engine to lose track of placeholder states, resulting in auto-hydration loops.

Diagnostic Verification:

Open the Dropbox Desktop App, click your profile picture, and navigate to Preferences > Sync.

Check the setting labeled Smart Sync default for new files.

Step-by-Step Fix:

1Update Account-Wide Default Preferences:

In Dropbox Preferences > Sync, set Smart Sync default to Online-only.

Toggle Save hard drive space automatically (Automatic Smart Sync) to On.

2Purge Local Database Caches:

Terminate Dropbox process via PowerShell or Terminal:

Windows: Stop-Process -Name Dropbox -Force

macOS: killall Dropbox

Delete the local sync engine cache folder (.dropbox.attr and instance cache):

Windows: Remove-Item -Path "$env:LOCALAPPDATA\Dropbox\instance*\sync_db" -Recurse -Force

macOS: rm -rf ~/Library/Application\ Support/Dropbox/instance*/sync_db

3Restart Dropbox Application:

Launch Dropbox to initiate a fresh, uncorrupted metadata scan against cloud servers.

Prevention & Long-Term Monitoring:

Communicate team-wide file state policies when sharing collaborative team folders to prevent team members from forcing full local syncs across shared drives.

What application level error or local database state is halting the Dropbox desktop client?

Dropbox application permissions on local configuration folders are corrupted or locked by OS administrative ACLs.
The local Dropbox SQLite metadata cache is corrupted, preventing file index synchronization.

Rebuilding System ACLs and Local Folder Ownership for Dropbox

Solution:

Root Cause: Access Control List (ACL) Permission Corruption

Dropbox requires explicit low-level filesystem access rights to read and write configuration files, build socket handles, and set NTFS reparse tags inside %LOCALAPPDATA%\Dropbox and %APPDATA%\Dropbox. If Windows permissions are modified during system migrations, domain policy updates, or user profile corruption, the Dropbox background worker service fails to initialize Smart Sync functions.

Diagnostic Verification:

Inspect local folder ownership and access permissions in PowerShell:

Get-Acl -Path "$env:LOCALAPPDATA\Dropbox" | Format-List

If the current user account lacks FullControl or if ownership is unassigned, permission errors will crash the sync daemon.

Step-by-Step Fix:

1Stop All Dropbox Executable Instances:

Run PowerShell as Administrator and force-terminate Dropbox:

taskkill /F /IM Dropbox.exe

2Reset Access Control Lists (ACLs) via Command Line:

Take ownership and reset NTFS inheritance recursively across all local Dropbox configuration directories:

icacls "$env:LOCALAPPDATA\Dropbox" /reset /T /C
icacls "$env:APPDATA\Dropbox" /reset /T /C
icacls "$env:USERPROFILE\Dropbox" /reset /T /C

3Grant Full Ownership to Active User Account:

Explicitly grant full control to the logged-in user:

icacls "$env:LOCALAPPDATA\Dropbox" /grant "$($env:USERNAME):(OI)(CI)F" /T
icacls "$env:APPDATA\Dropbox" /grant "$($env:USERNAME):(OI)(CI)F" /T

4Relaunch Application:

Start Dropbox normally to verify that configuration settings can now be written successfully.

Prevention & Long-Term Monitoring:

Do not execute manual takeown or permission resets on root user profiles without retaining recursive inheritance flags for app local data paths.

Performing an Advanced Clean Uninstallation and Database Rebuild

Solution:

Root Cause: Severe Local Metadata Index Corruption

When local SQLite indexes that track file states (filecache.dbx) become corrupt due to unexpected power losses or disk write failures, the Dropbox client cannot reconcile local placeholder states with remote cloud state manifests. The client hangs indefinitely during startup verification, causing Smart Sync indicators to fail across the entire system.

Diagnostic Verification:

Inspect the Dropbox crash log directory for database exception files:

Windows: %APPDATA%\Dropbox\logs\

macOS: ~/Library/Application Support/Dropbox/logs/

Check for log files recording DatabaseCorruptException or sqlite3.OperationalError.

Step-by-Step Fix:

1Perform Advanced Clean Uninstallation:

Download the official deployment package from Official Dropbox Knowledge Base to ensure you have the latest installer.

Uninstall Dropbox via Windows Settings or macOS Trash.

2Delete Residual Configuration and Database Folders:

Windows (PowerShell):

Remove-Item -Path "$env:LOCALAPPDATA\Dropbox" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:APPDATA\Dropbox" -Recurse -Force -ErrorAction SilentlyContinue

macOS (Terminal):

rm -rf ~/Library/Application\ Support/Dropbox
rm -rf ~/.dropbox

3Reinstall Dropbox with Default Smart Sync Options:

Run the newly downloaded installer, sign back in with your credentials, and select Smart Sync (Online-Only) when prompted during initial setup.

Prevention & Long-Term Monitoring:

Ensure systems are equipped with uninterruptible power supplies (UPS) or reliable battery management to avoid sudden write interruptions during database sync cycles.

Related Diagnostic Guides

Windows Update Error 0x80070002 Missing Files Diagnostic Guide

System Restore Failed 0x80070005 Antivirus Conflict Tree

Windows Photo Viewer Not Showing Thumbnails: Codec Diagnostic

Safe Mode Password Not Working With Microsoft Account Fix

Clipboard History Not Working Windows 11: Sync Service Tree

Subscribe to StepDiag

Embed Guide on Your Website