A feature update broke a driver, an app stopped working after Patch Tuesday, or you simply prefer the previous version. Windows offers several ways to undo changes, depending on what changed and how long ago. Here’s which one to use, and how.
Which method do you need?
| Situation | Method |
|---|---|
| Upgraded to a new Windows version (e.g. 10 → 11, or 23H2 → 24H2) in the last 10 days | Go back in Recovery settings |
| A monthly (quality) update caused problems | Uninstall the update |
| A driver, app install or setting change broke things | System Restore (if restore points exist) |
| Windows won’t start | Windows Recovery Environment (WinRE) |
| More than 10 days after an upgrade | Clean install of the older version, or restore from a backup image |
1. Go back to the previous version (within 10 days)
After a feature upgrade, Windows keeps the old system in C:\Windows.old for 10 days.
Windows 11: Settings → System → Recovery → Go back. Windows 10: Settings → Update & Security → Recovery → Go back to the previous version of Windows 10.
Windows asks why you’re going back, offers to check for updates first, then restarts and restores the old version. Your files and most apps are kept, but apps and settings changed after the upgrade may be lost. Back up important files anyway.
The button is greyed out or missing if:
- more than 10 days have passed;
- you ran Disk Cleanup or Storage Sense and removed “Previous Windows installation(s)”;
C:\Windows.oldwas deleted.
Extend the rollback window
Right after an upgrade, you can extend the window to up to 60 days from an elevated command prompt:
DISM /Online /Get-OSUninstallWindow
DISM /Online /Set-OSUninstallWindow /Value:60
This only works while the rollback files still exist.
2. Uninstall a problematic update
For monthly cumulative updates and other patches:
Windows 11: Settings → Windows Update → Update history → Uninstall updates. Windows 10: Settings → Update & Security → Windows Update → View update history → Uninstall updates.
From the command line:
wmic qfe list brief /format:table
wusa /uninstall /kb:5034441
(wmic is deprecated on new builds; use Get-HotFix in PowerShell to list updates.)
Some updates, such as servicing stack updates, can’t be uninstalled. To stop the update from reinstalling immediately, pause updates for a week or more in Windows Update settings while you wait for a fix.
3. System Restore
System Restore reverts system files, drivers, registry and installed programs to an earlier restore point, without touching your documents.
- Press Win+R, run
rstrui.exe. - Choose a restore point from before the problem.
- Click Scan for affected programs to see what will be removed.
- Confirm, and let it restart.
System Restore must have been enabled beforehand: on many PCs it’s off by default. Turn it on for the system drive in System Properties → System Protection → Configure, and create a restore point before big changes:
Checkpoint-Computer -Description "Before driver update" -RestorePointType MODIFY_SETTINGS
System Restore isn’t available on Windows Server. Use backups there (see below).
4. When Windows won’t boot: WinRE
After two or three failed boots, Windows opens the Recovery Environment automatically. You can also hold Shift while clicking Restart. Then: Troubleshoot → Advanced options:
- Uninstall Updates: remove the latest quality or feature update;
- System Restore: pick a restore point;
- Startup Repair: fix boot problems;
- Startup Settings: boot into Safe Mode to remove a bad driver or app;
- Command Prompt: for manual repairs (
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows,bcdedit).
5. More than 10 days later
Without Windows.old, the only way to an older version is:
- restore a system image backup taken before the upgrade; or
- do a clean install of the older version from Microsoft’s installation media, then restore your files from backup.
Windows Server and Windows VPS
Servers don’t offer “Go back” for in-place upgrades, and have no System Restore. Protect them before changes:
- take a full backup (Windows Server Backup, or your backup tool) before upgrades and major updates;
- test updates on a non-production server first;
- uninstall a problematic update with
wusa /uninstall /kb:…or from Installed Updates; - control timing with Windows Update policies. See Windows Server 2025.
On a VPS, keep the VNC console from your control panel in mind: it gives you access to the recovery screens even when RDP doesn’t work. See Windows VPS.
Prevent the next problem
- Create restore points (PCs) or backups (servers) before updates.
- Delay feature updates a few months, so early bugs get fixed first.
- Keep drivers from the hardware vendor, and update them deliberately.
- Keep a recent backup of your files: rollbacks are good, backups are better.
Quick reference
| Task | Where |
|---|---|
| Undo upgrade (≤10 days) | Settings → Recovery → Go back |
| Extend window | DISM /Online /Set-OSUninstallWindow /Value:60 |
| Remove update | Update history → Uninstall updates / wusa /uninstall /kb:N |
| Restore system state | rstrui.exe |
| Can’t boot | WinRE → Troubleshoot → Advanced options |
Related: Windows Server 2019 vs 2022.