0x80073701 Missing Manifests: Manual Repair of the Component Store

If you’re seeing error 0x80073701 while installing Windows updates, you’re dealing with a servicing/component store issue—typically “Missing Manifests.” This error usually appears in Windows Update, DISM, or CBS logs and points to missing or corrupted files in the Windows Component Store (WinSxS). Left unresolved, it can block updates, cumulative patches, and even feature upgrades. This guide goes beyond generic advice to show you how to manually repair the component store and restore Windows Update functionality step by step.

We’ll cover quick checks, in-depth DISM/SFC usage, servicing logs analysis (CBS.log), manual package repair from MSU/CAB files, offline repairs, and the in-place upgrade repair install—organized from simplest to most advanced.

Understanding the Error

Error 0x80073701 maps to ERROR_SXS_ASSEMBLY_MISSING. In plain terms, Windows can’t find one or more required manifest files (or related payloads) that describe system components. These manifests tell Windows how assemblies are structured, their versions, and dependencies. If a manifest is missing or corrupted, the servicing stack can’t complete updates, leading to failures in Windows Update, DISM, or SFC.

Common real-world situations where 0x80073701 appears:

• During Windows Update installation of cumulative updates (LCU), .NET updates, or language packs.
• When running DISM with /RestoreHealth or SFC /scannow after update interruptions or power loss.
• After using aggressive “cleanup” utilities that tamper with WinSxS.
• On systems upgraded across multiple builds without a clean component store.
• When the update payload or source files are unavailable or mismatched with the installed build.

Quick Reference Table

Cause	Symptom	Recommended Fix
Interrupted update or power loss	Updates fail repeatedly with 0x80073701	Reset Windows Update components; rerun update; DISM /RestoreHealth; SFC
Corrupted or missing component manifests	DISM shows ERROR_SXS_ASSEMBLY_MISSING	DISM /RestoreHealth with a matching ISO Source; manual add-package from MSU/CAB
Outdated or broken Servicing Stack	Updates won’t apply; CBS.log references servicing errors	Install latest SSU/LCU for your build (from Microsoft Update Catalog)
Third-party AV/cleanup tools tampered with WinSxS	Persistent update failures	Temporarily disable AV; reverse changes if possible; run DISM/SFC; manual package repair
File system or disk issues	SFC/DISM fail; CHKDSK finds errors	CHKDSK, then DISM /RestoreHealth and SFC; check SMART/drive health
Mismatched source files (wrong ISO)	DISM /RestoreHealth fails with 0x800f081f or doesn’t repair	Use correct ISO matching edition, language, and build; specify Source with /LimitAccess
Enterprise policy/WSUS complications	Updates stuck or superseded packages fail	Confirm WSUS policy, try standalone MSU, or in-place repair install if needed

Common Causes

• Corrupted WinSxS component store (manifests, catalogs, payloads)
• Incomplete update installations (power loss, forced shutdown, network drop)
• Missing or mismatched update payloads (wrong language/edition/build)
• Outdated or damaged Servicing Stack (SSU) or Windows Update components
• Aggressive system cleaning utilities deleting WinSxS entries
• Third-party antivirus or endpoint security interfering with servicing
• File system errors or failing storage
• Rarely, malware infection affecting system files
• Legacy systems (Windows 7/Server 2008 R2) requiring the System Update Readiness Tool (CheckSUR)

Preliminary Checks

Boot to Safe Mode (optional but helpful if updates/services are unstable)

• Windows 10/11:
  • Settings > Update & Security > Recovery > Advanced startup > Restart now
  • Troubleshoot > Advanced options > Startup Settings > Restart
  • Press 4 (Enable Safe Mode)
• Or run msconfig > Boot tab > Safe boot (Minimal), then restart. Remember to undo afterward.

Back up important data

• Use File History, OneDrive, or a simple copy with Robocopy:
  • Command: robocopy “C:\Users\YourName” “D:\Backup\YourName” /MIR /R:2 /W:2 /XD “Temp” “AppData\Local\Temp”

Run basic health checks

• File system scan (no reboot):
  • chkdsk C: /scan
• Full repair (requires reboot):
  • chkdsk C: /f
• System File Checker:
  • sfc /scannow
• Initial DISM assessment:
  • DISM /Online /Cleanup-Image /CheckHealth
  • DISM /Online /Cleanup-Image /ScanHealth

If SFC reports errors it cannot fix, and DISM shows corruption, proceed with the steps below.

Step-by-Step Troubleshooting

Follow these in order. Test Windows Update after each step.

1. Verify time, disk space, internet, and pause AV temporarily

• Ensure system time/time zone is correct and you have at least 10–20 GB free disk space for updates.
• Temporarily disable third-party antivirus real-time scanning to avoid servicing interference.
• Reboot once to clear transient states.

2. Reset Windows Update components
   Run Command Prompt as Administrator and execute:

• net stop wuauserv
• net stop cryptSvc
• net stop bits
• net stop msiserver
• ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
• ren C:\Windows\System32\catroot2 catroot2.old
• net start bits
• net start cryptSvc
• net start msiserver
• net start wuauserv

Try updates again. If 0x80073701 persists, continue.

3. Install the latest Servicing Stack Update (SSU) and LCU for your build

• Go to the Microsoft Update Catalog and download the latest SSU/LCU that matches your version/build (Windows 10/11). Install SSU first if it’s separate for your build; newer LCUs include SSUs.
• Reboot and retry updates.

4. Run DISM to repair the component store (online)

• DISM /Online /Cleanup-Image /CheckHealth
• DISM /Online /Cleanup-Image /ScanHealth
• DISM /Online /Cleanup-Image /RestoreHealth

If /RestoreHealth completes successfully, run SFC again:

• sfc /scannow

If /RestoreHealth fails with source errors (e.g., 0x800f081f) or still shows 0x80073701, use a matching ISO as a repair source (Step 5).

5. DISM /RestoreHealth with a matching Source (ISO)

• Download the exact ISO that matches your installed Windows edition, language, and build.
• Mount the ISO (right-click > Mount) to get a drive letter (e.g., D:).
• Identify the correct index in the WIM/ESD:
  • DISM /Get-WimInfo /WimFile:D:\sources\install.wim
  • or if ESD: DISM /Get-WimInfo /WimFile:D:\sources\install.esd
• Run /RestoreHealth specifying the index and limiting online access:
  • For WIM: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:IndexNumber /LimitAccess
  • For ESD: DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:D:\sources\install.esd:IndexNumber /LimitAccess

After success, run:

• sfc /scannow

6. Analyze and clean the component store

• DISM /Online /Cleanup-Image /AnalyzeComponentStore
• DISM /Online /Cleanup-Image /StartComponentCleanup
• Optional (cannot uninstall replaced updates afterward):
  • DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

7. Revert stuck pending actions (if servicing is stuck)
   Use with caution. If updates are “stuck pending,” run:

• DISM /Online /Cleanup-Image /RevertPendingActions
  Reboot immediately. Try Windows Update again and then DISM /RestoreHealth + SFC.

8. Manual repair of missing manifests via MSU/CAB
   When CBS.log shows entries like “CSI Manifest Missing,” identify the exact package/component. Then:

• Download the corresponding update (KB) from the Microsoft Update Catalog that provides the missing component.
• Extract the MSU and CAB:
  • Create a temp folder, e.g., C:\Temp\KB
  • expand -F:* C:\Path\To\windows10.0-kb########-x64.msu C:\Temp\KB
  • expand -F: C:\Temp\KB\.cab C:\Temp\KB\CAB
• Install the package with DISM:
  • If you have a single CAB: DISM /Online /Add-Package /PackagePath:”C:\Temp\KB\windows10.0-kb########-x64.cab”
  • Or add from .mum in CAB folder:
    • DISM /Online /Add-Package /PackagePath:”C:\Temp\KB\CAB\PackageName.mum”
• Reboot, then run:
  • DISM /Online /Cleanup-Image /RestoreHealth
  • sfc /scannow

Note: Avoid manually copying files into C:\Windows\WinSxS\Manifests. The supported way is to add packages via DISM to keep the servicing stack consistent.

9. Offline repair from Windows Recovery or another Windows install
   If online repair fails, perform an offline servicing repair:

• Boot to Windows Recovery Environment (Shift+Restart > Troubleshoot > Advanced options > Command Prompt), or use another Windows instance.
• Identify the Windows drive (it may not be C: in WinRE).
• Run offline SFC:
  • sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
• Run offline DISM with a mounted ISO as source:
  • DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:IndexNumber /LimitAccess
• Reboot and rerun Windows Update.

10. In-place upgrade repair install (keeps files and apps)
    If 0x80073701 persists, perform an in-place repair:

• Mount a matching Windows ISO and run setup.exe.
• Choose “Keep personal files and apps.”
• Proceed with the upgrade. This refreshes Windows while preserving data and applications.
• Afterward, run:
  • sfc /scannow
  • DISM /Online /Cleanup-Image /CheckHealth
• Reapply updates.

How to read servicing logs (CBS/DISM) to pinpoint missing manifests

• CBS log location:
  • C:\Windows\Logs\CBS\CBS.log
• Filter for SFC and manifest issues:
  • findstr /c:”[SR]” %windir%\Logs\CBS\CBS.log > “%userprofile%\Desktop\sfcdetails.txt”
  • findstr /c:”CSI Manifest Missing” %windir%\Logs\CBS\CBS.log > “%userprofile%\Desktop\manifestmissing.txt”
  • findstr /i “error failed 0x” %windir%\Logs\CBS\CBS.log > “%userprofile%\Desktop\cbs_errors.txt”
• DISM log location:
  • C:\Windows\Logs\DISM\dism.log
• Windows Update log (Windows 10/11):
  • PowerShell (as admin): Get-WindowsUpdateLog
  • This creates WindowsUpdate.log on your Desktop.

Tip: Map a missing component to a KB by searching the CBS snippet on the web or comparing with the packages listed under:

• DISM /Online /Get-Packages
  You can attempt to reinstall or remove/reinstall specific packages with DISM if appropriate.

Advanced Diagnostics

• Event Viewer for servicing/update errors:

  • Open Event Viewer (eventvwr.msc)
  • Check under:
    • Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational
    • Applications and Services Logs > Microsoft > Windows > Servicing > Operational
    • System and Application logs for related errors (e.g., SideBySide, TrustedInstaller)

• Get-WindowsUpdateLog (PowerShell) to correlate time-based update failures with CBS/DISM log entries.

• Driver Verifier note:

  • Driver Verifier is a tool for diagnosing driver-caused BSODs and is generally not pertinent to 0x80073701 (a servicing error). Use it only if you suspect concurrent driver instability. If you do enable it, proceed with extreme caution:
    • verifier /standard /all
    • Reboot and observe. If BSODs occur, boot Safe Mode and disable:
      • verifier /reset
  • Again: for servicing errors, focus on DISM/SFC/CBS/Windows Update logs instead of Driver Verifier.

• Process Monitor (advanced):

  • Use Sysinternals Procmon to capture file and registry access during update attempts. Filter on processes like TiWorker.exe and TrustedInstaller.exe to catch “ACCESS DENIED” or “NAME NOT FOUND” events pointing to missing manifests or blocked paths (e.g., AV).

Post-Fix Checklist

• Run both:
  • DISM /Online /Cleanup-Image /CheckHealth
  • sfc /scannow
• Confirm Windows Update installs without errors.
• Review Event Viewer (WindowsUpdateClient and Servicing) for a clean run post-fix.
• Reboot twice and re-check for stability.
• Optional: Run
  • DISM /Online /Cleanup-Image /AnalyzeComponentStore
  • DISM /Online /Cleanup-Image /StartComponentCleanup
• Ensure antivirus is re-enabled and functioning normally.

When to Seek Professional Help

• CHKDSK repeatedly finds errors or SMART reports drive health issues (consider replacing the drive).
• DISM /RestoreHealth fails even with the correct ISO source and offline servicing attempts.
• CBS.log shows persistent, unrecoverable corruption across core components.
• In-place upgrade repair fails or cannot complete.
• Enterprise systems with WSUS/SCCM policies complicate updates and you lack admin rights to adjust them.

At that point, a professional can perform hardware diagnostics, replace failing storage, or carry out a clean installation with data migration if necessary.

Prevention Tips

• Keep Windows current: apply monthly LCUs and ensure the Servicing Stack is up to date.
• Avoid aggressive registry/cleanup tools that “shrink” WinSxS; use:
  • DISM /Online /Cleanup-Image /StartComponentCleanup
• Maintain reliable power during updates (laptops: keep plugged in; desktops: consider a UPS).
• Practice “driver hygiene”: install only necessary drivers from OEM sources.
• Keep regular backups (File History, system images). Test restoring a file occasionally.
• Don’t delete or rename contents of C:\Windows\WinSxS manually.
• Ensure sufficient free disk space before updates.
• Use reputable antivirus and avoid conflicting endpoint security layers.

Conclusion

Error 0x80073701 (Missing Manifests) means Windows’ servicing stack can’t find the component metadata it needs to update your system. In most cases, you can resolve it by resetting Windows Update components, repairing the component store with DISM and SFC, and—if needed—supplying a correct ISO as a repair source. For stubborn scenarios, manually reinstalling the implicated packages, performing an offline repair, or running an in-place upgrade repair will restore update functionality. With the steps above, you should be able to diagnose and fix even complex cases of component store corruption.

Stay patient and methodical—most systems can be fully repaired without a clean install.

FAQ

What does error 0x80073701 mean in Windows Update?

It maps to ERROR_SXS_ASSEMBLY_MISSING and indicates missing or corrupted component manifests in the Windows Component Store (WinSxS). The servicing stack can’t locate required metadata to install or service components, so updates fail.

How is 0x80073701 different from 0x800f081f?

• 0x80073701: Missing assembly manifests (servicing metadata problem).
• 0x800f081f: “The source files could not be found.” Usually appears when DISM can’t find the payload to repair components—often fixed by specifying a proper Source (ISO) with DISM /RestoreHealth.

Is it safe to delete files from WinSxS to fix this?

No. Don’t manually delete or alter WinSxS contents. Use supported methods like DISM /StartComponentCleanup, DISM /RestoreHealth, and SFC. Manual deletions can break servicing and make issues worse.

Do I need internet access for DISM /RestoreHealth?

Not if you provide a correct local source (matching ISO) and use /LimitAccess. Without a local source, DISM may attempt to pull files from Windows Update, which requires internet.

Will an in-place upgrade repair remove my apps or files?

If you choose “Keep personal files and apps,” an in-place upgrade repair will preserve your installed applications and data. Always back up first as a best practice.

If you run into snags, don’t hesitate to ask for help—this error is fixable, and with careful steps you can get Windows Update running smoothly again. You’ve got this!