"We Couldn't Complete the Updates, Undoing Changes": Break the Loop

"We couldn't complete the updates. Undoing changes. Don't turn off your computer" means Windows tried to install an update, hit an error partway through, and is rolling itself back to the version that was working before — a safety feature, not a crash. It turns into a loop when the same broken update tries to reinstall on every restart, because Windows Update doesn't automatically learn that this particular update is the one causing trouble. The counterintuitive part: the rollback itself is rarely what breaks a PC for good. What breaks it is a frustrated hand on the power button during "Undoing changes," which turns a routine, self-healing process into a machine that genuinely won't boot.

What "We Couldn't Complete the Updates" Actually Means

Windows Update installs most feature and quality updates in two passes. The first happens quietly while you're using the PC, staging files in the background. The second pass — the one you actually see — happens at restart, when Windows applies those staged files to the running system. That second pass is riskier: a driver conflict, a corrupted download, a file that's locked by another process, or simply not enough free space can interrupt it midway.

When that happens, Windows doesn't leave your system half-updated. It reverses everything it changed and puts the previous, working state back — that's the "Undoing changes" text. This is deliberate rollback behavior, the same category of protection that lets a failed feature update on Windows 11 or Windows 10 leave you back where you started instead of with a broken install. On a healthy PC, you'd see this screen once, it would finish in twenty minutes to an hour, and Windows Update would quietly try again later, sometimes successfully, sometimes not. The loop people actually complain about is what happens when the underlying cause — corrupted cache, missing space, a stuck service — is still there on the next attempt, so the exact same failure repeats on every restart.

Why You Should Never Force a Restart During "Undoing Changes"

This is the single most damaging instinct in the whole scenario, and it's a completely understandable one. You've been staring at a blue screen for forty minutes, nothing seems to be happening, and holding the power button feels like taking back control. It's the opposite.

Ethan's take: "People treat the wait as the failure. It isn't — the wait is the process working. The failure is what happens forty seconds after someone gets impatient and holds the power button. I'd rather leave a machine sitting on that screen for three hours than interrupt it at minute forty just because it feels slow."

Give it real time before you assume it's stuck. On modern hardware with SSD storage, most rollbacks finish in twenty minutes to an hour; on older mechanical drives or heavily loaded machines, two hours isn't unusual. The screen genuinely can sit still with no visible progress indicator for long stretches — that alone is not evidence of a hang. What is evidence of a hang: the exact same message reappearing after a full restart, several times in a row. That's your signal to move to active troubleshooting rather than more waiting.

Which Situation Are You In?

Everything from here branches on one question: after the rollback finishes and the PC restarts, does it get you to your desktop or sign-in screen, even briefly, before the whole cycle starts again? Your answer decides which set of steps applies.

Route A: You Reach the Desktop Between Attempts (Windows 11)

If you can log in, even for a few minutes before the next scheduled restart tries again, deal with it from inside Windows rather than waiting for it to fail a third time.

1. Open Start > Settings > System > Troubleshoot > Other troubleshooters, then select Run next to Windows Update. This resets several update-related services and clears known-broken state automatically.
2. Restart when it finishes, then go to Settings > Windows Update and select Pause updates for 1 week. This stops the same update from grabbing another restart while you finish troubleshooting.
3. Go to clear the update cache below before you resume updates — the troubleshooter alone doesn't always remove a corrupted download.

One Windows 11 trap worth knowing: the troubleshooter used to live in a different menu on Windows 10, and muscle memory sends a lot of people hunting through Control Panel first. On Windows 11 it's entirely inside the Settings app now — Control Panel doesn't have an equivalent entry point for this one.

The Same Route on Windows 10

These steps are the same on both operating systems, just under a different Settings label. Open Settings > Update & Security > Troubleshoot > Additional troubleshooters, select Windows Update, then Run the troubleshooter. Pausing updates lives at Settings > Update & Security > Windows Update > Pause updates. Everything downstream — clearing the cache, uninstalling the offending update — is identical to Windows 11 from here.

Route B: It Never Reaches the Desktop

If the "Undoing changes" screen finishes, the PC restarts, and you land straight back in the exact same loop with no window to log in, you need to reach the Windows Recovery Environment (WinRE) — a small, separate recovery system that boots outside of the normal Windows startup. It's the same recovery layer whether you're on Windows 11 or Windows 10.

1. At the sign-in screen (if you ever see one, even briefly), select the Power icon, hold Shift, and select Restart. Keep holding Shift until the screen changes.
2. If you never see a sign-in screen at all, let the PC fail to boot normally two or three times in a row. Windows detects the repeated failure and launches Automatic Repair into WinRE on its own — you don't need to do anything except let it fail and restart again.
3. On the Choose an option screen, select Troubleshoot > Advanced options > Command Prompt. If your drive is encrypted, Windows will ask for your BitLocker recovery key here before it unlocks the drive for Command Prompt — see the trap below if you don't have it handy.

From that Advanced options screen you have two useful tools without touching a keyboard at all: Startup Repair, which runs an automated diagnostic and fix pass, and Uninstall Updates, which removes the specific update that's causing the loop. Try Uninstall Updates first if this started right after a specific update — it's faster and more targeted than Startup Repair, and it directly removes the thing that's failing instead of guessing at the cause.

Clearing the Corrupted Update Cache

Corrupt update files sitting in the download cache are one of the most common reasons the exact same update fails on every retry — Windows keeps trying to apply the same broken file instead of fetching a fresh copy. These steps work from a normal desktop (Route A) or from Command Prompt in WinRE (Route B); the commands are identical either way.

⚠️ Here's where a lot of guides get it wrong: renaming or deleting the SoftwareDistribution folder while the Windows Update service is still running does nothing at all — the service has the folder locked open. You have to stop the service first, or the "fix" silently fails and you'll assume it didn't work when really it never ran.

1. Press Win + R to open the Run box — a small dialog for launching a program or command by name — type services.msc, and press Enter. From WinRE Command Prompt instead, run net stop wuauserv and net stop cryptsvc.
2. Find Windows Update in the list, right-click it, and select Stop. Do the same for Cryptographic Services.
3. Open File Explorer, go to C:\Windows\SoftwareDistribution, and delete everything inside the folder (not the folder itself). Then go to C:\Windows\System32\catroot2 and rename that folder to catroot2.old rather than deleting it.
4. Restart both services — right-click each and select Start — or from Command Prompt run net start wuauserv and net start cryptsvc.

Restart the PC and check for updates again. This forces Windows to re-download the update from scratch rather than reapplying whatever was corrupted before.

Uninstalling the Specific Update

If a fresh cache doesn't stop the loop, the update itself may conflict with a driver or component on your specific machine rather than being corrupted in transit. From Troubleshoot > Advanced options > Uninstall Updates in WinRE, you can remove the most recent quality update or feature update without needing to log in first. If you can reach the desktop, the same thing is available at Settings > Windows Update > Update history > Uninstall updates.

After uninstalling, pause updates for at least a week from the Windows Update page before letting anything try to install again. This buys time for Microsoft to often push a corrected version of the same update, and it stops the exact same file from redownloading and reproducing the loop within minutes.

Disk Space and BitLocker: The Two Hidden Traps

Two causes get missed constantly because neither one shows up as an obvious error message.

Disk space. A feature or cumulative update needs headroom on the system drive to stage files before it can apply them — if that space isn't free, the install fails partway and rolls back, then fails the same way on the next attempt because nothing changed. Check free space from Settings > System > Storage while you can still log in, or from WinRE Command Prompt with dir C:\, which lists the drive's total and available bytes at the bottom of the output. If space is genuinely tight, freeing even a few gigabytes (temp files, the Downloads folder, old Recycle Bin contents) before retrying is often the entire fix.

BitLocker. If your drive is encrypted, WinRE's Command Prompt will ask for your recovery key before it can unlock the drive to run any of the commands above. Most people discover they don't have that key handy at exactly the wrong moment. We've covered where to find it and how to save a copy before you need it in our guide to recovering your BitLocker key after an update — it's worth checking before you're stuck in WinRE staring at a prompt for it.

When It Still Loops After All of That

If you've cleared the cache, uninstalled the update, confirmed free space, and it still comes back, the problem has likely moved from "one bad update" to "damaged system files that every update install trips over." One thing worth ruling out first: third-party antivirus or security software can lock files an update needs to replace, producing this exact partial-install-and-rollback pattern. If you're running something other than Windows Security, temporarily disable it before your next attempt. If the loop persists anyway, here's what's left, cheapest to most drastic.

The system file repair route: from an elevated Command Prompt (or WinRE's Command Prompt), run sfc /scannow first — it checks and repairs protected system files and reports what it fixed. Follow it with DISM /Online /Cleanup-Image /RestoreHealth, which repairs the underlying image that sfc draws from; running DISM first and sfc second is a common mix-up, and DISM needs an internet connection to fetch replacement files from Microsoft's servers. Restart and retry the update after both finish.

The in-place repair option, called "Fix problems using Windows Update recovery" in current Settings, downloads a repair version of the last update that installed successfully and reapplies system components without touching your personal files or most installed apps. It requires you to reach the desktop and stay connected to power and the internet throughout — it's not available if your device is managed by a workplace or school policy.

Laptops, Remote Desktop, and Other Edge Cases

A few setups need a slightly different approach than a plain desktop.

Laptops on battery. A rollback that stalls partway through because the battery died mid-write is one of the worst versions of this problem, since power loss during "Undoing changes" is exactly the scenario you're trying to avoid. Keep the charger connected for the entire process, from the moment you see the update start until you're back at a working desktop, even if the laptop shows a healthy charge going in.

Remote Desktop and headless machines. You can't hold Shift and click Restart over an RDP session in the way that works locally — and once a machine drops into the "Undoing changes" loop, RDP won't reach it at all until it's back to a normal boot. For a physical remote machine, you'll need someone at the console, or out-of-band management (iDRAC, iLO, or similar) if the hardware has it. There's no way to trigger WinRE purely over a standard remote session on a machine that can't boot normally.

Virtual machines. If you took a snapshot before the update, reverting to it is almost always faster than any of the steps above — you get back to a known-good state in seconds instead of working through cache clears and repairs. If you didn't snapshot first, the VM behaves exactly like physical hardware: use the hypervisor's console (not RDP) to reach the sign-in screen, then follow the same Shift+Restart path into WinRE.

Docked laptops and multi-monitor setups. If you can, undock and disconnect external monitors before troubleshooting. It's a minor thing, but a dock or an unusual display configuration occasionally interferes with the recovery environment's own display driver, and eliminating it removes one more variable while you're in WinRE.

Tablets and devices with no physical keyboard. Reaching WinRE without a keyboard usually means a hardware button combination — commonly a volume button held with the power button — but the exact combination varies by manufacturer, so check your device maker's documentation rather than assuming a Surface-style combination will match a different brand.

Stopping This From Happening Again

Once you're through the loop, a few habits cut the odds of hitting it again. Keep at least 20–25 GB free on your system drive at all times — more than updates strictly need, because temp files pile up during the install itself. Let updates install on their own schedule rather than manually forcing "Check for updates" repeatedly, which can interrupt a staged download partway. And if a specific update caused you real grief, know that it's not unusual for one release to have known issues that get fixed in a follow-up — if you want to check whether the update behind your loop had reported problems before you retry it, we track known issues for recent releases, including what changed and broke in the August 2026 Windows 11 update, separately.

Frequently Asked Questions

How long should I wait before I worry?

Give it a genuine one to two hours before treating it as stuck, especially on mechanical hard drives or heavily loaded machines. A silent, unmoving screen for a long stretch is normal during rollback; what actually signals a real problem is the identical message reappearing after a full restart, more than once.

Is my data safe during "Undoing changes"?

Yes, in the vast majority of cases. The rollback restores system files to their previous working state; it isn't designed to touch your personal documents, photos, or installed programs. The risk to your files comes almost entirely from interrupting the process with a forced power-off, not from the rollback itself.

What if I already force-restarted and now it won't boot at all?

Try to reach WinRE by letting it fail to boot two or three times in a row — Windows should launch Automatic Repair on its own. If Advanced options never appears, you'll need bootable Windows installation media created on another working PC to access a functioning recovery environment.

Does this happen on Windows 10 too, or only Windows 11?

Both. The rollback mechanism and the WinRE recovery tools work the same way on Windows 10 and Windows 11; only the Settings menu labels differ slightly between the two.

Will deleting the SoftwareDistribution folder delete my files?

No. That folder only holds downloaded update files and staging data, not your personal documents or installed programs. Windows recreates it automatically the next time it checks for updates.

Do I need my BitLocker recovery key to fix this?

Only if your drive is encrypted and you need to use Command Prompt inside WinRE — Windows will prompt for the key before unlocking the drive for that tool. The graphical options in Advanced options, like Uninstall Updates, generally don't require it.

Can low disk space really cause this on its own?

Yes. Updates need free space to stage files before applying them. If the drive doesn't have enough room, the install fails partway through and rolls back — and it will fail the same way again on the next attempt unless you free up space first.

Why does the same update keep reinstalling after I uninstall it?

Windows Update will offer it again once it's marked as available, since uninstalling doesn't automatically block it from being reinstalled. Pausing updates for a week, or checking for a corrected version before you resume, is what actually stops the repeat.

Is there a way to permanently block one specific update?

Pausing updates for up to a week from Windows Update settings is the built-in option and the one most people need. It's a deferral rather than a permanent block, but combined with checking for a corrected release before resuming, it covers the practical need.

What's the difference between "Undoing changes" and "We couldn't complete the updates"?

They're two lines of the same message, shown together. "We couldn't complete the updates" states that the install failed; "Undoing changes" describes what's happening right now — the rollback in progress that gets you back to a working state.

Can I use System Restore instead of these steps?

If you have an earlier restore point from before the failed update, System Restore, available from the same WinRE Advanced options menu, can roll your system back further than the automatic update rollback does. It won't fix the underlying cause, though — you'd still want to clear the cache or check disk space before letting the update try again.

Should I download the update manually from Microsoft Update Catalog?

It's a reasonable option once you've confirmed the update file itself is the issue, since a manual download bypasses whatever mechanism corrupted the automatic one. Use it after cache-clearing hasn't worked, not as a first step.

What if Startup Repair also fails?

Move to the system file repair commands, sfc and DISM, from WinRE's Command Prompt, then to an in-place repair if you can reach the desktop. If none of that works and WinRE itself is functioning, a clean reinstall from installation media is the remaining option.

Is a clean reinstall my last resort?

Yes, for this specific problem. It's the most drastic step on the list, and it should come after cache clearing, uninstalling the update, disk space checks, and system file repair have all been tried and the loop still recurs.

Can antivirus or third-party software cause this loop?

Third-party security software can interfere with an update install if it locks files the update needs to replace. If you have such software installed and the loop persists after the steps above, temporarily disabling it before the next update attempt is worth trying.

How do I know it's fixed for good?

Once the update installs cleanly through a full restart cycle with no rollback message, and Windows Update shows it in your update history rather than pending again, you're clear. Keep an eye on the next scheduled update cycle to confirm it wasn't a one-time success.

Revision note. Written August 2026, covering Windows 11 (25H2 and 24H2) and Windows 10 22H2, including the post-EOL Consumer ESU state. Microsoft periodically changes exact menu wording and troubleshooter locations, so if a path in here has shifted by the time you read this, the underlying WinRE and cache-clearing steps still apply. If you're staring at this screen right now at midnight with a deadline in the morning, take a breath — in almost every case, this is recoverable, and you're not the first person this has happened to tonight.