Windows repeatedly displays Undoing changes made to your computer, We couldn't complete the updates, or Something didn't go as planned, then restarts and repeats the same rollback.

The rollback screen often shows no code. Search the exact message, then obtain the code from Settings > Windows Update > Update history, Event Viewer, SetupDiag, or Windows Setup logs when Windows becomes accessible. For feature upgrades, search both the result code and the extended code—for example, 0xC1900101 - 0x30018.

Useful exact-message searches are Undoing changes made to your computer, We couldn't complete the updates, Something didn't go as planned, and Failure configuring Windows updates. Reverting changes. Do not assume 0xC1900101 means a storage-controller problem: it is a broad driver rollback family, and the setup logs must identify the actual driver or device.

Use this procedure after Windows has been allowed to complete one uninterrupted rollback attempt and the same message returns on a later boot or forms a repeatable loop.

Do not interrupt a rollback that is still making progress. Do not use this procedure when the drive is missing, the message follows a firmware update rather than a Windows update, or storage diagnostics indicate failure.

The exact KB number can remain unknown initially. Whether the failed operation was a quality update, feature update, or driver update should be determined from the available recovery options and later update history.

Before you start:

  • Windows Recovery Environment
  • Supported update-removal or restore options
  • Stable AC power throughout rollback

Allow one rollback attempt to finish without pressing the power button. If Windows automatically restarts and returns to the same message, enter WinRE and select Troubleshoot > Advanced options.

  • Do not repeatedly force power off while rollback is actively progressing.
  • Do not delete pending.xml or the SoftwareDistribution directory offline as a first-line fix.
  • Do not run /RevertPendingActions without confirming that a pending servicing action is the actual blocker.
  • Do not use a system-file source from an arbitrary Windows build.

Stop when rollback tools fail, the component store requires an exact repair source, or storage instability appears.

Check the cause

  1. Note the exact screen wording.

  2. Note whether the loop began after the monthly cumulative/quality update or during a version upgrade.

  3. Open Uninstall Updates and record which options are available.

  4. If Command Prompt is needed for evidence, preserve the servicing log rather than deleting servicing state:

    md W:\BootRepairBackup
copy W:\Windows\Logs\CBS\CBS.log W:\BootRepairBackup\CBS-before-update-recovery.log

  5. Do not interpret the existence of pending.xml as permission to delete it.

First choice — Remove the latest quality update

  1. Select Uninstall Updates.
  2. Select Uninstall latest quality update.
  3. Confirm the operation.
  4. Keep the computer connected to power and allow the rollback to finish.
  5. Restart normally.

If the loop began during a feature-version upgrade

  1. Return to Uninstall Updates.
  2. Select Uninstall latest feature update if offered.
  3. Complete the rollback and restart.

If update removal is unavailable or fails

  1. Return to Advanced options.
  2. Select System Restore.
  3. Choose a restore point from immediately before the failed update.
  4. Review affected programs and complete the restore.
  5. Restart.

If Safe Mode starts

  1. Select Startup Settings > Restart > Safe Mode.

  2. Once signed in, open an administrator Command Prompt.

  3. Repair the component store, then system files:

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

  4. Do not run SFC until DISM finishes and reports its result.

  5. Restart normally.

  6. Open Settings > Windows Update > Update history and record the failed update.

  7. Pause updates temporarily while the failed update or incompatible driver is investigated; do not permanently disable Windows Update.

If the same update repeatedly fails after Windows is usable

  1. Disconnect nonessential external devices.
  2. Update the ordinary chipset, storage, and display drivers appropriate to the exact computer model.
  3. Retry the update once.
  4. If it fails identically, preserve the new CBS and setup logs and stop repeating the installation.

Check the result

  • Windows completes three normal starts without displaying the rollback message.

  • winver shows the expected Windows version.

  • Update History records the removed or failed update.

  • DISM and SFC complete without an unresolved corruption message when those steps were used.

  • A later controlled update attempt either succeeds or produces preserved logs for a narrower diagnosis.

  • Latest quality update uninstalls and Windows starts: Record the KB from Update History before it is offered again.

  • Feature rollback succeeds: Verify the previous Windows version with winver.

  • Safe Mode works but rollback fails: A driver or third-party service may be interfering; perform a clean boot before another controlled update attempt.

  • DISM cannot find repair content: Do not improvise a mismatched source image; exact build/source matching becomes required.

  • The rollback message continues after all supported recovery options: Escalate to log-based servicing repair or an in-place repair workflow rather than deleting servicing files.

To undo the change:

System Restore can reverse driver or service changes made after returning to Windows. If updates were paused, record the pause date and re-enable them after the failed update or compatibility issue is resolved.