Troubleshooting “Windows Update says undoing changes made to your computer” is a diagnostic exercise before it is a repair exercise. The screen is a symptom with many diseases behind it, and the technicians who fix it fastest are not the ones with the most tools — they are the ones who observe first and act second. This walkthrough teaches that method: what to check, what each finding means, and which fix each finding earns.

The mental model to carry: Windows installs updates as transactions. The rollback screen means a transaction failed and is being reversed. Your troubleshooting goal is to find out why the transaction failed, because the reversal itself is healthy behavior. Every check below either names the cause or rules one out, and the fixes are attached to findings rather than thrown at the wall.

Gather your evidence before changing anything. If the rollback is currently running, observe it. If you are on the desktop, open Update history. Write down the KB number, the error code, the free space on C:, and whether the disk light shows activity. Those four data points drive every decision that follows.

Why this happens

  • Corrupted staged downloads: the update cache holds a package that fails integrity verification.
  • Component store corruption: WinSxS damage that prevents staging of any new components.
  • Driver migration failure: a driver that cannot move to the new build, aborting the transaction.
  • Disk space exhaustion: the update plus rollback snapshot exceeding available room mid-install.
  • Security software interference: file locks from kernel-level suites during installation.
  • Firmware prerequisite failure: outdated BIOS failing the update’s preflight checks.
  • Servicing stack inconsistency: leftover state from a previous incomplete update.
  • Defective update package: a KB with a genuine bug affecting specific hardware.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Triage — is the rollback running, and what failed?

Every troubleshooting session starts with triage. Spend ten minutes here and save hours later.

  1. If the rollback screen is up: confirm AC power, watch the disk light for 15 minutes. Blinking means working — wait it out.
  2. On the desktop, open Update history and record the KB number and error code.
  3. Check free space on C: in Settings, then System, then Storage.
  4. Open Reliability Monitor (search for it in Start) and find the exact failure timestamp and any accompanying driver failures.
  5. With these four facts, you can now match cause to fix instead of guessing. For a frozen screen specifically, the frozen rollback recovery guide is the right branch.

Fix 2: Read the Windows Update log

When the error code is vague, the log names the failing component.

  1. Open PowerShell as administrator and run Get-WindowsUpdateLog.
  2. Open the generated log file on your desktop in Notepad.
  3. Search for “failed” and “error” near the update’s timestamp.
  4. Note which component failed — download, staging, driver migration, or reboot phase.
  5. Match the phase to the fix: download failures mean cache reset, migration failures mean drivers, staging failures mean DISM. Microsoft’s update support documentation explains the log structure.

Fix 3: Reset the update cache (for download and integrity failures)

The standard cure for corrupt staged packages and poisoned update metadata.

  1. Open Command Prompt as administrator.
  2. Run net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  3. Rename C:\Windows\SoftwareDistribution to SoftwareDistribution.old and C:\Windows\System32\catroot2 to catroot2.old.
  4. Restart the services and reboot.
  5. Re-run Windows Update and verify the package downloads fresh.

Fix 4: Repair the component store (for staging failures)

When the log points at staging or the store, DISM and SFC rebuild the foundation.

  1. In an elevated Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth.
  2. Allow 10 to 30 minutes for completion.
  3. Run sfc /scannow afterward.
  4. Reboot and retry the update.
  5. If the troubleshooter also needs attention, the troubleshooter repair guide covers it.

Fix 5: Address driver migration failures

When the evidence implicates a driver, refresh the driver stack from the authoritative source.

  1. Identify the suspect device from the log or Device Manager warning icons.
  2. Download the current driver from your laptop manufacturer’s support site — not from Windows Update.
  3. Uninstall the old driver in Device Manager, reboot, and install the fresh package.
  4. Update the BIOS if firmware is several versions behind.
  5. Retry the Windows update and confirm the migration completes.

Fix 6: Resolve space and interference findings

For the environmental causes your triage already measured.

  1. If C: is under 20 GB free, run Disk Cleanup as administrator with system-files options until it is not.
  2. Disconnect USB peripherals, docks, and SD cards.
  3. Temporarily disable third-party antivirus and disconnect VPNs.
  4. Retry the update in this clean state.
  5. Hide a single repeat-offender KB with the show-or-hide updates troubleshooter if everything else passes.

Fix 7: Escalate with an in-place upgrade, then verify

The final diagnostic repair: rebuild the servicing stack and confirm the finding.

  1. Download the Windows 11 ISO from the official download page .
  2. Mount it, run setup.exe, choose “Keep personal files and apps.”
  3. Allow 30 to 90 minutes for completion.
  4. Run Windows Update and confirm the previously failing package installs.
  5. Document what fixed it — the KB, the code, and the fix — so the next loop starts with answers, a habit our step-by-step undoing changes guide also recommends.

Closing

Troubleshooting is the discipline of letting evidence choose the fix. The undoing-changes screen tempts everyone to act immediately — usually by hammering the power button — but the technicians who resolve it fastest are the ones who spent the first ten minutes observing. Triage, read the log, match the phase to the repair, verify after each step. That method does not just fix this loop; it fixes the next one faster too.

Frequently asked questions

What should I check first when troubleshooting this error?
Check three things before anything else: whether the rollback is still actively running (disk activity light), the failed KB number and error code in Update history, and free space on C:. Those three facts eliminate half the possible causes immediately. A working rollback needs patience, a 0x800f0922 code points at disk space, and a full drive explains itself — diagnosis first, tools second.
Which Windows logs help troubleshoot update rollbacks?
The most useful is the Windows Update log, generated by running Get-WindowsUpdateLog in PowerShell, which aggregates the servicing events into a readable file on your desktop. The Event Viewer under Windows Logs, then System, filtered for the WindowsUpdateClient source, shows the failure entries with error codes. Reliability Monitor also gives a timeline view of exactly when the update failed.
How do I troubleshoot if the laptop will not boot past the rollback?
Boot into the Windows Recovery Environment by interrupting startup twice at the logo, then use its tools in order: Startup Repair, System Restore to a pre-update point, and the command prompt for manual cache resets. Safe Mode from the recovery menus lets you run the troubleshooter and DISM. Each of these is covered as a fix step in this walkthrough.
When should I stop troubleshooting and reinstall Windows?
Stop when you have completed the full ordered sequence — cache reset, DISM/SFC, driver refresh, and an in-place upgrade repair — and the loop persists across different KB packages. At that point the evidence points to hardware, usually storage, so check SMART data before reinstalling. A clean install on a failing drive just produces a cleanly installed failing drive.