You are piloting Known Folder Move for a department in your organization, but the setup fails before it finishes. Users see errors like “We couldn’t move your folders” or the Known Folder Move policy appears to apply but the actual redirection does not happen. This failure typically occurs because of conflicting Group Policy settings, file path length limits, or insufficient permissions on the target OneDrive site. This article explains the root causes of Known Folder Move failures during department pilots and provides step-by-step fixes to resolve them.
Key Takeaways: Known Folder Move Pilot Failures
- OneDrive admin center > Sync > Known Folder Move: Controls tenant-wide KFM policy settings including folder selection and user notification preferences.
- Group Policy Object > Computer Configuration > Administrative Templates > OneDrive > Known Folder Move: Overrides tenant policy if set to Disabled or Not Configured incorrectly.
- OneDrive > Settings > Backup > Manage backup: The per-machine interface where users see the current KFM status and can retry failed moves.
Why Known Folder Move Fails Before Setup Completes
Known Folder Move redirects the Desktop, Documents, and Pictures folders to OneDrive. When the setup fails before completion, the root cause is almost always one of these three issues:
Conflicting Group Policy settings. Your organization may have a Group Policy Object that disables KFM or sets a different target folder location. The OneDrive sync client checks Group Policy first. If the policy says Disabled, the client stops the move immediately.
File path length exceeds 260 characters. Windows and OneDrive have a combined path length limit. If a file inside Desktop, Documents, or Pictures has a path longer than 260 characters, the move fails for that entire folder. The error message often says “Path too long.”
Insufficient permissions on the target OneDrive site. The user must have at least Contribute permission on their own OneDrive for Business site. If the site was created with limited permissions or the user was removed from the site members group, the move cannot complete.
Less common causes include: OneDrive sync client version older than 19.002, the user already has a redirected folder pointing to a network drive, or the OneDrive service is not provisioned for the user.
Steps to Diagnose and Fix Known Folder Move Failures in a Department Pilot
Follow these steps in order. Stop when the issue is resolved.
- Check the OneDrive sync client version
Right-click the OneDrive cloud icon in the system tray and select Settings. In the About tab, note the version number. If it is below 19.002, download the latest OneDrive sync client from the Microsoft 365 admin center. Restart the computer and retry the move. - Verify Group Policy settings for Known Folder Move
Open the Local Group Policy Editor by runninggpedit.msc. Navigate to Computer Configuration > Administrative Templates > OneDrive > Known Folder Move. Ensure the policy is set to Enabled or Not Configured. If it is Disabled, change it to Not Configured and rungpupdate /forcefrom an elevated Command Prompt. Restart the OneDrive process from Task Manager. - Confirm the user has a provisioned OneDrive site
In the Microsoft 365 admin center, go to Users > Active Users. Select the affected user. Under the OneDrive section, verify that the site URL appears and the storage quota is set to at least 1 TB. If the site is not provisioned, click Create OneDrive. Wait 5 minutes, then ask the user to sign out and sign back in to OneDrive. - Check for file path length issues
Open File Explorer and navigate to the user’s Desktop, Documents, and Pictures folders. Look for files or subfolders with names longer than 100 characters. If you find any, move them to a temporary folder on the C drive. Retry the Known Folder Move from OneDrive Settings > Backup > Manage backup. - Remove conflicting redirections
Open Registry Editor and navigate toHKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders. Check the values for Desktop, Personal (Documents), and My Pictures. If any value points to a network drive path like\\server\share\folder, change it back to the default local path. Default paths areC:\Users\%username%\Desktop,C:\Users\%username%\Documents, andC:\Users\%username%\Pictures. Restart the computer and retry the move. - Reset OneDrive sync client
Press Windows key + R, type%localappdata%\Microsoft\OneDrive\onedrive.exe /resetand press Enter. Wait 2 minutes. Press Windows key + R again, type%localappdata%\Microsoft\OneDrive\onedrive.exeand press Enter. Sign in again and retry Known Folder Move. - Enable the KFM policy in the OneDrive admin center
Go to the Microsoft 365 admin center > Settings > Org settings > OneDrive > Sync. Under Known Folder Move, select Desktop, Documents, and Pictures. Set the policy to Silently move known folders to OneDrive. Click Save. Wait 1 hour for the policy to propagate, then ask the user to restart the OneDrive sync client.
If Known Folder Move Still Fails After the Main Fix
OneDrive Shows Error Code 0x80070005 Access Denied
This error means the user does not have write permission to their OneDrive site. Open the SharePoint Online Management Shell and run Set-SPOUser -Site <UserOneDriveURL> -LoginName <UserUPN> -IsSiteCollectionAdmin $true. This grants full control. Wait 10 minutes, then ask the user to sign out and sign back in to OneDrive.
OneDrive Shows Error Code 0x80070057 Parameter Incorrect
This error occurs when a file or folder name contains invalid characters like a colon, asterisk, or question mark. Use the PowerShell script from Microsoft’s support site to find files with invalid characters in the Desktop, Documents, and Pictures folders. Rename or delete those files. Then retry the Known Folder Move from OneDrive Settings.
Known Folder Move Policy Applies but Folders Are Not Redirected
This happens when the OneDrive sync client is not restarted after the policy applies. Open Task Manager, find Microsoft OneDrive in the Processes tab, right-click it, and select End task. Then start OneDrive from the Start menu. The move should begin automatically within 2 minutes.
Multiple Users in the Same Pilot Group Fail with the Same Error
This indicates a tenant-wide configuration issue. Check the Microsoft 365 admin center > Health > Service health for any OneDrive service advisories. If no advisories exist, verify that the KFM policy is applied to the correct security group. In the OneDrive admin center, under Sync > Known Folder Move, confirm that the policy targets the pilot group’s security group, not an empty distribution group.
Known Folder Move Pilot Failures: Common Causes and Fixes
| Item | Group Policy Conflict | File Path Length Limit |
|---|---|---|
| Description | GPO disables KFM or sets conflicting target | File path exceeds 260 characters |
| Error message | “We couldn’t move your folders” | “Path too long” or error code 0x8007007B |
| Scope | All users in the pilot group | Individual users with deep folder structures |
| Fix | Set GPO to Not Configured or Enabled | Move or rename files with long paths |
You can now diagnose and fix Known Folder Move failures during department pilots. Start by checking Group Policy and the OneDrive sync client version. If the issue persists, examine file path lengths and user permissions. For ongoing pilot management, enable the KFM policy in the Microsoft 365 admin center and target the correct security group. As an advanced tip, use the OneDrive Deployment tool to pre-configure KFM settings in a script and run it during pilot onboarding to avoid manual per-machine configuration.