OneDrive for Business Known Folder Move troubleshooting for Windows 11 rollouts: fails before setup completes

You are deploying Windows 11 devices in your organization and have configured OneDrive for Business Known Folder Move to redirect Desktop, Documents, and Pictures. The setup process fails before it completes, leaving folders unmoved and users without access to their synced files. This failure typically occurs because of pre-existing folder redirection Group Policy, OneDrive sync client version mismatches, or insufficient permissions during the initial sign-in phase.

The Known Folder Move feature relies on the OneDrive sync client to detect current folder locations and initiate a move to OneDrive. When the move fails before setup finishes, the sync client cannot modify the Windows known folder paths due to conflicting policies or missing prerequisites.

This article explains the root causes of Known Folder Move failures during Windows 11 rollouts and provides step-by-step fixes for each failure pattern. You will also learn how to verify prerequisites and avoid common deployment mistakes.

Why Known Folder Move Fails Before Setup Completes on Windows 11

Known Folder Move is a OneDrive feature that automatically redirects the Desktop, Documents, and Pictures folders to OneDrive. During a Windows 11 rollout, the sync client attempts to move these folders during the first sign-in or shortly after. The move fails when the sync client encounters a conflict with existing folder redirection settings, when the OneDrive client version is older than 19.002.0107.0002, or when the user does not have write permissions to the target OneDrive location.

The most common technical root cause is a Group Policy Object that has already redirected these folders to a network share or another location. Windows 11 will not allow the sync client to override an active folder redirection policy. Another frequent cause is the OneDrive sync client being unable to authenticate with the correct tenant because the tenant ID in the client configuration does not match the user’s tenant.

A third cause involves stale registry entries from a previous OneDrive setup that was interrupted. These entries prevent the sync client from initiating a fresh Known Folder Move. The sync client may also fail if the Windows 11 device was joined to Azure AD before the user signed in and the OneDrive client did not receive the correct Azure AD token.

Steps to Resolve Known Folder Move Failures During Deployment

Before you start, ensure that all target Windows 11 devices have the latest OneDrive sync client installed. The minimum required version is 19.002.0107.0002. You can download the latest OneDrive deployment package from the Microsoft 365 admin center. Also verify that the user accounts have valid OneDrive for Business licenses assigned.

1. Remove conflicting folder redirection Group Policy
   Open the Group Policy Management Console. Navigate to User Configuration > Policies > Windows Settings > Folder Redirection. Right-click each folder that is redirected and select Properties. Set the Setting drop-down to “Not configured.” Run gpupdate /force on the target Windows 11 device. Restart the device.
2. Verify the OneDrive tenant restriction policy
   In the Group Policy Management Console, navigate to Computer Configuration > Administrative Templates > OneDrive > Allow syncing OneDrive accounts for only specific organizations. Set this policy to Enabled and enter your tenant ID. The tenant ID is available in the Microsoft 365 admin center under Organization Settings. Without this policy, the sync client may attempt to authenticate against the wrong tenant.
3. Clear stale OneDrive account registry entries
   Open Registry Editor on the Windows 11 device. Navigate to HKEY_CURRENT_USER\Software\Microsoft\OneDrive\Accounts\Business1. If this key exists, delete it. Repeat for any numbered subkeys under Accounts. Close Registry Editor and restart the OneDrive sync client by running %localappdata%\Microsoft\OneDrive\OneDrive.exe /reset from a command prompt.
4. Enable Known Folder Move via Group Policy
   In the Group Policy Management Console, navigate to Computer Configuration > Administrative Templates > OneDrive > Silently move Windows known folders to OneDrive. Set this policy to Enabled. Choose the folder redirection behavior: “Prompt users to protect their important folders” or “Move known folders to OneDrive without prompting.” Deploy the policy to the target Windows 11 devices.
5. Trigger a manual Known Folder Move after sign-in
   Have the user sign in to Windows 11 and open OneDrive from the system tray. In OneDrive Settings, go to the Sync and backup tab. Click Manage backup. If the Desktop, Documents, or Pictures folders show as not backed up, click the Start backup button. The sync client will attempt the move again.
6. Check the OneDrive sync client logs for error codes
   Open File Explorer and navigate to %localappdata%\Microsoft\OneDrive\logs. Open the most recent log file. Look for entries containing “KFM” or “KnownFolderMove” followed by an error code. Common error codes include 0x80070005 for access denied and 0x80070002 for file not found. Use the error code to identify the specific failure point.

If OneDrive Still Has Issues After the Main Fix

Known Folder Move shows “This folder is already being redirected by Group Policy”

This error indicates that a folder redirection policy is still active even though you removed it. Check for any linked GPOs at the domain, site, or OU level that may still apply the redirection. Use the Group Policy Results Wizard to identify which GPO is applying the setting. Remove or disable that GPO and run gpupdate /force again.

OneDrive sync client does not start after Windows 11 setup

The sync client may not start if the Windows 11 provisioning package skipped the OneDrive app installation. Verify that OneDrive is installed by checking for %localappdata%\Microsoft\OneDrive\OneDrive.exe. If the file is missing, install OneDrive from the Microsoft Store or deploy it via Microsoft Intune. After installation, run %localappdata%\Microsoft\OneDrive\OneDrive.exe to start the client manually.

Known Folder Move fails with error “We can’t move your folder right now”

This error often occurs when the user’s OneDrive storage quota is full. Check the user’s OneDrive storage usage in the Microsoft 365 admin center under Users > Active Users > OneDrive tab. If the quota is exceeded, increase the storage limit or ask the user to free up space. The error can also occur if the target folders contain files with unsupported characters. Rename any files in Desktop, Documents, or Pictures that have names containing characters like / : ? ” < > |.

Known Folder Move vs Manual Folder Backup: Key Differences

Item	Known Folder Move	Manual Folder Backup
Deployment method	Group Policy, Intune, or registry	User clicks Manage backup in OneDrive settings
Folder redirection	Redirects Desktop, Documents, Pictures to OneDrive automatically	Copies files to OneDrive but does not redirect folder location
User interaction required	None when set to silent mode	User must start the backup and confirm each folder
Group Policy conflict handling	Fails if conflicting folder redirection GPO exists	Works alongside folder redirection GPO
Best for	Large-scale Windows 11 rollouts with new devices	Existing devices or gradual migration

Known Folder Move is the recommended method for new Windows 11 deployments because it enforces consistent folder locations and reduces user help desk calls. Manual backup is suitable for existing devices where you want to add OneDrive protection without changing the folder path.

After resolving the Known Folder Move failure, verify that the Desktop, Documents, and Pictures folders point to the OneDrive path by opening File Explorer and checking the folder properties. You can also confirm the move by opening OneDrive settings and viewing the Sync and backup tab. For advanced deployments, consider using the OneDrive Known Folder Move PowerShell cmdlet Set-SPOTenantSyncClientRestriction to enforce tenant-wide settings and prevent tenant mismatch errors during future rollouts.