Windows 11 Update Keeps Failing and Rolling Back

Windows 11 Update Keeps Failing and Rolling Back

You watch the progress climb during a restart — “Working on updates, 40% complete” — and then it stalls, the number stops climbing, and a message appears instead: “We couldn’t complete the updates. Undoing changes. Please keep your computer on.” A few minutes later you’re back at your desktop, except the update you thought had gone through never actually installed.

This isn’t the same as an update that just sits at the same percentage forever, and it isn’t a PC that’s stuck unable to boot at all — this is Windows successfully catching a failed install partway through and reversing it before anything actually breaks. That’s reassuring in the moment, but it doesn’t explain why the install failed in the first place, and if nothing changes, the same rollback tends to repeat itself the next time the update tries again.

Quick explanation: this guide covers what the rollback message actually means, insufficient free disk space for staging the install, a corrupted file sitting in the update cache, a driver or third-party program conflicting with the installer, system files that were already damaged before the update began, and Windows’ own update-tracking database inside the SoftwareDistribution folder getting stuck repeating the same failed attempt.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

A Windows Update that downloads fine, starts installing, and then fails partway through — often flashing “We couldn’t complete the updates. Undoing changes” during the “Working on updates” restart phase — is Windows’ own rollback safety net doing its job rather than something catastrophic; it reverts cleanly to the version of Windows you had before. The specific error code shown afterward on the update history page is a useful clue, but it’s rarely the whole story. The most common underlying causes are running low on free disk space needed to stage the install, a corrupted file sitting in the update cache, a driver or third-party program conflicting with the install process, system files that were already corrupted before the update even started, and — after repeated failures — Windows’ own update-tracking data getting stuck re-attempting the same doomed install. Working through disk space, the update cache, drivers, and system file integrity in that order resolves the large majority of cases.

What “Undoing Changes” Actually Means

Before an update starts making changes to system files, Windows creates a checkpoint specifically so it can back out of the install cleanly if something goes wrong partway through — a driver conflict, a corrupted file, an interruption. “Undoing changes” is that checkpoint being used exactly as designed: Windows noticed the install wasn’t completing successfully and reverted rather than leaving your PC in a half-updated state that might not start at all.
That distinction matters for figuring out what to try next. An update that’s genuinely stuck sits at the same percentage indefinitely with no message and nothing happening on its own, while a rollback resolves itself automatically — you land back on a working, bootable copy of Windows, just not the one you were expecting. And because the rollback already succeeded, this is a different situation entirely from a PC that fails to boot after an update actually finishes installing; that’s Windows’ safety net not catching the problem in time, rather than catching it correctly like it did here.
The rollback message itself doesn’t explain why the install failed — it just confirms that it did. Windows Update history usually lists a specific error code next to the failed attempt once you’re back at the desktop, and that code is worth noting down as a starting point, though the same code can point to more than one underlying cause. The rest of this guide works through the actual reasons an install tends to fail partway through and trigger a rollback in the first place.

Not Enough Free Disk Space to Stage the Install

A Windows Update — especially a larger cumulative or feature update — needs room for more than just the new files it’s installing. It also needs space to keep a complete backup of what it’s about to replace, so that a rollback like this one has something intact to restore. Running low on free space right at that moment is one of the most common reasons an install fails and reverts.
Windows doesn’t always surface a clean, explicit “not enough disk space” warning when this happens — sometimes it just fails and rolls back with the generic undoing-changes message instead. That makes it worth checking actual free space directly rather than ruling this out just because no low-space warning appeared on screen.
Get-PSDrive C | Select-Object Used,Free
Fixyfier’s Cleanup & Optimize section includes Disk Cleanup, Clear Windows’ Temporary Files, and Clear Your Temporary Files as one-click ways to reclaim space quickly before the update tries again.

A Corrupted File Sitting in the Update Cache

Downloaded update files sit in a cache folder before Windows ever tries to install them, and if one of those files gets corrupted on the way in — an interrupted connection, a disk hiccup, security software interfering mid-download — that corruption carries straight into the install step. The installer hits the damaged data partway through, fails, and rolls back.
This is one of the more common reasons a rollback repeats identically every time you retry, since simply clicking “Check for updates” again often just re-runs the install against the same damaged cached files rather than fetching anything new. Clearing that cache out forces a genuinely fresh download on the next attempt instead of reusing whatever’s already sitting there.
Fixyfier’s Fix & Repair section includes Clear Windows Update Cache as a one-click action that does exactly this, without needing to stop services or rename folders by hand first.

A Driver or Third-Party Program Getting in the Way

Installing an update means touching some of the lowest-level parts of the system — drivers, disk access, security hooks — and a driver that’s out of date or a third-party program that intercepts those same low-level operations, such as some antivirus suites, disk-imaging tools, or older VPN clients, can end up conflicting with the installer at exactly the wrong moment. The result is the same pattern: the install fails partway through and Windows rolls it back.
A pattern worth watching for is whether the rollback happens at a consistent point — the same percentage, the same stage — rather than varying between attempts, and whether temporarily disabling third-party antivirus or disconnecting unusual peripherals before a retry changes the outcome. A driver showing a warning icon in Device Manager is also worth checking before assuming the cause is something else entirely.
Fixyfier’s Windows Tools section puts Device Manager a click away for spotting a flagged driver and updating or temporarily rolling it back before the next update attempt.
NordVPN
One Thing Worth Knowing

Looking Up a Rollback Error While Your PC Keeps Restarting Itself

A PC that's mid-rollback tends to restart itself more than once before it settles, which makes it a bad time to have it open in a browser tab — so there's a decent chance you're reading this on a phone or a second device, on whatever network happens to be closest. NordVPN keeps that research session encrypted no matter which network you end up borrowing while your main PC sorts itself out.

Protect This Session

System Files That Were Already Damaged Before the Update Began

Windows Update assumes the files it’s about to replace are themselves intact. If some of those system files were already corrupted — left over from an earlier crash, a bad sector, or a previous update that didn’t finish cleanly — the installer can run into them mid-install, fail, and trigger the same rollback, even though the update package itself was perfectly fine.
Running a DISM scan followed by an SFC scan checks the operating system against a Microsoft-hosted reference image and repairs individual files that don’t match, addressing this specific cause directly before the next update attempt rather than guessing at it.
Fixyfier’s Fix & Repair section includes both of these as one-click actions — Repair the Windows Image and Repair System Files — so you can rule this out without typing either command by hand.

An Update Queue Stuck in a Bad State After Repeated Failures

The SoftwareDistribution folder doesn’t just hold downloaded files — it also holds Windows’ own tracking of what’s pending, what’s already failed, and what still needs to install. After several rollback cycles in a row, that tracking data can itself get into an inconsistent state, where Windows keeps re-attempting the exact same doomed install rather than treating the next try as genuinely fresh.
This is the case where fixing the original cause — freeing up space, clearing the cache, resolving a driver conflict — doesn’t stop the rollback from happening again, because the queue itself is what’s stuck rather than any of those underlying issues individually. Fully clearing out the SoftwareDistribution folder, not just the download cache within it, forces Windows to rebuild its tracking from scratch on the next check, which is usually enough to break a loop that’s outlasted every other fix.
If this ends up looking less like a rollback that eventually resolves and more like an update that simply never finishes downloading or installing at all, that’s a different pattern covered in more depth in a dedicated guide on Windows Update stuck downloading or installing.

Frequently Asked Questions

Is a rollback the same thing as Windows Update being stuck?

No. A stuck update sits at the same percentage indefinitely with no message and no automatic resolution, while a rollback is Windows actively detecting that the install failed and reversing it on its own, usually with an explicit message about undoing changes. The rollback does resolve itself — you end up back on a working, bootable version of Windows — it just isn’t the outcome you were hoping for.

Will the same update just keep failing and rolling back forever?

It can, if whatever originally caused the failure is still in place the next time Windows tries — a full drive, a corrupted cached file, or a lingering driver conflict will usually produce the identical rollback again. After enough failed attempts, the SoftwareDistribution folder’s own tracking of what’s pending can also get stuck, which is why clearing it out sometimes breaks a loop that persists even after the original cause has already been fixed.

Where do I find the specific error code after a rollback happens?

Check Settings > Windows Update > Update history, where a failed install usually lists a specific error code next to it, or look in Reliability Monitor for the same event around the time of the restart. That code narrows things down, but it’s worth treating it as a starting point rather than the full explanation, since the same code can point to more than one of the causes covered in this guide.

Let Fixyfier Help Break the Update Rollback Cycle

Fixyfier’s Cleanup & Optimize section includes Disk Cleanup, Clear Windows’ Temporary Files, and Clear Your Temporary Files for reclaiming space before a retry, its Fix & Repair section’s Clear Windows Update Cache clears out whatever corrupted file may be causing the same failure to repeat, and its Repair the Windows Image and Repair System Files rule out damaged system files — between the three, enough to work through the most common causes before the same update fails and rolls back again.
Get Fixyfier from the Microsoft Store