Windows 11 Error with DISM RestoreHealth

Actually, I still get the RestoreHealth error code '0x800f0915' with the latest update, and it's spread to at least one more machine here. I just updated another machine and I'm checking to see if that one catches it as well. It's not looking good, it's stalled at 63.3%, usually a sign that it is hunting around for the content.

You need to do on the second computer that has the error what I indicated in my post 6, it might work and hold.

itsme1 said:

You need to do on the second computer that has the error what I indicated in my post 6, it might work and hold.

Windows 11 Error with DISM RestoreHealth

Hi all, I have an issue with my system and have tried the following: sfc /scannow - came back OK chkdsk on C drive - came back OK When running DISM /Online /Cleanup-Image /RestoreHealth, I get this error: Image Version: 10.0.26200.9445...

www.elevenforum.com

Click to expand...

Already tried and failed. Three of four computers I updated now have the same error. This is obviously Microsoft's quality improvement program in full swing!

It's rubbish.

Just one last thing, if you haven't done this already: run the `DISM /Online /Cleanup-Image /StartComponentCleanup` command when the component store needs cleaning (which is often after an update, except for the two non-removable packages), then reboot and run the `RestoreHealth` command.

That’s how it worked for me, the component store needed cleaning after the KB update.

One of my machines is fine. Even after doing the StartComponentCleanup, and restarting, I continue to get 0x800f0915 error on my laptop. Has Microsoft said anything about this issue...why some machines are fine...while many are not?

mccmw said:

One of my machines is fine. Even after doing the StartComponentCleanup, and restarting, I continue to get 0x800f0915 error on my laptop. Has Microsoft said anything about this issue...why some machines are fine...while many are not?

Click to expand...

I'm convinced something that is not replaced by either the DISM repair or a repair install is corrupt. The repair install should replace anything wrong with the component store and the running windows files. However, after several repair installs, I still have the same error. Another clue is SFC /SCANNOW runs error free and finds no problems. Windows also seems to run fine, it's just DISM that has an issue.

gunrunnerjohn said:

I'm convinced something that is not replaced by either the DISM repair or a repair install is corrupt. The repair install should replace anything wrong with the component store and the running windows files. However, after several repair installs, I still have the same error. Another clue is SFC /SCANNOW runs error free and finds no problems. Windows also seems to run fine, it's just DISM that has an issue.

Click to expand...

Same experience. I have attempted repair reinstall via both Windows Update as well as *.iso (Microsoft and UUP Dump). No change. SFC /scannow completes without any integrity violations.

So I was doing a little digging today with Gemini AI and it told me
this log output pinpoints the issue for my 26300.9550:

Notice the component causing the failure:arm64_userexperience-desktop_31bf3856ad364e35_10.0.26100.9549_...\CBS\webapps\guidedsetup\network\area-content\bg-BG\area-content.local.json

Out of 124 detected CSI Payload Corruptions, DISM successfully repairs 120 of them. The remaining 4 payload files (non-critical Bulgarian language JSON localization files for the Out-of-Box Guided Setup app) belong to the base build version 10.0.26100.9549, while your operating system is updated to 26300 / 26220.

When DISM attempts to pull these specific 26100.9549 legacy language payloads to reach 100% repair:

1. Windows Update no longer hosts the exact 26100.9549 language payload matches for your updated OS build track.
2. 26300/26220 ISOs do not contain 10.0.26100.9549 component versions (they contain newer payload versions).
3. DISM aborts at the final step, returning HRESULT = 0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING.

Shown in the log:

PS C:\WINDOWS\system32> Select-String -Path C:\Windows\Logs\CBS\CBS.log -Pattern "Corrupt", "Failed" | Select-Object -Last 20


C:\Windows\Logs\CBS\CBS.log:90856:2026-09-24 12:29:47, Info CBS Repair failed: Missing

replacement payload.

C:\Windows\Logs\CBS\CBS.log:90857:2026-09-24 12:29:47, Info CBS (p) CSI Payload Corrupt

arm64_userexperience-desktop_31bf3856ad364e35_10.0.26100.9549_none_c81047371a563106\r\CBS\webapps\guidedsetup\ne

twork\area-content\bg-BG\area-content.local.json

C:\Windows\Logs\CBS\CBS.log:90858:2026-09-24 12:29:47, Info CBS Repair failed: Missing

replacement payload.

C:\Windows\Logs\CBS\CBS.log:90864:2026-09-24 12:29:47, Info CBS Total Detected Corruption:

124

C:\Windows\Logs\CBS\CBS.log:90865:2026-09-24 12:29:47, Info CBS CBS Manifest Corruption: 0

C:\Windows\Logs\CBS\CBS.log:90866:2026-09-24 12:29:47, Info CBS CBS Metadata Corruption: 0

C:\Windows\Logs\CBS\CBS.log:90867:2026-09-24 12:29:47, Info CBS CSI Manifest Corruption: 0

C:\Windows\Logs\CBS\CBS.log:90868:2026-09-24 12:29:47, Info CBS CSI Metadata Corruption: 0

C:\Windows\Logs\CBS\CBS.log:90869:2026-09-24 12:29:47, Info CBS CSI Payload Corruption: 124

C:\Windows\Logs\CBS\CBS.log:90870:2026-09-24 12:29:47, Info CBS CSI FileFlags Corrupt: 0

C:\Windows\Logs\CBS\CBS.log:90871:2026-09-24 12:29:47, Info CBS Total Repaired Corruption:

120

C:\Windows\Logs\CBS\CBS.log:90883:2026-09-24 12:29:47, Info CBS Ensure CBS corruption flag

is clear

C:\Windows\Logs\CBS\CBS.log:90885:2026-09-24 12:29:47, Info CBS Count of times corruption

detected: 8

C:\Windows\Logs\CBS\CBS.log:90886:2026-09-24 12:29:47, Info CBS Seconds between initial

corruption detections: -1

C:\Windows\Logs\CBS\CBS.log:90887:2026-09-24 12:29:47, Info CBS Seconds between corruption

and repair: -1

C:\Windows\Logs\CBS\CBS.log:90888:2026-09-24 12:29:47, Info CBS Failed to run Detect and

repair. [HRESULT = 0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING]

C:\Windows\Logs\CBS\CBS.log:90892:2026-09-24 12:29:47, Info CBS Exec: Processing complete,

session(Corruption Repairing): 31280216_4285713401 [HRESULT = 0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING]

C:\Windows\Logs\CBS\CBS.log:90894:2026-09-24 12:29:47, Error CBS Session: 31280216_4285713401

failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0915 -

CBS_E_REPAIR_CONTENT_MISSING]

C:\Windows\Logs\CBS\CBS.log:90906:2026-09-24 12:29:47, Info CBS Finalize failed. [HRESULT =

0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING]

C:\Windows\Logs\CBS\CBS.log:90907:2026-09-24 12:29:47, Info CBS Failed to FinalizeEx using

worker session [HRESULT = 0x800f0915]

I ran DISM.... RestoreHeath for the first time in over a year, on Sept. 8th 2026, and it finished.
No errors. It took about 30 minutes though.



Maybe something at this link will help someone??

FrancoDT said:

So I was doing a little digging today with Gemini AI and it told me
this log output pinpoints the issue for my 26300.9550:

Notice the component causing the failure:arm64_userexperience-desktop_31bf3856ad364e35_10.0.26100.9549_...\CBS\webapps\guidedsetup\network\area-content\bg-BG\area-content.local.json

Out of 124 detected CSI Payload Corruptions, DISM successfully repairs 120 of them. The remaining 4 payload files (non-critical Bulgarian language JSON localization files for the Out-of-Box Guided Setup app) belong to the base build version 10.0.26100.9549, while your operating system is updated to 26300 / 26220.

When DISM attempts to pull these specific 26100.9549 legacy language payloads to reach 100% repair:

1. Windows Update no longer hosts the exact 26100.9549 language payload matches for your updated OS build track.
2. 26300/26220 ISOs do not contain 10.0.26100.9549 component versions (they contain newer payload versions).
3. DISM aborts at the final step, returning HRESULT = 0x800f0915 - CBS_E_REPAIR_CONTENT_MISSING.

Click to expand...

OK, but why in the world do I have Bulgarian language localization files for anyway? It that is the cause, why it it that not something that MSC can fix?

gunrunnerjohn said:

OK, but why in the world do I have Bulgarian language localization files for anyway? It that is the cause, why it it that not something that MSC can fix?

Click to expand...

Good question, I tried a few complex powershell commands it recommended to replace the files but they didn't work either so back to waiting on MS to do something about this now widespread issue.

Take a look in all your "lang" or "Language" folders, and you'll see either a "BG" or a "1026" file for Bulgarian, along with many other countries.

It's common.

I just had a similar discussion with Copilot. Feedback from my CBS and DISM logs was that it is a Microsoft servicing/catalog issue involving OOBE/CloudExperienceHost content. The recommendation is to wait for a future update to fix it, since SFC /scannow is successful and repair installs have been successful (except for DISM).

mccmw said:

The recommendation is to wait for a future update to fix it, since SFC /scannow is successful and repair installs have been successful (except for DISM).

Click to expand...

I got a similar recommendation. Only problem is this has been occuring for months now and it seems to be a very low priority for MS. I actually wonder if they are even working on it.

As long DISM/scanhealth does not find any errors , I will not use this "DISM/repairhealth" anymore .
Reading all these forum-items , makes me convinced this "repair"-command is a bug ( should be fixed by MS a long time ago already !)............

pietcorus2 said:

As long DISM/scanhealth does not find any errors , I will not use this "DISM/repairhealth" anymore .
Reading all these forum-items , makes me convinced this "repair"-command is a bug ( should be fixed by MS a long time ago already !)............

Click to expand...

But... DISM's /ScanHealth DOES find errors! It states that the component store is repairable. However, then the /RestoreHealth throws the error.

" But... DISM's /ScanHealth DOES find errors! "................not on my(2) rigs !
So , no need for the (buggy) "DISMrepairhealth............

I tried the following per AI search and DISM restore health finally worked. Some were already running.
Could just be a coincidence but worth trying.
Still took ages though.

1. Run the following commands one by one, pressing Enter after each:
   • net start bits
   • net start dosvc
   • net start usosvc
     
   • net start trustedinstaller
   • net start wuauserv
2. Try DISM restore health again. Good luck.

Garrett said:

I tried the following per AI search and DISM restore health finally worked. Some were already running.
Could just be a coincidence but worth trying.
Still took ages though.

1. Run the following commands one by one, pressing Enter after each:
   • net start bits
   • net start dosvc
   • net start usosvc
   • net start trustedinstaller
   • net start wuauserv
2. Try DISM restore health again. Good luck.

Click to expand...

Does nothing for me on the machine stuck on the 0x800f0915 RestoreHealth error I'm afraid. On the other two machines running Dism /Online /Cleanup-Image /StartComponentCleanup and rebooting will clear the 0x800f0915 error and let RestoreHealth complete.

FrancoDT said:

Does nothing for me on the machine stuck on the 0x800f0915 RestoreHealth error I'm afraid. On the other two machines running Dism /Online /Cleanup-Image /StartComponentCleanup and rebooting will clear the 0x800f0915 error and let RestoreHealth complete.

Click to expand...

I'll check again later...to confirm. But I just ran those commands and just got a successful restorehealth.