Windows 11 Error with DISM RestoreHealth

pseymour said:

Funny, we just do repair install, reboot, then RestoreHealth. ScanHealth and SFC come back clean after that, as does CBS.log. That's just actual experience with hundreds of devices though. Admittedly, I am not a large language model.



Claude apparently doesn't know its WinSxS from a hole in the ground.

Click to expand...

I've done the repair from the system menu, but it didn't solve everything. ScanHealth still shows "The component store is repairable" and while RestoreHealth is successful, it doesn't really repair, ScanHealth still shows "The component store is repairable"... it's a loop.

I ran a startComponentcleanup then a ScanHealth that said the component store was repairable, and finally a RestoreHealth and it said everything was fine! All fixed, right? Not so fast! I ran the ScanHealth again and it was back to the component store was repairable. I ran the RestoreHealth again and it said it can't find the repair files anywhere.

I think Microsoft really screwed up the works here!

There have been multiple threads here on the issue...

Fails for some, works normally for others (which it does for us...with no hoop jumping...25H2 with August 2026 updates installed).

A couple of free tools from Sysnative to detect and fix corruption...

ComponentsScanner

SFCFix

Some may disagree, but if sfc is working, and you can do an In-Place Upgrade, I wouldn't worry too much about dism.

The irony is that a fix was pushed in the June 2026 updates for the same thing.

A "fix".................... ?????