Windows Update error 0x80073701: how to fix it

Published Sources checked By helps.wiki editorial team

Error 0x80073701 means Windows servicing could not find an assembly (component) that the update needs, so the install fails and rolls back. It usually points to a damaged component store. Running DISM RestoreHealth and then SFC, which is Microsoft's general procedure for update corruption, is the first thing to try.

Applies to:Windows 10Windows 11Windows Server2016 and later
On this page

What it means

0x80073701 comes with the message \"The referenced assembly could not be found.\" During an update, Windows servicing looks for a component the update depends on, cannot find it, and gives up. The update is then rolled back.

The usual reason is damage in the component store (the WinSxS folder). The error belongs to the same family as 0x80073712 and 0x800f081f, so the repairs overlap. One caveat: Microsoft's DISM article does not list 0x80073701 by name. The steps below are Microsoft's general procedure for update corruption, and the wording of the error comes from a Microsoft Q&A thread about Windows Server 2016. That thread gives no confirmed root cause.

If you see an access-denied code instead, read Windows Update error 0x80070005.

Symptoms and causes

You are likely dealing with this problem if:

  • A cumulative or security update fails with 0x80073701 in Settings > Windows Update or in Update History.
  • The same error comes back on every retry, often for several different updates, and restarting does not help.
  • Installing the .cab or .msu file by hand fails with the same code.
  • sfc /scannow and DISM /ScanHealth may report no problems while the update still fails.

The usual causes, most common first:

Damaged component store
Manifests, MUM files or payload files in WinSxS are missing or corrupt, for example after a previous failed update. Microsoft's DISM procedure targets exactly this kind of corruption.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Run the Windows Update troubleshooter

Easy

A quick check that costs nothing. Its success rate for this error is low, but it takes a minute.

  1. Open Settings > System > Troubleshoot > Other troubleshooters.
  2. Next to Windows Update, select Run, and follow the prompts.
  3. Restart the PC and run Windows Update again.

2.Repair the component store with DISM and SFC

Easy

This is Microsoft's documented procedure for update corruption and targets the most likely cause.

  1. Open an elevated Command Prompt: search for Command Prompt, right-click it and choose Run as administrator.
  2. Run DISM first, and wait for it to finish (it can sit at a percentage for a while).
    Command Promptrun as administrator
    DISM.exe /Online /Cleanup-Image /RestoreHealth
  3. Then run the System File Checker.
    Command Promptrun as administrator
    sfc /scannow
  4. Restart and run Windows Update again. If RestoreHealth does not report success, open %windir%\Logs\CBS\CBS.log to see why.

3.Run DISM with an alternate repair source

AdvancedChanges settings

If RestoreHealth fails because Windows Update cannot supply the files (for example with 0x800f0906), point DISM at a matching Windows image instead.

Before you start: The source must match your installed Windows version and edition, otherwise the repair fails or does not help. Create a restore point before you start.

  1. Mount a Windows ISO of the same version, and note its drive letter (D: below). Check the image index first.
    Command Promptrun as administrator
    dism /Get-WimInfo /WimFile:D:\sources\install.wim
  2. Run the repair with that index (here 1) and block Windows Update as a source. For ESD media use /Source:ESD:D:\sources\install.esd:1.
    Command Promptrun as administrator
    DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess
  3. Alternatively, use a working PC on the same OS version, shared over the network.
    Command Promptrun as administrator
    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:\\<servername>\c$\windows /LimitAccess
  4. Finish with SFC and restart.
    Command Promptrun as administrator
    sfc /scannow

4.Repair the specific files named in CBS.log

AdvancedChanges settings

Microsoft's advanced procedure for when the automatic repair cannot find the files it needs.

Before you start: Create a restore point first. Only download updates from the Microsoft Update Catalog.

  1. Open %windir%\Logs\CBS\CBS.log and look for entries such as "CSI Payload Corrupt" or "CBS MUM Missing".
  2. Read the build revision from the file path in those entries (for example 10.0.19045.3636) and match it to a KB on the Windows release history page.
  3. Download that KB from the Microsoft Update Catalog and extract the .msu/.cab into C:\temp\Source using the PowerShell script from Microsoft's article.
  4. Run DISM against that folder, then verify.
    Command Promptrun as administrator
    DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\temp\Source\ /LimitAccess
DISM /Online /Cleanup-Image /ScanHealth

Check that it worked

  • Windows Update installs the previously failing update without 0x80073701 and it shows as installed in Update History.
  • DISM /Online /Cleanup-Image /ScanHealth reports no component store corruption.

If it still fails

  • Read %windir%\Logs\CBS\CBS.log and note which items it reports as corrupt or missing.
  • If RestoreHealth fails with 0x800f0906, use the alternate source method rather than repeating the default one.
  • If everything fails, contact Microsoft Support and bring the CBS.log. Back up your important files before any deeper repair.

Questions

Why does SFC say everything is fine when the update still fails?

SFC checks protected system files, not every part of the component store. A clean result does not rule out a store inconsistency, which is why DISM RestoreHealth is worth running anyway.

Should I delete or rename pending.xml?

Not as a routine step. It is risky unless you have confirmed the file is stale, and none of the steps here need it.

Sources

  1. Fix Windows Update corruptions and installation failuresOfficial · Microsoft Learn
  2. Windows failed to install the following update with error 0x80073701Official · Microsoft Q&A

Browse