You can revert to a previous Windows version easily within 10 days of upgrading, using Settings > System > Recovery > "Go back." That window is set by Microsoft and can't be extended once it closes. In practice, that's plenty of time, but the decision is often made harder by how Windows silently deletes your old system files later. This article covers the 10-day window, the exact steps, what the rollback keeps and loses, and the failure cases you won't find in most guides.
Why the 10-Day Rollback Window Exists and What Closes It
Microsoft's rollback window is exactly 10 days from the date the new version finished installing. That figure comes from Windows Update's own recovery behavior: after 10 days, Windows automatically deletes the Windows.old folder that holds the prior build, freeing disk space. The timer starts at the moment the installation completes, not the moment you first launch Windows, so if you install on a Monday morning, the window closes roughly 10 days later.
Behind the scenes, "Go back" works by restoring the previous build from Windows.old. Microsoft's guidance says the folder holds your prior Windows files, settings, and installed apps. If you've run Disk Cleanup and skipped "Previous Windows installation(s)" β a preset most users select to reclaim space β you've already deleted your escape route. Microsoft's own support page references this option explicitly, which is why you should verify Windows.old exists in File Explorer (C:\Windows.old) before you need it.
The window is fragile in a second way: it's fixed to the 10-day mark regardless of whether you've used Windows the whole time. That catches out users who install a feature update, leave for a two-week trip, log in, and find no rollback option because the timer ran through their absence. According to Microsoft's Windows Update lifecycle documentation, the automatic deletion is triggered by the installation timestamp rather than by active use.
Once the folder is gone, there's no Settings path back. The only real recovery is an in-place reinstall using the prior version's media, which requires matching the old version's release (22H2, 23H2, and so on) and rebuilding your settings manually. That's a much larger job than the simple rollback described below, so the cost of letting the window close is measured in hours, not seconds.
Confirm Your Rollback Is Available Before Touching "Go back"
Before you click anything, confirm three things: the current Windows version, the presence of Windows.old, and the elapsed days since installation. Check the version in Settings > System > About, where the OS build number identifies the release (for example, 22631 for 23H2). Microsoft publishes a current release health page at its support site, but the build number in About is what your machine reports and is the number to trust locally.
The Windows.old folder is the second check. Open File Explorer, type C:\Windows.old into the address bar, and press Enter. If it opens with folders like Windows, Users, and Program Files, the rollback data is intact. If it doesn't exist, the recovery option is gone or was never created. This happens when the update was installed as a clean install rather than an upgrade, a distinction worth noting because a clean install of the new version has no prior build to restore.
If the folder is present, open Settings > System > Recovery and look for "Go back." The screen also shows how many days remain, which is the clearest way to know your window. Microsoft's support documentation describes the option as available only within "the first 10 days after the update," which aligns with the countdown shown in Settings.
There's a fourth check most guides skip: storage. The rollback needs enough free space to reassemble the system volume, and Windows refuses if the space is insufficient. Microsoft's support page covers this indirectly by directing users to free up space; in practice, leave at least 128.0 MB of free disk space (a documented minimum Microsoft states in support notes for update prerequisites) and ideally much more. A rollback that starts and fails halfway is the worst outcome, so check free space before resolving the countdown.
Step-by-Step: Revert to Previous Windows Version Easily
Open Settings. Press Windows key + I, then select System > Recovery. Select "Go back." This appears under the Recovery options section. Click it and approve the User Account Control prompt. Choose a reason. Windows asks why you're rolling back. Pick the closest option (recent update caused issues, performance problems, apps not working), then click Next. Review "What to know before you go back." Check the notice about apps and settings. Click No, thanks if you don't want to check for updates first, or Next to proceed. Sign back in. Windows asks for your account password to re-enable the old build. Provide it. Confirm and wait. Click "Go back to [previous version]." The machine restarts once, shows a restore screen, and boots to the earlier build. Plan for 15β30 minutes on a typical laptop, longer on older hardware.
If the rollback fails partway, you'll see a blue "Restoring your previous version of Windows" screen; don't power-cycle the machine. If it hangs for more than about 45 minutes, Microsoft's recovery guidance is to try Safe Mode and use the System Restore option or, as a last resort, the reset options. If the option is missing from the Recovery screen, the cause is almost always a closed 10-day window or a missing Windows.old folder β both fallback cases covered later in this article.
What the Rollback Keeps, What It Loses, and What Sits in Between
Rollbacks preserve your personal files, but they do not preserve everything else, and most guides paint this too simply. Microsoft's "What to look for after you go back" page lists the categories it considers: files live on, apps and settings may not. The most useful way to plan is to sort your data into those three buckets before you click.
| Item | Behavior on rollback | Reason |
|---|---|---|
| Documents, photos, videos in user folders | Kept in place | Stored on the system volume, not part of the build swap |
| Apps installed after the update | Removed | The old build's app registry is restored, so post-update apps aren't registered |
| Apps installed before the update | Reinstalled/restored automatically | The old build's registry entries reappear |
| Settings changed after the update | Reverted to prior state | The old build's profile state is restored |
| Files created in the new version only | Kept in user folders but apps may not open them | Presence of files doesn't imply app compatibility |
| Features from the newer build | Gone | The old build has no code for them |
A second detail catches people who rely on OneDrive: files marked "online-only" and stored outside your local folder may not be downloaded before rollback and get reverted to their pre-update state. Microsoft's OneDrive documentation recommends checking sync status before major system changes, which is a small step most users skip. The practical fix is to open your important folders locally before rolling back so the content is physically downloaded.
The category Microsoft singles out most clearly is apps. The support page says apps installed after the update are "removed" and that you may need to reinstall some apps. In practice, this means the rollback keeps a list of what was installed before (so it restores that state) but drops anything added between the update and the rollback moment. Note that Microsoft's list is not exhaustive; it says "some" apps, so a full pre-rollback inventory is genuinely useful. Export a list of installed apps with PowerShell's Get-AppxPackage or Settings > Apps > Installed apps, then verify after boot.
Build Version Differences That Change the Rollback Experience
Rollbacks between Windows 10 and Windows 11 do not exist through the "Go back" option. That path works only for the previous version of the same OS family, meaning Windows 11 24H2 back to 23H2 is possible, but Windows 10 back to a Windows 11 install is not. Microsoft's support documentation is explicit that the previous version must be the immediate predecessor; you can't skip several builds at once, so a machine that jumped from 22H2 to 24H2 through multiple updates still only rolls back to the build recorded at the time of the last install.
Windows 10 specific builds have their own copy. Since Windows 10 reached the end of standard support on October 14, 2025, Microsoft's guidance for consumer devices shifted toward Windows 11, and a rollback from 11 to 10 through the Go back option doesn't work; the recovery path for that direction is an in-place reinstall with Windows 10 installation media. That's a meaningful edge case for people who upgraded in the last month and want to reverse it: the easy toggle is unavailable, and the process shifts to a full reinstall using the prior version's ISO.
Build numbers matter for choosing the right ISO. Windows 11 23H2 is build 22631; 24H2 is build 26100. Microsoft's release health page and the About screen reveal the numbers. If your old version was 22H2 (build 22621), you'd need that ISO, which is still downloadable from Microsoft's software-download page if you need a reinstall fallback.
The version-specific rules don't stop there. Windows 11's "Go back" also requires the old build's recovery partition to remain intact, and some OEM images strip it to save space. Microsoft's support pages don't list this edge case, but a machine with no recovery partition can still show the "Go back" option while failing to complete. Treat a missing recovery partition as a signal to do a full backup before attempting the rollback.
What to Back Up Before You Roll Back
Rollbacks preserve personal files but not app data in all cases; backup is the low-cost insurance. Microsoft's backup guidance recommends an external drive or OneDrive for files, and a one-time system image for the system files. The most practical pre-rollback routine is: copy your user folders to an external SSD, then export browser favorites as an HTML file (Chrome, Edge, and Firefox each have an export option), then note your app licenses in a text file. That package covers the rollback's known gaps.
The order matters more than the tool. Start with app data stored outside your user folder, like database files, virtual machines, and development projects. These live outside Documents and often get forgotten. Microsoft's "Go back" page states that some apps will need reinstalling; it's silent on app data inside the profile, so do your own audit, because the practical loss is the profile's hidden data. A simple count works: if you use a mail client or a photo editor with its own catalogue, those deserve a copy.
For the system, Settings > System > Storage > Advanced storage settings > Back up to a network or OneDrive can create a before-rollback snapshot; otherwise, the built-in Windows Backup tooling is worth a run. Microsoft's documentation lists a full system image as the more thorough option, and it's the one that saves you if a rollback fails and the recovery partition won't boot. Reserve about 20 GB for that image on modern Windows 11 builds, a figure Microsoft references on its system-image guidance for minimum free space.
Finally, set expectations for app licenses. Some apps reset their activation on rollback because the registry keys revert to an older state; Microsoft's install-apps documentation notes that moving to a new version of Windows may require reactivation. A license-key list in a text file costs minutes and prevents a support call. It's the cheapest step in this whole process.
Troubleshooting Missing "Go back" Options and Failed Restores
When "Go back" doesn't appear, the cause is almost always one of four things: the 10-day window expired, Windows.old was deleted, you installed Windows fresh rather than as an upgrade, or the recovery partition is missing. Microsoft's support page covers the first indirectly through the window wording; the other three come from the storage and recovery behavior of Windows Update. Check the countdown first, then the folder, then a disk check.
If the option is present but the rollback fails, the failure usually shows up on the restore screen after the first reboot. Try the recovery environment: hold Shift while selecting Restart from the Start menu power menu to reach the "Choose an option" screen, then select Troubleshoot > Advanced options > Startup Repair or System Restore, which uses a different mechanism than the Go back path. Microsoft's recovery environment documentation lists these tools and notes System Restore uses a pre-existing restore point rather than the Windows.old folder.
If both are unavailable, the honest answer is a clean reinstall of the prior build. That's a 30β60 minute process with Microsoft's media creation tool, and it requires you to reinstall apps and rebuild settings. It's the fallback that makes the "easy" rollback valuable in the first place, because doing it early is cheap and doing it after the window closes is not. The time comparison is what the guides underplay: minutes of preparation before the deadline vs. an evening of reinstall after.
One more failure mode worth naming: BitLocker. If BitLocker is enabled and a recovery key wasn't escrowed, the rollback can stall on a recovery prompt. Microsoft's BitLocker documentation recommends verifying the recovery key is saved to your Microsoft account before making build changes, which is a one-minute check in Settings > Privacy & security > Device encryption. Confirm it, then proceed.
How the Rollback Compares to Reset, Recovery Drive, and Restore Point
"Go back" isn't the only recovery tool, and the other three do different jobs. A reset reinstalls the current build, not the previous one. A recovery drive boots a recovery environment. A restore point restores system files and settings from a snapshot, not the whole build. Choosing the wrong one costs time, so compare on the same four dimensions.
| Recovery method | What it restores | Version changes | Keeps personal files | Typical time |
|---|---|---|---|---|
| Go back | Previous Windows build + prior settings | Yes, to immediate predecessor | Yes | 15β30 min |
| Reset this PC | Current build, clean state | No | Option to keep files | 30β60 min |
| Restore point | System files + settings + registry snapshot | No | Usually yes | 10β20 min |
| Recovery drive | Full system or current build reinstall | No (same build) | Depends on option chosen | 60+ min |
The key split is what each tool fixes. A restore point fixes a broken app install or a bad driver, but it can't replace the current Windows build. "Go back" does the opposite: it replaces the build entirely but doesn't help if the new build works and Windows just misbehaves. Microsoft's recovery options page lays out the same split, though it doesn't build this comparison, and that's exactly the table to keep nearby.
Cost matters too, and Microsoft's numbers are the ones to use. A clean reinstall of Windows 11 needs about 20 GB of free space plus your time to reinstall apps; a rollback needs the Windows.old folder, which is roughly the size of your previous install, often 15β25 GB on a current SSD. If you're tight on space, the fallback plan costs space as well as time, which is another reason not to skip the pre-deadline check.
When Rolling Back Is the Wrong Move and What to Do Instead
Rolling back to the previous Windows version isn't always the right call. If the issue after upgrading is a single app, a driver, or a peripheral, a rollback may not help because the new build's problem lies in a specific component, and the fix can be a reinstall of that component. Microsoft's Windows release health page recommends checking known issues before rolling back, because many upgrade problems are already documented with workarounds that keep you on the new build and avoid a rollback entirely. The features, the security patches, and the app compatibility you gain on the current build are worth keeping when the fix is small. If you're still on Windows 10, the end of standard support in October 2025 (per Microsoft's lifecycle page) means a rollback from 11 to 10 is the less secure route, and that's a judgment call beyond the scope of this article; consult a local IT professional if the stakes are high. Similarly, if you're supporting others' machines, a rollback plan should be documented before it's needed β a backup, a backup of the recovery key, and a written countdown. Do the prep early, because the 10-day window won't wait for a convenient moment. The 10-day rollback window is the single most important constraint, and it starts counting down the moment your upgrade completes.
FAQ
How many days exactly do I have to use Go back in Windows 11?
Ten days from the installation timestamp, as stated by Microsoft's Windows Update guidance. The countdown in Settings > System > Recovery shows the remaining days, but the deletion of the Windows.old folder is what actually ends it. If you're unsure, check C:\Windows.old in File Explorer; if it's there, the option is still present.
Does rolling back delete my files?
No for personal files in user folders, yes for apps and settings added after the update, and a qualified yes for anything outside your profile. Microsoft's support page says files are kept but some apps will need reinstalling. Copy your app data and licenses out before starting, since the built-in page doesn't list them explicitly.
Can I roll back after reinstalling or resetting Windows?
Not with "Go back." Both a reinstall and a reset replace or rebuild the current build, and Windows.old is created only by an upgrade. The only rollback path after a reset is a reinstall using the earlier version's installation media, which requires that version's ISO and about 30β60 minutes, per Microsoft's install media documentation.
Does Go back work if I upgraded from Windows 10 to Windows 11?
No. "Go back" only restores the immediate predecessor within the same OS family. To return to Windows 10 from Windows 11, Microsoft's recovery options require a clean reinstall with Windows 10 installation media, plus manual app restoration. That's the fallback for people who upgraded in the 10-day window but find the option missing.
How much free disk space does the rollback need?
More than a small buffer. The rollback must reconstitute the previous system volume from Windows.old, so leave at least the size of that folder plus working headroom β practically 20 GB or more on a current install. Microsoft's update prerequisites cite 128.0 MB as a minimum for update operations, which is far too low for a rollback.
Why is Go back grayed out or missing entirely?
Three common causes: the 10-day window closed, Windows.old was deleted with Disk Cleanup, or the installation was a clean install. A fourth, less common cause is a stripped OEM recovery partition. Check the folder first; if it's gone, Microsoft's recovery options point to a reinstall.
How long does a rollback take, and what happens if it fails?
Expect 15β30 minutes on modern hardware and longer on older laptops. If it fails, you'll see the "Restoring your previous version of Windows" screen; don't cut power. Use the recovery environment (Shift + Restart) to reach Startup Repair or System Restore, and if both fail, plan a clean install of the previous version.
Is a restore point a substitute for Go back?
No. A restore point restores system files, settings, and registry snapshots but doesn't change the Windows build. Microsoft's recovery options page lists the tools separately for exactly this reason. Keep a current restore point for driver problems and use "Go back" for build-level reversals.