Windows Repair Guide Β· 2026

How to Restore the Windows Component Store
in Windows 10 & Windows 11

A practical step-by-step guide to repairing WinSxS corruption, fixing DISM errors, and restoring system files without reinstalling Windows from scratch.

⏱ ~12 min read Windows 10 Windows 11 DISM / SFC / ISO repair source

The Windows component store is one of the most important repair mechanisms inside Windows 10 and Windows 11. It contains the files Windows uses to install features, repair system corruption, uninstall updates, and service the operating system. When this store becomes damaged, normal troubleshooting often stops working: Windows Update fails, optional features refuse to install, sfc /scannow cannot repair files, and DISM may return errors such as 0x800f081f or 0x800f0906.

πŸ’‘
Quick answer Open Command Prompt or Windows Terminal as administrator, run DISM /Online /Cleanup-Image /RestoreHealth, restart the PC, then run sfc /scannow. If DISM cannot download repair files, use a Windows ISO as the source, as shown later in this guide.

What Is the Windows Component Store and Why Does It Matter?

The component store is located mainly in the C:\Windows\WinSxS folder. It is not just a backup folder and should not be deleted manually. Windows uses it to keep component versions, install cumulative updates, enable optional features, and repair protected system files. DISM repairs the component store, while SFC uses the repaired store to replace corrupted operating system files.

What the component store is used for

  • Installing and uninstalling Windows updates.
  • Enabling optional features such as .NET Framework, Hyper-V, and SMB components.
  • Repairing system files with SFC and DISM.
  • Keeping side-by-side component versions required by Windows servicing.

What you should not do

  • Do not delete the WinSxS folder manually.
  • Do not remove component store files with third-party cleaners.
  • Do not interrupt DISM while it is repairing the image.
  • Do not use a repair ISO from a different Windows version or build if avoidable.

Common Symptoms of a Corrupted Windows Component Store

Component store corruption does not always appear as a direct WinSxS error. In many cases, it shows up as failed updates, missing system files, or repair commands that cannot complete.

Symptom What It Usually Means Best First Fix
sfc /scannow says it found corrupt files but could not fix some of them SFC cannot find clean replacements in the local store Run DISM /RestoreHealth, then run SFC again
Windows Update repeatedly fails Servicing stack, update cache, or component payload may be damaged Run DISM and reset Windows Update components
0x800f081f DISM cannot find the source files needed for repair Use a mounted Windows ISO as the repair source
0x800f0906 Repair source cannot be downloaded or accessed Check internet/proxy or use local source files
Optional features fail to install Windows cannot retrieve or apply feature payloads DISM repair plus Windows Update reset

Before You Restore the Component Store: Important Preparation Steps

DISM and SFC are safe built-in Windows tools, but component repair can take time and may require a restart. Prepare the system before running the repair commands.

  1. Open an elevated terminal. Right-click Start and select Terminal (Admin), Windows PowerShell (Admin), or Command Prompt (Admin).
  2. Connect to the internet. By default, DISM may use Windows Update to download missing repair files.
  3. Temporarily disable VPN or proxy software. If your connection blocks Microsoft update servers, DISM may fail with source-related errors.
  4. Make sure the system drive has free space. Keep at least several gigabytes free on drive C: before repairing or cleaning the component store.
  5. Create a restore point. Search for Create a restore point, open System Protection, and click Create.
⚠️
Important Do not close the terminal window while DISM is running. The progress indicator may appear frozen for several minutes, especially around 62.3% or another fixed percentage. This is often normal.

Check the Windows Component Store Health with DISM

Start with a health check. These commands do not repair anything at first; they tell you whether the component store is healthy, repairable, or marked as corrupted.

1. Run CheckHealth

CheckHealth is the fastest test. It checks whether Windows has already detected component store corruption.

DISM /Online /Cleanup-Image /CheckHealth

2. Run ScanHealth

ScanHealth performs a deeper scan. It takes longer but gives a more complete result.

DISM /Online /Cleanup-Image /ScanHealth

Possible results include:

Restore the Windows Component Store with DISM RestoreHealth

The main repair command is DISM /Online /Cleanup-Image /RestoreHealth. It scans the running Windows installation and attempts to replace damaged component store files. If the PC has access to Windows Update, DISM can usually download the required files automatically.

DISM /Online /Cleanup-Image /RestoreHealth

Wait until the command reaches 100%. When it completes successfully, restart the computer. Then continue with SFC in the next section. DISM repairs the component store; SFC repairs actual protected system files using that repaired store.

🧩
Recommended order Run DISM first, restart, then run SFC. Running SFC before DISM is not harmful, but if the component store is corrupted, SFC may not be able to complete repairs.

What to Do If DISM Gets Stuck

DISM can appear stuck even when it is still working. Leave it for at least 30–60 minutes on slow systems. If the PC is responsive but there is no disk or CPU activity for a very long time, restart Windows and run the command again from an elevated terminal.

Run SFC After DISM to Repair Windows System Files

After DISM finishes, run the System File Checker. This verifies protected Windows files and replaces corrupted copies with clean versions from the component store.

sfc /scannow

Interpret the result as follows:

If SFC still cannot repair files after DISM succeeds, check the CBS log:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfc-details.txt"

This creates a simplified report on the desktop named sfc-details.txt.

Use a Windows ISO as a DISM Repair Source

If DISM fails with 0x800f081f, 0x800f0906, or a message such as β€œThe source files could not be found”, Windows Update could not provide the repair files. In that case, use a Windows ISO that matches your installed version, edition, language, and architecture as closely as possible.

Step 1: Mount the Windows ISO

  1. Download the correct Windows 10 or Windows 11 ISO from Microsoft.
  2. Right-click the ISO file and select Mount.
  3. Note the new drive letter, for example D:.

Step 2: Check Whether the ISO Contains install.wim or install.esd

Open the mounted ISO and go to the sources folder. Look for one of these files:

Step 3: Find the Correct Edition Index

If the ISO contains install.wim, run:

DISM /Get-WimInfo /WimFile:D:\sources\install.wim

If the ISO contains install.esd, run:

DISM /Get-WimInfo /WimFile:D:\sources\install.esd

Find the index number that matches your installed edition, such as Windows 11 Pro or Windows 10 Home. You can check your edition in Settings β†’ System β†’ About.

Step 4: Run DISM with the ISO as the Source

Replace D: with your mounted ISO drive letter and replace 6 with the correct index number for your edition.

For install.wim:

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:6 /LimitAccess

For install.esd:

DISM /Online /Cleanup-Image /RestoreHealth /Source:ESD:D:\sources\install.esd:6 /LimitAccess

The /LimitAccess parameter tells DISM not to contact Windows Update and to use the specified local source instead. After the command completes, restart the PC and run:

sfc /scannow

Reset Windows Update Components If DISM Cannot Download Repair Files

DISM often relies on Windows Update as a repair source. If Windows Update itself is broken, component store repair may fail. Resetting the update cache and services can restore access to repair payloads.

Open Terminal (Admin) or Command Prompt (Admin) and run these commands one by one:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start msiserver
net start bits
net start cryptSvc
net start wuauserv

Restart Windows and run DISM again:

DISM /Online /Cleanup-Image /RestoreHealth
⚠️
Note Renaming SoftwareDistribution clears the local update cache. Windows Update history may look reset, but installed updates are not removed.

Clean Up the Windows Component Store Safely

Restoring the component store is different from cleaning it. Repair should come first. After Windows is healthy, you can reduce component store size using supported cleanup tools.

Analyze Component Store Size

DISM /Online /Cleanup-Image /AnalyzeComponentStore

Start Component Store Cleanup

DISM /Online /Cleanup-Image /StartComponentCleanup

This removes superseded components that Windows no longer needs. It is safer than deleting files manually from WinSxS.

Optional: ResetBase Cleanup

This command removes the ability to uninstall currently installed updates. Use it only when the system is stable and you do not need to roll back recent updates.

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Advanced Fixes When the Component Store Still Cannot Be Restored

If DISM and SFC still fail after using a correct ISO source, the Windows installation may have deeper servicing damage. Use the following options in order.

1. Check the disk for file system errors

Run a disk check on the system drive:

chkdsk C: /scan

If Windows reports problems that require offline repair, run:

chkdsk C: /f

2. Check system health in Safe Mode

Boot into Safe Mode and run DISM/SFC again. This helps when third-party antivirus, backup tools, or drivers interfere with repair operations.

Perform an In-Place Repair Install

An in-place repair install reinstalls Windows over the existing installation while keeping personal files, installed apps, and most settings. It is the best last-resort method before resetting the PC.

  1. Download a Windows ISO that matches your current Windows version.
  2. Mount the ISO.
  3. Run setup.exe from the mounted drive.
  4. Select Keep personal files and apps.
  5. Follow the installer until the repair upgrade completes.

Recommended Repair Sequence

Use this order for best results: CheckHealth β†’ ScanHealth β†’ RestoreHealth β†’ restart β†’ SFC β†’ ISO source repair β†’ Windows Update reset β†’ component cleanup β†’ in-place repair install.

Frequently Asked Questions About Restoring the Windows Component Store

Q Is it safe to run DISM RestoreHealth? β–Ό
Yes. DISM /Online /Cleanup-Image /RestoreHealth is a built-in Windows repair command. It repairs the servicing image and component store. It does not delete personal files or installed programs.
Q Should I run SFC or DISM first? β–Ό
For serious corruption, run DISM first, restart, and then run SFC. DISM restores the component store, and SFC uses that store to replace damaged system files.
Q Can I delete the WinSxS folder to free disk space? β–Ό
No. Do not delete C:\Windows\WinSxS manually. Use Disk Cleanup or DISM /Online /Cleanup-Image /StartComponentCleanup instead.
Q Why does DISM show error 0x800f081f? β–Ό
Error 0x800f081f usually means DISM cannot find the repair source files. Mount a matching Windows ISO and run DISM with the /Source parameter.
Q How long does component store repair take? β–Ό
On a fast SSD it may take 5–20 minutes. On older systems, heavily corrupted installations, or slow internet connections, it may take much longer. A stuck-looking progress indicator does not always mean the command has failed.

Best Way to Restore the Windows Component Store

The most reliable way to restore the Windows component store is to repair the servicing image with DISM, restart Windows, and then repair protected system files with SFC. If DISM cannot find the required source files, mount a matching Windows ISO and point DISM to install.wim or install.esd. Avoid manual WinSxS deletion and use only supported cleanup commands after the system is healthy.

βœ…
Final command set For most users, the essential repair sequence is: DISM /Online /Cleanup-Image /RestoreHealth β†’ restart β†’ sfc /scannow.