Fix Windows 11 25H2 Rolling Back to 24H2

You check for updates, Windows 11 25H2 downloads, the PC restarts a few times over twenty or thirty minutes, and then you're back at your desktop — still on 24H2. No error dialog, just a message that says something didn't go as planned, or nothing at all. A day later Windows Update tries again. Same result. This isn't Windows losing your files or forgetting your preference to stay on 24H2. It's Windows Setup doing exactly what it's designed to do: detecting that the upgrade can't finish cleanly and reverting to the last known-good build before it leaves you with a broken machine.

That's actually the reassuring part. The frustrating part is that the rollback wipes out most of the evidence you'd want to diagnose why it failed, unless you know where to look before the logs get cleaned up. This is that walkthrough.

What "automatic rollback" actually means here

Windows 11, version 24H2 Home and Pro editions reach end of servicing on October 13, 2026. Once that date is close, Microsoft moves unmanaged consumer devices — PCs not controlled by Intune, Windows Update for Business, or a domain — onto 25H2 through what Microsoft calls an intelligent, staged rollout rather than waiting for everyone to click "check for updates." That's documented on the official Windows 11, version 24H2 release health page. So if you didn't ask for this update and it just showed up, that's expected behavior, not a bug by itself.

The rollback you're seeing is a separate thing layered on top: Windows Setup for feature updates (the same underlying process used for every 24H2/25H2-style jump) runs in phases — Down-level, Safe OS, First Boot, Second Boot — and if any phase fails, Setup is built to automatically restore the previous OS rather than leave you stuck. It does this using a temporary copy of your old Windows install that it keeps around during the upgrade specifically for this purpose. You end up back on 24H2, intact, with the failure logged (briefly) for analysis.

This is different from the manual "go back to the previous version of Windows" option under Settings > System > Recovery, which only appears after a successful upgrade and only for 10 days, as Microsoft explains on its Recovery options in Windows support page. If your PC never actually finished landing on 25H2, that's not the mechanism at play — you're dealing with a failed install, not a completed one you're electing to undo.

Don't guess the cause. Read the setup logs first.

Generic "update failed" is not a diagnosis. It can be a driver, a disk space problem, a corrupted component in the servicing store, third-party security software, a stale boot manager, or hardware Setup doesn't trust. Guessing wastes hours. Two log locations matter, and timing matters more than people expect:

While the upgrade is still attempting to install: C:\$WINDOWS.~BT\Sources\Panther\setupact.log and setuperr.log
After a rollback has already happened: C:\Windows\Panther\setupact.log, and in some builds C:\Windows\Panther\NewOS\Panther\setupact.log

The $WINDOWS.~BT folder gets deleted once rollback completes, so if you want the richest log set, grab it the moment you're back at the desktop — before you reboot again or run Disk Cleanup. I've lost the good logs more than once by rebooting first "just to be safe." Don't do that.

Rather than reading raw logs line by line, run Microsoft's own SetupDiag tool against them. It's a free, officially supported diagnostic utility built specifically to parse these files and match them against known failure signatures, documented at Microsoft Learn's SetupDiag page.

mkdir C:\SetupDiag
cd C:\SetupDiag
:: download SetupDiag.exe from Microsoft into this folder, then run:
SetupDiag.exe /Output:C:\SetupDiag\SetupDiagResults.log /Format:Text

Run it from an elevated Command Prompt or PowerShell — SetupDiag needs admin rights to read the Panther logs. Open SetupDiagResults.log in Notepad afterward. If it matches a known rule, you'll get a plain-English cause and often a specific error code, not just "upgrade failed." If it finds nothing, that itself tells you something: the failure is either too new for SetupDiag's rule set or happened before Setup even got far enough to log meaningfully, which usually points at disk space or firmware-level blocks (see below).

Symptom, confirming check, and fix

What you're seeing	How to confirm it's this	Fix
Rollback happens near 35–36% during the reboot phase, error 0x800f0922	Check free space on the EFI System Partition (ESP) in Disk Management — right-click the small FAT32 partition, Properties. 10 MB or less free is the threshold Microsoft flags	Install the May 2026 cumulative update KB5089549 or later first, which addresses this specific failure pattern; if the ESP is still nearly full, free space with `diskpart` or a third-party partition tool before retrying
SetupDiag reports a DISM or component-store failure	SetupDiagResults.log names a DISM rule and an error like 0x800706ba or similar	Run `DISM /Online /Cleanup-Image /RestoreHealth` then `sfc /scannow`, reboot, and retry the upgrade
Rollback happens very early, before any meaningful setup log is written	$WINDOWS.~BT folder is tiny or Setup never got past "preparing"	Check overall free space on C: (Setup wants headroom well beyond the final image size) and temporarily disconnect non-essential USB devices, docking stations, and external drives
Setup fails specifically in the Safe OS or WinRE phase on a machine last upgraded from very old media	SetupDiag or setupact.log references Safe OS Dynamic Update or a boot manager mismatch	Update using current Windows Update or freshly downloaded installation media rather than an old ISO — current media already includes the corrected Safe OS Dynamic Update path that older media (pre-February 2025) lacked
SetupDiag flags a driver-related rule, or the last successful phase mentions a specific device	Rule name references OptionalComponent, driver install, or a named .sys file	Update or temporarily uninstall that driver (check the device's Properties > Driver tab for the exact name), then retry
Third-party antivirus or a filter driver appears in RegisteredAV or FilterDrivers in the SetupDiag output	Look at the "System Information" block at the top of SetupDiagResults.log	Temporarily disable or uninstall the third-party security suite for the duration of the upgrade, then reinstall it afterward

Check for a Microsoft-documented fix before you touch anything manually

Before you start editing the registry or reinstalling drivers on a guess, check whether Microsoft has already acknowledged and fixed your exact symptom. The Windows 11, version 25H2 known issues page and its companion resolved issues page list active and fixed problems by exact symptom and KB number, and they're kept current — use Ctrl+F to search for your error code rather than reading top to bottom. The ESP-space failure above is a good example: Microsoft names the exact error code, the exact completion percentage, and the exact KB that resolves it. If your symptom matches one of these entries and you're not already on the fixing update, installing it is the correct first move, ahead of anything below.

If your organization manages the PC and a known issue is fixed via Known Issue Rollback (KIR) rather than a full update, note that KIR requires a specific Group Policy MSI to be deployed on managed devices —home PCs generally get the equivalent fix automatically after a restart, per the same release health pages.

What I would not do

Don't keep clicking "check for updates" repeatedly hoping the tenth attempt works. If the underlying cause (disk space, a driver, a corrupted component) hasn't changed, neither will the result. You're just generating more rollback cycles and more wear on an already-stressed disk.
Don't jump straight to a clean install. I've seen people nuke a working 24H2 install over what turned out to be 200 MB of missing ESP space. Check the table above first.
Don't disable Windows Update entirely as a "fix." It stops the immediate annoyance but leaves you on an edition that stops receiving security patches on October 13, 2026. You're trading a solvable problem for an unpatched machine.
Don't run random "Windows Update reset" scripts from forum posts before you've read SetupDiagResults.log. Some of these scripts clear the exact SoftwareDistribution cache and BITS state that would have told you what actually went wrong, and most 25H2 rollback failures aren't Windows Update service corruption at all — they're Setup-phase failures, which that reset does nothing for.
Don't assume it's the same issue as a post-install reboot loop after a routine cumulative update. That's a related but different failure mode —the OS has already landed on 24H2/25H2 and a later monthly patch is causing instability. The fix there is uninstalling that specific update or waiting for a KIR/out-of-band patch, not anything in this article.

If SetupDiag comes back with nothing and your ESP has plenty of free space, don't keep guessing in the dark. Copy the Panther logs off the machine (from C:\Windows\Panther after rollback) before your next attempt overwrites them, and search the exact error code on the Resolve Windows upgrade errors reference, which breaks down what each code segment means.

Free up ESP space without breaking the partition layout

The EFI System Partition issue deserves its own section because it's the one most people don't even know exists it's a small, hidden FAT32 partition, and Windows doesn't manage its contents automatically. If diskpart shows it nearly full:

diskpart
list disk
select disk 0
list partition
select partition 1
detail partition

Common culprits are leftover boot files from old dual-boot setups, multiple Windows Recovery Environment images, or stale bootloader entries from prior in-place upgrades. Resizing or cleaning the ESP by hand is genuinely risky get it wrong and the machine won't boot at all so if you're not comfortable mounting and pruning it manually, this is a case where a repair install using current installation media (which regenerates a clean ESP layout) is the safer path than surgery on the existing partition.

If nothing above resolves it: repair install, then retry

When SetupDiag doesn't point at anything actionable, or you've applied the fix and 25H2 still rolls back, the next step before a full reinstall is a repair install of your current 24H2 build using freshly downloaded installation media (Media Creation Tool or the ISO from Microsoft's download page), which corrects component-store inconsistencies without touching your files or apps. Only after that still fails would I reach for backing up data and doing a clean installation from scratch. That's the last resort, not the second step.

Checklist before you try again

Grab C:\Windows\Panther\setupact.log and setuperr.log immediately after the rollback, before any further reboot
Run SetupDiag against them and read the actual rule match, not just the summary line
Check ESP free space in Disk Management or diskpart
Confirm you're not already covered by a documented fix on the 25H2 release health page
Temporarily pull third-party antivirus and unnecessary peripherals for the retry attempt
Only escalate to repair install, then clean install, if the targeted fixes don't resolve it