How to Fix 'OneDrive Can't Add Your Folder Right Now' (2026)

Fix the 'OneDrive can't add your folder right now' error instantly. Step-by-step guide for Windows, Mac, and SharePoint cache resets.

There’s nothing quite as frustrating as watching your cloud storage synchronization stall at 99%, only to be greeted by a harsh dialog box: "Sorry, OneDrive can't add your folder right now." It feels like the system is rejecting you personally, especially when you’re in the middle of a critical workflow. I’ve encountered this specific error more times than I care to admit, both in my own setups and while advising teams. Here’s the good news: in the vast majority of cases, this isn’t a broken app or a lost cause. It is usually a configuration conflict between the local client and the cloud backend.

Whether you are on Windows 10, Windows 11, or macOS, and whether you’re syncing personal files or a complex SharePoint library, the solution often lies in understanding why the sync is failing, not just blindly reinstalling the app. This guide covers everything from quick cache resets to advanced SharePoint administrative fixes, ensuring you get your folders back online quickly.

White letter tiles spelling 'ERROR' on a red backdrop, offering a minimalist design concept.

Understanding the Root Cause: Why OneDrive Sync Errors Occur

Before we start running commands or digging into admin consoles, it helps to understand what is actually happening. When you see an onedrive sync error fix is needed, it usually means the client and the server have disagreed on something. OneDrive is a hybrid service—it mirrors files from your computer to the cloud and vice versa. If the rules governing those files change on the server side, the client often throws up its hands and refuses to proceed.

SharePoint Library Configuration Conflicts

For many users, this error pops up specifically when trying to sync a team site or a shared library. OneDrive for Business has strict limitations on what SharePoint features it supports. Microsoft documentation clearly states that certain configurations make a library "sync-incompatible."

The most common culprit is the "Require Check Out" setting. In a collaborative environment, check-out ensures that two people aren’t editing the same document simultaneously. However, the OneDrive desktop client cannot handle this lock mechanism. If a library requires check-out, the client simply cannot create the local placeholder files it needs to manage the sync, resulting in the "can't add your folder" error.

Another frequent offender is Required Metadata Columns. SharePoint allows you to mandate that every document must have specific data (like a "Project Code" or "Client Name") before it can be saved. The OneDrive client doesn’t have a UI for filling out these forms during a drag-and-drop sync operation. If you try to sync a folder where files are missing required metadata, the sync halts.

Finally, restrictive Draft Item Security settings can block sync. If a library is set so that only the author or an approver can view drafts, the sync client—which needs broad read access to establish the file structure—gets locked out.

Client-Side Issues: Cache and Path Length

While SharePoint settings are the primary suspect for business users, individual machines often face simpler hurdles.

Corrupted temp files are a classic issue. OneDrive stores a significant amount of temporary data in your local appdata folders to track sync states. Over time, this data can become fragmented or corrupted, leading to sync loops where the app tries to upload a file, fails, clears the cache, and tries again indefinitely.

Then there is the age-old 260-character file path limit in Windows. While modern versions of Windows 10 and 11 have options to extend this limit via the registry, many organizations have not enabled it. If a folder structure is deep—for example, C:\Users\Name\OneDrive\Company\Projects\2024\Archive\Old\Backup\Final\Draft1\—adding a long filename can exceed the limit. The OS refuses to create the folder, and OneDrive reports it can’t add the folder right now.

Permission denied errors also fall into this bucket. If you’ve manually moved a folder outside of OneDrive or changed NTFS permissions on a parent directory, the sync client may lose its ability to write to that location.

Close-up of an iPhone with Apple logo on a black backdrop, showcasing sleek design.

Step-by-Step Fix: Reset OneDrive and Clear Cache

In my experience, the first line of defense should always be resetting the client. This clears the corrupted local state without deleting any actual data from the cloud. It’s a low-risk, high-reward step that solves the problem for most users.

Resetting OneDrive on Windows 10 and 11

You don’t need to uninstall the app to reset it. Microsoft built a specific command-line switch for this purpose.

  1. Close OneDrive: Right-click the OneDrive cloud icon in your system tray (bottom right corner) and select "Quit OneDrive." Wait for it to disappear from the tray.

  2. Open Run Dialog: Press the Windows Key + R on your keyboard.

  3. Enter the Reset Command: Copy and paste the following command exactly:

    %localappdata%\Microsoft\OneDrive\onedrive.exe /reset
    
  4. Execute: Press Enter.

    • Note: If you see a "Windows cannot find..." message, it means your installation path is different (likely a 32-bit install on a 64-bit system). Use this alternative command instead:

      C:\Program Files (x86)\Microsoft OneDrive\onedrive.exe /reset
      
  5. Wait for Restart: After you run the command, the OneDrive icon should reappear in your system tray within a minute or two. This indicates the reset was successful and the app has relaunched.

  6. Verify: Sign back in if prompted. OneDrive will begin re-syncing your files from the ground up. This might take some time depending on the volume of data, but your files are safe in the cloud.

If the reset doesn’t work, the next step is a manual cleanup. Close OneDrive again, then navigate to C:\Users\[YourUsername]\AppData\Local\Microsoft\OneDrive. Delete the contents of this folder (these are just local cache files). Then, go to Settings > Apps, find OneDrive, and click "Modify" or "Uninstall." Re-download the latest version from the official Microsoft website and reinstall it.

Resetting OneDrive on macOS

The process on Mac is slightly different because macOS handles application support folders differently.

  1. Quit the App: Click the OneDrive icon in the menu bar (top right) and select "Quit OneDrive."

  2. Delete Cache Folder: Open Finder. Press Cmd + Shift + G to open the "Go to Folder" dialog. Type the following path and hit Enter:

    ~/Library/Application Support/Microsoft OneDrive
    

    Delete the entire Microsoft OneDrive folder. This clears the cached metadata.

  3. Reinstall: Download the latest .pkg installer from the Microsoft 365 portal or the official OneDrive download page. Run the installer to restore the app with a clean slate.

  4. Sign In: Launch OneDrive and sign back into your account.

I’ve found that the Mac reset is particularly effective for users who have switched accounts or who have been dealing with persistent "login loop" errors alongside the sync failure.

Advanced Troubleshooting: SharePoint and Intune Configurations

If resetting the client didn’t work, the issue is almost certainly on the server side. As I mentioned earlier, this error is a hallmark of SharePoint configuration conflicts. If you are an IT administrator or have access to a site owner, you can fix this directly in the browser.

Adjusting SharePoint Document Library Settings

You need to modify the Versioning Settings of the specific library that is failing to sync. This requires Site Owner or Administrator permissions.

  1. Navigate to the Library: Open the SharePoint site where the error is occurring. Go to the affected document library.
  2. Access Settings: Click the gear icon in the top right corner and select Library settings. If you are in the modern interface, you might need to click "Show all settings" at the bottom of the settings page.
  3. Versioning Settings: Under the "Versioning settings" section, click on Versioning settings.
  4. Disable Require Check Out: Look for the option "Require documents to be checked out before they are edited?" Select No and click OK. This is often the single change that resolves the error for team sites.
  5. Adjust Draft Item Security: In the same Versioning Settings page, look for "Draft item security." Change this to Any user who can read items. This ensures that the sync client can see the files it needs to index, even if they are in draft status.
  6. Check Required Columns: Go back to the main Library settings page. Click on Columns (or "Create column" to see the list). Review any columns marked as Required.
    • Best Practice: For libraries that must sync with OneDrive, avoid using Required columns. If you must keep them, consider creating a separate library for local sync and using metadata only for web-based collaboration.

Once these changes are saved, go back to your OneDrive client. You may need to remove the problematic shortcut (right-click the folder in File Explorer > "Unsync this folder") and then re-sync it from the SharePoint web interface by clicking "Open in Explorer" or "Add a shortcut to My Files."

Handling Intune and Conditional Access Policies

For enterprise users, especially those on newly provisioned devices (like Windows Autopilot devices), the issue might not be the library itself, but the device’s compliance status.

Microsoft’s Zero Trust framework uses Conditional Access policies to control which devices can access corporate resources. If your organization has a policy that requires devices to be "Compliant" or "Hybrid Azure AD Joined" to access OneDrive, a brand-new device that hasn’t finished its Intune enrollment check-in might be blocked.

I’ve seen cases where the OneDrive client gets stuck in a loop, showing the "can't add your folder" error, because it fails the device compliance check in the background.

To troubleshoot this:

  • Check Intune Portal: Verify if your device shows as "Compliant" in the Microsoft Intune admin center.
  • Wait for Enrollment: If the device is new, give it time. Sometimes the compliance signal lags behind the initial login.
  • Review Conditional Access Rules: If you are an admin, check if there are specific conditional access policies targeting OneDrive for Business that might be excluding certain device states.

Also, consider Guest Accounts. Syncing from a SharePoint library where you are a guest (external user) is generally not supported. If you are trying to sync a folder from a partner’s organization, this error is expected behavior. The workaround is to use the web interface or download the files manually.

Data Recovery: Restoring Missing Folders and Files

One of the biggest fears when dealing with sync errors is data loss. Users often panic, thinking the error has deleted their files. In reality, the error usually prevents new changes from syncing, but it rarely deletes existing data. However, if you’ve been troubleshooting for days, you might have accidentally deleted a local folder or moved it elsewhere. Here is how to recover.

Using the Online Recycle Bin

The OneDrive Recycle Bin is your safety net. Unlike the Windows Recycle Bin, the OneDrive recycle bin retains deleted items for a longer period (typically 93 days for business accounts, depending on your tenant settings).

  1. Go to the Web Interface: Log in to onedrive.com or your organization’s SharePoint portal.
  2. Open Recycle Bin: Click the gear icon and select Recycle bin.
  3. Restore: Look for the missing folder. Select it and click Restore. This will return the folder to its original location in your OneDrive.
  4. Re-sync: Once restored in the cloud, your OneDrive desktop app should pick up the change and re-download the folder to your computer.

If you deleted the folder locally and it hasn’t synced the deletion yet, it might still exist in the second-stage recycle bin. In the Recycle Bin page, look for a link that says "Second-stage recycle bin." Deleted items are held there for 14 days after being removed from the primary recycle bin.

Preventing Future Data Loss

Avoiding this error in the future is about hygiene.

  • Keep Paths Short: Try to keep your file structures shallow. Instead of nesting folders five levels deep, consider using metadata tags or SharePoint columns to categorize files. This also helps bypass the 260-character path limit.
  • Regular Sync Checks: Periodically check the OneDrive status icon. Green checks mean all good. Blue arrows mean syncing. If you see a red circle with a minus sign, double-click it to see the specific error before it becomes a major issue.
  • Don’t Delete Locally During Errors: If you see a sync error, resist the urge to delete the problematic folder locally to "make it go away." This often leads to a mismatch between the cloud and the local client, causing more errors. Instead, mark it for sync exclusion or fix the underlying SharePoint setting.

FAQ

How do I fix OneDrive can't add your folder right now?

The most effective fix involves two main steps. First, reset your OneDrive client to clear corrupted cache files. On Windows, press Win + R, type %localappdata%\Microsoft\OneDrive\onedrive.exe /reset, and press Enter. If the issue persists, especially with SharePoint libraries, a site owner must disable "Require Check Out" and "Required Columns" in the library’s Versioning Settings. These SharePoint features are incompatible with local sync.

Why is OneDrive not syncing my folders even though I can see them in the browser?

This is a common point of confusion. The web interface and the desktop client operate under different rules. The browser can access SharePoint features like "Require Check Out," workflow approvals, and mandatory metadata fields. The OneDrive desktop client is designed for simple file synchronization and cannot handle these enterprise features. If a folder works in the browser but fails in the client, it is almost always due to these unsupported SharePoint configurations blocking the sync engine.

What is the file path length limit in OneDrive?

On Windows, the traditional file path limit is 260 characters. This includes the drive letter, colon, backslashes, folder names, and the filename. If your OneDrive folder is nested deep within other directories, or if you have long folder names, adding a file can exceed this limit. While Windows 10 and 11 support enabling long paths via the registry (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled), many corporate environments do not have this enabled. Renaming files to be shorter or moving them to a shallower directory structure is the best workaround.

How to clear OneDrive cache on Windows 10?

To clear the cache, you must first quit the OneDrive application from the system tray. Then, open the Run dialog (Win + R) and execute the reset command: %localappdata%\Microsoft\OneDrive\onedrive.exe /reset. This automatically deletes the local cache and restarts the app. If you prefer manual deletion, you can navigate to C:\Users\[YourUser]\AppData\Local\Microsoft\OneDrive and delete the contents of the folder after quitting the app. Note that this does not delete your cloud files, only the local sync metadata.

Conclusion

Encountering the "OneDrive can't add your folder right now" error is disruptive, but it is rarely a sign of permanent data loss or a broken application. As we’ve explored, the root cause usually falls into one of three buckets: a corrupted local client cache, a SharePoint library configuration that is incompatible with sync, or a device-level restriction from Intune policies.

For most users, the one drive reset command is the silver bullet. It clears the technical debt of corrupted temp files and refreshes the connection token. For enterprise users dealing with team sites, the solution lies in collaborating with your SharePoint admin to relax versioning settings—specifically disabling "Require Check Out" and removing required metadata columns from sync-enabled libraries.

Remember, cloud storage synchronization is a delicate balance between user convenience and enterprise governance. When those two forces clash, you get this error. By addressing both the client-side hygiene and the server-side configurations, you can restore seamless access to your files.

If you have tried all the steps in this guide—resetting the app, checking SharePoint settings, and verifying Intune compliance—and the issue still persists, it is time to escalate. Contact your organization’s IT support or Microsoft Support with your specific error logs. They can dig deeper into tenant-level diagnostics that are beyond the scope of standard troubleshooting.

← Back to Home