DISM Error Message: The repair content could not be found anywhere.

I am not a highly technical user, so I do not understand this following error message I received after running the DISM command: "The repair content could not be found anywhere."

My internet connection is fine.

My Windows version is:

Windows 11 Pro Insider Preview
Evaluation copy. Build 26300.8772.ge_prerelease_im.260626-2010

I like seeing the latest improvements, so I have the insider's Windows version and beta Office version.

Administrator: Elevated Command Prompt

Microsoft Windows [Version 10.0.26300.8772]
(c) Microsoft Corporation. All rights reserved.
C:\Windows\System32>DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.26100.8772
Image Version: 10.0.26300.8772
[==========================100.0%==========================]
Error: @x800f0915
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.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
C:\Windows\System32>


I have included two screenshots: first, DISM error message; and second, Windows version.

Also, I am not sure that I placed this message in the correct location. Please feel free to move.

I look forward to your help.

DISM error 0x800f0915 means "repair content could not be found." It usually happens because your Windows image and your DISM engine versions are mismatched, preventing Windows from pulling repair files from the internet.

I have periodically used DISM with my Insider’s Preview.

So do just wait for another Windows update and try again?

Stecyk said:

I have periodically used DISM with my Insider’s Preview.

So do just wait for another Windows update and try again?

Click to expand...

I have the same build 26300.8772 and the DISM version is 26100.8772.
So both same as yours.
The DISM command you used completes successfully on my system however.


Why don't you reinstall the OS using Windows Update? (System/Recovery/Fix problems using Windows Update)
You will not lose any settings or files. I think it's worth a try.

OAT said:

I have the same build 26300.8772 and the DISM version is 26100.8772.
So both same as yours.
The DISM command you used completes successfully on my system however.


Why don't you reinstall the OS using Windows Update? (System/Recovery/Fix problems using Windows Update)
You will not lose any settings or files. I think it's worth a try.

Click to expand...

Thank you, I am trying that now.

Stecyk said:

Thank you, I am trying that now.

Click to expand...

It will take a while because it is a full installation, so be patient.

OAT said:

It will take a while because it is a full installation, so be patient.

Click to expand...

It took about two hours for the reinstallation of the operating system. That's a lot longer than I thought it would take.

Then, when I tried the DISM command, it took about 50 minutes because it seemed to get stuck on 64.1 and 69.7. Those numbers don't seem to popular numbers that DISM usually gets stuck on.

The good news, however, is that DISM completed with no errors. Afterward, I ran sfc /scannow, and it found and corrected some corrupted files.

Again, here's the good news:

Administrator: Elevated Command Prompt

Microsoft Windows [Version 10.0.26300.8772] (c) Microsoft Corporation. All rights reserved.
C:\Windows\System32>DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.26100.8772
Image Version: 10.0.26300.8772
[==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully.
C : \Windows\System32>_


Out of curiosity, what happens to my "old" operating system? Was it overwritten? Does it get deleted in time? Is it still sitting there?