## TL;DR
0x8024200b means one update inside the package failed to install, classically a legacy print driver component in a cumulative update. Find the failing component in the CBS log, remove the stale printer driver it names, run DISM restore health, then install the KB standalone from the Update Catalog.

```text
windows 11 kb update failed with error 0x8024200b
```

## Use this when
- One Windows 11 KB fails every attempt with 0x8024200b while others install.
- The machine has old printers or print drivers carried from Windows 10.
- The same KB installs fine on other machines in the fleet.

## Not for this skill when
- All KBs fail with assorted codes. That points at the servicing stack, not one package.
- The KB fails at download with a different 0x8024 code. Treat it as a delivery fault.

## Steps
1. Note the KB number, then search mount the host path C at container path /Windows/Logs/CBS/CBS.log for 0x8024200b and read the lines above it for the failing component or driver name. Verify: a component or driver is named in the log
2. If a print driver is named, remove that printer and its driver package from Print Management or with pnputil. Verify: the stale driver no longer appears in the driver store list
3. Run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Verify: DISM completes at 100 percent with the restore operation successful
4. Download the KB standalone from the Microsoft Update Catalog and run the .msu. Verify: the standalone installer finishes without the 0x8024200b rollback
5. Restart and confirm in Update history. Verify: the KB shows Successfully installed

## Variant phrasings
### cumulative update 0x8024200b print driver
The classic print-driver root cause phrasing.
### KB fails to install 0x8024200b windows 11
The KB-first phrasing most admins search.
### windows update one update in package failed
The plain meaning of the code, used when the code itself is not quoted.

Compatibility: Compatibility: Windows 11 cumulative and preview updates; CBS log path is the same on Windows 10.

## Why it happens
Cumulative updates bundle many components, and this code is reported when the package as a whole is marked failed because one member update failed. For several Windows 11 KBs the member was an inbox print driver that no longer matched the print spooler state on upgraded machines, so the failure follows the machine, not the KB.

## Edge cases / pitfalls
- Preview and optional updates hit this more often; skipping an optional KB until the next cumulative is a valid call.
- Removing a print driver that is still in use breaks printing for that device; check the printer is really retired.
- If CBS.log shows a manifest hash mismatch instead, the fix is DISM repair plus standalone install, not driver removal.

## Provenance

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