Windows Server 2012 R2 — Windows Update Client reports package conflict between LCU and out-of-band fix — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Patch deployment on Windows Server 2012 R2 fails with 0x80073712 when an out-of-band update conflicts with the previously approved cumulative update.

Environment & Reproduction

Reproduces when WSUS approves both a regular LCU and a later OOB safety update that share component payloads.

Get-WUHistory | Where Status -EQ Failed | Select -First 5

Root Cause Analysis

Multiple updates touching the same components leave the manifest in an inconsistent state, blocking servicing.

Quick Triage

Examine the update history for the exact failed KB and conflict details.

Get-WindowsUpdateLog
Get-Content $env:USERPROFILEDesktopWindowsUpdate.log -Tail 200

Step-by-Step Diagnosis

Run DISM analyse to confirm component store sanity.

dism /online /cleanup-image /scanhealth

Solution — Primary Fix

Uninstall the conflicting OOB update, apply the latest LCU first, then reapply the OOB fix.

wusa.exe /uninstall /kb:5036OOB /quiet /norestart
wusa.exe windows10.0-kb5036000-x64.msu /quiet /norestart
wusa.exe windows10.0-kb5036OOB-x64.msu /quiet /norestart

Solution — Alternative Approaches

Decline the conflicting update in WSUS and rebuild approvals from a clean baseline.

Get-WsusUpdate -Approval Approved -Classification 'Security Updates' | Where Title -Like '*5036OOB*' | Deny-WsusUpdate

Verification & Acceptance Criteria

Get-HotFix lists the new combined patch state and update scans report no failures.

Get-HotFix | Where InstalledOn -gt (Get-Date).AddDays(-7)

Rollback Plan

Roll back to the prior LCU using DISM /remove-package if the combined state breaks production.

dism /online /remove-package /packagename:Package_for_KB5036OOB~31bf3856ad364e35~amd64~~10.0.1.0

Prevention & Hardening

Test OOB updates in a pilot ring before broad WSUS approval and document supersedence relationships.

# Review supersedence in WSUS report before approving OOB

Related Errors & Cross-Refs

Related: 0x800f0922 staging, SSU prerequisite errors, and DISM component store corruption.

Related tutorial: View the step-by-step tutorial for Windows Server 2012 R2.

View all Windows Server 2012 R2 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn guidance for managing out-of-band updates and update supersedence.