OneDrive Admin Checklist: Known Folder Move fails before setup completes for device refresh projects

When you run a device refresh project, you redirect user folders with Known Folder Move. The move fails before setup completes. This stops the migration and leaves folders in their original location. The root cause is often a combination of stale sync records, group policy conflicts, or network latency during the first sign-in. This article explains the technical reasons for the failure and provides a step-by-step admin checklist to resolve and prevent the issue.

Why Known Folder Move Fails During Device Refresh Setup

Known Folder Move redirects the Desktop, Documents, and Pictures folders to OneDrive. In a device refresh, the user signs into a new or wiped machine for the first time. The OneDrive sync client attempts to move these folders during the initial setup wizard. If the move fails before completion, the user sees an error message and the folders remain local.

The technical root cause is almost always one of three scenarios:

Stale Sync Relationship from the Old Device

When a user signs into a new device, the OneDrive client checks the Microsoft 365 tenant for an existing Known Folder Move state. If the old device still holds a sync relationship with the same folder set, the new client cannot claim ownership. The move operation fails with error code 0x80070194 or a generic Something went wrong message. This happens because the tenant has not received a RemoveDevice or DisableKFM signal from the old device.

Group Policy or Registry Lock

Many organizations deploy a group policy that disables Known Folder Move for security or compliance reasons. If the policy is still applied during the device refresh, the OneDrive client blocks the move before the setup wizard finishes. The same effect occurs if a stale registry key from a previous image remains in the Windows registry.

Network Latency or Interrupted Authentication

During the first sign-in on a refreshed device, OneDrive must authenticate with Azure Active Directory and fetch tenant policies. If the network is slow or the user credentials expire mid-setup, the sync client cannot complete the folder move. The setup wizard exits early, and Known Folder Move is left in a pending state.

Admin Checklist to Fix Known Folder Move Failures Before Setup Completes

Use this checklist in order. Complete each step before moving to the next.

1. Verify Known Folder Move policy in the Microsoft 365 admin center
   Go to Microsoft 365 admin center > Settings > Org settings > OneDrive > Sync. Under Known Folder Move, confirm the option Redirect known folders to OneDrive is selected. Verify the security group assigned to the policy includes the user or device. If the policy is set to Do not redirect known folders, change it and allow 15 minutes for replication.
2. Disable any group policy that blocks Known Folder Move
   Open Group Policy Management Console on a domain controller. Navigate to Computer Configuration > Administrative Templates > OneDrive. Find the policy Prevent Known Folder Move. Set it to Not Configured or Disabled. Run gpupdate /force on the target device or reboot it.
3. Remove stale registry keys from the device image
   On the new or refreshed device, open Registry Editor. Navigate to HKLM\SOFTWARE\Policies\Microsoft\OneDrive. Delete any value named DisableKFM or EnableKFM if they exist. Set DisableKFM to 0 if you cannot delete it. Close Registry Editor.
4. Sign out and clean the old sync relationship
   On the new device, open OneDrive settings. Go to Account and click Unlink this PC. Confirm the action. Then sign out of OneDrive completely. In File Explorer, navigate to %LocalAppData%\Microsoft\OneDrive\settings\Business1 and delete all files in that folder. Restart the OneDrive process from the Start menu.
5. Perform a clean sign-in and trigger Known Folder Move manually
   Sign into OneDrive with the user’s work or school account. When the setup wizard appears, select the folders you want to redirect. If the wizard does not prompt for Known Folder Move, go to OneDrive settings > Sync and backup > Manage backup. Click Manage backup and select Desktop, Documents, and Pictures. Click Start backup.
6. Verify the move completed successfully
   Open File Explorer. Right-click the Desktop, Documents, or Pictures folder. Select Properties > Location. The path should show %UserProfile%\OneDrive - [TenantName]\Desktop (or Documents, Pictures). If the path still shows the local C:\Users\[Username]\Desktop, the move failed. Repeat steps 1 through 5.

If Known Folder Move Still Fails After the Checklist

OneDrive shows error 0x80070194 or 0x80070193

These errors indicate the sync client cannot claim the folder because another device already owns it. Sign into the old device, open OneDrive, and unlink it. Then go to Microsoft 365 admin center > Health > Device sync and remove the old device entry. Wait 30 minutes and retry the move on the new device.

Known Folder Move is grayed out in settings

This means a group policy or registry key is blocking the option. Run rsop.msc on the device and look for the OneDrive administrative template under Computer Configuration. If the policy Prevent Known Folder Move is enabled, contact your domain administrator to disable it. If no policy appears, check the local registry at HKLM\SOFTWARE\Policies\Microsoft\OneDrive for any remaining keys.

OneDrive setup wizard closes before folder move starts

The user credentials may have expired or the device cannot reach Azure AD. Open a web browser and sign into https://portal.office.com with the same account. If authentication fails, reset the user password or re-enable the account. On the device, run dsregcmd /status in Command Prompt as administrator. Confirm the AzureAdJoined status is YES. If it shows NO, join the device to Azure AD again.

Known Folder Move Policies: Admin Center vs Group Policy vs Registry

Item	Microsoft 365 Admin Center	Group Policy (Computer Configuration)	Local Registry (HKLM)
Description	Central tenant-wide setting for Known Folder Move	Domain-level policy that overrides admin center settings	Machine-level key that can block or enable the feature
Scope	Applies to all users in the assigned security group	Applies to all domain-joined computers in the OU	Applies only to the local machine
Conflict resolution	Lowest priority	Medium priority	Highest priority
Common misconfiguration	Policy set to Do not redirect instead of Redirect	Prevent Known Folder Move is enabled	DisableKFM value set to 1

When all three layers conflict, the local registry wins. Always check the registry first when troubleshooting a device refresh failure. After you resolve the registry, verify the group policy, and then confirm the admin center setting.

You can now run a device refresh project with Known Folder Move working on the first sign-in. Start by unlinking old devices from the tenant before provisioning new machines. For large-scale projects, use the OneDrive deployment tool with the /silent and /configure switches to pre-set the Known Folder Move policy during imaging. This removes the dependency on the user completing the setup wizard.