0x800f0915 DISM Error

garlin · May 31, 2026

Not to go off-topic, but this has be discussed before. 28000 (26H1) is considered a "dead end" until 27H2 arrives. MS carefully chooses all of the Windows branch numbers, because you can only perform in-place upgrades to a higher branch.

26H1 was always intended to be an one-off branch for ARM PC's, to help showcase their AI features. While MS maintains the 28000 build pipeline for all architectures (ARM, x64), it was never intended for public release on x64.

Because 26H2 will be an Enablement Package release, it was always designed on top of 26100. Installing the 26H2 EP, just like the 25H2 EP before it, bumps up the virtual version to 26030. But the entire tree (24H2/25H2/26H2) was planned years in advance to be based on 26100.

You cannot downgrade from 28000 to 26030. Going backwards is forbidden, it requires a clean install.

The only logical path for 26H1 to converge with 26H2 is a future (so far unnamed) branch higher than 28000. Expert speculation is this will be 27H2. 25H1 was also an ARM special release, but the difference was Windows didn't chose to switch to a single-purpose branch.

xopxop2 · May 31, 2026

gabriellla said:
there is not a fix its know bug at this version..... 26200.8457 works all dism comands perfect

I concur, I started getting this error after updating to 26200.8524 preview update from 26200.8457 regular release.
Furthermore the 26200.8524 has additional stability issues, if you haven't updated yet stay away, and wait for regular update.
A few people or reddit also mention this.

larysid · Jun 1, 2026

Hello! After the latest May windows updates 05-2026 I am also facing the same bug error to both of my machines (to dell alienware ac16250 fully updated and to my PC desktop, WIN 1125H2 AMD RYZEN 5800X, ASUS ROG STRIX X570F GAMING AND NVIDIA GEFORCE RTX3080, fully updated of course including BIOS as well):.
dism restore health command which ends up at 100% but failing "the repair content couldn't be found anywhere".. I did not realize it in first place to my PC desktop (i ran normally sfc and the dism scan check and restore health) but I faced this error to my laptop.. So, just out of curiosity I reran the aforementioned commands to my desktop PC again and till now I am facing the same error to both of my machines!! SO YES it's a bug and I believe that the best choice is to wait for a fix via the next windows update... Never ever, I had faced these errors (before this update KB5089573) to my machines...

kelper · Jun 2, 2026

DISM RestoreHealth is working on my system 1, but took 15 minutes.

On my system 3, DISM took one hour and fifteen minutes and then failed with 0x800f0915
ScanHealth said the component store was repairable.

hader · Jun 2, 2026

garlin said:
Not to go off-topic, but this has be discussed before. 28000 (26H1) is considered a "dead end" until 27H2 arrives. MS carefully chooses all of the Windows branch numbers, because you can only perform in-place upgrades to a higher branch.

26H1 was always intended to be an one-off branch for ARM PC's, to help showcase their AI features. While MS maintains the 28000 build pipeline for all architectures (ARM, x64), it was never intended for public release on x64.

Because 26H2 will be an Enablement Package release, it was always designed on top of 26100. Installing the 26H2 EP, just like the 25H2 EP before it, bumps up the virtual version to 26030. But the entire tree (24H2/25H2/26H2) was planned years in advance to be based on 26100.

You cannot downgrade from 28000 to 26030. Going backwards is forbidden, it requires a clean install.

The only logical path for 26H1 to converge with 26H2 is a future (so far unnamed) branch higher than 28000. Expert speculation is this will be 27H2. 25H1 was also an ARM special release, but the difference was Windows didn't chose to switch to a single-purpose branch.

Thanks for the additional info.

So 28000 was released as a showcase. It seems that 26030 has more improvements inside it than 28000 has. (movable taskbar) A worthless showcase then. They probably not getting 26H2 right, let alone 27H2.
If looks we have to deal with the next foul-up after 24H2, 25H2 (worst to date. Bugs are crawling around in each update. So also in this preview.) and now 26H2. If hope they will renumber everything to a new baseline instead of keeping 26100.1742 stuff inside. A legacy that started with 24H2 and was continued inside 25H2.

Note; hackers seems by misusing the WinRE environment to get to Defender and let install malicious programs inside the system32 directory with the highest privileges (The TrustedInstaller = basically root like inside Linux) So hold on to your hats...

hader · Jun 2, 2026

@garlin "The insider version (haven't one) looks more like an extension (as you already mentioned) of 25H2."

Got an insider release of 26300 through UUP and installed it in a VM. This version has also trouble with DISM and stays a long time around 64%. Eventually it ended with succes. Unfortunately it also contains 2 non cleanupable packages also now called 26100.1743 (Previous it was 26100.1742)
When I look at WinSxS it contains 16.567 (10,7Gb) directory's (new install) but if you have an installation that has not been "repaired" or underwent an "Inplace-installment" it can grow to (looking at my PC) to 24.636 (12.15Gb) It is only an indication because we are talking over 2 different versions.

I suspect that Windows is not fully cleaning up after it self. I found out that the cleanmanager says it can cleanup some 380Mb of old update stuff. (With the warning that some updates can not be uninstalled anymore) OK. Clean those systemfiles then. It refused to do so. I ran to this issue a while back. The only solution was to do an Inplace-Installment. That got rid of that old stuff. Deleted the Windows.old by the cleanmanager and updated to that latest version and everything was OK again.

With this update DISM "thinks" that a file is missing; smbwmiv2.mfl It then tries to download it from MS and finds... That is not there also. (Because in every version it is not there on that location) This is a part of a component that has something to do with an SMB package. It has been there since 19-10-2025. It was not a problem in previous updates, now suddenly it is. Maybe it's looking at its manifest... But that has not been changed since 19-10-2025 also.

It is strange that some people has this problems while other don't. It seems that if you didn't repaired your PC, did a Inplace-Installement for a long while you more likely to run into this issue. Will undergo a Inplace-installment (to get rid of that 380Mb and other older Windows stuff) and check if this will resolve this issue. For others; just wait until the final update comes along. Begin June.

pseymour · Jun 2, 2026

@kelper is that with the preview update or the regular May update?

kelper · Jun 2, 2026

I think it is the preview update. I have 'get the latest updates as soon as they're available' selected.

hader · Jun 2, 2026

@kelper, @pseymour
We are talking about 26200.8524 that is the latest preview update to date. The final one is expected to be released begin June.
The previous update 26200.8457 did not have this problem.

Yet again a bugged preview release. This is not the first one. Seen it all before with 8116 etc.
Start to wonder are we all guineapigs? What's up with all those pre-release channels? This issue should popup there also before a preview update is released to the general public.....

KevTech · Jun 2, 2026

hader said:
This version has also trouble with DISM and stays a long time around 64%.

Seeming like it is stuck around 62.3% or 64% has always been the case when using restore health .

Most likely reason is the restore is downloading large repair packages or updates.

Can go faster or slower depending on your internet speed.

Does not mean anything is wrong.

kelper · Jun 2, 2026

I hope it's a coincidence, but since running DISM and EasyBCD to investigate this problem I have had a heap of trouble. The OS boot menu does not show or shows without the Metro GUI. Menu selection is ignored, boot is painfully slow. I have spent all morning trying to fix. I have even recreated the EFI partition with no effect. I restored from a very recent Macrium X backup and still have the same problems. I will now try a reinstall of Windows and will use Macrium to reinstall all but the EFI partition. I have run chkdsk, SFC, DISM etc.

pseymour · Jun 2, 2026

hader said:
We are talking about 26200.8524 that is the latest preview update to date. The final one is expected to be released begin June.
The previous update 26200.8457 did not have this problem.

The conversation is mostly about the preview update, but OP says in post 30 that they rolled back to 8457 and still have the same issue. Meanwhile, you're prattling on about 26H2, 27H2, and who knows what else that has nothing to do with the preview update.

hader said:
Yet again a bugged preview release. This is not the first one. Seen it all before with 8116 etc.
Start to wonder are we all guineapigs? What's up with all those pre-release channels? This issue should popup there also before a preview update is released to the general public

It's a Preview update. No one says you have to install it.

Scott · Jun 2, 2026

kelper said:
DISM RestoreHealth is working on my system 1, but took 15 minutes.

Same here.

System 1

System 2

System 3

larysid · Jun 2, 2026

Scott said:
Same here.

System 1
View attachment 173237

System 2
View attachment 173239

System 3
View attachment 173243

Don't be so sure about it! My pc desktop had the same success message written after installing this preview update, but after rerunning it 2 days before, the dism scan and check health said that the store is repairable and dism restore health failed with the error bug described above. I own 2 machines and they face exactly the same error. Not to mention that search indexer has about 400MBs to restore and it takes much time to finish... Never ever have I seen error to dism restore health..
So just wait for the next update so as to rerun these dism commands. Should they fail again, then I will format both of my machines.

Maxstar · Jun 3, 2026

hader said:
In the CBS log file I could see what is wrong: "CSI Payload Corrupt: 1" It's pointing to a package and it says that is missing a file inside the ComponentStore (C:\Windows\WinSxS) called "amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.26100.2161_nl-nl_b443d00bdbef7989\r\smbwmiv2.mfl"

Hi @hader

Attached you will find a copy of the Dutch (NL) component including the reverse differential.

If someone have the same component including the (R) differential for the following languages, please share....

Code:

amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.26100.2161_en-gb_f3af238f57bec9bd
amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.26100.2161_ja-jp_2a0826e4102d7ce2
amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.26100.2161_zh-cn_5abe491b3a095794

xopxop2 · Jun 3, 2026

Maxstar said:
Hi @hader

Attached you will find a copy of the Dutch (NL) component including the reverse differential.

If someone have the same component including the (R) differential for the following languages, please share....

Code:

amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.26100.2161_en-gb_f3af238f57bec9bd amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.26100.2161_ja-jp_2a0826e4102d7ce2 amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.26100.2161_zh-cn_5abe491b3a095794

I initially got 6 packages corrupted after the preview update, now I got only 1 and it is the same as yours but different language.
I was looking into Offline DISM repair with Win11 ISO, but that ISO is on build 8037 for my main language.

So I guess I will just wait till MS fixes the package on the server side or release new patch sooner.
Either way the file is not critical for my usage. The file contains language translation strings that is used mostly for file transfers on local network.
WMI services might be problematic though, but so far my PC is working fine. I got only problems with audio device service.

The file smbwmiv2.mfl (often accompanied by smbwmiv2.dll) is a core Windows system file. It acts as a WMI (Windows Management Instrumentation) provider for the SMB (Server Message Block) protocol. It is responsible for allowing Windows to monitor and manage file sharing and networking.How Critical Is It?It is moderately critical to the underlying operating system. While it won't stop your PC from booting or browsing the web, its absence or corruption will cause issues related to network shares, file transfers, and WMI services.

PS. I ran DISM twice today and it still is not fixed on MS server side.

pietcorus2 · Jun 4, 2026

antspants said:
Have experienced the same today after the update.

Also on my rig , went back with Macrium to 25 Mai ( before latest previeuw !) , problems are solved !
Will not install this latest previeuw , and wait untill next week , tuesday............ :wink:

btw; thinking of skipping these buggy previeuws !
costed me ( again) a lot of time to fix it............

hader · Jun 4, 2026

Well my question is this a update issue or not has been answered; (see Post #46) Yes. Despite a fresh Inplace Installement of 26200.8475 and updating it to 26200.8524 the initial result was; no errors. But after a cleanmgr.exe action the problem was back again. So an In-place-Installment is not a solution.
It is still falling over the same file and ends with Error: 0x800f0915 (Inside the CBS log: [HRESULT = 0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING]) while before the cleanmgr.exe action there was no issue. ("Refuse to cleanup" dropped from 380Mb in the old situation to Zero after the In-place-installment and went back again to 190Mb after the update and again cleanmgr.exe refused this new size also to cleanup.) To bad.... We have to wait for an solution from MS.

pietcorus2 · Jun 4, 2026

MS must be aware of the error , so we may expect it will be fixed , next week ...........
Only thing we can do is making a solid backup , before updating !

hader · Jun 5, 2026

Maxstar said:
Hi @hader

Attached you will find a copy of the Dutch (NL) component including the reverse differential.
....

Thanks. Picked up a copy of the smbwmiv2.mfl file in the attachment and tried to place it in that \r directory but I have not enough rights as Admin. The only user that have these rights is the TrustedInstaller itself. That makes sense. The location contains the Windows Component Store. And those files can only updated by the Update proces.

The strange part of it is; if I am looking at a VM with an older version of Windows (26200.7171) that file isn't there also on that location. In every case (not matter what version I am looking at) the file is present in the directory above it (above the \r dir) and absent inside the \r location.
For some other reasons it seems that DISM thinks it should be there. Tries to download it and could not find inside the MS servers also. In that way the error is correct; It is not there in the first place. What's wrong is that DISM thinks it should be there. So there is something wrong with the CBS mechanism and DISM false conclusion. We see a symptom but don't know if MS made some CBS mechanism changes. Let hope that it will be fixed with the next update.

Edit. Updated that VM from 7171 to 8457 also. SFC repaired some files, DISM also (despite it showed the normal message. A look inside the CBS.log I came to the that conclusion) After the update that file was also absent. DISM did not fell over this file at the first run. It took an abnormal long time *62,3%* to finish. A second run; it found 370 files corrupt (despite that first run) and fixed 269 files and came up with the same error. (expected that everything was fixed at the first run, not after 2 runs. You don't run DISM /RestoreHealth each day...) It seems that the problem may lay dormant also in 8457 in combination with Dutch? A third run reported an extra clue [HRESULT = 0x800f0950 - CBS_E_NO_OPTIONAL_CONTENT_FOUND_FOR_BUILD] (Optional means NL language) and yet again [HRESULT = 0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING] and Error: 0x800f0915.

So this issue is not restricted (If language other than US) to 26200.8524 it can also occur with 26200.8457. Find is all strange that component dates back from 19-10-2025 or maybe earlier. It's not a recent addition.

0x800f0915 DISM Error

Well-known member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Active member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Active member

My Computer My Computer

At a glance

Well-known member

Attachments

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computers

My Computers

My Computers

My Computer

My Computers

My Computers

My Computer

My Computers

My Computer

My Computers

My Computer

My Computer

My Computer

My Computers

My Computers

My Computers

My Computers