How to Fix SharePoint OneDrive Sync Problems
Why SharePoint OneDrive Sync Breaks
I've seen this exact problem on hundreds of machines: you open File Explorer, click into your SharePoint OneDrive sync folder, and either files are stuck with a spinning blue circle, the sync icon in the system tray shows a red X, or , worst of all , your changes just silently never make it to the cloud. No helpful error message, no explanation. Just broken sync.
Here's the frustrating reality: SharePoint OneDrive sync errors don't happen because you did something wrong. The sync client (officially called the Microsoft OneDrive sync app) is juggling a huge number of moving parts, your local file system, the SharePoint Online tenant, Microsoft 365 authentication tokens, Windows credential caching, and sometimes even Group Policy settings your IT department put in place without telling you. Any one of those can fail on its own.
The most common root causes I see in the field:
- Authentication token expiration. SharePoint OneDrive sync relies on OAuth 2.0 tokens that silently refresh in the background. When your organization enforces Conditional Access policies or MFA, those tokens can expire mid-session and not renew cleanly. The sync client stalls rather than prompting you to log back in.
- File path length violations. SharePoint enforces a 400-character combined URL path limit. Windows NTFS supports 260 characters by default (though that's expandable). When a deeply nested folder gets synced, the full SharePoint URL can blow past the limit and the file gets flagged with error code
0x8007016Aor0x80071129. - Invalid file or folder names. SharePoint bans characters like
# % & * : < > ? / \ { | } ~and reserved names likeCON,PRN,AUX,NUL. If a file contains any of these, it silently fails to upload. - File locked by another process. Office applications, Outlook attachments, antivirus scanners, and backup software all take exclusive locks on files. OneDrive can't sync a file while it's locked.
- Corrupted sync database. OneDrive stores its sync state in a local SQLite database under
%LocalAppData%\Microsoft\OneDrive\settings. If that database gets corrupted, usually from an improper shutdown or Windows update mid-sync, the entire sync process can enter a broken state. - SharePoint library threshold limits. SharePoint Online has a list view threshold of 5,000 items. Libraries with more than 5,000 files in a single folder can cause sync failures even if each individual file is fine.
I know this is frustrating, especially when it blocks your work or when you can't tell whether your colleagues are seeing the latest version of a document. The good news is that 80% of SharePoint OneDrive sync issues resolve with the same set of fixes, and this guide walks you through every one of them.
The Quick Fix, Try This First
Before spending 30 minutes in the registry, try this. It resolves the majority of SharePoint OneDrive sync problems in under two minutes and doesn't require admin rights.
Right-click the OneDrive cloud icon in your system tray (bottom-right corner of your taskbar, you may need to click the up-arrow to expand hidden icons). Select Help & Settings, then click Quit OneDrive. Confirm when prompted.
Wait ten seconds. Then reopen OneDrive from the Start menu, search for "OneDrive" and click the app. It will re-initialize, re-establish your authentication session, and re-scan your sync queue. Watch the icon: if it shows a steady cloud with a checkmark within 60–90 seconds, you're done.
If you see a red X or a spinning icon that doesn't clear, click the OneDrive icon and look for any sync errors listed in the activity center, the pop-up panel that appears when you click the icon. Each error has a small arrow icon on the right. Click it to see exactly which file is stuck and what error code is shown. Note that error code down, you'll need it for the steps below.
The single most effective next step if a plain restart doesn't work: sign out and sign back in to OneDrive. Go to Help & Settings → Settings → Account tab → Unlink this PC. This disconnects OneDrive without deleting your local files. Then sign back in with your Microsoft 365 account. OneDrive re-syncs from scratch. I've seen this alone fix stubborn sync loops that persisted for weeks.
The first thing I always do is look at what's actually stuck. Open your OneDrive activity center by clicking the cloud icon in the system tray. If you see a "sync paused" message, click Resume syncing first, sometimes Windows Controlled Folder Access, a battery saver mode, or a VPN reconnect event causes OneDrive to pause itself without telling you.
If there are active sync errors, click the "X errors" or "Upload blocked" link. For each flagged file, OneDrive shows one of these common error codes:
0x8007016A, Cloud file provider is not running (usually a Windows service issue)0x80071129, File path too long or invalid characters0x8004de44, Authentication problem, your sign-in session expired0x80c8043e, SharePoint library is full or throttled0x8004de86, Sync paused because this account is not allowed by policy
For files with path errors (0x80071129), you need to rename or move them locally. Navigate to the file in File Explorer, right-click, and rename it, remove any special characters from the name. Shorten deeply nested folder paths by moving folders higher up in the hierarchy.
For authentication errors (0x8004de44), go to Settings → Account → Unlink this PC and re-sign in. If your organization uses Azure AD / Entra ID Conditional Access, you may need to complete an MFA challenge on your phone during the re-authentication.
If the error clears and the file starts syncing, you'll see it move to the activity list with a green checkmark. If it's still stuck after you've addressed the error, move to Step 2.
A full client reset clears the local sync database and forces OneDrive to re-index everything. This is safe, it doesn't delete any of your files locally or in the cloud. It just wipes the cached sync state, which is exactly what you want when things are stuck.
First, quit OneDrive completely (right-click the tray icon → Help & Settings → Quit OneDrive).
Then open a Run dialog (Win + R) and paste this command:
%localappdata%\Microsoft\OneDrive\onedrive.exe /resetHit Enter. You'll see the OneDrive icon briefly appear in the tray, then disappear. That's normal, it's resetting. Wait about 60 seconds.
If OneDrive doesn't restart automatically after two minutes, manually relaunch it:
%localappdata%\Microsoft\OneDrive\onedrive.exeOneDrive will open the sign-in screen if the reset was complete. Sign in with your Microsoft 365 account. If you're domain-joined and using SSO, it may sign you in automatically. The first sync after a reset can take anywhere from a few minutes to several hours depending on library size, this is expected.
You should see the OneDrive icon show a steady blue circular-arrow animation (syncing) rather than a red X. Once it settles to a white cloud with a checkmark (or blue cloud for personal accounts), sync has resumed successfully.
Sometimes the problem isn't OneDrive itself, it's the specific SharePoint library connection that's broken. This happens most often after a SharePoint site migration, a URL change, a tenant rename, or after IT reconfigures site permissions.
Open File Explorer and look in the left panel for your SharePoint library under "OneDrive – [Organization Name]". Right-click the library folder and check if you see a "Stop syncing" option. If you do, click it. This disconnects only that library, your other synced folders remain unaffected.
Now go to the SharePoint Online site in your browser. Navigate to the Documents library (or whichever library was failing). Click the Sync button in the top toolbar, it may be under the ... menu depending on your SharePoint view. Your browser will prompt you to open Microsoft OneDrive. Allow it.
OneDrive will now set up a fresh sync relationship with that library. You'll see it appear in File Explorer within about 30 seconds. The initial sync downloads all files in the library, again, existing local copies are kept and matched, so you won't get duplicates.
One thing to watch for: if the Sync button is grayed out in SharePoint, your IT admin has disabled sync for that library via SharePoint admin center policy. In that case, you'll need to contact your IT department, there's nothing you can fix on the client side.
SharePoint OneDrive sync relies on Windows Credential Manager to store your Microsoft 365 authentication tokens. When those credentials get stale or corrupted, especially after a password change, MFA method update, or an Azure AD conditional access policy change, sync breaks silently.
Open Control Panel → User Accounts → Credential Manager. Click Windows Credentials tab. Look for any entries starting with:
MicrosoftOffice16_DataOneDrive Cached CredentialMicrosoftOffice15Office 365 Credential
Remove every one of these by clicking the entry and then clicking Remove. Don't worry, this forces a fresh sign-in rather than deleting anything important.
After clearing the credentials, relaunch OneDrive. It will prompt you to sign in. Enter your Microsoft 365 email address and password. If your organization has MFA enabled, complete that prompt on your phone or authenticator app. Once authenticated, OneDrive writes fresh credential tokens to Credential Manager and sync resumes.
If you're on a domain-joined machine with SSO via Azure AD Hybrid Join or Windows Hello for Business, you may not get a prompt at all, the system authenticates automatically using your Windows session token. In that case, just watch the OneDrive icon to confirm sync resumes.
This step also fixes the common complaint of "OneDrive keeps asking me to sign in", stale credentials in Credential Manager are almost always the culprit.
This sounds basic, but it matters more than most people realize. The OneDrive sync client updates independently of Windows Update, and running an outdated version against a newer SharePoint Online backend causes all kinds of subtle sync failures, including issues with Files On-Demand, selective sync, and real-time co-authoring.
Right-click the OneDrive tray icon → Help & Settings → About Microsoft OneDrive. Note the version number shown. As of early 2026, the current production ring version is in the 24.x branch. If you're on anything below 23.x, an update is overdue.
To force an update check, open the OneDrive settings (Help & Settings → Settings) and go to the About tab. Click Check for updates. OneDrive will download and install the latest version silently, then restart itself.
If you're in an enterprise environment where IT controls OneDrive updates via the OneDrive update ring settings (set via Group Policy under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive), you may be locked to an older version intentionally. Check with IT before attempting a manual update, they may have a deployment scheduled.
Also verify that Windows is current. Open Settings → Windows Update and install any pending updates, then restart. Several OneDrive sync bugs, including the 0x8007016A "Cloud file provider not running" error, were fixed in specific Windows cumulative updates. KB5012170 and KB5014697 are two that directly addressed OneDrive Files On-Demand stability issues.
Advanced Troubleshooting
If the steps above haven't resolved your SharePoint OneDrive sync problem, you're dealing with something deeper, usually a policy conflict, a corrupted system component, or an enterprise configuration issue. Here's how to dig further.
Check Event Viewer for OneDrive Sync Errors
Open Event Viewer (Win + R, type eventvwr.msc). Expand Applications and Services Logs → Microsoft → Windows → OneDrive. Look for Warning or Error entries. Key Event IDs to look for:
- Event ID 1000, Application crash. If OneDrive is crashing silently, this tells you the faulting module.
- Event ID 4625, Logon failure. If your Windows authentication is failing for the OneDrive background service, this surfaces here.
Also check Windows Logs → Application and filter by Source = "OneDrive". Error messages here often give you the exact internal error code that the tray icon glosses over.
Group Policy Conflicts
In enterprise environments, IT can block personal OneDrive accounts, restrict which SharePoint tenants can be synced, or enforce file type restrictions, all via Group Policy. Open a Run dialog and type gpedit.msc (requires admin rights or a domain-joined machine with appropriate rights). Navigate to:
Computer Configuration → Administrative Templates → OneDriveCheck these specific policies:
- Prevent users from syncing personal OneDrive accounts, if enabled, blocks all personal account sync
- Allow syncing OneDrive accounts for only specific organizations, set to your tenant ID; if set incorrectly, blocks sync entirely
- Block syncing of specific file types, may be blocking file extensions you're trying to sync
If any of these are misconfigured, contact your IT department, you shouldn't change Group Policy settings on a domain-joined machine without authorization.
Registry Check for Tenant Allow-List
On domain-joined machines, IT sometimes sets a tenant allow-list registry key. Open Registry Editor (regedit.exe) and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive\AllowTenantListIf this key exists and your organization's Azure AD Tenant ID is not listed, OneDrive will refuse to sync SharePoint libraries from that tenant. Your IT admin needs to add the correct GUID here.
OneDrive Diagnostic Logs
OneDrive stores detailed sync logs at %LocalAppData%\Microsoft\OneDrive\logs. The most useful file is SyncEngine-20xx-xx-xx.*.log, sorted by date. Open the latest one in Notepad and search for "error" or "failed". These logs are verbose but reveal exactly which file operation triggered the failure and what the underlying HRESULT was.
Files On-Demand Reregistration
The error 0x8007016A specifically means the Windows StorageService that handles Files On-Demand placeholders is not running properly. Fix it by running this in an elevated PowerShell window:
Get-AppxPackage -Name "Microsoft.Windows.StorageSense" | Reset-AppxPackageThen restart OneDrive. If that doesn't work, you may need to re-enable the OneDrive Files On-Demand feature entirely:
fsutil behavior set SymlinkEvaluation R2R:1 R2L:1 L2R:1 L2L:1If you've completed all the steps above and sync is still broken, especially if you're seeing errors like 0x8004de86 (policy block), persistent 0x8007016A after a clean reset, or sync failures only affecting specific users in your organization, this is likely a tenant-level or Azure AD configuration issue that requires Microsoft support to investigate on the backend. Collect your OneDrive diagnostic logs first (Help & Settings → Help → Send Feedback, this bundles logs automatically), then open a ticket at Microsoft Support. Include your tenant ID, the specific error codes, and the time window when failures occurred, this lets them pull server-side telemetry that matches your session.
Prevention & Best Practices
Once you've fixed the immediate SharePoint OneDrive sync problem, a few proactive habits will stop it from coming back. I've watched organizations go from constant sync tickets to almost zero by making these changes.
Keep file and folder names clean from day one. The biggest source of ongoing sync errors is files created with special characters, usually copied from emails, downloaded with auto-generated names, or created by third-party applications. Train your team: no # % & * : < > ? \ | ~ characters in file names, no file names longer than 200 characters, no folders nested more than 10 levels deep. SharePoint's combined URL limit of 400 characters fills up faster than most people expect once you add the site URL prefix.
Keep your OneDrive client on the Production update ring. In enterprise environments, IT often sets OneDrive to "Deferred" or "Slow" ring to avoid pushing updates that haven't been tested. That's sensible, but make sure the ring is actually configured and not just forgotten. Machines on no update ring at all can fall years behind the current client version, which causes compatibility issues with newer SharePoint features. Check the current ring setting in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive\GPOSetUpdateRing.
Monitor the Windows Credential Manager periodically. After any password change or MFA method update in Azure AD, old cached tokens in Credential Manager will eventually expire and cause sync to fail. Make it a habit, after any account change, proactively clear MicrosoftOffice16_Data* entries from Credential Manager and let OneDrive re-authenticate cleanly rather than waiting for a sync failure to surface it.
Don't exceed 300,000 files per SharePoint library. Microsoft officially supports up to 30 million items in a SharePoint library, but OneDrive sync has practical performance limits. Libraries with more than 300,000 files can cause the sync client to stall during initial indexing. Split oversized libraries into multiple document libraries if your organization is approaching that threshold.
- Set a calendar reminder every 90 days to check your OneDrive client version and update if needed
- Enable "Files On-Demand" to reduce local disk usage and minimize locked-file conflicts during sync
- After any password or MFA change, clear Microsoft credentials in Credential Manager before OneDrive breaks
- Audit your SharePoint library file names quarterly, a simple PowerShell script can flag files with invalid characters before they cause problems
Frequently Asked Questions
Why does OneDrive keep showing a red X even after I restart it?
A persistent red X after a restart almost always means one of two things: either a specific file in your sync queue is permanently blocked (invalid name, path too long, or locked by another app), or your authentication token has expired and OneDrive can't silently renew it. Click the red X icon and look at the error list, it will tell you which file is stuck. If there's no specific file flagged, go to Settings → Account → Unlink this PC and re-sign in. That clears any expired auth tokens and usually resolves the red X within two minutes.
Will resetting OneDrive delete my files?
No, running onedrive.exe /reset does not delete any files, locally or in SharePoint. It only clears the local sync state database, which is the record of what OneDrive thinks has been synced. After a reset, OneDrive re-scans both your local folder and the cloud, then re-matches them. Files that were already successfully synced before the reset remain safe. The only time you need to worry is if you have local files that were never synced, make sure those have uploaded before you do a full Unlink this PC action.
Why can I see files in SharePoint Online in the browser but they don't show up in File Explorer?
This usually means the selective sync (Choose Folders) setting has excluded that library or subfolder from your local sync. Right-click the OneDrive tray icon, go to Settings → Account → Choose folders, and make sure the folder in question is checked. If it's grayed out, it may have exceeded the sync file count limit or your IT department has restricted sync for that library. Another possibility: the SharePoint library was added after you first set up OneDrive, go to the library in SharePoint Online and click the Sync button to add it to your local sync.
My OneDrive says "Processing changes" for hours, is something wrong?
"Processing changes" for extended periods usually means OneDrive is indexing a very large library for the first time, or it's caught in a loop trying to sync a file it can't upload. Click the OneDrive icon and look at the activity center, if it shows a specific count of files being processed and that number is decreasing, it's genuinely working and just slow (large libraries with thousands of files can take hours on first sync). If the file count isn't changing, or if you see the same file name repeatedly in the activity log, that file is likely stuck. Identify it from the error list and rename or move it to unblock the queue.
Can I sync SharePoint OneDrive on two different computers at the same time?
Yes, OneDrive is designed to sync the same SharePoint library across multiple devices simultaneously. Each device maintains its own local copy and syncs changes through SharePoint Online as the middle layer. However, simultaneous edits to the same file from two machines will create a version conflict. OneDrive handles this by creating a "conflicted copy" with your computer name in the filename rather than overwriting the other person's version. To avoid conflicts, use Office 365 co-authoring in the browser when multiple people need to edit the same document at once instead of working from local copies.
Error 0x8004de86 keeps appearing, what does it mean?
Error 0x8004de86 means your account has been blocked from syncing by an organization policy, specifically the "Allow syncing OneDrive accounts for only specific organizations" Group Policy setting. OneDrive is seeing your account as belonging to a tenant that isn't on the approved list. This is almost always an IT configuration problem, not a user error. If you're on a corporate device, raise a ticket with your IT helpdesk and mention error 0x8004de86, they'll know exactly what to check. If you're an admin yourself, verify the tenant GUID listed under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive\AllowTenantList matches your organization's Azure AD Tenant ID.