OneDrive Admin Checklist: Known Folder Move fails before setup completes for Windows 11 rollouts

When rolling out Windows 11 to users, you might see Known Folder Move fail before the setup wizard finishes. The error typically appears as a red banner in OneDrive Sync status: “We couldn’t move your folders” or “Setup did not complete”. This happens because the prerequisite policies or permissions are not fully applied before OneDrive attempts the folder move. This article explains the root cause and provides a step-by-step admin checklist to resolve the failure during Windows 11 rollouts.

Why Known Folder Move Fails Before Setup Completes on Windows 11

Known Folder Move, or KFM, redirects the Desktop, Documents, and Pictures folders to OneDrive. On Windows 11, the setup process runs during the first OneDrive sign-in or after a policy is applied via Group Policy or Intune. The failure occurs when OneDrive tries to move folders before the user has completed the Windows 11 out-of-box experience, or before the device has finished Azure AD registration.

The technical root cause is a timing conflict. OneDrive initiates the folder move as soon as the user signs in and a KFM policy is detected. However, if the Windows 11 device is still in the provisioning phase — for example, the user has not yet accepted the organization’s terms of use, or the device has not synced its Intune compliance status — OneDrive cannot verify the user’s identity and folder ownership. This results in a permission denied error and KFM stops before moving any files.

Another common cause is the presence of existing folder redirection policies from Group Policy that conflict with OneDrive’s KFM. If a user’s Desktop or Documents folder is already redirected to a network share via Group Policy, OneDrive will see the target path as invalid and fail the move.

Admin Checklist to Fix Known Folder Move Failures on Windows 11

Follow this checklist in the exact order. Each step must complete before moving to the next. Do not skip any step even if you think it is already configured.

1. Verify Azure AD Join Status
   Open Windows 11 Settings > Accounts > Access work or school. Confirm the device shows “Connected to “ and that the connection status is “Azure AD joined”. If the device is not joined, KFM will fail. Run dsregcmd /status in Command Prompt as administrator to confirm the AzureAdJoined field is YES.
2. Check Intune Compliance Policy Sync
   In the Microsoft Intune admin center, go to Devices > All devices. Select the target device and verify the compliance status is Compliant. If the device is Noncompliant or Pending, wait for the next sync cycle or trigger a manual sync from Windows 11 Settings > Accounts > Access work or school > Info > Sync.
3. Remove Conflicting Folder Redirection Policies
   Open Group Policy Management Console. Navigate to User Configuration > Policies > Windows Settings > Folder Redirection. If any folder policy is set to Basic or Advanced, change it to Not Configured. Run gpupdate /force on the target device to apply the change.
4. Enable KFM via Group Policy or Intune
   For Group Policy: Open the OneDrive Group Policy template. Go to Computer Configuration > Administrative Templates > OneDrive > Silently move Windows known folders to OneDrive. Set it to Enabled. For Intune: Create a Settings Catalog policy and search for “Silently move Windows known folders”. Set it to Enabled and assign it to the device group.
5. Set the OneDrive Tenant Sync Policy
   In the Microsoft 365 admin center, go to Settings > Org settings > OneDrive > Sync. Ensure the option “Allow syncing only on computers joined to specific domains” is either disabled or includes the domain of the Windows 11 device.
6. Clear Existing OneDrive Cache on the Device
   On the Windows 11 device, right-click the OneDrive cloud icon in the system tray and select Settings > Account > Unlink this PC. Then press Windows key + R, type %localappdata%\Microsoft\OneDrive\ and delete all files inside. Restart OneDrive and sign in again.
7. Deploy OneDrive with the Correct Build
   Ensure the OneDrive sync app is version 22.222 or later. Older builds do not support Windows 11 folder structures correctly. Download the latest build from OneDrive release notes.
8. Trigger KFM Manually on a Test Device
   After the above steps, sign in to OneDrive on a test Windows 11 device. Open OneDrive Settings > Sync and backup > Manage backup. Click Start backup next to Desktop, Documents, or Pictures. If the button is grayed out, the policy is not applied. Recheck steps 4 and 5.

If Known Folder Move Still Has Issues After the Main Fix

OneDrive Shows “We couldn’t move your folders” with no details

This generic error usually means the user does not have sufficient OneDrive storage. Check the user’s OneDrive storage quota in the Microsoft 365 admin center under Users > Active users > select the user > OneDrive tab. If the quota is below 1 GB, increase it to at least 5 GB or remove unnecessary files. KFM requires enough free space to copy the folder contents.

KFM moves only some folders and skips others

OneDrive may skip a folder if it contains files with unsupported characters or path lengths exceeding the Windows MAX_PATH limit of 260 characters. Use the OneDrive Folder Protection diagnostic tool to identify which files are blocking the move. Run %localappdata%\Microsoft\OneDrive\OneDriveStandaloneUpdater.exe with the /diagnose switch to generate a report.

OneDrive keeps prompting for folder move after it already completed

This loop occurs when the KFM policy is applied but OneDrive cannot save the redirected folder path to the registry. Open Registry Editor and navigate to HKEY_CURRENT_USER\Software\Microsoft\OneDrive\Accounts\Business1. Check the value KfmMoveState. If it is not set to 3, the move did not finalize. Delete the KfmMoveState key, restart OneDrive, and sign in again to re-trigger the move.

Known Folder Move vs Manual Folder Backup: Key Differences

Item	Known Folder Move	Manual Backup
Trigger	Group Policy or Intune policy	User clicks Start backup in OneDrive settings
User interaction required	None — silent move	User must approve backup dialog
Folder redirection method	Changes shell folder registry paths	Copies files to OneDrive but does not redirect shell folders
Supported on Windows 11	Yes, with build 22.222+	Yes
Conflict with existing Group Policy folder redirection	Fails if policy exists	Works independently

You can now deploy Known Folder Move on Windows 11 without setup failures by verifying Azure AD join, removing conflicting policies, and applying the correct OneDrive build. Next, test the move on a small pilot group before rolling out to all users. As an advanced tip, use the OneDrive Admin Center report under Health > OneDrive sync health to monitor KFM success rates across your organization in real time.