0x800f0915 DISM Error

kelper · May 29, 2026

Can you update your specs to say if you have Windows 11 Home or Pro?

kelper · May 29, 2026

@OP Why are you running DISM? Have you run chkdsk and SFC /SCANNOW

FallenDemon · May 29, 2026

kelper said:
Can you update your specs to say if you have Windows 11 Home or Pro?

I'm using Windows 11 build 25H2 26200.8524, and I've also updated my system specifications in my signature. Thank you.

kelper · May 29, 2026

FallenDemon said:
I'm using Windows 11 build 25H2 26200.8524, and I've also updated my system specifications in my signature. Thank you.

Yes, but is it Home or Pro?

IanMosley · May 29, 2026

Reported to MS via Feedback Hub - Join Windows Insider – Get early access to Windows 11 features & updates

FallenDemon · May 29, 2026

kelper said:
Yes, but is it Home or Pro?

I apologize, it's my mistake. I'm using the Home Single Language version.

FreeBooter · May 29, 2026

Try in-place upgrade to repair Windows 11.

You can also perform in-place upgrade of Windows 11. In-place upgrade is to use to replace the current operating system files on your computer. Unlike a clean installation of Windows, you can start a Windows in-place upgrade when your OS is still running. And an in-place upgrade can keep your files, settings, & apps during the upgrade process. You can perform a Windows 11 in-place upgrade is to use the Windows 11 Media Creation Tool. Make sure to select Upgrade this PC now and click Next. Follow the on-screen guide to perform a Windows 11 in-place upgrade.

Repair Install Windows 11 with an In-place Upgrade

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

kelper · May 29, 2026

I think you need to download the latest ISO si it matches your current version.

I had to use the Media Creation Tool to get an ISO version 8457 which is the very latest available.

FallenDemon · May 29, 2026

I reverted to build 26200.8457 because there were indeed problems with build 8524. I'll try to see if there are any problems with build 8457.

FallenDemon · May 29, 2026

I tried build 26200.8457 and interestingly, it gives the same error, but build 8037 doesn't have this problem. It's really strange.SFC/scannow completes without any problems, but the DISM tool encounters an issue.

kelper · May 29, 2026

I updated my laptop to 8524 and ran dism /online /cleanup-image /restorehealth with no errors but it took a long time and paused at 64% for ages.

antspants · May 29, 2026

IanMosley said:
Reported to MS via Feedback Hub - Join Windows Insider – Get early access to Windows 11 features & updates

Upvoted, thanks, Ian

hader · Saturday at 4:09 AM

Weird. This issue appeared also at my system today. Strange. Did run this command after the update with no problems. It seems to have some difficulty with finding it's source. Used the /source method with a mounted Win11_25H2_<lang>_x64_v2.iso. Pointed at the install.wim file inside the /source directory... Gave the same result. Something seems to be broken in Windows. Have no clue yet what that might be.

It seems to be stuck for a long while at 64% what others also observed. Used the media creation tool to check what version it download instead of the official Win11_25H2_<lang>_x64_v2.iso (26200.8037) The download media version was 26200.8457 (The build before this recent update) Did a source check again with this build; (install.esd instead of the install.wim file): This gave the same result but was much faster then with install.wim (.wim=6,93Gb, .esd=6,14Gb)

Why it now suddenly appears? I have no clue. It is possible that DISM reaches briefly out to a MS site that is down at this moment.
At this moment I am not planning to do a In-Place-Installment yet. I find it strange that it functioned after the update and now today it fails. There might be a external reason for this. I will try it again tomorrow. As far as I can notice Windows is functioning and behaving as normal.

kelper · Saturday at 4:56 AM

@hader

Which DISM command did you use?

FallenDemon · Saturday at 5:16 AM

hader said:
Weird. This issue appeared also at my system today. Strange. Did run this command after the update with no problems. It seems to have some difficulty with finding it's source. Used the /source method with a mounted Win11_25H2_<lang>_x64_v2.iso. Pointed at the install.wim file inside the /source directory... Gave the same result. Something seems to be broken in Windows. Have no clue yet what that might be.

It seems to be stuck for a long while at 64% what others also observed. Used the media creation tool to check what version it download instead of the official Win11_25H2_<lang>_x64_v2.iso (26200.8037) The download media version was 26200.8457 (The build before this recent update) Did a source check again with this build; (install.esd instead of the install.wim file): This gave the same result but was much faster then with install.wim (.wim=6,93Gb, .esd=6,14Gb)

Why it now suddenly appears? I have no clue. It is possible that DISM reaches briefly out to a MS site that is down at this moment.
At this moment I am not planning to do a In-Place-Installment yet. I find it strange that it functioned after the update and now today it fails. There might be a external reason for this. I will try it again tomorrow. As far as I can notice Windows is functioning and behaving as normal.

Windows seems to be working fine, yes, I still have the same problem, but I preferred to leave it as it is to avoid dealing with it. I'll wait for the next update; it's behaving strangely. I tried the exact same methods you did, but I got no results, it's really odd. If I did the same things today, it would probably give the same error again, so I don't want to bother. But there's one thing I don't understand; for example, the SFC/scannow command works without any problems and performs repairs if there are any, which is interesting. But the DISM command is completely broken.

hader · Saturday at 9:08 AM

kelper said:
@hader

Which DISM command did you use?

Just the regular Dism /Online /Cleanup-Image /RestoreHealth command.

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" The strange thing is that there is also en-us version directory and that file is also missing in that r directory. Dism is not complaining about it is missing there also.....

Replayed this whole scenario in a VM with a 26200.8246 US version. Updated it to 26200.8257 and then to 28200.8524. Saw at each step some errors flying by in the CBS log but they all ended with [HRESULT = 0x00000000 - S_OK] instead of now [HRESULT = 0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING] I think that something is broken in the DISM engine. It uses 3 MS sites; (They are protected by a certificate, username and password. Only the Windows engine can get through. We not.)

WU: Update service is not default AU service, skip. URL: https://tas02.cws.update.microsoft.com/, Name: DCat Flighting Prod
WU: Update service is not default AU service, skip. URL: https://tas01.cwsapp.update.microsoft.com/, Name: Windows Store (Prod)
WU: Microsoft Update service is the default, URL: https://fe2cr.update.microsoft.com/v6/, Name: Windows Update
(One thought crossed my mind; What if one of these sites was down? but no...)

Where it downloads good files (in 3 situations) if they are corrupted. It went OK in the US version but fails in a non-US version. Can this be a language related issue???
I think it has something to do that 8524 is yet again a preview version. I'll just wait until the final next update that will be distributed at the beginning of June..... Spent already to much time to figure out what is wrong. Doing a in-place installment to 8257 will fix the issue but waiting on the next update will solve the issue also. So why bother..... I'll wait.

pseymour · Saturday at 9:26 AM

FallenDemon said:
But there's one thing I don't understand; for example, the SFC/scannow command works without any problems and performs repairs if there are any, which is interesting. But the DISM command is completely broken.

They work on two different things.

“DISM provides the files required to repair your corrupted files. You should run DISM prior to running the System File Checker.”

“The sfc /scannow command will scan all protected system files and replace corrupted files with a cached copy”

Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support

Describes how to use the System File Checker tool to troubleshoot missing or corrupted system files in Windows.

support.microsoft.com

hader · Saturday at 9:41 AM

FallenDemon said:
....But there's one thing I don't understand; for example, the SFC/scannow command works without any problems and performs repairs if there are any, which is interesting. But the DISM command is completely broken.

They both fix errors but not at the same level. SFC is looking more at system files and can repair them when damaged. But DISM is more looking at the Windows Component Store (C:\Windows\WinSxS) it checks if all packages residing in that store are without any errors. If so it will download them and replaces the corrupted or damaged files. This Windows Component Store is what is updated with each update and is a part of the Windows engine. If there is a new build version the update will place here it's newer version and delete the old ones it should replace. Sometimes some old packages are left behind because the new version was not finished yet to be rolled out. Will be deleted at the next update when there is a new replacement.

Made a script to see what is new and how the different builds are distributed. Some set of package will remain in the store until a complete new base build (like 26H1) is ready. This version (8524) looks something like this; The total is different; The US version has only en-us versions while my version (Dutch) have both; nl-nl and en-us. Those 26100.1742 will remain in Windows 11 because it is some base-build. Deleting them all wil result in a corrupt Windows system. Many tried to delete 2 1742 files because they pop-up as "cleanable" with the DISM AnalyzeComponentStore command. It will hamper updates and cause problems. And with a In-Place-Installment they are back again. Stopped with deleting those to because now they are gone and at the next time they are back again. It has no use to delete these. There are no benefit to be achieved here; only that DISM command will say 0 instead of the normal 2.

Code:

------------------------------------------------------------
This Update 26200.8524 contains 12 different build versions.
------------------------------------------------------------
   74X  1742           
   17X  26100.1       
    1X  5503           
    1X  6584           
    1X  6717           
    1X  8037           
    2X  8117           
    1X  8519           
   71X  8521           
    3X  8524           
    1X  9319           
    1X  9337           
============================================================
Total number of packages found: 174

As you can see; there are only 3 packages that are marked 8524 but the remainder are 8521. A lower number . Despite everything this build is still called 8524. And a other thing is noticeable; there is not one package that starts with 26200. Only 26100 ones. So basically they are using numbers that belongs to 24H2. Only Winver and some other programs reports 26200.xxxx. (You will also not find 26200 packages in the physical Component Store. (C:\Windows\WinSxS) )

garlin · Saturday at 10:48 AM

hader said:

Code:

------------------------------------------------------------
This Update 26200.8524 contains 12 different build versions.
------------------------------------------------------------
   74X  1742           
   17X  26100.1       
    1X  5503           
    1X  6584           
    1X  6717           
    1X  8037           
    2X  8117           
    1X  8519           
   71X  8521           
    3X  8524           
    1X  9319           
    1X  9337           
============================================================
Total number of packages found: 174

Those are different component versions. When a new build introduces a new feature or updates an existing one, the component version is numbered the same as the build that first released this version of the component.

Cumulative updates are cumulative. That means it includes all previously released component updates. A component can be patched once and never be touched every again. So it's version is frozen, unless it gets replaced (superseded). But it's included in a cumulative update which the overall build number will always increase over time, even if the child component hasn't been updated in a while.

The distribution of component versions only represent how far back, different parts of Windows were patched. MS doesn't re-number everything when the next CU releases, just to make the versions match up.

.1 components are often metadata components for Features on Demand (FOD). They never change. While other components can be superseded, the .1 components for FOD's are always there serving as a baseline for image servicing reasons.

26200 (25H2) is a virtual Windows version, based on the UBR. All components are numbered on the base branch of the family (24H2 or 26100). When 26H2 releases, you will still have components based on 26100, even though the virtual version will be bumped to 26300.

hader · Sunday at 6:53 AM

garlin said:
....
Cumulative updates are cumulative. .....

....
26200 (25H2) is a virtual Windows version, based on the UBR. .....

Yes. #1 & #2; I know, that was what I was saying and implying. Those build version shows just from which build they originated from. Some package are around for a long while because they don't need to be updated by a new version like 26100.1, 5503, 9319, 9937 and some others. 26H2 will have again a base build with an other build on top of it. I hope that they fix /AnalyzeComponentStore in such a way that it is saying 0 packages to be cleaned up. People will react as we have seen with 25H2. (Deleting 2 packages) Gave this advice a long time ago to MS but they ignored it.

On the subject of 26H2; I have installed an MVS (28000.2113 dated May 2026) of 26H1 x64 on a VM and have found that it base starts with 28000 instead of 26100. Reviewed the packages in this build also and it came with the following results using an adapted script based on 28000;

Code:

--------------------------------------------------
This Update contains 6 different build versions.
--------------------------------------------------
    1X  1575           
    1X  1706           
    1X  2103           
   62X  2113           
   70X  28000.1       
    1X  9335           
==================================================
Total number of packages found: 136

The found packages matches with the number of packages (136)

I have to agree that looking at the insider version 26300.8493 (still called 25H2 at system and has a moveable taskbar) that would become "26H2".
So I am a little bit confused; Why 2 versions? Official 26H2 was intended for new devices for ARM but why bring out a version for x64 also?
The insider version (haven't one) looks more like an extension (as you already mentioned) of 25H2. Can't imagine that there will be 2 versions for 26H2 one based on 28000 and an other on 26300 (with packages based on 26100) both for x64. One intended for ARM (28000) and an other (26300) for x64; yes. What is your view on things? (Attached all the packages inside 28000. Incl. Dutch version and VMWare Broadcom packages.)

Sorry guys for deviating from the subject. I think some people are curious also.

0x800f0915 DISM Error

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Windows Insider

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Like a rolling drone.

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

putting the mental back in experimental

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

Attachments

My Computer

Similar threads