Windows Update Error 0x80073712: Repair the Component Store Step by Step

Error 0x80073712 (ERROR_SXS_COMPONENT_STORE_CORRUPT) means Windows Update found that the component store — the folder of every system file version Windows might ever need to patch itself, called WinSxS — is missing a piece or has a piece that doesn't match what it expects. The fix, in order, is: run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, then reset the Windows Update cache if it still fails. Running SFC before DISM can actually make things worse, not better, because SFC copies replacement files from the very store DISM is meant to repair — if that store is the broken thing, SFC is copying from a source that's already damaged.

What error 0x80073712 actually means

ERROR_SXS_COMPONENT_STORE_CORRUPT translates, literally, to "the component store is in an inconsistent state." The component store is a real folder on your drive: C:\Windows\WinSxS. SxS stands for "side-by-side," because that folder holds side-by-side copies of nearly every version of every system component — DLLs, drivers, manifests — that Windows has ever installed on your machine or might need to install. When you apply a cumulative update, Windows doesn't overwrite a file in place; it stages a new version into WinSxS and switches a pointer to it. That's how updates can be uninstalled cleanly. It's also why the folder is enormous and, occasionally, why a piece of it goes missing or mismatched.

Windows keeps a running log of every check and repair attempt it makes against that store, at %windir%\Logs\CBS\CBS.log (and a rolled-over copy at CBS.persist.log). CBS stands for Component Based Servicing — the subsystem that manages WinSxS. When Windows Update or DISM scans the store and finds a manifest, a registration, or a payload file that doesn't match what it expects, it writes a line to CBS.log describing exactly what's wrong, and it surfaces 0x80073712 (or a related SXS/CBS code) to the update UI. The error isn't vague by nature — the vague part is that Settings never shows you the log entry that explains it.

The practical upshot: this is not the same problem as a failing hard drive, and it's rarely malware. It's a specific, nameable file or registry entry under one of a small number of locations — %SYSTEMROOT%\Servicing\Packages, %SYSTEMROOT%\WinSxS\Manifests, or the registry keys under HKEY_LOCAL_MACHINE\Components and HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing — that DISM checks and, in most cases, can replace on its own.

Why the component store gets corrupted in the first place

Nobody breaks WinSxS on purpose, and there's no single cause — but a few patterns show up over and over in the update logs:

• An update was interrupted mid-install. A forced shutdown, a power cut, or closing the lid during "Working on updates" can leave a package half-staged.
• The drive ran out of space while a large cumulative update was applying. WinSxS needs headroom to stage the new files before it can retire the old ones.
• A previous manual fix went wrong. Deleting files inside WinSxS by hand, restoring an old system-image backup over a newer one, or running a "system cleaner" that touches Windows folders can remove a file the store still expects to find.
• Disk errors. A failing sector under a WinSxS file corrupts the payload without deleting it, so the file exists but doesn't match its recorded hash.
• A servicing stack update is missing or out of order. Cumulative updates sometimes depend on a newer servicing stack update being applied first; skipping ahead can leave the store expecting a package that was never installed.

Malware that specifically targets WinSxS is uncommon, but it's not zero, so a quick scan with whatever you're already running (Microsoft Defender's built-in scan counts) is a reasonable five minutes before you move on — it's not the first suspect, and it's rarely the actual cause.

Jake's first guess, every time, is malware. "Something got in, right? That's why it's corrupted?" Ethan pushes back on that instinct. "It's almost never the villain people want it to be," he says. "It's usually a stalled update or a drive that was too full, not something sneaking in. Run the scan if it helps you sleep, but don't let it delay the actual fix by an afternoon."

Three things to check before you run anything

DISM and SFC both need working room. Skipping this step is the single most common reason people run the repair twice for no reason.

1. Free disk space. Open File Explorer, right-click your C: drive, and check Properties. DISM and SFC both need working room to stage replacement files; a nearly-full drive is a common reason a repair fails partway through with a different, unrelated-looking error. If you're low, run Disk Cleanup first.
2. No pending restart. If Settings > Windows Update is showing "Restart required," restart first. A pending restart means an earlier update is only half-applied, and DISM will report the same inconsistency you're trying to fix.
3. Stay on power. If you're on a laptop, plug it in. An interrupted repair is exactly the kind of event that caused this error in the first place.

Fix it on Windows 11 (25H2 and 24H2)

These commands work the same on Windows 11 Home and Pro — component-store repair doesn't touch anything Home edition is locked out of, so you don't need Group Policy or any Pro-only tool here.

1. Open an elevated Command Prompt using the shortcut above.
2. Run the DISM repair:

   DISM.exe /Online /Cleanup-image /Restorehealth

   Microsoft's own guidance is blunt about this one: it may take several minutes to complete, and it can look stalled at points while it verifies rather than downloads. Let it run.

3. Wait for the result line. You want to see "The restore operation completed successfully." If instead it says the operation completed but with "The source files could not be found," see the offline-source section below.
4. Run System File Checker, in the same window:

   sfc /scannow

   SFC checks protected system files against the (now-repaired) component store and replaces anything it finds mismatched. Running it after DISM, not before, is the order that actually matters — SFC's replacement source is the store DISM just fixed.

5. Restart the PC, then check for updates again: Settings > Windows Update > Check for updates.

Fix it on Windows 10

Windows 10 reached the end of free support on October 14, 2025. Your PC still boots, still runs, and DISM still works exactly as described below — but if you're seeing 0x80073712 while trying to install a security update on an un-enrolled Windows 10 machine, there is no longer a fresh monthly fix coming unless you've enrolled in Extended Security Updates. More on that after the steps.

The repair itself is identical to Windows 11:

1. Press Win, type cmd, right-click Command Prompt, and choose Run as administrator. (Windows 10's context menu isn't condensed the way Windows 11's is, so the option shows up directly.)
2. Run DISM.exe /Online /Cleanup-image /Restorehealth and wait for it to finish.
3. Run sfc /scannow.
4. Restart and retry Windows Update.

These steps are the same on both versions of Windows — the only difference is how you get to an elevated prompt, and the ESU question above.

If DISM says it fixed "some" corruption: reading CBS.log

Sometimes DISM's summary line reads something like "The restore operation completed" with a caveat, or the operation result shows an error code even after repairs happened. Open %windir%\Logs\CBS\CBS.log in Notepad and search (Ctrl+F) for "Summary:" — the last one in the file is the most recent scan. It looks like this:

Total Detected Corruption: 2
   CBS Manifest Corruption: 2
Total Repaired Corruption: 1
   CBS Manifest Repaired: 1

That means DISM found two problems and could only fix one on its own. The lines just above the summary, marked (p), name the specific package or file it couldn't repair — something like Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.26100.4291. The long number at the end is the build the file belongs to.

If a specific package name shows up unfixed, you can match its build number against the Microsoft Update Catalog and copy that one package's files into a source folder for DISM to pull from — that's an IT-professional-level fix meant for a single stubborn package, not a first move, and most home users never need it. For nearly everyone, the next step is simpler: reset the update cache and let DISM run again with a clean starting point.

Still failing? Reset the Windows Update components

If DISM and SFC both report success but the same update keeps failing with 0x80073712 or a related error, the problem may not be the store itself anymore — it may be a stuck, corrupted download sitting in the Windows Update cache. Clearing that cache is a different repair from anything above, and it's safe: it doesn't touch your files or installed programs, only the update download queue.

1. In the same elevated Command Prompt, stop the three services involved:

   net stop wuauserv
net stop cryptsvc
net stop bits

2. Rename the two cache folders so Windows rebuilds them fresh:

   ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
ren %systemroot%\System32\catroot2 catroot2.bak

3. Restart the services:

   net start wuauserv
net start cryptsvc
net start bits

4. Restart the PC and check for updates again.

You can safely delete the .bak folders once the update has installed successfully. If it still fails afterward, try the automated Windows Update Troubleshooter (Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run) — it runs a version of this same reset plus a scan-cycle restart, and occasionally catches something the manual steps miss.

No internet connection, or DISM can't find source files

DISM's default repair pulls replacement files straight from Windows Update, so it needs a connection. If your PC can't reach the internet, or DISM reports the source files couldn't be found even though you're online, you can point it at a working Windows installation instead — either another PC on the network running the identical Windows version, or a mounted installation image:

DISM /Online /Cleanup-Image /RestoreHealth /Source:\\SERVERNAME\c$\windows /LimitAccess

Replace SERVERNAME with the name of the source computer, and make sure it's running the same build. This is the same command IT departments use to repair machines with no internet access on their network at all.

What this page genuinely cannot do for you: if you have no internet connection, no second PC on the same build, and no installation image, there is no local trick that substitutes for a working source. DISM repairs by copying signed files from somewhere; if there's nowhere to copy them from, the repair cannot complete, full stop. That's the point at which borrowing a friend's laptop and a USB drive, or waiting until you're back on a connection, is the honest next step — not a registry edit.

The last resort: repair install (not a clean install)

If every step above still leaves you with 0x80073712, the component store's corruption is deeper than DISM can patch — usually meaning multiple packages are missing with no local or network source available. Windows has a built-in option for exactly this: if Settings ever shows the message "Reinstall your current version of Windows to repair system files and components," selecting Reinstall now opens a guided repair that reinstalls Windows over itself while keeping your files, apps, and settings. If that prompt doesn't appear on its own, you can trigger the same kind of repair manually with the Windows 11 Installation Assistant or the Windows 10 Media Creation Tool from Microsoft, choosing Keep personal files and apps when it asks.

Windows 11 vs. Windows 10: what's actually different here

People assume component-store repair needs a "Pro" edition because so many Windows fixes do. It doesn't — DISM and SFC are identical, command for command, across Home and Pro on both Windows 11 and Windows 10. What actually differs is the surrounding path to a fix:

What to skip, and what actually helps

Ethan has strong feelings about the third-party "PC repair" and registry-cleaner tools that show up in search results for this error. "They're the worst of the shortcuts people try here," he says. "A registry cleaner doesn't know what a valid Component Based Servicing key looks like — it just sees an entry it doesn't recognize and offers to delete it. That's how you turn a fixable 0x80073712 into a Windows install that won't boot." His advice: if a tool asks to "optimize" or "clean" anything under HKEY_LOCAL_MACHINE\Components, close it.

What does help, alongside the DISM/SFC repair: pausing any third-party antivirus's real-time scanning for the few minutes the repair runs (some security suites intercept file writes into WinSxS and can interfere), making sure you're not mid-download on a metered or unstable connection, and, if this is a recurring problem on the same machine, running chkdsk /scan from an elevated prompt to rule out a failing drive as the reason files keep going bad in the first place.

The adjacent question: is a huge WinSxS folder a sign this will happen again?

Once people learn what WinSxS is, the next question is usually "why is it 10+ GB, and should I shrink it?" You can check for yourself, from the same elevated Command Prompt:

DISM /Online /Cleanup-Image /AnalyzeComponentStore

This prints a breakdown — the reported size, how much is actually shared with running Windows versus held as backups for old, superseded components, and a line that reads either "Component Store Cleanup Recommended: Yes" or "No." If it says yes, you can reclaim space with:

DISM /Online /Cleanup-Image /StartComponentCleanup

Adding /ResetBase to that command goes further and permanently removes every superseded version of every component, which frees more space but means you can no longer uninstall updates that are already applied. Windows actually runs a version of this cleanup automatically, on its own schedule, through a Task Scheduler entry at Task Scheduler Library\Microsoft\Windows\Servicing\StartComponentCleanup — by default it waits at least 30 days after a component updates before removing the older version, specifically so you still have a rollback option in the meantime.

Ethan's blunt about the size question: "A big WinSxS folder isn't proof anything's wrong. It's proof the store is doing exactly what it's built to do — keeping old component versions around in case you need to roll back." He only runs StartComponentCleanup on a machine he's sure isn't about to need an uninstall, and he treats ResetBase as a one-way door, not a routine chore.

Don't run cleanup as a fix for 0x80073712 itself, though — it solves a different problem. If /AnalyzeComponentStore fails or reports the store itself is damaged, that confirms you're dealing with corruption, not bloat, and the DISM /RestoreHealth steps earlier in this post are still the right next move, not this one.

Related reading

Frequently asked questions

What does error 0x80073712 mean?

It's ERROR_SXS_COMPONENT_STORE_CORRUPT: Windows Update checked the component store (the WinSxS folder that holds every version of system files Windows might need) and found a file, manifest, or registry entry missing or mismatched.

Is 0x80073712 caused by a virus or malware?

Rarely. Most cases trace back to an interrupted update, low disk space during an install, or a manual edit to system folders. A quick malware scan is reasonable but is usually not where the answer lives.

Will I lose my files fixing this?

No, not for the DISM, SFC, or update-component-reset steps — none of them touch personal files. Only the very last resort, a full Reset This PC with "Remove everything" selected, removes files, and that option is never required just to fix this error.

Do I need to be signed in as an administrator?

You need administrator rights to run an elevated Command Prompt, which every fix on this page requires. On a personal PC, your own account is usually already an administrator; on a work or school PC, you may need IT to run these steps for you.

How long does the DISM repair take?

Microsoft's own guidance describes it as taking several minutes to complete, and it can appear to stall at points while it verifies files rather than downloading them. That's expected, not a freeze.

What if DISM says it "could not complete the operation"?

Open CBS.log, find the last "Summary:" section, and check whether the source files couldn't be found — if so, try the offline-source command with a network share or installation image. Otherwise, move on to resetting the Windows Update components.

Should I run SFC before DISM, or after?

After. SFC repairs system files by copying replacements from the component store; if that store is what's corrupted, run DISM first so SFC has a good source to copy from.

Can I fix this without an internet connection?

Yes, if you have access to another working PC on the same Windows version, or a mounted Windows installation image, by pointing DISM at that source with the /Source and /LimitAccess options instead of letting it reach out to Windows Update.

Does this happen on Windows 10 too, or only Windows 11?

Both. The component store and the DISM/SFC repair process are the same architecture across both versions; only the path to an elevated prompt and the update-support status differ.

What if I don't have enough free disk space?

Free up space with Disk Cleanup (search for it, then "Clean up system files") to clear old update leftovers and temporary files, or move large personal files to external storage temporarily, then try the repair again.

Should I use a third-party registry cleaner to fix this?

No. Registry cleaners don't understand which Component Based Servicing entries are valid, and deleting the wrong one can turn a fixable error into a Windows install that won't boot. DISM is the tool built to make this exact judgment safely.

What if the error happens during a feature update, like moving to a new version?

The same DISM and SFC repair applies before you retry the feature update. If it still fails afterward, using the Installation Assistant (Windows 11) or Media Creation Tool (Windows 10) to perform the upgrade directly, rather than through Windows Update, sometimes succeeds because it uses a full, self-contained source instead of an incremental patch.

Can antivirus software cause this error?

Some third-party security suites intercept file writes during servicing operations and can interfere with a repair in progress. It's worth temporarily pausing real-time protection while DISM and SFC run, then re-enabling it afterward.

What's the difference between "Reset this PC" and a repair install?

A repair install (reinstalling Windows while keeping files and apps) rebuilds the component store and system files but leaves your installed programs in place. "Reset this PC" with "Remove everything" wipes the drive back to a clean state. For 0x80073712, a repair install is the appropriate last resort; a full reset is not necessary.

Will resetting Windows Update components delete my update history?

It renames the download cache and re-creates it, which can clear the visible list of recently offered updates in Settings, but it does not uninstall updates already applied to your system or remove any personal files.

Is Windows 10 still getting fixes for this kind of error after end of support?

DISM and SFC still work on Windows 10 regardless of ESU status, since they're local repair tools, not delivered updates. What ESU affects is whether new security updates keep arriving after the store is fixed; without enrollment, Windows 10 (22H2) stopped receiving free security updates on October 14, 2025.

Revision note. Written August 2026, covering Windows 11 (25H2 and 24H2) and Windows 10 22H2, Home and Pro editions on both. This will need a fresh look once ESU enrollment closes for good or a future Windows release restructures how DISM sources repair files, so refer latest folks if not worked or let me know. If you've been staring at this error for a while, take a breath — it almost always ends with two commands, not a reinstall.