OneDrive 'Processing changes' forever — break the sync loop

I had a client email me last March in actual tears. She'd been writing a wedding speech for her brother in a Word doc on her laptop, last edited Monday night. The wedding was Saturday. By Wednesday morning the OneDrive icon was still spinning, "Processing changes," and she didn't know if her latest version was saved to the cloud or living only on a laptop she was about to leave on a plane to Toronto.

OneDrive's most maddening failure mode. The two little circling arrows in the system tray, the tooltip that has read "Processing changes" for somewhere between forty minutes and four days. Nothing's uploading. Nothing's downloading. The world is on pause and you have a meeting in eleven minutes.

Good news: "Processing changes" almost always means the sync engine has hit one specific file it can't reconcile. Find that file. Deal with it. The rest of the queue flushes in seconds.

What "Processing changes" actually means

OneDrive maintains a queue of operations. Upload this file, download that one, rename, delete, hash-check. "Processing changes" means the engine is iterating through that queue. If the queue is small, you see the message for two seconds and never think about it. If the queue gets stuck on a single problem operation, you see the message forever, because OneDrive's retry logic loops on the failed item without moving on to the next one.

So the workflow is: identify the blocker, remove or fix it, let the queue drain. That's it.

Step 1: Open the Activity Center

Click the OneDrive cloud icon in the system tray. The pane that opens is the Activity Center. Status at the top, file list below it.

What you're looking for:

• A file with a red circle and an X. Sync error.
• A file with a yellow triangle. Warning, often "filename contains invalid characters" or "file in use."
• A file repeatedly retrying with the same name. That's your culprit.

Hover over any file with an error and OneDrive often gives you a one-line explanation. Read it before doing anything else. It tells you which fix from the rest of this article applies.

If the Activity Center shows no errors at all but the icon is still spinning, scroll all the way to the bottom. Sometimes the failing file isn't flagged but is sitting in the queue anyway. Click "View online" on a file to compare cloud and local versions.

Step 2: Common blockers and their fixes

Restrictive characters in filenames

OneDrive (and SharePoint underneath, which is what's really running the show) refuses to sync files whose names contain any of: < > : " / \ | ? *. Plus a few oddballs like ~ at the start, leading or trailing spaces, and the names CON, PRN, AUX, NUL, COM0-9, LPT0-9 (Windows reserved device names that nobody remembers).

If you renamed something on a Mac to "Q1: Forecast.xlsx" and then tried to sync, that colon is the problem. Same goes for paths copy-pasted from web pages where the colon turned into a smart quote without you noticing.

Fix: find the file in Explorer and rename it. Letters, numbers, hyphens, underscores, spaces. Boring works. The next sync cycle picks it up.

Files over 250 GB or paths over 400 characters

Single-file size limit for OneDrive sync is currently 250 GB. Most users will never hit that. Video editors and database admins sometimes do.

Path length is the more common one. If your file is at:

C:\Users\YourName\OneDrive - Acme Corp\Projects\2026\Clients\Big Client Inc\Phase Three Documentation\Subfolder\Sub-subfolder\Final Final v3 (with comments from legal)\my document.docx

you can blow past 400 characters easily once the OneDrive root path is added in. SharePoint's hard limit is around 400 characters total. OneDrive may queue the file forever rather than tell you why. Useful, that.

Fix: shorten folder names higher in the tree, or move the file closer to the root. Sync engine reconciles within minutes.

A .lock file from another app

Some apps drop a .lock companion file next to a document while the app's open. Adobe InDesign does this. AutoCAD does this. Excel with shared workbooks does this. Certain CAD tools do it. OneDrive sometimes refuses to sync .lock files, or syncs them and then re-syncs them every time the parent app touches them. Infinite loop.

Look for files named like ~$document.docx, document.lock, .~document.indd. If the parent application is closed and the lock file is still there, the parent crashed. Delete the lock file. Sync resumes.

A file that's currently open

OneDrive can't upload a file that has an exclusive lock from a running application. If you've got Excel open with the file in question, OneDrive will show "Processing" until you close Excel. Close the app, watch the icon. Usually clears within 30 seconds.

Blocked file types per tenant policy

Some Microsoft 365 tenants block specific extensions from sync. .exe, .bat, .ps1, .dll, sometimes anything executable at all. If your queue is stuck on a .exe you copied to a synced folder, OneDrive will neither sync it nor tell you why. The tenant admin sees it. You don't.

Fix: move the file out of the synced folder, or zip it. Ask your IT team for the blocked extension list if you suspect this is happening.

Step 3: Restart the sync engine

If you can't pin down a single blocker, restart OneDrive cleanly. More invasive than a normal "Quit OneDrive" right-click, because the standard quit sometimes leaves background workers running in the corner.

Open PowerShell or Command Prompt and run:

taskkill /f /im OneDrive.exe

Then relaunch:

%localappdata%\Microsoft\OneDrive\onedrive.exe

Roughly 30% of "stuck forever" cases clear with this alone. The sync engine restarts, re-reads its queue, and discovers that whatever it was hung on is no longer relevant.

Step 4: Unlink and re-link the account

If the restart didn't do it, your local sync metadata is corrupt. Unlinking does NOT delete your files. It just disconnects this device from your OneDrive cloud account.

1. Click the OneDrive icon, then the gear icon, then Settings.
2. Account tab.
3. Unlink this PC.

OneDrive stops syncing. Your local files stay exactly where they are.

To re-link:

1. The OneDrive setup window appears (or click the cloud icon and sign in again).
2. Sign in with the same account.
3. When asked for the OneDrive folder location, point at the existing folder you already have. OneDrive will scan it and merge with the cloud rather than re-downloading everything from scratch.

This rebuilds the local sync database. The "Processing changes" loop is broken because the database that was looping no longer exists.

Step 5: The reset command (when nothing else works)

This is the nuclear option. It destroys the local sync state entirely and re-syncs from the cloud. Your cloud files are untouched. Anything you'd queued for upload but not yet uploaded may be lost. So.

Open Run (Win+R) and paste:

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

Hit Enter. The icon disappears for one to two minutes, then reappears. Sign in if prompted.

Before doing this, make sure:

• Anything you've edited locally in the past few hours is also saved somewhere safe. A copy in Documents. An email to yourself. Whatever.
• You note which folders you had set as "Always keep on this device." The reset removes that designation and you'll have to reapply.

If /reset doesn't return your icon within 5 minutes, manually relaunch OneDrive from the path above.

"Free up space" as a recovery tactic

A counterintuitive trick. If a single folder's sync is stuck, right-click the folder in Explorer and pick Free up space. This converts every file in the folder to online-only (small cloud icon, no local copy). The next time you open one, it downloads on demand.

Why this helps: it forces OneDrive to re-evaluate the folder's entire state. Often clears whatever ghost reference was making one file impossible to process. Once the folder is online-only and quiet, you can right-click again and pick Always keep on this device to bring everything back down. The new download path bypasses the corrupted queue.

This is also the right move if you simply have too many files locally and you're running out of disk. OneDrive sometimes processes slowly or stalls when free space drops below about 10 GB. That number isn't documented anywhere as far as I can tell, but I've seen it consistently across about a dozen client laptops.

Step 6: Check the OneDrive sync logs

If you want to know exactly which file is hanging, without guessing, OneDrive writes detailed logs to:

%localappdata%\Microsoft\OneDrive\logs\Personal
%localappdata%\Microsoft\OneDrive\logs\Business1

(Business2, Business3, etc. if you have multiple work accounts. Yes, people do.)

Open the most recent .odl log in Notepad. They're partially obfuscated for privacy reasons but you can usually spot the failing file path in the noise. Search for "error", "fail", or "blocked".

For a more readable view, Microsoft puts a OneDriveLogParser script on GitHub that decodes the .odl format. For most people the raw log search is enough.

Symptoms vs. causes cheatsheet

Symptom	Likely cause	First fix
Spins for hours on one specific filename	Restricted character or excess path length	Rename or move
Spins after copying many files at once	Queue overload, normal	Wait, then restart if over 2 hrs
Spins, no file shown in Activity Center	Corrupted sync database	Unlink/re-link
Spins immediately after a Windows update	Auth token expired	Sign out, sign back in
Spins on a .lock or ~$ file	Parent app crashed	Delete lock file
Spins on a file you can't find locally	Cloud-only file with metadata mismatch	Free up space, then re-pin
Spins and CPU usage is high	OneDrive scanning loop	/reset

So, the order of operations

When OneDrive sticks on "Processing changes":

1. Open the Activity Center and look for any flagged file. That's your blocker about 60% of the time.
2. Check filenames for < > : " / \ | ? *, leading/trailing spaces, or reserved Windows names.
3. Check for paths over 400 characters or folders nested ten levels deep.
4. Close any application that has an open file in the synced folder.
5. Kill OneDrive with taskkill /f /im OneDrive.exe and relaunch.
6. If that fails, unlink and re-link from Settings, Account.
7. If still stuck, run %localappdata%\Microsoft\OneDrive\onedrive.exe /reset as a last resort.

Resist the urge to delete the OneDrive folder. Resist the urge to sign out of Windows entirely. Both of those will lose data. The fixes above are recoverable. The dramatic ones are not.

(My client with the wedding speech, by the way? Restricted character. She'd put a slash in the filename to mark it as "draft 2/3." Renamed it, the queue cleared in eleven seconds, and the speech made it to the cloud. Toast went well, I'm told.)