OneDrive: sync stuck — paused or a red X on the icon

Hi, it's BlueByte. Your OneDrive stops syncing: the icon shows a red circle with a white cross, or it sits on Paused, and edits you make locally never reach the cloud. Nothing is deleted — OneDrive has stopped the sync loop and is waiting. We'll walk through what the icon states mean, why sync stalls, how to read the activity list to find the reason, restart or reset the client to clear it, and how to keep it running.

What a paused sync or a red X on the icon means

OneDrive shows its health in the tray (Windows) or menu-bar (Mac) icon. A red circle with a white cross means a sync error — one or more files can't sync. A pause symbol means sync is paused, by you or automatically (a metered network, battery saver). A grey icon with "Sign in" means the account isn't connected. None of these is data loss: your files are intact both locally and in the cloud; only the link between them is stalled.

Why OneDrive stops syncing

A stalled sync comes from one of a few causes:

• Sync was paused — by you, or automatically on a metered or low-battery connection.
• The account signed out or its token expired, so the client can't reach the service.
• You're over quota — Microsoft is explicit that if you exceed your storage you can't upload, edit, or sync new files.
• A file it can't sync — a name with an unsupported character, a path over the length limit, or a file locked open by another program — stalls the queue behind it.
• A wedged client — the OneDrive process is running but stuck, common after a network drop or an update.

Read the icon and the activity list before you touch anything

Don't reset first — look at what OneDrive is telling you. Select the OneDrive icon to open the activity centre; a sync error lists the exact files it's stuck on and why. Check the process is even running:

Get-Process OneDrive -ErrorAction SilentlyContinue

No output means OneDrive isn't running — start it from the Start menu. If it's running but the icon is red, note whether the error names specific files (a quota or bad-name problem) or everything (a connection or client problem). That split decides your fix.

Restart OneDrive — the fix that clears most stalls

For a wedged client, quit and relaunch it. Close it, then start it again:

Stop-Process -Name OneDrive -Force
Start-Process "$env:LOCALAPPDATA\Microsoft\OneDrive\onedrive.exe"

Give it a minute; the icon should go from red or paused to the plain "up to date" cloud. A restart re-establishes the connection and re-runs the queue, which clears most stalls left by a network blip or an update.

Reset OneDrive when a restart isn't enough

If a restart doesn't clear it, reset the sync connections. This is Microsoft's documented step, and it does not delete your files — it disconnects and rebuilds the sync links only. Press Win + R and run the path that matches your install:

%localappdata%\Microsoft\OneDrive\onedrive.exe /reset

If that path reports the file isn't found, use the Program Files locations instead:

C:\Program Files\Microsoft OneDrive\onedrive.exe /reset
C:\Program Files (x86)\Microsoft OneDrive\onedrive.exe /reset

The icon disappears for a minute or two while OneDrive rebuilds, then returns and runs a full sync. If it doesn't reappear on its own, start OneDrive again from the Start menu. After a reset you may need to re-choose which folders to sync.

When it's quota or a bad file name, not a stall

If the activity list names specific files, a client reset won't help — fix the cause. For over quota, free space or reduce what you sync; you can't sync new files until you're back under the limit. For a file OneDrive won't accept, rename it to drop unsupported characters (" * : < > ? / \ |) or shorten an over-long path, then let it re-queue. One rejected file can hold up everything behind it, so clearing it often unblocks the whole queue.

A real case: sync paused after a network blip

You're on a laptop that dropped Wi-Fi on a train. Back online, OneDrive shows the red X and "We can't sync right now." The activity centre lists no specific file, so it's the client, not a file. You run Stop-Process -Name OneDrive -Force and relaunch it — still red. You reset with %localappdata%\Microsoft\OneDrive\onedrive.exe /reset; the icon vanishes, rebuilds over about a minute, and comes back running a full sync. Within a few minutes it settles on the plain "up to date" cloud, and the edits you made offline upload. No file was lost — the reset only rebuilt the connection.

Confirm sync is caught up

Watch the icon settle to the "up to date" state — a plain cloud, no red, no pause. Open the activity centre and confirm it reads that everything is synced, with no error list. As a direct check, edit a small file in the synced folder and confirm the change appears on onedrive.com within a moment — that proves the loop is live end to end.

Keep sync running, and how this differs from "path too long"

Keep OneDrive updated, stay under quota, and don't force-quit it — let it close cleanly so it doesn't come back wedged. If you sync on metered connections, check that pause-on-metered isn't stopping you unexpectedly. And note the difference from a "path too long" failure: that error names one file whose full path exceeds the limit and blocks only that file, and the fix is to shorten the path, not to reset the client. A general red-X stall with no named file is the client or the connection, and a reset clears that; a single stubborn file is a per-file problem you fix on the file itself.