T The Triage ManualTechnical Guides for IT Emergencies
P3 · Microsoft 365 & Collaboration

OneDrive Sync Errors — Missing Files, Duplicate Conflict Copies, and Stuck Uploads (Windows / macOS)

OneDrive for Business and personal OneDrive sync clients enter broken sync states manifesting as failed uploads, missing files, conflict-suffix duplicates, or persistent 'Syncing' badges that never resolve. Root causes span invalid file/path naming (SharePoint naming rules), expired authentication tokens, local cache/database corruption, storage quota exhaustion, and network or proxy interference breaking HTTPS to Microsoft endpoints. Resolution follows a layered approach: identify the specific error class via the activity centre and diagnostic logs, then apply the targeted fix (rename, re-link, quota clear, or client reset) in order of least disruption. A full client reset clears the local sync database and forces a full rescan; copy local-only files to a safe location before running it.

Indicators

Likely causes

Diagnostic steps

  1. Click the OneDrive system tray icon and open the activity centre. Review each file-level error message. Note exact error text, filenames flagged, and whether the issue is account-wide or isolated to specific files.
    Determines whether the failure is file-specific (naming/size/type) or affects the entire sync relationship (auth, network, or client corruption) — directs which fix path to follow.
  2. Verify OneDrive storage quota: navigate to https://onedrive.live.com (personal) or Microsoft 365 portal > OneDrive settings > Storage. Confirm the account is not at or near its quota limit.
    Rules out storage exhaustion, which presents identically to other sync failures but requires a completely different remediation.
  3. Inspect flagged file and folder names for naming violations: invalid characters (* " : < > ? / \ |), reserved Windows names (CON, PRN, AUX, NUL, COM1–COM9, LPT1–LPT9), leading/trailing spaces or periods, and total path length exceeding 400 characters.
    Identifies whether specific files are blocked by SharePoint/OneDrive naming restrictions — must be renamed before sync can proceed.
  4. Verify account sign-in: right-click the OneDrive tray icon > Settings > Account tab. Confirm the signed-in account email matches the expected account. Check for a warning icon indicating an authentication error.
    Confirms whether an expired or corrupt authentication token or an account mismatch is causing the sync failure.
  5. Review OneDrive sync diagnostic logs: right-click the OneDrive tray icon, hold Ctrl, click 'Get diagnostics' (Windows) to open the SaRA log bundle, or manually inspect %localappdata%\Microsoft\OneDrive\logs\SyncDiagnostics.log and the latest *.odl log files.
    Provides detailed error codes and event sequences from the sync engine to pinpoint the exact failure mode.
  6. Test network connectivity to OneDrive service endpoints in PowerShell: Personal: `Test-NetConnection -ComputerName onedrive.live.com -Port 443` Business: `Test-NetConnection -ComputerName <tenant>-my.sharepoint.com -Port 443` Also confirm no proxy or SSL inspection is intercepting the connection.
    Determines whether network or proxy interference is preventing the sync client from reaching Microsoft's servers.
  7. Check whether stuck-uploading files are locked by another process: open Task Manager (Ctrl+Shift+Esc) > Resource Monitor > CPU tab > Associated Handles, search for the filename to identify the locking process. Alternatively, use Process Explorer (Sysinternals) Find Handle.
    Identifies file locks held by Office applications or other processes that prevent OneDrive from completing the upload.

Resolution path

Prevention

Tools

References

OneDriveOneDrive for Businesssync errormissing filesduplicate filesconflict filesstuck uploadMicrosoft 365SharePointfile synccloud storageWindowsmacOSnaming violationquotaclient resetauthenticationKnown Folder MoveKFM