Fix 0xC015001A SXS Component Store Corrupt

Quick answer

Run DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt, then sfc /scannow, and restart. If that doesn't clear the error, reinstall the app that's failing to launch.

What's actually happening here is Windows is trying to load a Win32 app that depends on a side-by-side assembly library — usually a Visual C++ runtime or a .dll from the Windows SxS (side-by-side) folder. That folder, located at C:\Windows\WinSxS, is the system's versioned component store. When it gets corrupted — whether from a botched update, a crashed Installer process, a failing hard drive, or a forced shutdown mid-update — Windows can't find a valid copy of the assembly it needs. The result is this exact error code, and the app dies before it even starts.

I've seen this happen most often after a Windows Feature Update gets interrupted, or after a security tool (looking at you, aggressive AV) quarantines a file inside the WinSxS folder. The key thing to understand is that the component store isn't just a cache — it's the source of truth for system file integrity. So fixing it is a two-step deal: first you repair the component store itself (DISM), then you fix any files that were already extracted from it (SFC).

Fix steps

Open an elevated Command Prompt. Hit Start, type cmd, right-click Command Prompt, and pick "Run as administrator." You need admin rights because you're modifying system files.
Run DISM to repair the component store. Type this and press Enter:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
DISM uses Windows Update as the repair source by default. It checks the component store for corruption and replaces broken files. This can take 10 to 20 minutes, so let it finish — don't kill it.
Run SFC to fix system files. After DISM reports success (even if it says "no corruption detected," run this anyway), type:
```
sfc /scannow
```
SFC compares every protected system file against the freshly repaired component store and replaces any mismatches.
Restart your PC. This isn't optional. DISM and SFC stage changes that only apply cleanly on boot.
Try launching the app again. If it starts, you're done. If not, go to the alternative fixes below.

Why this order works

The reason step 2 must come first is that SFC pulls replacement files from the component store. If the store itself is corrupt, SFC will either fail to repair files or — worse — copy a corrupt file over a good one, making things worse. DISM repairs the store at the source. Think of it as fixing the library before you try to check out new books.

If the main fix doesn't work

Sometimes DISM can't fix the component store because the corruption is too deep, or Windows Update can't connect. Here's what to do then.

Alternative 1: Use a known-good source for DISM

If your network is flaky or you have a Windows ISO handy, you can point DISM at a WIM file instead of Windows Update. Mount the ISO or insert the install USB, note the drive letter, then run:

DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess

Replace E: with your actual drive. This bypasses the internet entirely.

Alternative 2: Reinstall the app that triggers the error

If DISM and SFC both come back clean but the error persists, the problem might not be the global component store — it might be a specific app's local installation. Uninstall the app completely, delete any leftover folders in Program Files and AppData, then reinstall the latest version. For Visual C++ redistributables specifically, download the fresh installer from Microsoft's site and run it. That sometimes repairs an SxS registration that system tools won't touch.

Alternative 3: System Restore or in-place upgrade

If you have a restore point from before the trouble started, roll back to it. If not, an in-place upgrade repair install — running setup.exe from a Windows 10 or 11 ISO while keeping your files and apps — rewrites the entire OS while preserving your data. It's heavy, but it's the nuclear option that works when DISM can't.

Prevention tips

Never force-shutdown during Windows updates. The component store is most vulnerable mid-update. Let the update finish, even if it seems stuck for an hour.
Run chkdsk /f on your system drive quarterly. Disk errors are a silent cause of corruption. If chkdsk finds bad sectors, replace the drive sooner rather than later.
Keep your antivirus from scanning WinSxS aggressively. Most modern AVs exempt system folders. If yours doesn't, add C:\Windows\WinSxS to the exclusion list.
Take regular system restore points. One before each major app install or update. It's a ten-second click that can save you an afternoon.

The component store is one of those Windows internals you never think about until it breaks. But once you understand that it's the master copy for every system file, the fix logic becomes obvious: repair the master, then repair the copies. That's all DISM and SFC are doing. Don't skip the restart, and don't panic if the first scan takes a while — it's working.