sodcalculator

10 Tech How-To

0x80073701 Install Error Windows 11 Fix

Guide 10-49066 · Updated · Step by step

The 0x80073701 error in Windows 11 means the system file checker (SFC) or Windows Update could not repair missing or corrupted component store files. This guide explains the most reliable fixes, starting with the DISM tool, and includes steps to prevent the error from returning.

What Causes Error 0x80073701?

This error code is tied to the Windows Component Store (the folder C:\Windows\WinSxS), which holds all system files needed for updates, driver installations, and feature changes. When a file in this store is missing or corrupted, Windows Update or the System File Checker (SFC) cannot complete its job, and you see 0x80073701. Common triggers include:

  • An interrupted Windows Update installation (e.g., power loss or forced shutdown)
  • Disk corruption from a failing hard drive or improper shutdown
  • Third-party antivirus software interfering with system file operations
  • Manual deletion of files inside the WinSxS folder (which should never be done)
  • Running out of disk space during an update

Unlike some errors that point to a specific update, 0x80073701 is generic: it simply says the component store is in an inconsistent state.

Before You Start: Check Disk Space and Permissions

Two quick checks can save you time. First, make sure you have at least 20 GB of free space on the drive where Windows is installed (usually C:). Windows Update needs room for temporary files, and a full disk can cause this exact error. Second, ensure you are logged in as an administrator—all the commands below require admin rights.

If you have a third-party antivirus (like Norton, McAfee, or Bitdefender), temporarily disable its real-time protection during the repair. These tools sometimes lock system files, causing SFC and DISM to fail. Re-enable it after the repair finishes.

Fix 1: Run DISM to Repair the Component Store

The Deployment Imaging Service and Management Tool (DISM) is the first line of defense for component store corruption. It uses Windows Update to download healthy copies of corrupted files. Here’s how to run it:

  1. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
  2. Type the following command and press Enter:
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Wait for the process to complete (it can take 15–30 minutes). Do not close the window.
  4. When it finishes, restart your PC.

If DISM fails because Windows Update itself is broken, you can point it to a known-good source using the /Source parameter with a Windows 11 installation USB or ISO. For example:
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim /LimitAccess
Replace D: with the drive letter of your USB or mounted ISO.

Fix 2: Run SFC to Repair System Files

After DISM succeeds, run the System File Checker to replace any corrupted or missing system files. In the same admin terminal, type:

  1. sfc /scannow
  2. Let it run to completion (usually 10–20 minutes).
  3. If it finds and fixes issues, restart your PC.

If SFC still reports errors after running DISM, run SFC again—sometimes it needs a second pass. If the error persists, move to the next fix.

Fix 3: Reset Windows Update Components Manually

Sometimes the Windows Update service itself is stuck. Resetting its components manually often clears the way. In an admin terminal, run these commands one at a time, pressing Enter after each:

  1. net stop wuauserv
  2. net stop cryptSvc
  3. net stop bits
  4. net stop msiserver
  5. ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  6. ren C:\Windows\System32\catroot2 catroot2.old
  7. net start wuauserv
  8. net start cryptSvc
  9. net start bits
  10. net start msiserver

This renames the update cache folders (the .old suffix lets Windows create fresh ones). After restarting, try Windows Update again.

Fix 4: Use the Windows 11 Installation Assistant or Media Creation Tool

If the above steps don’t work, the most reliable method is an in-place repair upgrade. This reinstalls Windows 11 while keeping your files, apps, and settings. Download the Windows 11 Installation Assistant from Microsoft’s official website (or the Media Creation Tool for a bootable USB). Run the assistant, and it will download the latest Windows 11 and repair the component store. This is not a full reset—your personal files remain intact.

After the upgrade, run sfc /scannow again to confirm the system is clean.

Common Mistakes and Misconceptions

A frequent mistake is running SFC before DISM. SFC relies on the component store; if the store is broken, SFC can’t fix anything. Always run DISM first.

Another misconception is that you need to reinstall Windows completely. That is rarely necessary—an in-place repair upgrade solves most cases. Also, do not manually delete anything from C:\Windows\WinSxS. Windows manages that folder automatically; deleting files there breaks the component store further.

Finally, if you have a dual-boot system, ensure you are running these commands in the correct Windows installation. Running DISM or SFC from the wrong OS can target the wrong drive.

Frequently Asked Questions

Can I fix 0x80073701 without admin rights?

No. All repair commands (DISM, SFC, net stop/start) require administrator privileges. If your account is not an admin, you’ll need to ask someone with admin rights to run the commands, or use the built-in administrator account temporarily.

Will these fixes delete my files?

No. DISM, SFC, and the Windows Update component reset do not touch your personal files. The in-place upgrade also preserves files, apps, and settings. Only a full “Reset this PC” option would remove files, and you should not need that for this error.

How long does the DISM command take?

Typically 15–30 minutes, but it can take up to an hour on slower systems or if Windows Update is slow. Do not interrupt it—closing the window mid-run can cause additional corruption.

I get an “Access Denied” error when running DISM. What now?

This usually means your terminal is not elevated. Right-click the Start button and choose “Terminal (Admin)” or “Command Prompt (Admin)”—the word “Admin” in the title bar confirms it. If you still see the error, check that your account is in the Administrators group.

What if the error appears during a Windows feature update (like 24H2)?

Run the same fixes in the same order. The in-place upgrade via the Installation Assistant is especially effective for feature updates. If the update still fails, consider pausing updates for a week and trying again—Microsoft sometimes pulls a problematic update and re-releases it.

Is 0x80073701 the same as 0x80073712?

They are similar—both indicate component store corruption—but the codes are different. 0x80073712 specifically means a component store file is missing, while 0x80073701 is a more general “corrupted” state. The fixes are identical.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →