Forum Discussion
Restore Health Cleanup-Image on Windows 11
Error 0x800f0915 was a documented DISM /RestoreHealth issue fixed by Microsoft in the June 2026 cumulative update. Your 26200.8894 build is newer than the fixed 26200.8655 build, so first install pending updates, restart, and run RestoreHealth from an elevated Command Prompt. Check the final line carefully: only “The restore operation completed successfully” means the repair succeeded; an error code means it did not, even if progress reached 100%. If it fails, review C:\Windows\Logs\DISM\dism.log and C:\Windows\Logs\CBS\CBS.log at the matching timestamp for the failing package or missing source. Then run sfc /scannow. If DISM reports source problems, mount Windows media matching the installed edition, language, architecture, and servicing level, then rerun RestoreHealth with that image as /Source and /LimitAccess. If matching 25H2 media is unavailable or logs still show 0x800f0915, use Settings > System > Recovery > Fix problems using Windows Update for a repair reinstall while keeping files and apps.
I did all of those things and the issue has remained through three releases up to the present. I tried three repair installs, first with WU as the source of the files, then a local ISO built using the MCT tool of the same build I'm running.
None of that worked, the error persists. My current build is 26200.9278 and this issue still occurs. SFC /SCANNOW runs with no errors found. Since the repair install should have replaced any corrupted files in the component store, that didn't surprise me. Obviously, something is corrupted that is not "fixed" by a repair install.