Update error 0x80070308 on Windows 11 means the Component Based Servicing (CBS) engine tried to commit an update while a previous servicing operation was still pending — a stuck-state problem, not file corruption. That is why DISM /RestoreHealth and sfc /scannow report success but change nothing: both tools repair damaged files, and there is no damaged file here. The fix is to clear the stale pending state, or, failing that, perform an in-place repair upgrade.
Why the error occurs
The code 0x80070308 maps to ERROR_REQUEST_OUT_OF_SEQUENCE: a component requested an operation that is invalid given its current state. In practical terms, an earlier update was half-applied — staged, but never committed or rolled back — and every subsequent attempt to install a cumulative update collides with that unfinished transaction. Clicking Retry, rebooting normally, or re-running the update will never resolve it, because the stale state survives all of those actions.
A common red herring: package version numbers
On 25H2 systems, running DISM /Online /Get-Packages and seeing only 26100.* versioned packages can look alarming, but it is completely normal. Windows 11 25H2 is not a separate installation; it is an enablement package layered on top of the 24H2 core. It switches on features already shipped inside monthly 24H2 updates and does not lay down a new set of system files. Every package in the store, including the RollupFix entries, remains versioned 26100.* by design, even though winver reports a 26200.* build. Don't chase this.
Diagnosis: confirm the pending state
Before changing anything, verify that a reboot request is stuck. From an elevated Command Prompt, check both servicing keys:
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending"
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired"
If either key exists, an operation is half-committed. You can also search the full CBS.log (in C:\Windows\Logs\CBS) for 0x80070308; the lines immediately above the first hit usually name the specific component that failed to commit. Ignore 0x80070216 lines about "scavenging starvation report" — those are harmless log noise.
Fix 1: clear the pending transaction from WinRE
Because the pending state must be edited while Windows is not running, boot into the Recovery Environment: hold Shift and click Restart, then choose Troubleshoot → Advanced options → Command Prompt. Rename the pending queue rather than deleting it:
rename C:\Windows\WinSxS\pending.xml pending.xml.bak
Then clear the pending flag from the offline COMPONENTS registry hive:
reg load HKLM\SU_COMPONENTS C:\Windows\System32\config\COMPONENTS
reg delete HKLM\SU_COMPONENTS /v PendingIdentifier /f
reg unload HKLM\SU_COMPONENTS
Reboot normally and retry the update. This is the classic remedy for 0x80070308: the PendingIdentifier value is what keeps telling CBS a transaction is still in flight.
Fix 2: in-place repair upgrade
If the pending-state cleanup doesn't work — or the machine has missed several months of cumulative updates — an in-place upgrade is the most reliable solution and far more effective than endlessly resetting update components. Download the Windows 11 ISO from Microsoft, mount it, run setup.exe, and choose Keep personal files and apps. This re-installs the operating system over itself, rebuilding the servicing stack and package database from scratch while preserving your data and installed software. It also brings a system that hasn't taken a cumulative update in months fully current in a single pass.
Prevention and pre-checks
Two boring checks prevent most stuck transactions in the first place:
- Free disk space. A latest cumulative update needs several gigabytes of headroom to stage and commit. A nearly full system drive is a frequent cause of transactions that can't complete.
- Third-party interference. Antivirus suites and "system optimizer" utilities can hold file locks during servicing. Temporarily disable or uninstall them before large updates.
- Don't force power off during an update. Interrupting the commit phase is exactly how pending states get created.
Frequently Asked Questions
Why did DISM and SFC both pass if my system is broken?
Because nothing is broken in the sense those tools check. They verify the component store and protected system files. A stuck pending transaction is a state problem, not a corruption problem, so both tools legitimately find nothing to repair.
Is it normal that no packages show my current build number?
Yes. 25H2 is an enablement package on top of the 24H2 core, so all servicing packages carry 26100-based version numbers even on a 26200 build.
Can I just delete pending.xml instead of renaming it?
Renaming is safer. Keeping a backup lets you restore the queue if something else goes wrong, and Windows will simply ignore the renamed file.
Will an in-place upgrade remove my programs or files?
No, provided you select "Keep personal files and apps" in setup. It re-lays the OS files over the existing installation and leaves data and applications intact.
Should I reset Windows Update components (SoftwareDistribution, catroot2) instead?
You can try, but for this specific error it rarely helps, because the stuck state lives in the CBS pending queue and registry, not in the download cache. Clear the pending state or do the repair upgrade.