DISM Error 0x800f0915 persists despite Windows update and reinstall

Question

Forgive me as I am not tech proficient but I am having issues with the DISM /Online /Cleanup-Image /RestoreHealth function that continues to throw up the Error 0x800f0915.

This only began after the last update to KB5089573 (OS build 26200.8524) and KB5092427 (.NET Framework). Since others were having this issue I followed every one of the fix suggestions from the various DISM clean up routines (Scan health, reset base, etc which all say the component store is repairable) to enabling the NET Framework, stopping and restarting BITS and App Readiness, and finally reinstalling the latest version of Windows 11 from the ISO file on the Microsoft website and this still didn't help.

N.B - Each time I run this restore health command it slows down around 63% and crawls for about 25 minutes before completion. And running sfc/scan now before and after makes no difference.

The last thing I tried was to mount the ISO and redirect the source to that and it still throws up the same error message that it can't be located and "The DISM engine version (10.0.26100.8521) does not match the updated image version (10.0.26200.8524)".

Now, as I said above I'm fairly dense when it comes to this stuff but doesn't this suggest the latest Windows update is not compatible with my DISM version? Do I need to wait for Microsoft to update DISM since none of the fixes work or is there one I've not yet encountered? Any help or advice would be appreciated

My PC stats are Windows 11 Home, 25H2, OS build 26200.8524, Windows Feature Experience Pack 1000.26100.315.0

Thanks in advance.

Answer 1

Hi Lee,

Generally, the error 0x800f0915 occurs if some files in the component store are missing. However, the problem is faced by many users after installing the May cumulative updates. From what I have seen, after installing the May update, a reverse-differential file named smbwmiv2.dll is flagged as missing when you run DISM. You can verify this by checking the CBS.log file after running DISM. This is most likely a minor bug in the May update. If possible, please upload the file C:\Windows\Logs\CBS\CBS.log in your next reply.

Since there are no problems installing updates and your system is up to date (OS Build 26200.8524), I'd suggest ignoring this issue and waiting for the June cumulative update, which will be released today (i.e., June 9, 2026).

Answer 2

Hi Lee,

Don't call yourself dense—you actually found the exact reason why this is happening!

Look at the error message you noticed: "The DISM engine version does not match the updated image version." This is a known issue that sometimes happens after a major Windows Update (like your recent KB5089573). Windows updated your core system files, but it forgot to update the DISM tool itself. Because your DISM tool is now "older" than the Windows system it is trying to scan, it gets confused, slows down around 63%, and throws that error.

Since you have already reinstalled Windows from a fresh ISO file and run sfc /scannow successfully, your computer is actually perfectly healthy. The only thing broken right now is the troubleshooting tool itself, not your actual system.

Here is what you can do right now:

1. The Best Option: Just Wait It Out

Since this is a version mismatch caused by the latest update, Microsoft usually fixes this automatically in the very next monthly Windows Update by giving the DISM tool a matching version number. Since your PC is currently running fine and sfc /scannow didn't find major issues, you don't need to panic. You can safely ignore this error until the next update patch drops.

2. If you absolutely need to fix it today (The Side-Load Method)

If you need DISM to work right now for another reason, you have to force it to look at a clean source that matches your build.

Go to Microsoft's website and download the Windows 11 installation ISO again (ensure it's the exact same 25H2 / 26200 build).

Double-click the downloaded ISO file to "Mount" it (it will show up like a virtual DVD drive, let's say it becomes drive E:).

Open Command Prompt as Administrator and run this exact command (replace E with whatever letter your virtual drive used):

DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess

If that still fails due to the version mismatch, it confirms Microsoft needs to push a hotfix for your specific build version, and you are totally safe to just ignore the tool until they do!

Answer 3

Hi Lee,

smbwmiv2.mfl is the only missing file, and as mentioned in my last reply, it's a bug in 25H2, especially caused by the May update.

Here's an excerpt from the CBS log.

2026-06-09 15:00:21, Info                  CBS    (p)	CSI Payload Corrupt	(n)			amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.26100.2161_en-gb_f3af238f57bec9bd\r\smbwmiv2.mfl
2026-06-09 15:00:21, Info                  CBS    Repair failed: Missing replacement payload.

Other than that, the component store is healthy.