Microsoft has quietly removed the option to keep files local during Windows 11 setup, automatically enabling OneDrive’s Known Folder Move (KFM) for anyone who signs in with a Microsoft account. The change, first spotted in recent public builds, redirects your Desktop, Documents, and Pictures folders into the cloud without an obvious opt-out. While the company frames this as a protective measure against data loss, it has reignited debates over user choice and local control — and left many wondering how to reverse it.

During the Out of Box Experience (OOBE), the fine print now states, “We’ll also back up your files and photos on this device to OneDrive to help keep them safe.” Previously, a small “Only save files to this PC” link let you decline the cloud sync. That link is gone in the latest Windows 11 releases, and users who skip through setup can end up with their entire Desktop, Documents, and Pictures library living under OneDrive. The shift aligns with Microsoft’s broader push to tie its flagship productivity products — Windows, Office, and OneDrive — more tightly to the Microsoft cloud.

What OneDrive Backup Actually Does

Known Folder Move (also called “Protect your important folders”) doesn’t delete files; it relocates them. The Windows “known folders” — Desktop, Documents, and Pictures — are moved from C:\Users\yourname\ to C:\Users\yourname\OneDrive\, and Windows gets pointer updates so that apps continue to save to those locations as if nothing changed. Behind the scenes, OneDrive syncs those folders to Microsoft’s servers, making them available across devices and enabling features like Office AutoSave, version history, and ransomware recovery.

Crucially, stopping the backup does not move files back automatically. When you disable KFM, the folder pointers revert to the original local paths, but the actual files remain inside the OneDrive folder. Manual intervention is required to restore them — a UX mismatch that’s the root cause of most confusion.

Why Microsoft Made the Change

From a product standpoint, cloud‑first defaults offer real benefits: seamless cross‑device access, built‑in versioning, and protection against hardware failure or theft. Microsoft 365 subscribers get 1 TB of storage, which easily absorbs typical document libraries. The company also collects revenue from cloud services, and steering users toward OneDrive increases the likelihood they’ll need a paid plan once they exceed the free 5 GB quota. As one Windows pipeline watcher noted, “The company collects revenue from its cloud services, and steering user files into the cloud encourages those customers to pay for more storage.”

Still, there are legitimate privacy, compliance, and bandwidth reasons to keep files local. Not everyone wants their personal documents on Microsoft’s servers, and the absence of a clear opt‑out during setup erodes trust. ZDNET’s Ed Bott, who first documented the vanished opt‑out, called the move “aggressive,” and forum discussions echo that sentiment, with many users feeling “tricked” into the sync.

Step‑by‑Step: Undoing OneDrive Backup and Restoring Local Files

The following tested procedure assumes you’re signed into Windows 11 with a personal Microsoft account and OneDrive Backup is active. It prioritizes safety: verify file integrity at every stage before deleting anything from the cloud.

1. Open OneDrive Backup Settings

Right‑click the OneDrive cloud icon in the notification area and select Settings (gear icon), or in File Explorer’s left navigation pane, right‑click OneDrive – Personal and choose OneDrive > Settings. Go to the Sync & backup tab and click Manage backup. Note which folders are listed as “Backed up.”

2. Prepare File Explorer Windows

Open a second File Explorer window and type %userprofile% in the address bar to see your local profile. Use multiple tabs: create one tab for the local Documents, one for Pictures, and one for Desktop. In the first window, navigate to the corresponding OneDrive folders (OneDrive\Documents, etc.). Arranging windows side‑by‑side makes the copy process error‑proof.

3. Turn Off OneDrive Backup for Each Folder

Return to the Manage Backup dialog. For each folder — Documents, Pictures, Desktop — slide the toggle to Off and confirm by clicking Stop backup. You must do this for each folder individually. Once stopped, the OS directory pointers revert to the local profile paths, but your files still sit in OneDrive.

4. Move Files Back to Local Folders

In the OneDrive folder tab, select all items (Ctrl+A), then cut (Ctrl+X). Click into the local folder tab and paste (Ctrl+V). Repeat for each folder. When copying from Pictures, check subfolders like Screenshots and Camera Roll: copy their contents individually to avoid duplicate folder structures. For very large libraries, move files in batches to prevent sync throttling or quota hiccups.

5. Verify Integrity Before Cleanup

Open a representative sample of documents, photos, and other files from the local folders. Confirm they open correctly, and check that metadata (dates, thumbnails) survived. Only after you’re thoroughly satisfied should you delete the duplicate files from your OneDrive folder or via onedrive.com. Deleting sooner risks accidental loss.

If you want OneDrive gone entirely, first ensure no redirected folders remain. Then, in OneDrive settings under the Account tab, click Unlink this PC. After unlinking, you can uninstall OneDrive from Settings > Apps if desired. Never uninstall while shell folder pointers still point to OneDrive locations; that can break the Desktop and other shell folders.

Office’s Stealthy Autosave‑to‑Cloud Default

In parallel, Microsoft 365 preview builds have introduced a default that creates new Word, Excel, and PowerPoint files directly in the cloud. When enabled, the “Create new files in the cloud automatically” checkbox is active, disabling AutoSave if you choose to save locally. This feature is expected to hit the Current Channel later this year.

To reverse it:

  • Open Word (or Excel/PowerPoint), go to File > Options > Save.
  • Clear the checkbox “Create new files in the cloud automatically.”
  • Select “Save to Computer by default” and pick a local folder.

Be aware that clearing that box also disables Office AutoSave, which requires cloud storage. Forum testers report that the exact labels can vary between build numbers and channels, so if you don’t see the option, check your Office update channel.

Three Practical Strategies for Windows Users

Option 1: Embrace the Cloud (Pay If Needed)

Keep OneDrive Backup on, upgrade to Microsoft 365 (1 TB storage), and enjoy continuous off‑device backup, seamless device sync, Office AutoSave, version history, and ransomware file recovery. This is the path of least resistance and genuinely benefits users who work across multiple PCs.

Option 2: Go Completely Local (Manual Backup)

Undo KFM as described above, and rely on external drives, NAS, or an alternate cloud service for backups. Use File History, Windows Backup, or a third‑party image backup. This satisfies privacy requirements and avoids recurring subscription costs, but you assume full responsibility for data protection.

Option 3: Hybrid (Selective Cloud)

Keep active working files in OneDrive for convenience, but move large archives or sensitive documents to local storage. Use Files On‑Demand to display cloud files without downloading them, saving local disk space. This requires discipline: regularly audit your OneDrive folder to avoid quota exhaustion and duplicate content.

Enterprise and IT Admin Controls

For organizations, user‑level ad‑hoc folder redirection poses compliance and data residency risks. IT administrators should use Group Policy or Microsoft Intune to disable Known Folder Move on managed devices, or pilot it with clear communication. When a fleet‑wide rollout is planned, automated migration tooling is far safer than manual user actions. Admins must also monitor cross‑account sign‑ins, because a personal Microsoft account can accidentally absorb corporate data if users aren’t careful.

Key administrative policies:
- Disable KFM via Group Policy: Administrative Templates\OneDrive\Prevent users from moving their Windows known folders to OneDrive (set to Enabled).
- Set Known Folder Move via Intune: Use administrative templates or a custom OMA‑URI to control folder redirection.
- Enforce storage quotas: Block unmanaged personal accounts syncing with corporate devices.

Common Risks and Hard‑Won Lessons

  • Quota Exhaustion: The free 5 GB fills up quickly with photos and documents. When the limit is reached, sync errors appear, files stop updating, and users panic.
  • Perceived Deletion: Because files vanish from their usual spots, many assume they’ve been “stolen,” unaware they’ve simply moved. Before panicking, always check C:\Users\yourname\OneDrive or onedrive.com.
  • The Disconnect Between Backup Stop and File Location: Stopping backup does not move files back. This is the single biggest point of user confusion. Manually copying is mandatory.
  • Bandwidth Hogs: Syncing a 50 GB photo library over a metered connection can be slow and costly. Move large libraries offline first.
  • Office Autosave Dependency: Disabling cloud defaults in Office kills AutoSave. Decide whether you value uninterrupted save lanes more than local storage.

Quick Reference Checklist

  • [ ] Verify KFM status in OneDrive > Settings > Backup > Manage backup.
  • [ ] To go local: stop each folder backup, copy from OneDrive to local, verify, delete cloud duplicates, unlink if desired.
  • [ ] To keep the cloud: check your storage tier (5 GB free vs. 1 TB Microsoft 365).
  • [ ] To stop Office cloud saves: File > Options > Save > clear “Create new files in the cloud automatically.”
  • [ ] For enterprise: use Group Policy/Intune to control KFM, and train users on folder locations and quotas.

What This Means Going Forward

Microsoft’s decision to remove the opt‑out in Windows 11 setup signals a fundamental shift: the company considers cloud‑first storage the default, not a choice. While the benefits are undeniable for many — productivity, device‑agnostic access, built‑in file recovery — the lack of transparency during OOBE is a legitimate UX flaw. Users who value local control must now treat the initial Windows setup as a moment of vigilance, and those who unknowingly accept the cloud sync must navigate a multi‑step manual undo process.

For individual users, the safest path is to decide before you sign in: do you trust Microsoft with your files, or are you willing to shoulder backup duties yourself? There’s no wrong answer, but there is a wrong sequence. As one forum veteran put it, “Getting this sequence wrong is the most common cause of accidental file loss or confusion.”

The best defense is a clear checklist and a separate backup — whether that’s an external drive, NAS, or another cloud provider — so that no single service failure wipes out your data. In an era of aggressive cloud defaults, local backups are more vital than ever.