You may encounter the following message after installing Windows updates:

“Undoing changes made to your computer…”

or:

“We couldn't complete the updates. Undoing changes. Don't turn off your computer.”

This normally means Windows attempted to install one or more updates, encountered a problem during installation or configuration, and is now rolling back the changes so the computer can return to its previous working state.

The message itself is therefore usually a rollback/recovery process rather than the original error.

The actual problem occurred earlier when Windows failed to successfully install or configure the update.

The issue can affect both:

• Windows 11
• Windows 10

It may happen after a cumulative update, security update, .NET update, driver update, or feature upgrade.

Common Symptoms

A computer affected by this problem may:

• Download Windows updates normally.
• Ask for a restart.
• Display “Working on updates.”
• Reach a certain percentage and restart.
• Display “Updates are underway.”
• Restart several times.
• Display “Undoing changes made to your computer.”
• Eventually boot normally after rolling back.
• Attempt the same update again later.
• Enter a repeating update/rollback cycle.
• Become stuck on the Undoing Changes screen.
• Fail to reach the Windows desktop.

One common sequence is:

Downloading Update → Installing Update → Restart → Update Fails → Undoing Changes → Restart → Windows Desktop

The update may then appear again in Windows Update.

Why Does Windows Say “Undoing Changes Made to Your Computer”?

There is no single cause. The failure can occur because of several Windows servicing, software, storage, or hardware conditions.

Common causes include:

1. Corrupted Windows Update Cache

Windows temporarily stores downloaded update files in locations including:

C:\Windows\SoftwareDistribution

If cached update files become corrupted or incomplete, installation can fail.

2. Corrupted Windows Component Store

Windows uses the component store, including WinSxS components, when installing and servicing Windows.

Component-store corruption can prevent updates from being correctly installed.

Microsoft recommends DISM for detecting and repairing Windows image/component-store corruption.

3. Corrupted Windows System Files

Damaged or missing protected Windows files can interfere with the update process.

System File Checker can detect and repair many such problems.

4. Insufficient Disk Space

Windows needs free disk space not only to download an update but also to:

• Extract installation files
• Create temporary files
• Maintain rollback information
• Install new Windows components

A nearly full C: drive can therefore cause updates or upgrades to fail.

5. Driver Compatibility Problems

An incompatible or outdated device driver can cause Windows installation or feature upgrades to roll back.

Common areas include:

• Display drivers
• Storage drivers
• Chipset drivers
• Network adapters
• Bluetooth devices
• USB devices
• Printer drivers
• Third-party storage controllers

6. Antivirus or Security Software Conflicts

Some third-party antivirus, endpoint protection, encryption, or security applications can interfere with Windows servicing operations.

This is particularly relevant during major Windows feature upgrades.

7. Windows Update Services Are Not Working Properly

Windows Update depends on several Windows services and components.

Important services include:

• Windows Update (wuauserv)
• Background Intelligent Transfer Service (BITS)
• Cryptographic Services (cryptsvc)

Problems with these services can interfere with downloading, verifying, or installing updates.

8. Damaged SoftwareDistribution or Catroot2 Data

Windows Update uses directories including:

C:\Windows\SoftwareDistribution

and:

C:\Windows\System32\catroot2

Corruption in these update-related stores can cause repeated installation failures.

9. Disk/File-System Problems

File-system errors or storage problems can prevent Windows from correctly reading or writing files during the update process.

10. Interrupted Update Installation

A Windows update can also fail if the computer:

• Loses power
• Is forcefully shut down
• Runs out of battery
• Crashes
• Experiences storage errors
• Is interrupted during a critical update stage

Laptop users should normally keep the AC adapter connected while installing significant Windows updates.

IMPORTANT: First Allow Windows to Finish Undoing Changes

If the screen currently says:

“Undoing changes made to your computer…”

do not immediately force the computer off.

Windows may legitimately need time to restore the previous configuration.

The process can sometimes take a significant amount of time depending on:

• Update size
• SSD/HDD performance
• Computer speed
• Number of changes being rolled back
• System corruption
• Available disk space

If the disk activity indicator is active or the system periodically restarts, Windows may still be processing the rollback.

Repeatedly forcing shutdowns during Windows servicing can make the situation worse.

Solution 1: Restart Windows and Try Windows Update Again

If Windows successfully returns to the desktop, start with the simplest approach.

Restart the computer once manually.

Then open:

Settings → Windows Update

Select:

Check for updates

Install the available updates again.

A temporary installation problem may disappear after a clean restart.

If the same update fails repeatedly, continue with the solutions below.

Solution 2: Check Available Disk Space

Open:

File Explorer → This PC

Check the available space on Local Disk (C:).

If the system drive is nearly full, remove unnecessary files before attempting the update again.

You can also use:

Settings → System → Storage

Consider removing:

• Temporary files
• Recycle Bin contents
• Old downloads you no longer require
• Unnecessary applications
• Temporary Windows files

Do not randomly delete files from:

C:\Windows

or:

C:\Windows\WinSxS

Manually deleting Windows servicing files can damage Windows.

Solution 3: Run the Windows Update Troubleshooter

On current Windows 11 systems, Microsoft recommends beginning Windows Update troubleshooting through the Get Help troubleshooting experience.

You can also check:

Settings → System → Troubleshoot → Other troubleshooters

Locate:

Windows Update

and run the available troubleshooter.

Allow Windows to detect and attempt to correct update-related problems.

Restart the computer afterward.

Then check Windows Update again.

Solution 4: Repair Windows with DISM

DISM — Deployment Image Servicing and Management — can repair corruption in the Windows component store.

Open:

Command Prompt → Run as administrator

Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait until the process completes.

Do not close Command Prompt simply because the percentage appears to stop moving temporarily.

DISM can take considerable time on some systems.

A successful operation should report that the restore operation completed successfully.

Microsoft documents DISM /RestoreHealth as a supported method for repairing component-store corruption associated with Windows Update installation failures.

Solution 5: Run System File Checker

After DISM completes successfully, run:

sfc /scannow

Wait until:

Verification 100% complete

SFC may report one of several results.

Result 1

Windows Resource Protection did not find any integrity violations.

No protected Windows system-file corruption was detected.

Result 2

Windows Resource Protection found corrupt files and successfully repaired them.

Restart Windows and try Windows Update again.

Result 3

Windows Resource Protection found corrupt files but was unable to fix some of them.

Further repair may be required.

You can investigate:

C:\Windows\Logs\CBS\CBS.log

For Windows Update-related corruption, the recommended sequence is generally:

DISM.exe /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

Solution 6: Reset Windows Update Components

If updates continue failing, rebuilding the Windows Update cache is one of the most useful advanced troubleshooting procedures.

Open Command Prompt as Administrator.

Stop the relevant services:

net stop wuauserv

net stop bits

net stop cryptsvc

Rename the update-cache folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

Restart the services:

net start cryptsvc

net start bits

net start wuauserv

Restart Windows.

Then open:

Settings → Windows Update → Check for updates

Windows will recreate the necessary update-cache structures.

Microsoft documents resetting SoftwareDistribution and Catroot2 as part of Windows Update troubleshooting.

Important: Rename these folders rather than manually deleting arbitrary Windows files.

Solution 7: Check the Windows Component Store

For additional diagnostics, open Command Prompt as Administrator and run:

DISM /Online /Cleanup-Image /CheckHealth

This performs a quick check for previously detected component-store corruption.

For a deeper scan:

DISM /Online /Cleanup-Image /ScanHealth

If corruption is detected and repairable, run:

DISM /Online /Cleanup-Image /RestoreHealth

Then:

sfc /scannow

Restart Windows.

Solution 8: Check the System Drive for Errors

Open Command Prompt as Administrator.

Run:

chkdsk C: /f

If Windows reports that the volume is currently in use and asks whether you want to schedule the check for the next restart, enter:

Y

Restart the computer.

CHKDSK will check and repair supported file-system problems.

If the machine repeatedly develops file corruption, however, also investigate the health of the SSD/HDD rather than assuming Windows Update itself is the only problem.

Solution 9: Disconnect Unnecessary External Hardware

Before attempting the update again, temporarily disconnect unnecessary external devices such as:

• USB storage drives
• External hard disks
• Unnecessary printers
• USB adapters
• Card readers
• Docking devices
• Other unnecessary peripherals

Keep essential devices connected, such as:

• Keyboard
• Mouse
• Display
• Network connection where required

This is particularly useful when troubleshooting major Windows upgrades where a device or driver may cause compatibility problems.

Solution 10: Temporarily Remove Third-Party Security Conflicts

Third-party antivirus or endpoint-security software can occasionally interfere with Windows upgrades.

If you suspect this is happening, verify that the security product is compatible with your Windows version and fully updated.

For troubleshooting, it may sometimes be necessary to temporarily uninstall conflicting third-party security software and retry the update.

Important: Do this only when you understand the security implications and know how to reinstall/reactivate the product afterward.

Do not leave a business or production computer unnecessarily unprotected.

Solution 11: Perform a Clean Boot

A clean boot can help determine whether third-party services or startup software are interfering with Windows Update.

Press:

Windows + R

Enter:

msconfig

Open the Services tab.

Select:

Hide all Microsoft services

This step is extremely important.

Then disable unnecessary third-party services for troubleshooting.

Open:

Task Manager → Startup apps

Temporarily disable unnecessary startup applications.

Restart Windows and attempt the update.

After testing, restore the normal startup configuration.

Solution 12: Identify Which Update Is Failing

Instead of repeatedly troubleshooting Windows Update generally, determine exactly which update is failing.

Open:

Settings → Windows Update → Update history

Look for:

Failed to install

Record the KB number, for example:

KBxxxxxxx

Also record any error code displayed by Windows.

Examples might include:

• 0x80070002
• 0x80070003
• 0x80070005
• 0x8007000D
• 0x80070020
• 0x80070057
• 0x80070570
• 0x80070643
• 0x80073701
• 0x80073712
• 0x800F081F
• 0x800F0831
• 0x800F0922

The error code can dramatically narrow the troubleshooting process.

Solution 13: Manually Install the Problematic Update

If Windows Update repeatedly fails on one particular KB update, search for that KB in the official Microsoft Update Catalog.

Download the package matching your:

• Windows version
• Architecture
• Update type

For most modern PCs, the architecture is typically x64, but always verify before downloading.

Install the update manually and restart the computer.

This can sometimes work when automatic Windows Update delivery is malfunctioning.

Solution 14: Update Important Device Drivers

Driver-related failures are particularly important when a feature update or major Windows upgrade is rolling back.

Check the computer manufacturer's support website for current:

• BIOS/UEFI
• Chipset driver
• Storage controller driver
• Graphics driver
• Network driver
• Bluetooth driver

For branded computers, prefer drivers intended for the exact model.

Be particularly careful with BIOS/UEFI updates.

A firmware update should not be interrupted by loss of power.

Solution 15: Uninstall the Latest Problematic Update

If Windows boots but problems began immediately after installing a particular update, you may be able to uninstall it.

Go to:

Settings → Windows Update → Update history

Look for:

Uninstall updates

Select the relevant removable update and uninstall it.

Restart Windows.

Not every update can necessarily be removed.

Also remember that uninstalling a security update should generally be treated as a temporary troubleshooting measure rather than a permanent solution.

What If Windows Cannot Reach the Desktop?

The troubleshooting strategy changes when the PC is trapped in:

Installing Updates → Restart → Undoing Changes → Restart

and never reaches Windows.

In this case, use the Windows Recovery Environment.

Solution 16: Enter Windows Recovery Environment

Windows may automatically enter recovery after repeated failed startup attempts.

You may see:

Preparing Automatic Repair

followed by:

Advanced options

From there select:

Troubleshoot → Advanced options

You may have options including:

• Startup Repair
• Startup Settings
• Command Prompt
• Uninstall Updates
• System Restore

Available options can differ depending on the Windows installation and recovery environment.

Solution 17: Uninstall the Latest Update from Recovery

From Windows Recovery Environment:

Troubleshoot → Advanced options → Uninstall Updates

Windows may offer options such as:

Uninstall latest quality update

or:

Uninstall latest feature update

If the computer stopped booting immediately after an update, removing the latest problematic update can allow Windows to boot again.

Solution 18: Try Safe Mode

From Recovery Environment select:

Troubleshoot → Advanced options → Startup Settings → Restart

Choose the appropriate Safe Mode option.

If Windows boots in Safe Mode, you can investigate:

• Recently installed drivers
• Security applications
• Startup applications
• Failed Windows updates
• System corruption

You can also back up important data before attempting more invasive repair operations.

Solution 19: Use System Restore

If System Restore was enabled and a suitable restore point exists:

Troubleshoot → Advanced options → System Restore

Choose a restore point created before the update problem started.

System Restore can revert system files, registry settings, drivers, and certain installed software changes while generally preserving personal documents.

However, applications or drivers installed after the selected restore point may need to be reinstalled.

Solution 20: Advanced Recovery – Revert Pending Actions

For severely stuck servicing operations, DISM includes the advanced /RevertPendingActions capability for recovery scenarios.

Microsoft documents the DISM option:

DISM /Image:<offline-Windows-path> /Cleanup-Image /RevertPendingActions

This is an advanced recovery procedure intended for an offline Windows image.

It should not be blindly copied as an online repair command.

In Windows Recovery Environment, Windows drive letters may also differ from their normal assignments.

For example, your normal:

C:\Windows

installation might appear as:

D:\Windows

inside recovery.

Therefore, identify the correct Windows partition before using offline DISM commands.

This procedure is best reserved for experienced administrators or technicians.

Solution 21: If DISM Reports “Source Files Could Not Be Found”

DISM normally attempts to obtain repair content using the configured Windows repair source, which may include Windows Update.

If it cannot obtain the required files, you may encounter errors such as:

0x800f081f

In this situation, DISM can use a compatible Windows image as a repair source.

Microsoft supports using /Source together with /RestoreHealth.

Example concept:

DISM /Online /Cleanup-Image /RestoreHealth /Source:<repair-source> /LimitAccess

The repair source must be appropriate for the Windows installation being repaired.

Using the wrong:

• Windows version
• Edition
• Architecture
• Build/source

can cause repair operations to fail.

This is an advanced repair procedure.

Solution 22: Check CBS and DISM Logs

For persistent failures, technicians should examine Windows servicing logs.

Important locations include:

C:\Windows\Logs\CBS\CBS.log

and:

C:\Windows\Logs\DISM\dism.log

These logs can reveal:

• Missing components
• Corrupt manifests
• Package failures
• Servicing errors
• Access-denied errors
• Component-store problems

For business environments or repeatedly failing systems, log analysis is much more useful than repeatedly running random repair commands.

Solution 23: Perform an In-Place Repair Installation

If:

• DISM does not permanently solve the problem
• SFC continues detecting corruption
• Windows Update repeatedly fails
• Update components have already been reset
• Windows still operates sufficiently to run Setup

consider an in-place repair installation using appropriate Windows installation media.

A repair installation can reinstall core Windows components while preserving supported:

• Personal files
• Applications
• User accounts
• Many system settings

Back up important data before performing any operating-system repair or upgrade.

Solution 24: Reset or Reinstall Windows as a Last Resort

If Windows remains badly damaged despite all troubleshooting, the final options may include:

Reset this PC

or a clean Windows installation.

Before proceeding, back up:

• Documents
• Desktop
• Downloads
• Browser data
• Email data
• Application databases
• Accounting data
• Software licenses
• Product keys
• Certificates
• Encryption/recovery keys
• Business data

For business PCs, verify backups before resetting or reinstalling Windows.

Recommended Troubleshooting Sequence

For most computers that can still boot into Windows, use this order:

1. Restart Windows

↓

2. Check free disk space

↓

3. Run Windows Update troubleshooter

↓

4. Run DISM

DISM.exe /Online /Cleanup-Image /RestoreHealth

↓

5. Run SFC

sfc /scannow

↓

6. Restart Windows

↓

7. Retry Windows Update

↓

8. If it fails again, identify the KB number and error code

↓

9. Reset Windows Update components

↓

10. Retry the update

↓

11. Check disk and important drivers

↓

12. Try manual installation of the failing update

↓

13. Consider clean boot

↓

14. Analyze CBS/DISM logs

↓

15. Consider an in-place repair installation

This sequence moves from lower-risk troubleshooting toward more advanced repair.

Recommended Troubleshooting Sequence When Windows Will Not Boot

If the PC cannot reach the desktop:

Windows Recovery Environment

↓

Advanced Options

↓

Uninstall latest problematic update

↓

Try Safe Mode

↓

Try System Restore

↓

Use advanced offline servicing only if necessary

↓

Repair/reinstall Windows if recovery fails

Always protect important data before major recovery operations.

Commands Quick Reference

Repair Windows Component Store

DISM.exe /Online /Cleanup-Image /RestoreHealth

Check System Files

sfc /scannow

Check Component Store

DISM /Online /Cleanup-Image /CheckHealth

Deep Component Store Scan

DISM /Online /Cleanup-Image /ScanHealth

Check C: Drive

chkdsk C: /f

Stop Windows Update Service

net stop wuauserv

Stop BITS

net stop bits

Stop Cryptographic Services

net stop cryptsvc

Rename Windows Update Cache

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

Rename Catroot2

ren C:\Windows\System32\catroot2 catroot2.old

Restart Services

net start cryptsvc

net start bits

net start wuauserv

Important Precautions

Before performing advanced Windows Update repair:

Back Up Important Data

Especially on business computers.

Keep Laptops Connected to Power

Do not perform major Windows updates on a nearly discharged battery.

Do Not Randomly Delete WinSxS

Never manually delete:

C:\Windows\WinSxS

to free disk space.

The component store is essential to Windows servicing.

Do Not Interrupt DISM or Windows Servicing Without Reason

Some operations can appear stalled while they continue processing.

Record the Error Code

A specific error such as:

0x800f081f

is much more useful diagnostically than simply knowing “Windows Update failed.”

Verify Storage Health When Corruption Repeats

Repeated corruption can indicate a deeper problem involving storage, memory, drivers, or unexpected shutdowns.

Frequently Asked Questions (FAQ)

1. What does “Undoing changes made to your computer” mean?

It generally means Windows could not successfully complete an update and is reverting the changes made during the failed installation.

2. Is “Undoing Changes” itself an error?

Not necessarily.

It is usually the recovery or rollback phase following an update failure. The important task is identifying why the update failed in the first place.

3. How long does “Undoing changes made to your computer” take?

There is no fixed duration.

It depends on the update, computer performance, storage speed, system condition, and number of changes being reverted.

Avoid interrupting the process simply because it is taking longer than expected.

4. Should I turn off the computer while it says “Undoing Changes”?

Normally, no.

Allow Windows sufficient time to complete its rollback. Forced shutdown during Windows servicing can create additional problems.

5. Will undoing changes delete my personal files?

Normally, Windows is rolling back the failed update rather than deleting personal documents.

Nevertheless, maintain regular backups because unexpected system or storage failures can always create data-loss risk.

6. Why does the same Windows update keep failing?

Possible causes include:

• Corrupted update cache
• Component-store corruption
• Damaged system files
• Insufficient storage
• Driver incompatibility
• Security software conflicts
• File-system problems
• A problem specific to the update or machine configuration

Check Update history for the failing KB number and error code.

7. What does DISM /RestoreHealth do?

DISM /Online /Cleanup-Image /RestoreHealth

checks the Windows image/component store for corruption and attempts to repair detected problems.

8. What does SFC /scannow do?

System File Checker verifies protected Windows system files and attempts to replace corrupted files with valid copies.

9. Should I run SFC or DISM first?

For update-related component corruption, a useful supported sequence is:

DISM.exe /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

DISM repairs the Windows image/component store that SFC may rely on for healthy replacement files.

10. Is it safe to rename SoftwareDistribution?

Renaming the SoftwareDistribution folder is a commonly used Windows Update troubleshooting procedure when the relevant services are stopped.

Windows recreates the necessary update-cache structure.

11. Is it safe to rename Catroot2?

Renaming Catroot2 as part of a controlled Windows Update component reset is a documented troubleshooting technique.

Do not confuse:

catroot2

with other Windows system folders or randomly delete servicing files.

12. Can antivirus software cause Windows updates to fail?

It can in some cases, particularly if security software or low-level drivers conflict with an upgrade.

Use only compatible and updated security products, and reinstall protection promptly if it must be removed temporarily for troubleshooting.

13. Can low disk space cause “Undoing Changes”?

Yes.

Windows needs adequate working space for downloading, staging, installing, and potentially rolling back updates.

14. What if Windows keeps restarting and undoing changes?

Enter Windows Recovery Environment and investigate options such as:

• Uninstall Updates
• Safe Mode
• System Restore
• Startup Repair
• Advanced Command Prompt repair

15. Can I uninstall the failed Windows update?

If the update was partially or successfully installed and is removable, Windows may provide an uninstall option through Update History or Windows Recovery Environment.

Not every update is uninstallable.

16. Should I disable Windows Update permanently?

Generally, no.

Windows updates contain important security and reliability fixes. The better approach is to identify and resolve the underlying reason updates are failing.

17. What if DISM gets stuck at a percentage?

DISM may remain at the same displayed percentage for some time while still working.

Allow it sufficient time unless there is strong evidence that the process has genuinely stopped.

18. What if DISM gives error 0x800f081f?

This commonly indicates that required repair source files could not be located.

You may need a compatible Windows repair source and the DISM /Source option.

19. Where can I find detailed Windows Update repair information?

Useful Microsoft resources include Microsoft Support's Windows Update troubleshooting guidance and Microsoft Learn's Windows servicing documentation.

Microsoft's current Windows Update troubleshooting guidance:
https://support.microsoft.com/windows/deployment/updates-lifecycle/troubleshoot-problems-updating-windows

Microsoft Learn Windows Update corruption troubleshooting:
https://learn.microsoft.com/troubleshoot/windows-server/installing-updates-features-roles/fix-windows-update-errors

20. What should I do if none of these solutions work?

If Windows Update continues failing after:

• Troubleshooter
• DISM
• SFC
• Update component reset
• Disk checking
• Driver checking
• Clean boot
• Manual update installation

consider analyzing the CBS/DISM logs and performing an in-place Windows repair installation.

A full reset or clean installation should normally be reserved for situations where less destructive repair methods have failed.

Conclusion

The “Undoing Changes Made to Your Computer” message usually appears because Windows could not successfully complete an update and has started rolling the system back to its previous configuration.

The message should therefore be treated as a symptom rather than the root cause.

For most systems, the most effective troubleshooting path is:

Check disk space → Windows Update Troubleshooter → DISM → SFC → Restart → Retry Update → Reset Windows Update Components → Identify failing KB/error code → Check drivers/disk → Manual update → Advanced repair if necessary.

If the computer cannot boot normally, use Windows Recovery Environment to remove the problematic update, start Safe Mode, use System Restore, or perform other recovery procedures.

Avoid immediately reinstalling Windows. Many cases can be repaired without deleting applications or personal data.

50 #Tags

#WindowsUpdate #UndoingChanges #UndoingChangesMadeToYourComputer #Windows11 #Windows10 #WindowsUpdateError #WindowsUpdateFailed #WindowsUpdateFix #WindowsTroubleshooting #WindowsRepair #UpdateFailed #UpdateRollback #WindowsRollback #WindowsBootLoop #WindowsRecovery #DISM #DISMRestoreHealth #SFC #SFCScannow #SystemFileChecker #WindowsUpdateTroubleshooting #WindowsUpdateRepair #WindowsUpdateComponents #SoftwareDistribution #Catroot2 #WindowsUpdateCache #WindowsCorruption #SystemFileRepair #ComponentStore #WinSxS #WindowsUpdateService #BITS #CryptographicServices #WindowsSafeMode #WindowsRecoveryEnvironment #WindowsStartupRepair #SystemRestore #WindowsUpdateLoop #WindowsUpdateStuck #WindowsUpdateProblem #Windows11Troubleshooting #Windows10Troubleshooting #WindowsUpdateCommands #CHKDSK #MicrosoftWindows #PCRepair #ComputerRepair #ITSupport #WindowsSupport #TechSupport