Restore Health Cleanup-Image on Windows 11

Select Keep personal files and apps to repair Windows without data loss.

The 0x800f0915 error often indicates a missing or corrupted source file. You can specify a source for Windows updates, such as Windows installation media.

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.

The CheckHealth and ScanHealth results are the important part here: both report that the component store is healthy. If the final DISM line shows Error: 0x800f0915, the command did not complete successfully even though it reached 100%, but that does not by itself mean the Windows installation is damaged. This error usually means that DISM could not obtain the repair content it was looking for.

Run sfc /scannow once from an Administrator Command Prompt. If it reports that no integrity violations were found and Windows is otherwise working normally, there is no reason to reset the PC or use a random ISO as a repair source. Keep Windows Update current and restart after installing the next cumulative update. Microsoft has previously shipped fixes for this DISM error on some Windows 11 24H2 and 25H2 builds, so an update is the sensible first step. 

If SFC finds files that it cannot repair, or there are actual Windows problems, then check C:\Windows\Logs\DISM\dism.log for the missing component. A repair source must match the installed Windows version, edition, language, and servicing level; an older or mismatched ISO can fail in the same way. Microsoft’s guidance is to use Windows Update as the normal source, or a known-good matching repair source when one is needed.