OneDrive Admin Checklist: Known Folder Move fails before setup completes for department pilots

As a Microsoft 365 administrator, you are deploying Known Folder Move to a department pilot group. The setup starts but fails before it finishes. Users report that OneDrive shows an error or the Known Folder Move wizard closes without moving their Desktop, Documents, or Pictures folders. This failure typically occurs because the required Group Policy settings, tenant policies, or client prerequisites are not configured correctly. This article provides a step-by-step admin checklist to identify and resolve each cause so your pilot completes successfully.

Why Known Folder Move Fails Before Setup Completes for Pilot Users

Known Folder Move redirects the Desktop, Documents, and Pictures folders from the local user profile to OneDrive. The feature relies on a chain of dependencies: tenant policy, Group Policy, client version, and user permissions. If any link in this chain is misconfigured, the setup wizard will fail before moving any folders.

The most common root cause is a conflicting Group Policy setting that prevents users from redirecting known folders. The policy is located under Computer Configuration > Administrative Templates > OneDrive and is named “Prevent users from redirecting their Windows known folders.” When this policy is set to Enabled, the OneDrive client blocks the Known Folder Move action at the start of the wizard. The user sees a generic error or the wizard closes immediately.

Another frequent cause is that the tenant-level OneDrive sync settings in the Microsoft 365 admin center have Known Folder Move disabled or restricted to specific security groups. If the pilot users are not in the allowed group, the client will not offer the feature or will fail silently during setup.

A third cause is the OneDrive client version. Known Folder Move requires OneDrive build 22.022 or later. Many organizations deploy OneDrive via Microsoft 365 Apps for enterprise, but the update ring may be set to Semi-Annual Channel, which delivers client updates months after they are available. Pilot machines running an older build will fail.

Admin Checklist: Steps to Enable Known Folder Move for Department Pilots

Follow these steps in the order listed. Each step addresses one of the failure points described above.

1. Verify tenant-level Known Folder Move policy
   Open the Microsoft 365 admin center at admin.microsoft.com. Go to Settings > Org settings > OneDrive > Sync. Under the Sync tab, locate the Known Folder Move section. Confirm that the toggle “Show the ‘Sync important folders’ prompt” is set to On. If you use group-based targeting, ensure the security group containing your pilot users is added. Click Save.
2. Check Group Policy for conflicting settings
   On a pilot machine, run gpedit.msc. Navigate to Computer Configuration > Administrative Templates > OneDrive. Look for the policy “Prevent users from redirecting their Windows known folders.” If the state is Enabled, double-click it, select Not Configured or Disabled, and click OK. Run gpupdate /force from an elevated command prompt. Restart the OneDrive process from the system tray.
3. Update OneDrive to the required build
   On the pilot machine, right-click the OneDrive cloud icon in the system tray and select Settings. Go to the About tab and note the build number. The minimum required build is 22.022. If the build is older, download the latest OneDrive installer from microsoft.com and run it. Alternatively, in the Microsoft 365 admin center, go to Software download and licensing > Microsoft 365 Apps. Set the update channel to Current Channel or Monthly Enterprise Channel for pilot devices. This ensures OneDrive receives updates within weeks of release.
4. Confirm the user has a valid OneDrive license
   In the Microsoft 365 admin center, go to Users > Active users. Select the pilot user and check the Licenses and apps tab. The user must have OneDrive for Business included in their license. Common plans that include OneDrive are Microsoft 365 Business Basic, Business Standard, Business Premium, and Enterprise E3/E5. If the license is missing, assign one and wait 15 minutes before retrying Known Folder Move.
5. Clear existing folder redirection GPOs
   If your organization uses Folder Redirection Group Policy to redirect Desktop or Documents to a network share, Known Folder Move will conflict. Open Group Policy Management Console. Locate the GPO that applies to pilot users. Go to User Configuration > Policies > Windows Settings > Folder Redirection. Set each folder policy to Not Configured. Run gpupdate /force on the pilot machine. The user must sign out and sign back in for the change to take effect.
6. Use the OneDrive Known Folder Move diagnostic tool
   Download the OneDrive Known Folder Move diagnostic tool from microsoft.com. Run it on a pilot machine. The tool scans Group Policy, tenant policy, client version, and folder permissions. It outputs a detailed report listing any blocking settings. Address each item in the report and then retry Known Folder Move.
7. Run Known Folder Move manually on a test machine
   On a clean Windows 11 or Windows 10 machine that is a member of your domain, sign in with a pilot user account. Open OneDrive and complete the initial setup. Right-click the OneDrive cloud icon and select Settings > Sync and backup > Manage backup. Click the Start backup button next to Desktop, Documents, or Pictures. If the button is grayed out or missing, the checklist above has not resolved all issues. Recheck each step.

If Known Folder Move Still Fails After the Main Checklist

OneDrive Shows Error Code 0x8007017C

Error 0x8007017C means the OneDrive client cannot access the local known folder because the folder path contains an unsupported character or is too long. The maximum path length for Known Folder Move is 260 characters. Ask the user to rename any folders or files in Desktop, Documents, or Pictures that exceed this limit. After renaming, retry the Known Folder Move wizard from OneDrive Settings > Sync and backup > Manage backup.

Known Folder Move Wizard Opens but Closes Immediately

This behavior is often caused by the Group Policy setting “Prevent users from redirecting their Windows known folders” being Enabled. Even if you disabled the policy, a second GPO may be applying it. Run gpresult /h gpresult.html on the pilot machine and open the HTML report. Search for “Prevent users from redirecting.” If the policy appears with a Winning GPO name, edit that specific GPO and set the policy to Not Configured. Run gpupdate /force and restart OneDrive.

Known Folder Move Fails for Specific Users but Not Others

If one pilot user succeeds and another fails, the issue is likely user-specific. Compare the failed user’s OneDrive license assignment, group membership, and local folder permissions against a successful user. The failed user may have a personal OneDrive folder that is already syncing a different Microsoft 365 tenant. Sign out of that personal account in OneDrive Settings > Account. Then retry Known Folder Move.

Known Folder Move Pilot Requirements: Client vs Tenant vs Group Policy

Item	Tenant Policy	Group Policy	OneDrive Client
Purpose	Enables or restricts Known Folder Move org-wide	Blocks or allows users to redirect known folders on managed devices	Provides the user interface and performs the folder move
Configuration location	Microsoft 365 admin center > Settings > Org settings > OneDrive > Sync	Group Policy Management Console > Computer Configuration > Administrative Templates > OneDrive	OneDrive Settings > Sync and backup > Manage backup
Required state for pilot	Known Folder Move toggle On, pilot group added	“Prevent users from redirecting” set to Not Configured or Disabled	Build 22.022 or later
Effect if misconfigured	Known Folder Move is hidden or fails with generic error	Wizard opens but closes immediately; no error message	Wizard does not appear or shows unsupported version error

Use this table to quickly identify which layer is misconfigured based on the symptom your pilot users see.

With this checklist completed, you can now deploy Known Folder Move to your department pilot without mid-setup failures. Next, expand the pilot to a second department and monitor the OneDrive sync health dashboard in the Microsoft 365 admin center. For advanced management, consider using the OneDrive Known Folder Move PowerShell cmdlet Set-SPOTenantSyncClientRestriction to programmatically enable the feature for multiple security groups at once.