Stuck on 'Undoing Changes Made to Your Computer' in Windows 11? How to Break the Loop

You shut down or rebooted after a Windows update, and now the screen reads "Undoing changes made to your computer" with a spinning circle that never seems to end. This message appears when a cumulative or feature update fails to install, and Windows rolls the partial install back to a working state. In most cases the rollback finishes on its own and you boot normally. The trouble starts when the process stalls for hours or returns the same failure every time the machine restarts. This guide explains when to wait, when to intervene, and how to stop the loop for good.

Key takeaways

• "Undoing changes" is a normal rollback after a failed update, give it 30 to 60 minutes before assuming it is stuck.
• Low disk space, a corrupt update cache, and bad system files are the usual reasons an update fails repeatedly.
• If the loop persists, boot into Safe Mode, then repair system files and reset Windows Update components.
• A pending update that keeps failing can be removed from Windows Recovery Environment (WinRE) without a full reinstall.

Here is why the update keeps failing and which fix targets each cause:

Cause	Symptom	Fix
Update still rolling back	No progress but disk light flickers	Wait 45 to 60 minutes
Corrupt system files	Same update fails every attempt	DISM then SFC (Fix 3)
Poisoned update cache	Same broken package re-downloads	Reset Update components (Fix 4)
Low disk space	Feature update cannot stage	Free up 20 GB or more (Fix 5)
One bad KB	Loop tied to a single update	Uninstall from WinRE, pause updates (Fix 6)

First: is it actually stuck?

The rollback writes files back in the background, and the screen can sit on the same message with no visible progress for a long time. Before you do anything drastic:

• Wait at least 45 to 60 minutes. A large feature update on a slow mechanical drive can take that long to unwind.
• Watch the hard-drive activity light if your machine has one. Occasional flickering means work is still happening.
• Do not pull the power mid-rollback unless the screen has been frozen, with zero disk activity, for well over an hour. Interrupting a rollback can corrupt the boot files.

Fix 1: Force into the recovery environment

If the loop will not end, you need to interrupt it deliberately to reach the recovery tools.

1. Hold the power button for 10 seconds to force a shutdown.
2. Press the power button to turn it back on.
3. As soon as you see the Windows logo or spinner, hold the power button down again to force another shutdown.
4. Repeat this two or three times. After the third failed boot, Windows launches Automatic Repair, which leads to Windows Recovery Environment.
5. Choose Advanced options to reach the troubleshooting menu.

Fix 2: Boot into Safe Mode

Safe Mode loads Windows with the minimum drivers and lets the rollback complete in a stripped-down environment.

1. From Advanced options, select Startup Settings, then Restart.
2. When the list appears, press 5 or F5 for Safe Mode with Networking.
3. Let Windows boot. If it reaches the desktop, the immediate crisis is over.
4. Reboot once normally to confirm it boots without the loop.

Fix 3: Repair system files

Corrupt system files often cause the same update to fail on every attempt. Run these from an elevated Command Prompt, either inside Safe Mode or from Advanced options > Command Prompt.

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM repairs the underlying component store that SFC relies on, so run it first. If you are working from WinRE where there is no running OS, point DISM at your offline image instead:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

Fix 4: Reset Windows Update components

A poisoned update cache makes the same broken package download and fail over and over. Clearing it forces a clean re-download.

1. Open an elevated Command Prompt.
2. Stop the services:

   net stop wuauserv
   net stop bits
   net stop cryptsvc
   

3. Rename the cache folders so Windows rebuilds them:

   ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
   ren %systemroot%\System32\catroot2 catroot2.old
   

4. Restart the services:

   net start wuauserv
   net start bits
   net start cryptsvc
   

5. Reboot and check for updates again.

This is the same component-reset that resolves many install errors, including the 0x80073712 and 0x800f0993 update failures that share the same corrupt-cache root cause.

Fix 5: Free up disk space

A feature update needs several gigabytes of free space to stage and apply. If your system drive is nearly full, the install will fail and roll back endlessly.

• From Safe Mode, open Settings > System > Storage and run Storage Sense or Cleanup recommendations.
• Delete the Windows.old folder and previous update files through Disk Cleanup (run cleanmgr and tick Windows Update Cleanup).
• Aim for at least 20 GB free before retrying a feature update.

Fix 6: Uninstall the failing update from WinRE

If a single specific update keeps breaking, remove it without reinstalling Windows.

1. From Advanced options, choose Uninstall Updates.
2. Select Uninstall latest quality update (or feature update if a version upgrade triggered the loop).
3. Confirm and let Windows remove it, then reboot.

After it boots cleanly, pause updates for a week in Settings > Windows Update so the same broken package does not immediately reinstall. Microsoft frequently reissues a fixed version within days.

Last resort: reset this PC

If repairs and component resets all fail, use Advanced options > Reset this PC and choose Keep my files. This reinstalls Windows while preserving documents, though installed apps are removed. A boot-time reset like this overlaps with the recovery paths for deeper boot failures such as INACCESSIBLE_BOOT_DEVICE, so if the loop is paired with a blue screen, start there.

Frequently asked questions

How long should I wait before assuming it is stuck?

Give it a solid 45 to 60 minutes. Large feature updates on slower drives genuinely take that long to roll back. Only intervene if the screen has shown no disk activity and no progress for well over an hour.

Will I lose my files in this loop?

No. The rollback is designed to return your system to its pre-update state, so your personal files are untouched. Even a "Reset this PC" with Keep my files preserves your documents, though it removes installed applications.

Why does the same update keep failing?

The most common reasons are insufficient free disk space, a corrupt update cache in SoftwareDistribution, or damaged system files. Fixes 3, 4, and 5 target all three. If one specific KB is at fault, uninstall and hide it until Microsoft reissues a corrected build.

Is it safe to force a power-off?

Only when you are confident the rollback is genuinely frozen, no disk activity for an hour or more. Interrupting an active rollback can corrupt boot files and make the system unbootable, which is harder to recover from than the loop itself.

Quick recap

Wait the rollback out first. If the loop persists, force your way into recovery, boot Safe Mode, then repair system files, reset the update cache, and free up disk space. As a targeted fix, uninstall the specific failing update from WinRE and pause updates until Microsoft ships a corrected version.