## TL;DR
A pending reboot that survives real reboots is a stale flag, not a pending operation. The usual flags are the CBS RebootPending key, PendingFileRenameOperations, and the Windows Update reboot-required key. Check which flag is set, confirm no update is actually mid-install, restart the servicing stack once cleanly, and only as a last resort clear the stale CBS flag as Microsoft support documents.

```text
updates require restart stuck pending reboot
```

## Use this when
- Patch or compliance tooling lists hosts as restart required for days.
- The hosts have been rebooted, sometimes more than once, with no change.
- New updates will not install because a restart is always pending.

## Not for this skill when
- The host installed updates an hour ago and has not rebooted yet. That pending state is real; reboot it.
- A specific application installer set the pending rename flag. Let that software finish its own reboot cycle.

## Steps
1. On a stuck host, check the three flag locations: the CBS RebootPending subkey, the WindowsUpdate Auto Update RebootRequired subkey, and PendingFileRenameOperations in Session Manager. Verify: you know which flag is actually set
2. Confirm in Update history and CBS.log that no update is mid-transaction. Verify: the last transaction completed or rolled back fully
3. Restart the host once more while watching for Working on updates activity. Verify: either the flag clears (it was real) or it persists (it is stale)
4. If stale, follow the documented remediation for that flag: for CBS, remove the RebootPending subkey only after confirming no pending transaction, as Microsoft support guidance describes. Verify: the subkey is gone and you exported it first as a backup
5. Force a fresh update scan and compliance evaluation. Verify: the host reports no pending restart and accepts new updates

## Variant phrasings
### pending reboot flag stuck CBS RebootPending clear
The root-cause phrasing.
### updates require restart message never goes away
The user-symptom phrasing.
### sccm client pending restart stuck compliance
The fleet-tooling phrasing.

Compatibility: Compatibility: Windows 10, 11, and Server; flag locations are registry paths checked by most compliance tools.

## Why it happens
Windows signals pending reboot through several independent flags owned by different subsystems, and compliance tools report the union of them. If a servicing transaction is interrupted at the wrong moment, the CBS flag can remain after the work it described is long finished. Because tools trust the flag, the host looks permanently unrebooted and patch cycles stall behind it.

## Edge cases / pitfalls
- Never clear PendingFileRenameOperations blindly; pending renames for drivers and in-use files are often real and needed at the next boot.
- A flag that returns after every reboot points at an installer or agent that re-sets it each cycle; find that writer instead of clearing repeatedly.
- Export any registry key before modifying it on a production host, and record the change in the patch log.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_o4riR-tuofcvAtkqoCiUtg