Fix “Sorry we can’t sync this folder” on OneDrive, SharePoint & Teams

If you rely on cloud collaboration tools for daily work, seeing the message “Sorry, we can’t sync this folder” can instantly slow everything down. This error commonly appears while trying to sync folders in Microsoft OneDrive, Microsoft SharePoint, or Microsoft Teams, especially when using the desktop sync client on Windows 11 or Windows 10.

At first glance, the issue looks vague because it does not clearly explain whether the problem is related to permissions, file naming rules, storage limits, or account conflicts. That uncertainty often leads users to try random fixes. Instead of guessing, you need a structured approach that addresses the real causes behind the sync failure.

In this guide, you will learn exactly why this error appears and how to fix it step by step.

Fix “Sorry we can’t sync this folder” on OneDrive, SharePoint & Teams

The error typically occurs due to permission issues, unsupported file names, exceeded path length, sync client glitches, or account conflicts. Since OneDrive is also responsible for syncing libraries from SharePoint and Teams, most solutions focus on the OneDrive sync app installed on your PC.

Follow the steps below carefully. After each step, check whether the folder syncs successfully before moving to the next one.

Step 1: Verify Your Account and Permissions

Before adjusting settings, confirm that your Microsoft account or work account has the correct access rights to the folder.

Open your browser and sign in to OneDrive online. Try accessing the same folder directly from the web version. If the folder does not open or shows restricted access, the issue is likely permission-related.

If the folder belongs to a SharePoint site or a Teams channel, open the related site in your browser. Make sure you are listed as a member with edit permissions. If you only have view access, the sync client may refuse to sync the folder.

You can also sign out and sign back in from the OneDrive desktop app. Right-click the OneDrive icon in the system tray, open Settings, go to the Account tab, and confirm that the correct account is connected.

Many users overlook this simple check and spend hours troubleshooting something that is actually a permissions mismatch. Once you confirm that access is correct, move ahead and see what else could block the sync.

Step 2: Check Folder and File Naming Restrictions

OneDrive, SharePoint, and Teams follow strict file naming rules. If your folder contains unsupported characters or reserved names, the sync will fail with the message you are seeing.

Look for characters such as quotation marks, colons, asterisks, question marks, or trailing spaces in file and folder names. Rename any file that includes these characters.

Also check for reserved names like CON, PRN, AUX, or NUL. These system reserved words cannot be synced on Windows.

Another common issue is a file name that ends with a period or space. Even if it looks normal in File Explorer, OneDrive may block it during sync.

After correcting the names, restart the OneDrive app and try syncing again. If the problem still appears, the issue may not be naming-related. That means we need to dig deeper into file path limits and storage constraints.

Step 3: Ensure the File Path Length Is Within Limits

Even on modern Windows versions, there is a practical limit to how long a full file path can be. When syncing SharePoint or Teams libraries, the folder structure can become very deep, especially if the site name and document library name are long.

Open the local sync folder in File Explorer and check the full path of the problematic folder. If the total character count of the path exceeds around 400 characters in the cloud context, the sync may fail.

You can shorten the path by renaming higher-level folders to shorter names or moving the synced library closer to the root directory. For example, instead of syncing under C:\Users\YourName\OneDrive – Company Name\Documents\Projects\Archive, move it directly under C:\Sync.

After adjusting the location, try syncing again. If reducing the path length does not resolve the issue, it is time to examine storage limits and quota restrictions.

Step 4: Check Available Storage and Site Quotas

When your OneDrive storage or SharePoint site storage reaches its limit, sync errors often appear without clearly mentioning storage as the cause.

Open OneDrive in your browser and check the storage indicator. If you are close to the maximum limit, delete unnecessary files or move them to external storage.

For SharePoint libraries, open the site settings and check site storage metrics. If the site is full, contact your administrator to increase the quota.

In Teams, remember that files shared in channels are stored in the connected SharePoint site. If that backend storage is full, syncing through Teams will fail as well.

After freeing up space, restart your PC and allow OneDrive to reinitialize the sync process. If storage is not the issue, we should focus on resetting the sync client itself.

Step 5: Reset the OneDrive Sync Client

Sometimes the error appears because the OneDrive sync app is stuck in a corrupted state. Resetting it can clear internal configuration issues without deleting your cloud files.

Press Windows + R to open the Run dialog. Type the reset command for OneDrive and press Enter. The OneDrive icon may disappear for a few moments and then reappear.

Once it restarts, sign in again if prompted. Then manually select the folder you want to sync.

This reset often resolves unexplained sync failures because it rebuilds the local cache and reconnects to Microsoft servers.

If the folder still refuses to sync after a reset, the next step is to unlink and relink your account.

Step 6: Unlink and Reconnect Your Account

Open OneDrive settings from the system tray. Under the Account tab, choose the option to unlink this PC.

After unlinking, close OneDrive completely. Restart your system to clear temporary processes. Then launch OneDrive again and sign in with your work or personal account.

When prompted, choose a fresh local sync location. Avoid selecting the same corrupted folder path if you suspect directory issues.

Reconnect the SharePoint or Teams library from the browser by clicking the Sync button again. This establishes a new sync relationship and eliminates broken links.

Many persistent errors disappear at this stage because the old configuration is replaced entirely.

If the issue continues even after relinking, the problem may be administrative or policy-based.

Step 7: Check Organizational Policies and Admin Restrictions

In work or school environments, IT administrators may restrict syncing certain libraries to unmanaged devices.

If you see the error specifically for one SharePoint library but not others, contact your IT administrator and ask whether sync restrictions or device compliance policies are enabled.

In some cases, conditional access policies block sync on devices that are not enrolled in company management systems.

Verifying this early can save you from trying technical fixes that will never work due to policy enforcement.

Once administrative restrictions are ruled out, you can be confident that your local environment is responsible for the problem.

FAQs

Why does the error appear only for one folder?

This usually indicates a problem with that specific library. It may contain restricted file types, long paths, or permission conflicts.

Can I access the folder online even if it does not sync?

Yes, in many cases, you can still access files through the web version of OneDrive, SharePoint, or Teams. The issue is often limited to the desktop sync client.

Does reinstalling OneDrive fix the problem?

Reinstalling can help if the app files are corrupted. However, try resetting and unlinking first before going for a full reinstall.

Is this issue related to Windows 11 updates?

Sometimes system updates affect background services, but the error is more commonly related to account, path, or storage issues.

Summary

The message “Sorry, we can’t sync this folder” in OneDrive, SharePoint, or Teams may look generic, but it usually points to specific technical causes. By checking permissions first, correcting naming issues, reducing path length, verifying storage limits, resetting the sync client, reconnecting the account, and reviewing organizational policies, you can systematically eliminate it.