🟠 High   ⏱ 5–30 min  Last verified: 18 May 2026
Affected versions: Windows Server 2016

📖 ~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

Updates fail with missing assembly references and rollback repeatedly. Vulnerability exposure remains unresolved.

Environment & Reproduction

Triggered after interrupted servicing, failed supersedence chains, or corrupted WinSxS components.

dism /online /cleanup-image /scanhealth
sfc /verifyonly

Root Cause Analysis

CBS cannot stage required component versions because manifest metadata is missing or damaged.

Quick Triage

Collect CBS excerpts around failure and verify source media availability for repair.

findstr /i /c:"0x80073701" C:WindowsLogsCBSCBS.log
Get-Volume

Step-by-Step Diagnosis

Identify exact package identity and architecture to map correct repair source.

dism /online /get-packages | findstr /i pending
Get-WindowsUpdateLog -LogPath C:Tempwu-180.log
Illustrative mockup for windows-server-2016 — cbs_log_analysis
Manifest and package failure traces — Illustrative mockup — Progressive Robot

Solution — Primary Fix

Run DISM restore with validated source, then re-run SFC and retry update.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

dism /online /cleanup-image /restorehealth /source:wim:D:sourcesinstall.wim:4 /limitaccess
sfc /scannow
usoclient StartScan
Illustrative mockup for windows-server-2016 — terminal_or_powershell
DISM restore sequence — Illustrative mockup — Progressive Robot

Solution — Alternative Approaches

Apply missing package manually from Update Catalog when source media does not match baseline.

dism /online /add-package /packagepath:C:PatchRepomissing.cab

Verification & Acceptance Criteria

No corruption reported and update installation completes without CBS rollback.

dism /online /cleanup-image /checkhealth
Get-HotFix | Select -First 5

Rollback Plan

Revert to last known good backup image if component corruption persists.

wbadmin get versions

Prevention & Hardening

Use tested golden images and avoid abrupt power events during servicing windows.

Get-WinEvent -LogName System -MaxEvents 50 | Where-Object {$_.Id -in 41,6008}

Related: 0x800f081f source files not found, 0x80073712 component store corruption.

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

View all Windows Server 2016 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft DISM servicing repair references and CBS troubleshooting guidance.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.