SharePoint OneDrive Sync Stuck on Processing Changes: What Site Owners Should Check

When the OneDrive sync client shows “Processing changes” for a SharePoint document library and never finishes, site owners face stalled workflows and frustrated users. This stuck state usually occurs because the sync client is overwhelmed by a large number of file changes, conflicting metadata updates, or a corrupted local sync cache. In this article, you will learn the specific causes behind this symptom and the exact steps site owners can take to resolve it without waiting for Microsoft support.

Why the Sync Client Gets Stuck on Processing Changes

The OneDrive sync client communicates with SharePoint by comparing file metadata between the local cache and the server. When this metadata comparison cannot complete, the client displays “Processing changes” indefinitely. The root cause is almost always one of these three scenarios:

Too Many File Changes at Once

If a site owner or automated process moves, renames, or edits hundreds of files in a short time, the sync client must process each change individually. The client queues these changes but may stall if the queue grows beyond 10,000 items. This is common after migrating files, restructuring folders, or running a bulk metadata update.

Corrupted Local Sync Cache

The sync client stores a local database of file metadata. If this database becomes corrupted due to a system crash, disk error, or abrupt shutdown, the client cannot reconcile its local state with SharePoint. The result is a permanent “Processing changes” state that persists even after restarting the client or the computer.

SharePoint Site Storage or Throttling Limits

ShareOnline applies throttling when a site exceeds its storage quota or when a user makes more than 5,000 file changes per hour. The sync client receives a delay signal from the server and enters a waiting loop. Site owners must check the site storage metrics in the SharePoint admin center to confirm this is not the issue.

Steps to Resolve Stuck Sync for Site Owners

Site owners should follow these steps in order. Each step addresses a different possible cause. Do not skip any step.

1. Pause and Resume Sync
   Open the OneDrive sync client by clicking the OneDrive cloud icon in the system tray. Select Help & Settings > Pause sync and choose 2 hours. After the pause period ends, the client will resume. This forces the client to re-evaluate the change queue and often clears a temporary backlog. If the stuck state returns, proceed to step 2.
2. Stop Sync for the Affected Library
   In the OneDrive sync client, click Help & Settings > Settings. Go to the Account tab. Under the SharePoint library that is stuck, click Stop sync. This removes the local folder but does not delete your files from SharePoint. After stopping sync, restart the OneDrive client and re-add the library by going to the SharePoint site and clicking Sync again. This creates a fresh local cache.
3. Clear the OneDrive Sync Cache
   If stopping sync does not help, clear the entire sync cache. Close OneDrive completely by right-clicking the cloud icon and selecting Exit. Press Windows Key + R, type %localappdata%\Microsoft\OneDrive\settings\Business1 and press Enter. Delete all files in this folder. Then restart OneDrive. This forces the client to rebuild its database from scratch. Note: this step requires the user to re-sync all libraries.
4. Check SharePoint Site Storage
   Go to the SharePoint admin center > Active sites. Select the site where the library is located. Click Settings and look at Storage limit. If the site is near or over its limit, increase the storage quota or remove unused files. After adjusting, wait 30 minutes for the change to propagate before retrying sync.
5. Review Throttling Status
   In the SharePoint admin center, go to Reports > Usage analytics. Look for the site in question and check the API calls metric. If the site shows more than 5,000 API calls per hour, throttling is active. Reduce the number of automated operations on the site. Common culprits are Power Automate flows, custom scripts, or bulk file uploads. After reducing activity, throttling lifts automatically within 24 hours.

If SharePoint Still Has Issues After the Main Fix

Sync Stuck on a Single Large File

A single file larger than 250 GB cannot sync. The client shows “Processing changes” while it repeatedly fails to upload or download the file. Check the library for files exceeding the limit. Use SharePoint’s file size column to sort by size. Remove or compress the oversized file. After removal, restart OneDrive and resume sync.

Sync Stuck After Renaming a Folder

Renaming a folder that contains thousands of files forces the sync client to reprocess every file path. This can cause a multi-hour stuck state. To avoid this in the future, rename folders only when they contain fewer than 100 files. If already stuck, stop sync for the library and re-add it (step 2 above).

Sync Stuck Due to File Name or Path Length

SharePoint and OneDrive support file paths up to 400 characters. Files with longer paths or names that include invalid characters like # % & { } \ cause the sync client to stall. Use the SharePoint Check Out feature to identify files with invalid names. Rename or move these files to a shorter path. Then restart the sync client.

Site Owner Sync Controls vs End User Sync Controls

Item	Site Owner Controls	End User Controls
Access location	SharePoint admin center > Active sites > Site settings	OneDrive sync client > Settings > Account tab
Storage limit	Can increase or reduce site storage quota	Cannot change storage; can only see used space
Sync blocking	Can block sync for entire site via tenant policy	Can stop sync for individual library only
File size limits	Cannot change 250 GB limit; must inform users	Cannot change limit; must avoid large files
Throttling visibility	Can see API usage in usage analytics	Cannot see throttling data

Site owners have access to storage and throttling controls that end users lack. When sync is stuck, start with the site-level checks before asking users to clear their cache.

You now know the three main causes of the stuck “Processing changes” state and the five steps to resolve it. Start by pausing sync, then stop sync for the affected library. If the problem persists, check the site storage quota in the SharePoint admin center. For recurring issues, reduce the number of automated file operations on the site to stay within the 5,000 changes per hour throttle limit.