how to roll back windows update after install failed

Not specified by the original author.

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

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

Thread query: 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.

Not specified by the original author.

TL;DR

Stop trying to uninstall that cumulative update in place: 0x800f0905 means the package was made permanent by servicing stack cleanup, so restore from backup or snapshot, or repair with an in-place upgrade, instead of DISM remove-package. Prove it on one failing machine before rolling it to the rest of machines in the deployment, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

cumulative update uninstall failed error 0x800f0905 the component store cannot roll back this package

Use this when

• You see this exact error or symptom: cumulative update uninstall failed error 0x800f0905 the component store cannot roll back this package.
• The failure is in Windows Update, WSUS, SCCM / MECM or Intune servicing on the affected machines, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one failing machine first and capture the evidence before changing anything: check Windows Update history, the CBS and DISM logs, and the WSUS or SCCM console status for one failing machine, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Stop trying to uninstall that cumulative update in place: 0x800f0905 means the package was made permanent by servicing stack cleanup, so restore from backup or snapshot, or repair with an in-place upgrade, instead of DISM remove-package. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Record the before and after state for this fix (the exact setting, record, or file changed) so the change can be reverted cleanly if the symptom returns in a different form. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: rescan and reinstall on one machine and confirm Update history (or the SCCM / Intune status) shows the update installed. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of machines in the deployment in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

0x800f0905 fix

The verbatim error or code phrasing for this fault in Windows Update; the fix is the same one in the steps above.

cumulative update uninstall failed error 0x800f0905 the component store

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix cumulative update uninstall failed error 0x800f0905 the

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Windows 10 and 11, Windows Server 2016 and later, WSUS, SCCM / MECM, Intune, DISM and the Microsoft Update Catalog as named in the title.

Why it happens

This fault happens because the fault sits at a boundary between two systems, each of which reports its own side as healthy, so the evidence has to be lined up on both sides to see it. In this case the condition is the one named in the title, in Windows Update, WSUS, SCCM / MECM or Intune servicing on the affected machines: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst9sfuEWngcJkecJ-O-zVng

Resolved from the public thread: https://vectle.com/posts/pst9sfuEWngcJkecJ-O-zVng

Thread query: cumulative update uninstall failed error 0x800f0905 the component store cannot roll back this package

TL;DR: Stop trying to uninstall that cumulative update in place: 0x800f0905 means the package was made permanent by servicing stack cleanup, so restore from backup or snapshot, or repair with an in-place upgrade, instead of DISM remove-package. Prove it on one failing machine before rolling it to the rest of machines in the deployment, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

Not specified by the original author.

TL;DR

Stop trying to uninstall that cumulative update in place: 0x800f0905 means the package was made permanent by servicing stack cleanup, so restore from backup or snapshot, or repair with an in-place upgrade, instead of DISM remove-package. Prove it on one failing machine before rolling it to the rest of machines in the deployment, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.

cumulative update uninstall failed error 0x800f0905 the component store cannot roll back this package

Use this when

• You see this exact error or symptom: cumulative update uninstall failed error 0x800f0905 the component store cannot roll back this package.
• The failure is in Windows Update, WSUS, SCCM / MECM or Intune servicing on the affected machines, and it repeats on the same action rather than happening once and clearing.
• Other items on the same path are working, so the path itself is up and this specific condition is the blocker.

Not for this skill when

• A different error code, message, or tool is involved. Work that error's own skill, because the fix here targets this specific condition.
• The whole service or platform is down. Restore the service first; this skill fixes the named condition, not an outage.
• You cannot identify one affected item to test on. Find one first, because an untested fix rolled out broadly is how this fault gets worse.

Steps

1. Confirm the fault on one failing machine first and capture the evidence before changing anything: check Windows Update history, the CBS and DISM logs, and the WSUS or SCCM console status for one failing machine, and record the exact error text, the record or host involved, and the time it happened. Verify: you can point to the exact error and the exact item it belongs to, not just the symptom
2. Stop trying to uninstall that cumulative update in place: 0x800f0905 means the package was made permanent by servicing stack cleanup, so restore from backup or snapshot, or repair with an in-place upgrade, instead of DISM remove-package. Verify: the specific fault named in the title no longer occurs on that item when you repeat the action that produced it
3. Record the before and after state for this fix (the exact setting, record, or file changed) so the change can be reverted cleanly if the symptom returns in a different form. Verify: the guard or check is in place and is visible in the run, log, or configuration you changed
4. Retest end to end: rescan and reinstall on one machine and confirm Update history (or the SCCM / Intune status) shows the update installed. Verify: the retest completes without the original error and the resulting state matches what a manual check shows
5. Roll the fix out to the rest of machines in the deployment in the same way, watching the first few for the same error, and note the root cause and the change in the run or incident record. Verify: the remaining items complete without the error recurring, or the ones that still fail are listed individually with their own evidence

Variant phrasings

0x800f0905 fix

The verbatim error or code phrasing for this fault in Windows Update; the fix is the same one in the steps above.

cumulative update uninstall failed error 0x800f0905 the component store

The full symptom phrasing as it appears in the console, log, or report where this failure surfaces.

how to fix cumulative update uninstall failed error 0x800f0905 the

The how-to phrasing for the same fault; start with the TL;DR fix, then work the steps in order.

Compatibility: Windows 10 and 11, Windows Server 2016 and later, WSUS, SCCM / MECM, Intune, DISM and the Microsoft Update Catalog as named in the title.

Why it happens

This fault happens because the fault sits at a boundary between two systems, each of which reports its own side as healthy, so the evidence has to be lined up on both sides to see it. In this case the condition is the one named in the title, in Windows Update, WSUS, SCCM / MECM or Intune servicing on the affected machines: the receiving or acting side reports the failure faithfully, but the underlying state (a record, a setting, a credential, a file, or a mapping) does not match what that action assumes. Fixing the state, as in step 2, clears it; retrying the action without changing the state returns the same error every time, which is why this failure looks stubborn until the state itself is corrected.

Provenance

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

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

Thread query: cumulative update uninstall failed error 0x800f0905 the component store cannot roll back this package

TL;DR: Stop trying to uninstall that cumulative update in place: 0x800f0905 means the package was made permanent by servicing stack cleanup, so restore from backup or snapshot, or repair with an in-place upgrade, instead of DISM remove-package. Prove it on one failing machine before rolling it to the rest of machines in the deployment, because this fault repeats identically wherever the same condition holds and a fleet-wide or batch-wide first attempt multiplies the damage when the diagnosis is wrong.