Windows 11 "The Component Store is Repairable"

KevTech said:

After running restore health are you also checking the system files?

sfc /scannow

Correct order is to restore health then check system files with sfc.

Click to expand...

wiganken said:

After restorehealth restart the computer and then run sfc

Click to expand...

wiganken said:

After restorehealth restart the computer and then run sfc

Click to expand...

KevTech said:

Restart is not necessary to check system files.

Click to expand...

zbook said:

1) Please post a link for these zipped files:

C:\windows\logs\CBS\CBS.log
C:\windows\logs\CBS\CbsPersist


2) Download to a new desktop folder:

Download Official Windows 11 ISO file from Microsoft

This tutorial will show you how to download an official Windows Server or Windows 11 64-bit or ARM64 ISO file from Microsoft. Microsoft provides ISO files for Windows Server and Windows 11 to download. You can use these ISO files to clean install or in-place upgrade Windows 11. The Flight Hub...

www.elevenforum.com

Download Windows 11

3) Uninstall any of these non-Microsoft software:
a) antivirus
b) firewall


4) Detach non-windows disk drives


3) Mount the iso

Mount or Unmount ISO and IMG File in Windows 11

This tutorial will show you how to natively mount or unmount ISO and IMG image files in Windows 11. An ISO or IMG file is a DVD disk image file. When you mount an .ISO or .IMG file, it will be added as a DVD drive in File Explorer > This PC. ISO and IMG files cannot be mounted on removable...

www.elevenforum.com

4) Perform an in place upgrade repair:

Repair Install Windows 11 with an In-place Upgrade

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

Click to expand...

PorkSnork said:

So I ran sfc/scannow and got the following output

Click to expand...

Rollback_Jockey said:

Success!

Click to expand...

PorkSnork said:

Only issue is that after this it still says when I scan again that "The component store is repairable"

Click to expand...

Rollback_Jockey said:

You can kill that with an InPlace update.

Click to expand...

zbook said:

zbook said:

See if these steps make any difference:


1) Open administrative command prompt and copy and paste:

DISM /Online /Cleanup-Image /StartComponentCleanup

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Analyze and Clean Up Component Store (WinSxS folder) in Windows 11

This tutorial will show you how to analyze and clean up the component store (WinSxS folder) to reduce its size in Windows 10 and Windows 11. The WinSxS folder is located in the Windows folder, for example C:\Windows\WinSxS. It’s the location for Windows Component Store files. The Windows...

www.elevenforum.com

2) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Code:

2025-05-28 19:09:48, Info                  CBS    FLOW: Entering stage: CheckCsi
2025-05-28 19:10:33, Info                  CSI    0000000c Hashes for file member [l:16]'Task Manager.lnk' do not match.
 Expected: {l:32 ml:33 b:56fc544564946602b9d008ee854f2662e8e305136d1d189228ec73e51763dbfa}.
 Actual: {l:32 b:2d00b6df170550288cd3b28b95dabf19b4051feb8d08b9ba5836051ea50caaf5}.
2025-05-28 19:10:33, Info                  CSI    0000000d Warning: Unable to repair payload file ([l:16]'Task Manager.lnk') for component ([l:98 ml:140]'amd64_microsoft-windows-advancedtaskmanager_31bf3856ad364e35_10.0.26100.3912_none_4a73810a9bade185') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

Click to expand...

Running Tuneup plus right now. I have already input the commands you posted just before and afterward performed a scanhealth, and it showed again that the component store is repairable :/

Click to expand...

PorkSnork said:

Only issue is that after this it still says when I scan again that "The component store is repairable"

Click to expand...

Steve C said:

I did a sfc /scannow scan on my desktop PC last week which was fine. I had the same reply "The component store is repairable" using the dism scanhealth command. I then ran the dism restorehealth command which worked but the PC failed to boot and had to reciver from my Reflect backup! ChatGPT advises there are situtaions where the restorehealth command is not reliable.

Click to expand...

Analyze and Clean Up Component Store (WinSxS folder) in Windows 11

This tutorial will show you how to analyze and clean up the component store (WinSxS folder) to reduce its size in Windows 10 and Windows 11. The WinSxS folder is located in the Windows folder, for example C:\Windows\WinSxS. It’s the location for Windows Component Store files. The Windows...

www.elevenforum.com

gunrunnerjohn said:

The first error is known issue.

Analyze and Clean Up Component Store (WinSxS folder) in Windows 11

This tutorial will show you how to analyze and clean up the component store (WinSxS folder) to reduce its size in Windows 10 and Windows 11. The WinSxS folder is located in the Windows folder, for example C:\Windows\WinSxS. It’s the location for Windows Component Store files. The Windows...

www.elevenforum.com

I haven't run across the failure with restorehealth like that. I would think that unless you ran the SFC /SCANNOW that the actual boot process wouldn't change regardless what happened to the system image in WinSxS. The SFC is what repairs the operating files from the WinSxS image folder.

Click to expand...

So why did DISM cause a new problem?​

1.​

• DISM /RestoreHealth pulls clean system components either from:
  
  • Windows Update (default)
  • A local install.wim/esd file if you provide one
• The replacements may be newer, or slightly mismatched, compared to the rest of your installed updates or drivers — especially if you're on a Preview, Insider, or non-standard install.

2.​

• You had no functional issues before — so the "corruption" DISM fixed may have been:
  
  • Benign metadata inconsistencies (harmless mismatches)
  • Stale cache entries in the Component Store
• DISM may replace DLLs or modules (like wcnagent.dll, .mui files etc. — as you saw in the log), which were not actually broken. Windows doesn’t always behave well if modules are replaced unexpectedly.

3.​

• DISM doesn’t know or care about 3rd-party integrations.
• If any account-switching hooks, drivers, or startup items rely on files DISM touched, you can get freezes or even BSODs — particularly when switching users triggers profile unload/reload events.

4.​

• If you recently had a Windows Update (especially a preview build, security patch, or driver update), and DISM reverted certain files, it may have caused driver or service mismatches.
• You mentioned past Wi-Fi driver errors — if any system components tied to networking or user profiles were reverted, it could have exposed a previously dormant incompatibility.

Why​

• sfc /scannow only checks core system files — it doesn't validate version consistency across the entire OS.
• SFC is less aggressive than DISM — it won’t replace things unless the hash is known to be wrong.
• Your system was stable because it had working, though slightly nonstandard, components — DISM "fixed" them and broke the balance.

Bottom Line:​

• If your PC was working perfectly and sfc /scannow showed no issues, running DISM /RestoreHealth was not needed and, in your case, introduced instability.
• The so-called “corruption” DISM repaired likely involved non-critical, localised payload metadata — nothing that was harming performance or stability.

Recommendation:​

• Your system works perfectly now
• sfc /scannow shows no issues
• The Component Store "corruption" was minor and now avoided