0X00003712

Fix ERROR_SXS_COMPONENT_STORE_CORRUPT (0x00003712) in Windows

The Windows component store is corrupt. This usually shows when installing updates or apps. Here's how to fix it, step by step.

What's happening?

You're seeing error 0x00003712 — that's ERROR_SXS_COMPONENT_STORE_CORRUPT. It means Windows can't read its own component store, which is the database of system files and updates. This usually hits when you're trying to install a Windows update, a software package, or a .NET Framework feature. I've seen it most often after a failed update or a sudden power loss during an update.

The good news: this is fixable. The bad news: you might need to work through a few steps. I've organized them from quickest to most thorough. You can stop as soon as the error goes away.

Step 1: Quick DISM scan (30 seconds)

Start here. It's fast and fixes most cases of component store corruption.

  1. Open the Start menu, type Command Prompt, right-click it, and pick Run as administrator. Click Yes on the UAC prompt.
  2. In the command window, type exactly this and press Enter:
    DISM /Online /Cleanup-Image /RestoreHealth
    Expect: A progress bar will show. It'll take about 10-20 minutes. Don't close the window. After it finishes, you'll see a message like "The restore operation completed successfully" or it'll tell you if it found corruption.
  3. Once that's done, type:
    SFC /SCANNOW
    Expect: This checks system files. It'll take 5-10 minutes. It will say either "Windows Resource Protection did not find any integrity violations" or it will fix files and ask you to restart.
  4. Restart your PC, even if SFC didn't find anything. Then try whatever triggered the error again — install the update, the software, or the feature.

If the error is gone, you're done. If not, move to Step 2.

Step 2: Moderate fix - Manual component store repair (5 minutes)

Sometimes the DISM scan needs a source to pull clean files from. Here's how to give it one.

  1. You'll need access to a Windows installation media — a USB stick or an ISO file. If you don't have one, download the Windows Media Creation Tool from Microsoft's website and create a bootable USB. I'm assuming you have a USB drive plugged in and it's assigned drive letter E: (adjust if yours is different).
  2. Open Command Prompt as admin again (same as Step 1).
  3. Type this command, substituting your USB drive letter:
    DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess
    Expect: This uses the clean install.wim file from your USB as a repair source. It'll take 10-20 minutes. Watch for the success message.
  4. After it finishes, run SFC again:
    SFC /SCANNOW
  5. Restart your PC and retest.

Still seeing the error? Let's go deeper.

Step 3: Advanced fix - Component Store corruption deep repair (15+ minutes)

This handles the toughest corruption. It involves resetting the component store using the servicing stack itself. You'll need a Windows installation USB again.

  1. Boot from your Windows installation USB. You can do this by restarting your PC and pressing the boot menu key (F12, F2, Esc — depends on your motherboard). Select the USB drive.
  2. On the Windows Setup screen, click Next, then click Repair your computer in the bottom-left corner.
  3. Go to Troubleshoot > Advanced options > Command Prompt.
  4. Now you're in the Windows Recovery Environment. First, find out which drive letter Windows is using. Type:
    diskpart
    list volume
    Look for the volume with the label "Windows" or the one that's about 100-200GB. Note its drive letter (probably D: or C:). Type exit to leave diskpart.
  5. Run the DISM command targeting your offline Windows installation (replace D: with your actual drive letter):
    DISM /Image:D:\ /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess
    Expect: This runs DISM against the offline Windows image. It'll take 15-30 minutes. If it succeeds, you'll see "The restore operation completed successfully."
  6. Once done, type exit to close the command prompt, then click Continue to reboot into Windows normally.
  7. After booting, run SFC again just to be safe. Open Command Prompt as admin and type:
    SFC /SCANNNOW
  8. Restart one more time, then test your original action.

This should fix it. If not, the corruption might be too deep, or you could have a failing hard drive. Run chkdsk C: /f (as admin, in normal Windows) to check for bad sectors. But in my experience, the offline DISM repair catches 95% of these cases.

What if none of this works?

Then you're looking at a Windows reinstall. Keep your data by choosing "Keep my files" during the reset. Go to Settings > Update & Security > Recovery > Reset this PC — pick the option that keeps your personal files. It's a last resort, but it'll clear the corrupt component store completely.

Related Errors in Windows Errors
Taskbar Search Box Disappeared? Fix It Fast 0X00002038 Fix ERROR_DS_OBJECT_RESULTS_TOO_LARGE (0X00002038) 0X000000CE Fix ERROR_FILENAME_EXCED_RANGE (0X000000CE) in Windows 0X80290215 Fix TBSIMP_E_NOTHING_TO_UNLOAD (0x80290215) in Windows

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.