Can't repair install with dism. The repair content could not be found anywhere

gunrunnerjohn · Sep 15, 2026

Banjoman301 said:
What does the CBS log say?

To be candid, it says a lot of things, but wading through thousands of lines of a log file with no real idea of what I'm looking for isn't something that is going to consume that much of my day.

Banjoman301 · Sep 15, 2026

gunrunnerjohn said:
but wading through thousands of lines of a log file with no real idea of what I'm looking for

No problem...

@pseymour included a script with search arguments that does the work for you (you'll have more time for posting on the forum)...

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

You could add your own, such as Error, Missing, Cannot resolve, Repair.

gunrunnerjohn · Sep 15, 2026

kelper said:
Saying the store is repairable does not mean it needs to be repaired - just chill.

Really, that's not my understanding! All the other machines tell me that no corruption was found. Since the repair also appears to actually "repair" something, I suspect your understanding just may be flawed.

Here's one of the other machines output from the ScanHealth run.

And also a RestoreHealth run from a known-good machine.

xxx

From this computer, it's a different story, clearly it does see something wrong.

Also, on this computer, there is apparently a repair that takes place, every time! It doesn't just say there is no problem.

Banjoman301 · Sep 15, 2026

Slight variation on @pseymour's script, which uses multiple search arguments and writes results to a text file on the user's Desktop

Code:

Select-String -Path "$env:windir\Logs\CBS\CBS.log" -Pattern "corrupt", "error", "cannot resolve", "missing" | Out-File "$env:userprofile\Desktop\CBS_Errors.txt" -Width 1000

Banjoman301 · Sep 15, 2026

Interesting (to me) is a /ScanHealth result that said no corruptions, and that completed successfully...but...30 corruptions were found and fixed by /RestoreHealth, which completed successfully.

MachineLanguage · Sep 15, 2026

You underestimate @glasskuter insights at your own peril.

kelper · Sep 16, 2026

gunrunnerjohn said:
Really, that's not my understanding! All the other machines tell me that no corruption was found. Since the repair also appears to actually "repair" something, I suspect your understanding just may be flawed.

Here's one of the other machines output from the ScanHealth run.

View attachment 183066

And also a RestoreHealth run from a known-good machine.

xxx

From this computer, it's a different story, clearly it does see something wrong.

View attachment 183068

Also, on this computer, there is apparently a repair that takes place, every time! It doesn't just say there is no problem.

View attachment 183069

OK. I'll refine that; repairable does not always mean a repair is needed. Sometime a reboot will fix it.

gunrunnerjohn · Sep 16, 2026

kelper said:
OK. I'll refine that; repairable does not always mean a repair is needed. Sometime a reboot will fix it.

Well, multiple reboots haven't fixed this one, so I think it's crying for a repair that it can't seem to digest.

JaapV · Monday at 5:53 PM

Well, well, well... I've read all the ideas in this thread (and some in other threads) and tried out a couple, but nothing would work. I've had this trouble with DISM in Windows 11 for some weeks now. Then, my eye fell on a post by “Lychee-Ng” on https://learn.microsoft.com/en-ie/answers/questions/5903701/severe-system-lag-dism-error-0x800f0915-after-2026 , dated 29 May. Part of the post read:

“Open Settings > System > Recovery
Find Fix problems using Windows Update
Choose Reinstall now > follow the instructions”.

I had little faith in it, but thought: “I can at least try”. Which I did. And, lo and behold... it worked! Before I tried this, this was on my screen following the command

Code:

dism /online /cleanup-image /restorehealth

:

“Deployment Image Servicing and Management tool
Version: 10.0.26100.8972

Image Version: 10.0.26300.9457

[==========================100.0%==========================]
Error: 0x800f0915

The repair content could not be found anywhere.
Check the internet connectivity or use the "Source" option to specify the location of the
files that are required to restore the image. For more information on specifying a source
location, see Configure a Windows Repair Source.”

After following the suggestion in the post mentioned above, this turned into:

“Deployment Image Servicing and Management tool
Version: 10.0.26100.8972

Image Version: 10.0.26300.9457

[==========================100.0%==========================] The restore operation complet
ed successfully.
The operation completed successfully.”

and everything is hunky dory. So it's not the difference per se between the DISM verson and the image version that's causing the trouble, because these have stayed the same. Apparently, the “recovery reinstall” from Settings has changed something else. I'm glad something finally worked, but would like to know what this “recovery reinstall” changed. Ideas, anyone?

Regards, Jaap.

Banjoman301 · Monday at 5:57 PM

JaapV said:
I've had this trouble with DISM in Windows 11 for some weeks now

As have a lot of others...

Several recent threads on the topic.

If sfc /SCANNOW runs without finding errors, I wouldn't be too concerned.

JaapV said:
Open Settings > System > Recovery
Find Fix problems using Windows Update
Choose Reinstall now > follow the instructions

Unfortunately, that won't work for those running Windows 11 on unsupported hardware.

It will trigger the hardware checks that will fail the install.

gunrunnerjohn · Monday at 7:36 PM

JaapV said:
Well, well, well... I've read all the ideas in this thread (and some in other threads) and tried out a couple, but nothing would work. I've had this trouble with DISM in Windows 11 for some weeks now. Then, my eye fell on a post by “Lychee-Ng” on https://learn.microsoft.com/en-ie/answers/questions/5903701/severe-system-lag-dism-error-0x800f0915-after-2026 , dated 29 May. Part of the post read:

“Open Settings > System > Recovery
Find Fix problems using Windows Update
Choose Reinstall now > follow the instructions”.

I had little faith in it, but thought: “I can at least try”. Which I did. And, lo and behold... it worked! Before I tried this, this was on my screen following the command

Code:

dism /online /cleanup-image /restorehealth

:

“Deployment Image Servicing and Management tool
Version: 10.0.26100.8972

Image Version: 10.0.26300.9457

[==========================100.0%==========================]
Error: 0x800f0915

The repair content could not be found anywhere.
Check the internet connectivity or use the "Source" option to specify the location of the
files that are required to restore the image. For more information on specifying a source
location, see Configure a Windows Repair Source.”

After following the suggestion in the post mentioned above, this turned into:

“Deployment Image Servicing and Management tool
Version: 10.0.26100.8972

Image Version: 10.0.26300.9457

[==========================100.0%==========================] The restore operation complet
ed successfully.
The operation completed successfully.”

and everything is hunky dory. So it's not the difference per se between the DISM verson and the image version that's causing the trouble, because these have stayed the same. Apparently, the “recovery reinstall” from Settings has changed something else. I'm glad something finally worked, but would like to know what this “recovery reinstall” changed. Ideas, anyone?

Regards, Jaap.

You are a sample of one. I tried that exact thing, both using the on-line sources and also doing the repair using a downloaded ISO. While the repair install did complete without errors and Windows works fine, the Error: 0x800f0915 remains to this day.

Can't repair install with dism. The repair content could not be found anywhere

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

Attachments

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

Active member

My Computer My Computer

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

Similar threads

My Computers

My Computer

My Computers

My Computer

My Computer

My Computers

My Computers

My Computers

My Computer

My Computer

My Computers