Fix “We Couldn't Complete the Updates, Undoing Changes”

“We Couldn't Complete the Updates, Undoing Changes” means Windows failed to install an update and is restoring the previous system state. Let that rollback finish; if Windows reaches the desktop, run the Windows Update troubleshooter, clear the update cache, repair system files, and retry the update. If Windows loops or never reaches the desktop, use Windows Recovery Environment to repair startup or remove the latest update before considering a reset.

Is Windows actually stuck, or should you keep waiting?

We Couldn't Complete the Updates, Undoing Changes

Windows shows this message when an update cannot be applied. It reverses the partial installation so the previous Windows installation can start again. Your personal files normally remain untouched.

Leave the computer connected to power while the rollback runs. Watch for a blinking disk-activity light or occasional screen changes. A normal rollback can take several minutes and sometimes considerably longer, especially after a large feature update or on a slow storage drive. Do not interrupt it only because the percentage has stopped moving.

A forced restart is reasonable when the computer has shown no visible activity for a prolonged period, the display is frozen, or it repeatedly returns to the same message after completing a restart. Hold the power button until the computer turns off, wait briefly, and turn it on once. Do not repeatedly interrupt startup; doing so can leave recovery incomplete.

If Windows starts Automatic Repair, let it finish. If Windows cannot reach the desktop, you can deliberately open Windows Recovery Environment: turn the computer on and, when the Windows logo appears, hold the power button to turn it off. Repeat this interruption until recovery options appear. Choose Advanced options, not a reset, as the first step.

Which fix applies to your situation?

These steps apply to supported Windows 10 and Windows 11 installations. Most repair commands require an Administrator account. Restarts are required at several points. Back up important files before making recovery changes, particularly before using Reset this PC.

Start with these safe checks:

• Disconnect unnecessary USB drives, docks, printers, external hard drives, and other accessories. Leave the keyboard, mouse, display, and network connection attached.
• Check the Windows drive for adequate free space. Open File Explorer, select This PC, and inspect the system drive, usually C:. A nearly full drive can prevent an update from unpacking and rolling back correctly.

Use the desktop path if Windows starts normally. Use the recovery path if it restarts repeatedly, shows Automatic Repair, or never reaches the sign-in screen. If the failure began immediately after a monthly security or quality update, remove the latest quality update. If it followed a major version upgrade, use the feature-update option. A driver change may require rolling back that driver after Windows starts.

Fix the update in the safest order

Start with the least invasive action and stop when Windows Update works again. Do not delete random files from C:\Windows or use a registry cleaner.

1. If Windows has returned to the desktop, restart it normally. Remove unnecessary devices first, connect the computer to reliable power, and confirm that the internet connection is stable. If Windows does not reach the desktop, skip to the recovery steps in “How to prevent another failed update and recover from a boot loop.”
2. Run the built-in Windows Update troubleshooter. Open Settings and run it from this path:

Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run

On some Windows 10 installations, use:

Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update

Apply any recommended repair and restart. A successful run applies the listed repair; if the troubleshooter reports that it could not fix the problem, continue to the next step rather than repeating it indefinitely.

3. Clear the Windows Update cache from an elevated Command Prompt. Open Start, type Command Prompt, select Run as administrator, and approve the prompt. Stop the update services, rename the cache folders, and start the services again:

net stop wuauserv
net stop bits
net stop cryptsvc
ren %windir%\SoftwareDistribution SoftwareDistribution.old
ren %windir%\System32\catroot2 catroot2.old
net start cryptsvc
net start bits
net start wuauserv

Windows recreates fresh cache folders after the old folders are renamed. Renaming is safer than deleting because the old folders remain available. If a service refuses to stop, close Settings and update-related tools, restart, and run the commands again. If the folders cannot be renamed, continue to the repair commands below; the cache was not cleared.

4. Remove the failed update if it is listed. In Windows, open:

Settings > Windows Update > Update history > Uninstall updates

Select the most recent update associated with the failure, usually a quality update, and choose Uninstall. Do not remove several updates at once. Restart and test Windows. If the update is not listed or cannot be removed from Settings, use Windows Recovery Environment:

Troubleshoot > Advanced options > Uninstall Updates > Uninstall latest quality update

If the failure followed a major Windows version upgrade, choose Uninstall latest feature update instead. If Windows still cannot start, continue with the recovery options in the final section.

5. Repair the component store and protected system files from an elevated Command Prompt. Run each command separately and wait for it to finish:

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

DISM repairs the Windows component store that supplies replacement files. sfc then checks and repairs protected system files. The expected SFC result is Windows Resource Protection did not find any integrity violations or a message saying it found and repaired corrupted files. If DISM reports that source files could not be found, make sure Windows Update is working and the computer is online, then run it again. If SFC says some files could not be repaired, restart and run sfc /scannow once more. If the commands complete without an error, continue to the next step.

6. Retry Windows Update after the cache has been rebuilt and repairs have completed. Install only the pending update, not several optional drivers or applications at the same time. Let the restart finish without powering off the computer. If the update fails again, record its name or error code instead of repeatedly forcing restarts.

How to confirm Windows is fixed before trying again

After the rollback or repair, confirm that Windows completes a full shutdown and startup. Sign in, open several normal applications, and check that your Desktop, Documents, Pictures, and other personal folders still contain their files. The rollback should not remove personal files, but keep a backup before further recovery work.

Check the update history here:

Settings > Windows Update > Update history

A failed entry can remain in history after the problem is fixed. What matters is that the current update is no longer pending and Windows does not immediately request another rollback.

Run Windows Update and install the pending update once. After the restart, return to Update history and confirm that the update has a successful status. Run winver from Start to confirm that Windows opens normally, then open the applications and folders you use most. If the same update fails again, record its knowledge-base identifier, such as KB followed by numbers, and the displayed error code before trying another change.

Prevent another failed update and recover from a boot loop

Before retrying a large update, connect the computer to dependable power and use a stable internet connection. Keep adequate free space on the Windows drive, remove unnecessary temporary files, and do not start an update while the drive is nearly full. Install current manufacturer drivers, especially storage, chipset, graphics, and network drivers, but avoid installing several optional drivers at the same time as the Windows update.

Back up important documents, photos, browser data, and application files to another drive or a trusted backup service. A restore point is useful for system changes, but it is not a substitute for a separate copy of personal files.

If Windows is trapped in a restart loop or will not reach the desktop, enter Windows Recovery Environment and use these options in order:

1. Choose Troubleshoot > Advanced options > Startup Repair. Let it diagnose and repair boot problems, then restart. If Windows reaches the desktop, test the computer before attempting the update again.
2. If Startup Repair does not help, choose Troubleshoot > Advanced options > Uninstall Updates. Try Uninstall latest quality update first. Use Uninstall latest feature update only when the failure began during or immediately after a major Windows version upgrade. Restart and check whether Windows reaches the desktop.
3. If the problem began after a driver or other system change, choose System Restore and select a restore point from before that change. System Restore normally preserves personal files but can remove recently installed drivers and applications. Restart after the restore completes.
4. If recovery tools still cannot start Windows, choose Startup Settings > Restart, then choose Safe Mode. In Safe Mode, uninstall the failed update from Update history, roll back a recently changed driver in Device Manager, and run DISM and SFC from an elevated Command Prompt. Restart normally to test the result.
5. Use Reset this PC only after the repair and recovery options fail.

Read the reset choices carefully and back up your data first. Keep my files preserves personal files but removes applications and settings. Do not choose Remove everything unless you have deliberately backed up your data and intend to erase the installation.

If BitLocker asks for a recovery key, retrieve it from the Microsoft account or organization that manages the computer before changing recovery settings. Without the key, encrypted data may not be accessible through offline repair.

Conclusion

Let the rollback finish while Windows is still making progress. If the desktop returns, run the troubleshooter, rebuild the update cache, repair Windows with DISM and SFC, and retry the update once. If Windows still cannot start, use Startup Repair, System Restore, or the latest quality or feature update removal before considering a reset.

Frequently Asked Questions

Will “Undoing Changes” delete my personal files?

A normal Windows Update rollback is designed to restore system files and normally leaves personal files alone. Back up important data before using recovery tools, especially before a reset or offline repair.

Can I turn off the computer while this message is displayed?

Avoid turning it off while the rollback is visibly progressing. If the screen is frozen for a prolonged period or the computer repeatedly loops, one forced shutdown is reasonable; then use Windows Recovery Environment instead of repeatedly powering it off.

Why does the same update keep failing?

Common causes include insufficient free space, a damaged update cache, corrupted system files, incompatible drivers, unstable power or internet, and software that interferes with installation. Clear the cache, run DISM and SFC, check storage and drivers, then retry once. If it fails again, record the KB identifier and error code.