Resolving OneDrive sync conflicts and stuck files

OneDrive sync problems should be worked from the least destructive fix upward. Most issues resolve at step 1 or 2; jumping straight to a re-link throws away sync state unnecessarily and can take hours to rebuild on large libraries.

The reset ladder

• Step 1 — Pause and resume sync from the system tray icon. Fixes transient token problems.
• Step 2 — Restart the client: quit OneDrive fully, relaunch from Start. Clears a wedged upload queue.
• Step 3 — Targeted unstick: rename the conflicting file locally (append -local), let the cloud copy sync down, merge manually.
• Step 4 — Client reset: onedrive.exe /reset. Re-scans everything; allow 30+ minutes on large libraries.
• Step 5 — Re-link the account. Last resort — all selective-sync choices are lost.

Files that never finish syncing

Check the filename against the restricted set: names ending in a dot or space, and paths over 400 characters, upload forever without a useful error. PST files sync but generate massive delta churn — they belong on a mapped drive or in Shared Mailboxes, not OneDrive.

# Find paths that exceed the OneDrive limit under the user profileGet-ChildItem $env:OneDrive -Recurse |    Where-Object { $_.FullName.Length -gt 400 } |    Select-Object FullName, @{n='Length';e={$_.FullName.Length}} |    Sort-Object Length -Descending

When it is not the client

If multiple users report sync failures simultaneously, check the M365 service health dashboard before touching any endpoint — a service-side incident looks identical to a local problem from the user’s desk.