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 did multiple repair installs using different media, on-line and ISO, the error still persists. SFC /SCANNOW doesn't report any errors, right after the repair install, so my thinking is some data that is not touched by a repair install is really causing the DISM failures.
Yep, just tried that again yesterday with build 26200.9445, did that, than a ScanHealth that said the component store was repairable, then the RestoreHealth that appeared to finish successfully. However, another ScanHealth said the component store was repairable and another RestoreHealth show the same "can't find the repair files anywhere" I've been seeing for the last few months.
I get similar now, I run DISM.exe /Online /Cleanup-Image /StartComponentCleanup then reboot which now clears the RestoreHealth error and RestoreHealth then completes successfully but Scanhealth will still show repairable anytime it's run.
I've stopped trying to fix this, obviously Microsoft has something hosed since a number of people here, and I see more if I do an Internet search on the issue. All these people can't have suddenly developed this oddball error at once without some help from Microsoft.
Same, going in circles downloading and installing ISO repairs that no longer correct the issue is not a workable solution.I've stopped trying to fix this, obviously Microsoft has something hosed since a number of people here, and I see more if I do an Internet search on the issue. All these people can't have suddenly developed this oddball error at once without some help from Microsoft.
Yep, and then I get the same indications.
Repair-WindowsImage -Online -CheckHealth
Repair-WindowsImage -Online -RestoreHealthGet-Content C:\Windows\Logs\CBS\CBS.log | Select-String -Pattern 'Payload[\s]+Corrupt'
Scroll to the "Improvements" section...
support.microsoft.com
If SFC works, and the system is running well (and repair installs are not failing), I personally wouldn't worrry about DISM.
That's amusing because the June update is when I started having these problems! Before that, I never saw an error 0x800f0915!Scroll to the "Improvements" section...
June 9, 2026—KB5094126 (OS Builds 26200.8655 and 26100.8655) | Microsoft Support
June 9, 2026—KB5094126 (OS Builds 26200.8655 and 26100.8655)
