windows update keeps failing and rolling back changes on reboot

TL;DR

When Windows installs an update, restarts, and then announces it is undoing changes, the failure is happening during the commit phase at boot - often a driver, a pending operation from an earlier update, or component store damage that only surfaces when changes are applied offline. Clear any stale pending operations, repair the component store, update drivers, and install one cumulative update alone so the rollback log names a single suspect. Check the CBS log from the rollback boot for the first failing package.

windows update keeps failing and rolling back changes on reboot

Use this when

• The machine shows failure configuring updates or undoing changes during restart, repeatedly.
• Windows Update history shows the same cumulative update failing with install codes after each reboot.
• The machine otherwise runs normally once the rollback finishes.

Not for this skill when

• A version upgrade rolls back to the previous Windows release with a 0xc1900 code. That is setup rollback, a different process.
• Updates fail before any restart is requested, during download. Fix the download stage first.

Steps

1. Break the loop safely first: if the machine is cycling restarts, let a rollback complete fully without powering off mid-undo, then sign in and pause updates briefly through settings or policy so you can work on a stable machine instead of racing the next automatic attempt. Verify: the machine sits stable at the desktop with updates paused for a defined short window while you repair it
2. Read the evidence from the failed commit: open the CBS.log covering the rollback time and find the first package or driver error during the commit phase, plus check update history for the code recorded for that attempt. Later errors in the log are consequences; the first one is the lead to follow. Verify: you have the first failing package or component from the rollback, and the recorded failure code
3. Clear stale pending state: check for a pending operations file and pending renames left by earlier interrupted updates, restart cleanly once with no update attempt, and confirm the machine boots without trying to configure anything. A clean baseline separates old debris from the current update fault. Verify: the machine restarts with no configuring or undoing activity and no pending operation prompts
4. Repair the servicing foundation: run DISM RestoreHealth, then SFC, then update chipset, storage, and network drivers from the hardware vendor, since boot-phase commits load drivers early. Address any specific package the CBS log named, including uninstalling a conflicting application the log implicates. Verify: DISM and SFC report healthy, drivers are current, and any log-named blocker is resolved
5. Unpause and install only the latest cumulative update, staying present through its restart. If it rolls back again, the fresh CBS log from a single-update attempt gives a clean, attributable record for escalation or for a repair install decision. Verify: the cumulative update commits successfully across its restart, or a clean single-update rollback log supports the next escalation step

Why it happens

Many update changes cannot be applied to running files, so Windows stages them and commits during shutdown and the next boot, before most services start. If a staged file conflicts with a driver loaded at that phase, a previous pending operation is corrupt, or the component store entry being committed is damaged, the boot commit aborts and Windows protects the system by undoing every change from that attempt. The rollback is the protection working; the fault is whatever the commit hit first. Because each automatic retry repeats the same staged commit, the cycle continues until the staged content or its blocker is repaired.

Variants and edge cases

Undoing changes after every cumulative update on one model

A shared driver or firmware level across the model is a strong suspect. Compare driver versions with a working machine of the same model.

Rollback caused by a pending rename from an application install

Software that queues file renames at reboot can collide with update commits. Complete or clear the application pending operations with a clean restart before patching.

Rollback on a server with a database or line of business role

Stage the repair in a maintenance window, snapshot or back up first, and install the cumulative update alone so a rollback does not take the service down repeatedly during business hours.

Compatibility: Applies to Windows 10, Windows 11, and Windows Server 2016 and later using component based servicing.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Bx7aBqV7IXIjS2p1IauteQ