0x80073712 Error | Fix Windows Update Corruption Fast

Guide / By

The 0x80073712 error usually points to damaged Windows component-store files, so updates fail until the store is repaired.

You’ll often see this code after a cumulative update stalls, a feature update stops partway through, or Windows Update loops on “retry.” This error is rarely random. You can work through fixes in a clean order.

This guide walks you through repairs that restore the component store, clear stuck update caches, and get Windows Update installing again on Windows 10 and Windows 11, plus a Windows 7 note.

What The 0x80073712 Error Means

Windows Update relies on a “component store” (WinSxS) that keeps trusted copies of system components. When the store is inconsistent or missing pieces, Windows Update can’t assemble the update payload, so it stops with this code.

Microsoft’s guidance for image repair recommends fixing the servicing image with DISM and then verifying protected files with SFC. The DISM flow is outlined in Microsoft Learn: Repair a Windows image, and SFC behavior is documented in Microsoft Learn: sfc command reference.

If you only take one idea from this section, take this: when the store is damaged, Windows Update won’t heal it by itself. Repair the store first, then retry the update again.

Fast Checks That Save Time

Before you run repair commands, do a few quick checks that often unblock installs without touching system files.

  • Restart Once — A reboot clears a half-finished servicing session and releases file locks that can block repairs.
  • Free Up Space — Leave room for the update to stage. On many PCs, 10–20 GB free on the system drive avoids mid-install failures.
  • Disconnect Extra Drives — Unplug unneeded USB storage during the update. It reduces driver churn and keeps the update focused on the system disk.
  • Pause Third-Party Antivirus — If you run a non-Microsoft antivirus, pause it during the install window so it doesn’t quarantine update staging files.
  • Run The Built-In Troubleshooter — Windows can reset common update settings and services. Microsoft lists the steps for running it in Settings. Windows Update troubleshooter steps

If the update still fails after these checks, move on to store repair. That’s where this error code usually sits.

If you want to confirm you’re fixing the right failure, open Settings > Windows Update > Update history and note the update that failed. The same screen may show “component store has been corrupted” along with the code. Seeing that pairing is a strong clue that store repair is the right next move for the 0x80073712 error.

  • Write Down The KB Number — The KB identifier helps if you end up installing the update by hand from the Microsoft Update Catalog.
  • Copy The Full Message — A short note like “install error” is vague; the full text helps you spot servicing or download issues.
  • Check CBS Log Location — Servicing logs live at C:\Windows\Logs\CBS\CBS.log, which is useful when repairs report they fixed files.

Fixing Error 0x80073712 On Windows 10 And 11

This section is the repair track: DISM first to repair the component store, then SFC to verify files, then a retry of Windows Update.

Pick The Right Terminal

Use Windows Terminal or Command Prompt with admin rights. On Windows 11, right-click Start, then choose Terminal (Admin). On Windows 10, right-click Start, then choose Windows PowerShell (Admin) or Command Prompt (Admin).

Tool What It Repairs When To Run
DISM Component store (servicing image) First, when updates fail with store errors
SFC Protected system files After DISM, to clean up leftovers
Update Retry Pending update install flow After repairs, to confirm the fix

Run DISM Store Repair

DISM can scan the servicing image and replace damaged parts. Microsoft’s image-repair documentation uses this workflow for online systems. DISM workflow on Microsoft Learn

  1. Open Terminal As Admin — Launch an admin terminal so DISM can write into system servicing areas.
  2. Run RestoreHealth — Enter DISM /Online /Cleanup-Image /RestoreHealth and let it finish. It can sit at one percentage for a while.
  3. Restart Windows — Reboot after DISM completes to reset servicing state and release locks.

Run SFC After DISM

SFC checks protected files and swaps in clean copies when it finds mismatches. Microsoft documents the scan and replacement behavior in its SFC references. SFC command documentation

  1. Open Terminal As Admin — Use the same admin window after reboot, or open a new one.
  2. Run Scannow — Enter sfc /scannow and wait for 100% completion.
  3. Restart Again — Reboot once more so repaired files load cleanly.

Retry The Update

Go to Settings, open Windows Update, then check for updates and install. If the same code returns, move to the next section and give DISM a better source.

When DISM Needs A Local Repair Source

DISM often pulls replacement components from Windows Update. If Windows Update itself is tangled, DISM may report it can’t find source files. In that case, point DISM at a local Windows image from an ISO that matches your installed build.

Get A Matching ISO

Download a Windows 10 or Windows 11 ISO from Microsoft’s official download pages, then mount it by double-clicking it.

  • Match Edition And Language — Home vs Pro and language should line up so the component payload fits.
  • Match Version Closely — A close version match reduces “source not found” errors during repair.

Run DISM With /Source

Microsoft notes that you can provide a repair source location with the /Source argument. /Source option on Microsoft Learn

  1. Locate The Install Image — Inside the mounted ISO, open sources and find install.wim or install.esd.
  2. Run RestoreHealth With Source — Use one of these patterns:
    • Use WIM — DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\install.wim:1 /LimitAccess
    • Use ESD — DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:X:\sources\install.esd:1 /LimitAccess
  3. Replace X — Swap X for the mounted ISO drive letter.
  4. Restart Then Run SFC — Reboot, then run sfc /scannow again to finish verification.

After this, try Windows Update again. Many stubborn cases clear once DISM has a local source to pull from.

Reset Windows Update Components And Retry

If the component store is healthy yet Windows Update still errors, the cache or update services may be stuck. Resetting update components clears queued downloads and rebuilds the local update store. Microsoft’s Windows Update troubleshooting page walks through common reset steps and follow-up checks. Microsoft Windows Update troubleshooting

Reset The Cache Folders

These commands stop update services, rename the cache folders, then start services again.

  1. Open Terminal As Admin — Use Terminal (Admin) or Command Prompt (Admin).
  2. Stop Update Services — Run:
    • Stop Wuauserv — net stop wuauserv
    • Stop Bits — net stop bits
    • Stop Cryptsvc — net stop cryptsvc
  3. Rename Cache Folders — Run:
    • Rename SoftwareDistribution — ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
    • Rename Catroot2 — ren %systemroot%\System32\catroot2 catroot2.old
  4. Start Services Again — Run:
    • Start Cryptsvc — net start cryptsvc
    • Start Bits — net start bits
    • Start Wuauserv — net start wuauserv
  5. Restart And Retry Update — Reboot, then check for updates again.

If the update installs, you can delete the .old folders later to reclaim space. If it fails again, the next step is a repair reinstall that keeps your files and apps.

Repair Reinstall Options That Keep Your Apps

When store repair and cache reset don’t clear the issue, a repair reinstall rebuilds Windows system files while keeping your data and installed apps. Two options are worth knowing: an in-place upgrade from an ISO, and the Settings option that reinstalls the current version using Windows Update.

Run An In-Place Upgrade From ISO

Mount a matching Windows ISO, run Setup.exe, then choose to keep personal files and apps. This refreshes servicing components.

  1. Mount The ISO — Double-click the ISO so it appears as a drive.
  2. Start Setup — Open the drive and run Setup.exe.
  3. Choose Keep Files And Apps — Pick the option that retains your apps and data, then let it complete.
  4. Run Windows Update — After the upgrade, check for updates again.

Use The “Fix Problems Using Windows Update” Reinstall

Windows 11 includes a system repair option that reinstalls your current version from Windows Update. Microsoft describes it as a way to fix issues, with Windows Update problems called out as a common trigger. Reinstall current version details

  1. Open System Repair Settings — Settings > System > System Repair.
  2. Select Reinstall Now — Under “Fix problems using Windows Update,” choose Reinstall now if it’s available.
  3. Follow The Prompts — Keep the device plugged in and let Windows finish the reinstall.
  4. Check For Updates — Once you’re back at the desktop, run Windows Update again.

If you’re on Windows 10, the ISO in-place upgrade is the closest equivalent. If you’re on Windows 7 in a legacy setup, use the note below.

Windows 7 Note And Server Edge Cases

Some offline or legacy devices still run Windows 7. On Windows 7, this error can tie to servicing store corruption that the System Update Readiness Tool (CheckSUR) was designed to repair. Microsoft still hosts the package in the Update Catalog. Update Catalog entry for KB947821

  • Install CheckSUR — Pick the KB947821 package that matches x86 or x64, install it, then reboot and retry updates.
  • Review The Log — CheckSUR writes logs you can read if it reports it can’t fix a component.

On Windows Server, the same core idea applies: repair the component store with DISM, run SFC, then retry the update or the role/feature install. Microsoft’s troubleshooting article for update corruption on Windows Server lays out DISM-based repair steps and deeper servicing options. Windows Server update corruption repair

Habits That Reduce Repeat Failures

Once you’ve cleared the error, a few habits lower the odds of hitting it again. They reduce the usual triggers that damage update staging.

  • Keep Free Space Available — Updates need room to stage and roll back. Low disk space often shows up before broken installs.
  • Avoid Hard Power-Offs — If Windows says it’s installing, let it finish. Forced restarts mid-servicing can leave the store inconsistent.
  • Stick To Built-In Cleanup — Some aggressive cleaners remove files Windows expects to keep. Use Storage settings or Disk Cleanup.
  • Restart After Big Updates — After large cumulative updates or feature updates, a restart helps finalize component registration.
  • Run Periodic File Checks — If you’ve had crashes or unexpected shutdowns, running sfc /scannow once can catch issues early.

If you hit the same code again, return to the same order: quick checks, DISM, SFC, then cache reset. Save repair reinstall options for the cases where servicing is too tangled for command-line repairs.

One last note: write down the code exactly if you’re saving it for later. A single digit off can lead you down the wrong trail. If you see 0x80073712 error in update history again after finishing the repair track, it’s a good signal to use the ISO source method instead of looping on scans.