How to Fix OneDrive Error: The Folder Cannot Be Added Right Now
Question details
Users are unable to synchronize specific SharePoint sites using OneDrive due to a persistent folder addition error.
- Product
- OneDrive
- Device & OS
- not provided
- Scenario
- Attempting to sync specific SharePoint document libraries to a local computer using the OneDrive desktop client.
- Observed behavior
- OneDrive displays 'The folder cannot be added right now' for specific SharePoint sites, even when other sites sync normally and resetting or reinstalling OneDrive fails to resolve the issue.
Ensure all your currently synced and modified files are saved to avoid data loss, and verify that you have administrative access to your computer to modify OneDrive account settings.
Unlink Account and Synchronize SharePoint Sites Individually
Use this solution to clear the current synchronization state by unlinking your device, restarting, and individually pulling down the affected SharePoint sites before re-adding your primary account.
This approach bypasses cached account errors by temporarily disconnecting your local OneDrive client from Microsoft 365, ensuring that the background synchronization state is completely reset before establishing a fresh connection to the problematic SharePoint sites.
Click the OneDrive cloud icon in your system tray, open 'Help & Settings' > 'Settings', navigate to the 'Account' tab, and click 'Stop sync' next to all currently linked SharePoint sites.
Still in the 'Account' tab of OneDrive Settings, click 'Unlink this PC' and confirm the prompt to disconnect your Microsoft 365 account from the device.
Reboot your computer. When the computer restarts and the OneDrive setup screen appears automatically, do not sign in right away; simply close the window.
Open your web browser, navigate to the required SharePoint site, and click the 'Sync' button located in the toolbar. Sign in to OneDrive when prompted by the application.
Wait for the individual SharePoint sites to finish downloading. Once complete, open OneDrive settings, go to the 'Account' tab, and select 'Add an account' to sign back into your main OneDrive storage.
Request Log Analysis from Microsoft Support
Use this step if standard unlinking or clean Windows installations fail to resolve the synchronization error, indicating a backend account issue.
Experience Hassle-Free Document Management with WPS Office
If persistent Microsoft 365 and OneDrive synchronization errors are interrupting your workflow, consider switching to WPS Office. It provides a lightweight, highly compatible, and user-friendly experience for your document management without heavy background sync conflicts.
- 1. Download and Install WPS Office: Visit the official WPS website, download the free installer, and complete the rapid installation process.
- 2. Connect Your Preferred Cloud: Open WPS Office, click 'Open' on the left sidebar, select 'Cloud', and easily link your preferred cloud storage provider.
- 3. Work Without Interruptions: Open, edit, and save your documents directly to the cloud with robust format compatibility and fewer synchronization errors.
Frequently Asked Questions
Why does OneDrive say 'The folder cannot be added right now'?
This error typically occurs due to synchronization state conflicts, corrupted sync caches, or backend account credential mismatches between your local OneDrive client and the remote SharePoint server.
Will unlinking my OneDrive account delete my currently synced files?
No. Unlinking your PC only disconnects your computer from the cloud. The files you have already downloaded will securely remain on your hard drive in their original local folders.
How do I sync only a specific folder instead of an entire SharePoint site?
Instead of clicking 'Sync' at the root of the SharePoint site, click into the specific document library or subfolder you need via the web interface, and then click the 'Sync' button in the toolbar.
What if reinstalling OneDrive doesn't fix the SharePoint sync issue?
If reinstalling the app and unlinking the account fail, the issue is likely tied to your account's server-side configuration. You will need to contact Microsoft 365 support to perform a backend log trace to resolve the underlying conflict.
