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.
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
WinSxSfolder 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.
- Open an elevated terminal. Right-click Start and select Terminal (Admin), Windows PowerShell (Admin), or Command Prompt (Admin).
- Connect to the internet. By default, DISM may use Windows Update to download missing repair files.
- Temporarily disable VPN or proxy software. If your connection blocks Microsoft update servers, DISM may fail with source-related errors.
-
Make sure the system drive has free space. Keep at least several gigabytes free
on drive
C:before repairing or cleaning the component store. - Create a restore point. Search for Create a restore point, open System Protection, and click Create.
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:
- No component store corruption detected β the store appears healthy.
- The component store is repairable β continue with
/RestoreHealth. - The component store cannot be repaired β use a repair source or perform an in-place upgrade.
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.
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:
- Windows Resource Protection did not find any integrity violations β system files are OK.
- Windows Resource Protection found corrupt files and successfully repaired them β restart the PC.
- Windows Resource Protection found corrupt files but was unable to fix some of them β run DISM again, then repeat SFC.
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
- Download the correct Windows 10 or Windows 11 ISO from Microsoft.
- Right-click the ISO file and select Mount.
- 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:
D:\sources\install.wimD:\sources\install.esd
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
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.
- Download a Windows ISO that matches your current Windows version.
- Mount the ISO.
- Run
setup.exefrom the mounted drive. - Select Keep personal files and apps.
- 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? βΌ
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? βΌ
Q Can I delete the WinSxS folder to free disk space? βΌ
C:\Windows\WinSxS manually. Use Disk Cleanup or
DISM /Online /Cleanup-Image /StartComponentCleanup instead.
Q Why does DISM show error 0x800f081f? βΌ
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? βΌ
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.
DISM /Online /Cleanup-Image /RestoreHealth β restart β sfc /scannow.