SharePoint Files Not Syncing with OneDrive: Fix Missing Files and Sync Errors

A SharePoint document library opens normally in a browser, but folders are missing on a Windows PC. Other users can see newly edited documents online while your local copies stay unchanged. Or the OneDrive cloud icon displays “Sync pending,” “Processing changes,” or a red X next to the SharePoint library. These symptoms can have very different causes: wrong account, missing library permissions, disabled offline availability, excessive path length, unsupported file names, client configuration or cloud-service connectivity.

SharePoint libraries commonly synchronize through the OneDrive sync client, but they are not identical to an individual’s personal OneDrive files. This guide explains how to isolate browser access versus local syncing, repair a stuck library without deleting files, review Microsoft 365 policy controls and choose between Sync and Add shortcut to OneDrive. All actions prioritize preservation of unsynced local changes.

Safety first: Before unlinking accounts, stopping a library’s sync, resetting the client or deleting folders, identify any files marked pending or edited only locally. Copy those unsynced items to a separate folder outside the active sync root, then verify the originals are present online before removing local data.

Quick diagnostic table

Step 1: Verify the file exists in SharePoint online

Open Microsoft 365 with the work or school account assigned to the SharePoint site. Navigate to the site and the exact document library, then find one affected file. Record its path and Modified date. If the document is missing in the browser too, do not reset OneDrive yet: investigate library permissions, deletion, movement, views, version history or server-side workflow.

Microsoft’s Fix SharePoint Online sync problems begins by checking access to the SharePoint library. It also explains that if Sync is unavailable or the library-selection dialog is unexpected, the site may not be configured for offline synchronization and the owner should review Offline Client Availability.

Step 2: Confirm you’re using OneDrive for work or school

On Windows, inspect the OneDrive icon near the clock; organizations commonly use a blue cloud icon for work/school accounts. Select it to view recent sync errors. Open OneDrive Settings → Account and confirm the signed-in organization’s identity and the expected SharePoint library. A second personal Microsoft account may coexist, so do not confuse the personal OneDrive folder with the employer’s SharePoint library.

A user signed into the wrong tenant may find online file links but lack sync access. Resolve identity and permission issues through the company account rather than creating a personal workaround.

Step 3: Read the exact sync error

1. Click the OneDrive cloud icon in the Windows notification area.
2. Open any displayed problem or View sync problems entry.
3. Record the file name, library, path and message.
4. Avoid bulk renaming files before identifying the pattern.
5. Resolve one representative file, wait for sync to update, and then retest the remaining files.

A red X might mean one unsupported file name, while the rest of the library is healthy. Conversely, one large library could prevent the queue from clearing. A targeted fix is safer than unlinking every account.

Step 4: Check file names and path length

SharePoint and OneDrive have restrictions on file names, reserved names and total paths. Microsoft’s SharePoint service limits document a 400-character decoded path limit for OneDrive and SharePoint in Microsoft 365. A deeply nested departmental folder path can hit that limit unexpectedly even when an individual file name is short.

• Shorten excessively long folder and file names using an approved library change process.
• Review characters such as ", *, :, <, >, ?, /, \ and | that are not valid in Windows paths.
• Check for special reserved file or folder names and organization-specific restrictions.
• Avoid renaming a synced root folder directly in File Explorer after the relationship is created.
• If many files are affected, test a controlled subset in a separate pilot library before performing bulk changes.

Microsoft’s troubleshoot sync issues article warns that unsupported file names, sizes and item counts can stop syncing. An invalid name is a file problem, not proof that OneDrive needs to be reinstalled.

Step 5: Check available storage and local free space

Even with adequate SharePoint tenant storage, your Windows PC can run low on disk space. Inspect Settings → System → Storage. If the library uses files on demand, determine which items are online-only versus locally available. A very large file or many simultaneous downloads can leave the client busy for a long time without meaning the files are corrupt.

Avoid clearing the local folder to free space until verifying online copies and unsynced work. For compliance-controlled devices, use managed storage cleanup policies. If you are above a Microsoft 365 storage allocation, your administrator must review the correct SharePoint or OneDrive quota rather than simply deleting local icons.

Step 6: Inspect SharePoint library permissions

A user may browse a folder but not have the right access to edit or synchronize certain items. If the OneDrive client reports permission denied, test access to the exact file through the browser. Check whether permissions were recently changed or inherited from a site, library or folder. Ask the site owner to restore appropriate access through standard membership and sharing processes.

Do not make the library public to solve one employee’s sync issue. Permissions should be least-privilege, and shared links with temporary permissions may not behave like normal long-term library membership.

Step 7: Determine whether Sync or Add shortcut to OneDrive was used

Microsoft 365 offers more than one way to make SharePoint content appear in OneDrive or File Explorer. Sync connects a document library to the local OneDrive client. Add shortcut to OneDrive surfaces selected shared content through the user’s OneDrive area. Depending on tenant settings and the existing relationship, trying both on the same folder can produce confusing duplicates or conflicts.

Ask users to identify whether they originally clicked Sync at the SharePoint library or added a shortcut. When changing methods, use Microsoft’s supported stop-sync or remove-shortcut workflow, confirm data integrity and avoid deleting the source folder itself.

Step 8: Update the OneDrive sync client

Outdated client builds may contain bugs or compatibility problems. Check the installed version and update through approved Microsoft or enterprise software deployment channels. Microsoft maintains official procedures for updating or reinstalling the sync app. On company-managed PCs, administrators may control releases via policy and deployment rings, so use the approved channel rather than a third-party binary mirror.

After updating, restart the OneDrive client and retest one affected library. If the client cannot sign in, repair authentication first; changing document libraries won’t resolve a broken account token.

Step 9: Recover from a paused or offline client

Open the OneDrive cloud icon and confirm syncing is not paused. Check Wi-Fi, VPN and proxy connectivity, and test whether standard Microsoft 365 sites load from the same device. If network policy blocks access to cloud services, contact the organization’s network team. Do not disable corporate proxy or endpoint security as a blanket fix.

If a coworker on the same network synchronizes normally but your laptop does not, compare client versions, work account state, the specific library and local disk capacity before assuming a service outage.

Step 10: Stop and restart syncing one library — safely

Microsoft documents procedures for stopping a library’s sync relationship and starting it again. Before doing so, copy pending local-only files to a safe folder outside the synchronized directory and verify online items. Write down the library URL and the currently synced folder path.

1. Open OneDrive Settings → Account.
2. Identify the affected SharePoint library rather than the entire work account.
3. Choose the supported Stop sync option for that library when available.
4. Verify the online library still contains the expected documents.
5. Return to SharePoint, open the same library and select Sync, using the organization’s supported flow.
6. Let the client build a fresh synchronization relationship, checking whether it creates a differently named local folder.
7. Compare known test files and restore only confirmed local-only edits intentionally.

The older folder may remain on the disk. Do not delete it automatically; Microsoft notes that previously synced files can be retained locally, and restarting sync may create a folder with an added number. See Microsoft Learn — Resolve sync issues.

Step 11: Reset OneDrive when simpler fixes fail

A OneDrive reset is a later-stage repair when you have ruled out individual file errors, account access, paused syncing and outdated software. Microsoft’s Reset OneDrive guide explains that a reset changes client settings and disconnects sync relationships. It is not equivalent to deleting cloud files, but you must still preserve unsynced local changes first.

Follow the current Microsoft instructions for your installed OneDrive release rather than relying on an old internet command copied without context. After reset, sign in with the intended account, restore the authorized library sync relationships and check for new local folder names. On managed devices, coordinate with IT before resetting a heavily customized client.

Step 12: Microsoft Teams files and SharePoint library syncing

Files uploaded to a Teams channel are generally stored in a connected SharePoint site. A channel’s Files tab may show the document even when its synced File Explorer location is stale. Test the source SharePoint site and the same document library directly. Do not assume that rejoining a Teams meeting or reinstalling Teams repairs a OneDrive sync queue.

When multiple Teams channel libraries fail for one user, review account identity, permissions and the number of synchronized items. Administrators may set OneDrive policies for allowed tenant sync and other controls, described in Microsoft’s OneDrive policy documentation.

Fix document conflicts instead of overwriting collaborators

Office files can be edited simultaneously. If your client shows a conflict or separate copies, compare modification times and review SharePoint version history before choosing a version. Avoid renaming and overwriting the cloud version without discussing active edits. For a file with unsynced local changes, preserve a local copy first and use the supported document merge or version-restoration process.

OneDrive “Processing changes” never finishes

A queue stuck on processing might be working through a large file, blocked by a problematic item, or affected by another client issue. Inspect OneDrive activity and any exact file errors. Reduce the scope by testing one small known-good document in a simple library location. Avoid trying to force synchronization by moving an entire live library out and back in; that can create duplicated changes or heavy uploads.

SharePoint sync error after a password reset

A work password change, multifactor authentication change or tenant switch can require fresh authentication. Open OneDrive account settings, verify the work account and complete supported sign-in prompts. If authentication loops persist, involve the identity team, especially if Conditional Access requires a compliant Intune device. Do not remove corporate device enrollment or turn off multifactor authentication to fix sync.

Admin checklist: policies, logs and service health

• Confirm the SharePoint site is accessible to the affected user and the library permits offline synchronization.
• Check whether a tenant policy limits which organizations can synchronize to the device.
• Review OneDrive sync client version, last sync, disk free space and effective account.
• Check filename/path limits and current library size before resetting clients.
• Verify Microsoft 365 service health if the issue affects many users or sites simultaneously.
• Compare logs from one affected and one healthy computer, following approved diagnostic collection procedures.
• Verify retention, sensitivity labels and data-loss prevention rules before recommending file exports.

Verify the final result

Select one small test document, edit it in an approved workflow, save the change and confirm the same content appears in SharePoint online and the synchronized folder. Repeat with a second test file, if appropriate, then verify previously affected paths. Check OneDrive reports no errors and that the correct work account remains connected after reboot.

The aim is not merely to make the red X disappear: the local and server versions must agree without losing a colleague’s changes. Record which sync relationship was reset and which local-only files were preserved.

SharePoint sync scenarios that need different solutions

A large project folder shows a red X next to one document

Do not reset every synced library. Open OneDrive’s View sync problems and identify the exact file name and error message. A very long path, unsupported character, local lock or access problem can block one document while other files synchronize normally. Test with a single harmless document in the same library. If the new file syncs, the environment is broadly healthy and you can focus on the problematic path. When changing names in a shared library, notify collaborators: a mass rename can disrupt stored links and workflows.

A user sees a SharePoint folder in the browser but not in File Explorer

First check whether the user ever added that library to the sync client. Browser access does not automatically imply local synchronization. Open the library online and look for Sync, then check the OneDrive account’s existing libraries. If a library’s Sync option is disabled, involve the site owner; Microsoft documents that site configuration can control offline availability. If a user added a shortcut instead, it may appear in a different OneDrive location. Avoid setting up both a sync relationship and shortcut to the exact same content without checking for overlap.

A colleague edits a spreadsheet but your local copy never changes

Compare the browser document’s modification time and version history with the local file’s details. Look for a OneDrive synchronization pause or error. If you have local-only edits, copy them outside the sync folder before troubleshooting. Do not overwrite the browser version or click “Replace” merely to remove a warning; the newer server version might contain the colleague’s changes. For complex Excel workbooks, a deliberate compare/merge process is safer than automatic assumptions about the latest file.

Sync worked before a password or MFA policy change

The device may need to satisfy new identity requirements. Confirm that the employee’s work account is active and that OneDrive can authenticate through the organization’s supported flow. If Conditional Access requires a compliant Intune endpoint, verify device compliance separately. Disconnecting the PC from company management is not a safe workaround. Administrators should examine sign-in logs and ensure the intended OneDrive app is allowed by the policy.

A SharePoint library is accessible to admins but not to a new contractor

This points toward sharing permissions and organizational access, not a defective OneDrive installation. Ask the site owner whether the contractor has site or library access, whether external sharing is permitted, and whether sensitivity labels or guest restrictions apply. Avoid making the site publicly accessible. Grant only the minimum authorized permission and test that the contractor can open the actual library in a browser before enabling local sync.

Plan a safe library re-sync in organizations

For a large library, schedule any re-sync when bandwidth and user activity permit. Record the SharePoint URL, the local sync path and the employee’s work account. Warn users not to simultaneously edit documents in the old disconnected folder and the new synchronized folder. Confirm the cloud library is healthy, copy local-only material aside, and restart the relationship through the supported OneDrive interface. The client may create a new folder with a suffix; it is dangerous to assume similarly named directories are duplicates with identical content.

Keep a written change record showing when syncing was stopped and restarted, who approved it and what verification passed. If sensitive documents are involved, copying them to USB devices or unmanaged personal cloud accounts may violate retention or data-loss prevention rules. Use approved enterprise backup and incident processes instead.

Sync folder performance: item count and deep hierarchy

Even when each file meets upload limits, a very large number of objects can place strain on local indexing and the sync client. Excessively deep hierarchies produce path-length failures, particularly when the OneDrive sync root includes a long organization name. Focus on the smallest set of files employees need offline and the specific libraries relevant to their work. Don’t sync entire historical libraries by default simply because the Sync button is available.

If the organization uses automatic deployment of libraries through policy, the admin should review its intended scope. Users may be unable to remove or change a library that is centrally required. Attempting to override corporate policy via undocumented registry changes can cause recurring re-enrollment or duplicated roots.

Use SharePoint version history rather than guessing which copy won

Version history is often the safest way to establish what changed and when. Open the document in the SharePoint library and review available prior versions before restoring anything. A restore may affect other collaborators, so confirm business ownership first. For a recently edited file, compare content rather than only timestamps; network delays and local clock settings can complicate timing. Keep the local conflicting copy until the merged or restored version has been validated.

File locks, checked-out documents and coauthoring

Some libraries use mandatory check-out, approvals or workflow-specific controls. A checked-out or locked file can fail normal editing expectations even though the sync client is connected. Determine whether the library requires check-out, whether the user has permission to check the document back in, and whether Office coauthoring supports that file type. Do not remove a lock or force a check-in without coordinating with the person editing the file. This is a document workflow issue, not always a general OneDrive sync failure.

Microsoft 365 outage versus local-device problem

Make the scope determination before taking destructive actions. One missing document is not justification for resetting 200 employees’ OneDrive clients.

Operational checklist for verification

After recovery, verify an intentional change in both directions where the user’s permissions allow: create or edit a small file in SharePoint online and observe it locally, then create a harmless local test file and confirm it appears in the correct online library. Do not test by editing real customer records. Inspect OneDrive for error indicators, verify the correct tenant account and check that the sync remains healthy after restarting the client.

Provide users with a simple rule: if the cloud icon reports a conflict, stop and preserve the local work before deleting or moving anything. This avoids turning a manageable sync issue into data loss.

Synchronizing only what a team actually needs

Organizations sometimes configure entire departmental libraries for offline availability even when most employees use only a few folders. A better approach is to review which work genuinely requires local copies and whether shortcuts or web access serve the remainder. Excessive local synchronization increases device storage use, indexing work and the number of potential conflicts. A change in scope should be agreed with the library owner and tested with pilot users, not imposed by deleting everyone’s local folders without notice.

Use OneDrive’s supported account and folder controls to adjust synchronization. On managed devices, the organization may deploy policies that control which libraries appear automatically. Do not use unsupported registry changes to remove an unwanted folder when the management policy may add it back.

Handling a former employee’s unsynced documents

When an employee leaves, their local computer may contain documents that never completed synchronization. Before reassigning or wiping that device, follow the company’s data-retention and endpoint procedures. Confirm that needed documents exist in SharePoint online, capture relevant business records through approved methods, and have the owner review files still pending locally. Removing the OneDrive account or reimaging the computer without this check can erase unique drafts even while the main shared library remains intact.

A shared library’s central storage is a major advantage, but it does not guarantee that every offline edit had already been uploaded. An employee’s computer might have remained offline during their final edits. The safest recovery process examines sync status and preserves authorized business data before device retirement.

What to do when SharePoint version history conflicts with a local copy

If the browser shows a newer version but the device contains additional offline edits, there are two plausible sources of useful content. Preserve the local file outside the synced folder, open the online version separately and compare changes with the document owner. For Office documents, use approved compare or merge workflows where available. Avoid replacing the online version wholesale just because the local file’s timestamp looks later. A workstation clock can be wrong, and edits to different sections may need to be combined.

When restoring an earlier SharePoint version, explain the effect to collaborators. Version restoration can reverse work that happened after the chosen version. Keep a record of who approved the rollback, which version was restored, and whether the final content was reviewed.

Enterprise security and sensitivity labels

A library may contain sensitive information protected by Microsoft Purview labels, data-loss prevention policies or restrictive sharing rules. A file that cannot open locally or cannot synchronize as expected may be governed by those controls rather than broken. Ask IT to investigate the exact warning and applied policy. Do not remove sensitivity labels or export confidential documents to personal storage to sidestep a restriction. These actions can cause compliance violations even if they make a sync icon disappear.

Fixing OneDrive without confusing it with a backup system

File synchronization distributes changes; it is not the same as an immutable backup. If a user deletes an item from a synchronized library, the deletion may propagate. SharePoint’s recycle bin and version history can offer recovery options under the organization’s settings, but they are not substitutes for a comprehensive backup and retention plan. Teach employees to preserve a copy of locally unsynced edits before making account or library changes, then verify cloud consistency after the client reconnects.

Planning for device replacement and new laptops

For a replacement device, verify the user’s work account and the specific libraries that are approved to sync. Ensure the old device finished uploading outstanding edits before moving it out of service. On the new PC, let the OneDrive client create its managed sync roots and avoid copying an old connected directory wholesale on top of the new one. If a separate working copy is needed, keep it outside the active sync directory and compare before merging.

Official references and further reading

• Microsoft Support — Fix SharePoint Online sync problems
• Microsoft Learn — Resolve sync issues in OneDrive for work or school
• Microsoft Learn — SharePoint service limits
• Microsoft Support — Reset OneDrive
• Microsoft Learn — OneDrive policies for administrators

Editorial note: Independent guide reviewed October 16, 2026. Microsoft 365 features and tenant policies differ, so administrators should verify their organization’s actual configuration.