Restorehealth Error 800F0915

Sir_George · 2026-09-03T13:02:28-0400

I am sending a screenshot of the error mentioned in the title of this post.

1. Is this a serious problem (as in, could Windows become unstable, for example)?
2. Is there a way to fix it? I have attempted to resolve this using ChatGPT without success.
Thanks for any help you can provide.

FreeBooter · 2026-09-03T13:07:07-0400

To fix the "source files could not be found" DISM error, you need to provide the command with a working repair source, such as a mounted Windows installation ISO file.

Download the official Windows ISO file matching your exact operating system version.

Right-click the downloaded ISO file in File Explorer and select Mount.

Note the new drive letter assigned to the mounted drive.

Open Command Prompt or PowerShell as an administrator.

Run this command to see the available image indexes, replacing X with your mounted drive letter:

Batch:

dism /get-imageinfo /imagefile:X:\sources\install.wim

Note the index number (#) that matches your specific edition of Windows (such as Windows 10 Pro or Windows 11 Home).

Run the repair command with your custom source and limit access to Windows Update, replacing X with the drive letter and # with your index number:

Batch:

DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:# /LimitAccess

After DISM completes successfully, type the following command and press Enter:

Code:

sfc /scannow

Restart your computer once the scan finished.

gunrunnerjohn · 2026-09-03T13:43:54-0400

Welcome to the club. My advice is not to bother trying to fix this particular error right now. I worked on this one as some length, but clearly it's something that got screwed up about three releases ago. Apparently Microsoft has been apprised of this issue and I suspect someday they'll finally fix it. I did all of the suggested fixes and more, none of them eliminated this error.

kelper · 2026-09-03T13:49:20-0400

This is known bug. If you run DISM /Online /Cleanup-Image /CheckHealth and it reports "No component store corruption detected." then don't worry. Using an ISO as source will give the same error.

glasskuter · 2026-09-03T14:00:30-0400

What issue are you experiencing that you need to run dism in the first place?

KevTech · 2026-09-03T14:34:32-0400

kelper said:
If you run DISM /Online /Cleanup-Image /CheckHealth and it reports "No component store corruption detected."

Actually it should be scanhealth if you want to check the component store files.

Checkhealth just looks for pre-existing flags of corruption marked by a process in the registry and does not scan the actual files.

If checkhealth does not find anything flagged in the registry then it will report "no component store corruption detected" even though there may be corrupted files in the component store.

Scanhealth scans the entire Windows component store file by file.

FrancoDT · 2026-09-03T14:38:45-0400

And I'll add that for many with this now widespread issue on multiple Windows builds the ISO repairs will no longer fix this bug.

Ramesh Sharma · 2026-09-03T15:11:30-0400

Hello Everyone,
In such case, Recovery Drive, if already prepared while windows in good condition, is very helpful to replace corrupt system files without deleting personal files, folders, and data.
Boot from Recovery Drive, Select US, TROUBLESHOOT, Command Prompt and then run following commands.

1. x:\windows\system32>wmic logicaldisk get caption, volumename, size
OR
2. x:\windows\system32 >wmic logicaldisk get deviceid, volumename, size
OR
3. x:\windows\system32>diskpart
Diskpart\>list volume
Note drive letter of windows which is offline now from WinPE ENVIRONMENT as well as drive letter of Recovery Drive.
Assuming E is windows drive letter offline, and I is Recovery Drive letter in WinPE ENVIRONMENT.
Now run these commands
x:\windows\system32 > I:
I:\> md Scratch
I:\>x:
x:\windows\system32 > CHKDSK E: /f /r /x

x:\windows\system32 > sfc /scannow /offbootdir=E:\ /offwindir=E:\Windows

x:\windows\system32 > dism /image:E:\ /cleanup-image /restorehealth /source:I:\sources\Reconstruct.WIM /limitaccess /ScratchDir:I:\Scratch

x:\windows\system32 > dism /image:E:\ /cleanup-image /restorehealth /source:I:\sources\Reconstruct.WIM2 /limitaccess /ScratchDir:I:\Scratch

(Please note, Reconstruct.WIM and Reconstruct.WIM2 are in sources folder in Recovery Drive I:)

Again run following command to verify no integrity violations.
x:\windows\system32 > sfc /scannow /offbootdir=E:\ /offwindir=E:\Windows

I prepared Recovery Drive for WTG having Windows 11 v25H2 OS Build 26200.8037 (Drive letter is K: for WTG and L: for Recovery Drive in disk management in Live OS.)
So from live os Windows 11 v25H2 OS Build 26200.9168 on internal ssd on laptop , K is offline image to be repaired from Recovery Drive L: So command will be

C:\Windows\System32>dism /image:K:\ /cleanup-image /restorehealth /source:L:\sources\Reconstruct.WIM /limitaccess

Deployment Image Servicing and Management tool
Version: 10.0.26100.8972

Image Version: 10.0.26200.8037
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\System32>dism /image:K:\ /cleanup-image /restorehealth /source:L:\sources\Reconstruct.WIM2 /limitaccess

Deployment Image Servicing and Management tool
Version: 10.0.26100.1

Image Version: 10.0.26200.8037

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
Thanks.

gunrunnerjohn · 2026-09-03T15:40:18-0400

Ramesh Sharma said:
Hello Everyone,
In such case, Recovery Drive, if already prepared while windows in good condition, is very helpful to replace corrupt system files without deleting personal files, folders, and data.
Boot from Recovery Drive, Select US, TROUBLESHOOT, Command Prompt and then run following commands.
1. x:\windows\system32>wmic logicaldisk get caption, volumename, size
OR
2. x:\windows\system32 >wmic logicaldisk get deviceid, volumename, size
OR
3. x:\windows\system32>diskpart
Diskpart\>list volume
Note drive letter of windows which is offline now from WinPE ENVIRONMENT as well as drive letter of Recovery Drive.
Assuming E is windows drive letter offline, and I is Recovery Drive letter in WinPE ENVIRONMENT.
Now run these commands
x:\windows\system32 > I:
I:\> md Scratch
I:\>x:
x:\windows\system32 > CHKDSK E: /f /r /x

x:\windows\system32 > sfc /scannow /offbootdir=E:\ /offwindir=E:\Windows

x:\windows\system32 > dism /image:E:\ /cleanup-image /restorehealth /source:I:\sources\Reconstruct.WIM /limitaccess /ScratchDir:I:\Scratch

x:\windows\system32 > dism /image:E:\ /cleanup-image /restorehealth /source:I:\sources\Reconstruct.WIM2 /limitaccess /ScratchDir:I:\Scratch

(Please note, Reconstruct.WIM and Reconstruct.WIM2 are in sources folder in Recovery Drive I:)

Again run following command to verify no integrity violations.
x:\windows\system32 > sfc /scannow /offbootdir=E:\ /offwindir=E:\Windows

Thanks.

Doesn't work for this one. I tried a repair install from both WU sources and a local ISO source, neither were able to correct the issue. There is some data that apparently even a repair install doesn't touch and is the cause of the error.

FWIW, I believe the component store and Windows running files are fine, my feeling is that the checking process is at fault. I'm hoping Microsoft gets enough flack that they finally address the issue!

Ramesh Sharma · 2026-09-03T15:46:15-0400

gunrunnerjohn said:
I tried a repair install from both WU sources and a local ISO source,

Hello @gunrunnerjohn ,
Recovery Drive is different source than WU or local iso.

gunrunnerjohn · 2026-09-03T15:51:18-0400

Ramesh Sharma said:
Hello @gunrunnerjohn ,
Recovery Drive is different source than WU or local iso.

I know, but they come from the same place. Folks are free to tilt at that windmill, but I'm going to wait for a real solution.

garlin · 2026-09-03T15:57:58-0400

A Windows Recovery is a (presumably) an earlier copy of your own component store (WinSxS).

It's not any more special than using a MCT or UUP dump ISO of the same build number, as the source image.

Ramesh Sharma · 2026-09-03T16:05:51-0400

Thanks everyone.
WIM files in sources folder of Recovery Drive work 100% when used as source by DISM.

garlin · 2026-09-03T16:14:44-0400

The Recovery drive is a backup of your system's WinSxS. So you're running a DISM check against an earlier copy of your own WinSxS.

The point is to run a DISM check against an external (and non-corrupted) source, because your own DISM can't figure out how to repair itself. Which is either caused by a DISM or Servicing Stack bug, or since your WinSxS is already corrupted.

Obviously comparing a copy of yourself against yourself will return no errors...

KevTech · 2026-09-03T16:27:32-0400

Ramesh Sharma said:
wmic logicaldisk get caption, volumename, size

WMIC was deprecated and is now removed from Win 11.

Poweshell alternative

Code:

Get-Volume | Select-Object DriveLetter, FileSystemLabel, Size

Ramesh Sharma · 2026-09-03T16:33:19-0400

Thanks @garlin.
I think two ways to verify image health if restored or not.
1.If first run of sfc / scanow shows integrity violations, and dism /restorehealth completes 100% and again run sfc /scannow....
This time it should show no integrity violations.
2. bcdboot E:\Windows /s S /f UEFI
This should repair corrupt boot loader.

Ramesh Sharma · 2026-09-03T16:35:17-0400

KevTech said:
WMIC was deprecated and is now removed from Win 11.

Poweshell alternative

Code:

Get-Volume | Select-Object DriveLetter, FileSystemLabel, Size

wmic runs from Recovery Drive in WinPE environment.

Sir_George · 2026-09-03T16:37:19-0400

FreeBooter said:
To fix the "source files could not be found" DISM error, you need to provide the command with a working repair source, such as a mounted Windows installation ISO file.

Download the official Windows ISO file matching your exact operating system version.

Right-click the downloaded ISO file in File Explorer and select Mount.

Note the new drive letter assigned to the mounted drive.

Open Command Prompt or PowerShell as an administrator.

Run this command to see the available image indexes, replacing X with your mounted drive letter:

Batch:

dism /get-imageinfo /imagefile:X:\sources\install.wim

Note the index number (#) that matches your specific edition of Windows (such as Windows 10 Pro or Windows 11 Home).

Run the repair command with your custom source and limit access to Windows Update, replacing X with the drive letter and # with your index number:

Batch:

DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:# /LimitAccess

After DISM completes successfully, type the following command and press Enter:

Code:

sfc /scannow

Restart your computer once the scan finished.

I did the above and it didn't work. See attachment.

Banjoman301 · 2026-09-03T17:11:44-0400

Sir_George said:
I did the above and it didn't work. See attachment.

Documented in other threads as well...

In the meantime, you might look into a couple of tools from Sysnative for diagnosing and fixing potential corruption...

ComponentsScanner

SFCFix

As others have mentioned, the /RestoreHealth issue will likely require a Microsoft fix.

The irony is a fix for this issue was pushed out in the June 2026 cumulative update for 24H2 (see Improvements section)...

June 9, 2026—KB5094126 (OS Builds 26200.8655 and 26100.8655) | Microsoft Support

June 9, 2026—KB5094126 (OS Builds 26200.8655 and 26100.8655)

support.microsoft.com

Still is not showing in known issues on the Windows Release Health page for 25H2...

Windows 11, version 25H2 known issues and notifications

View announcements and review known issues and fixes for Windows 11, version 25H2

learn.microsoft.com

Sir_George · 2026-09-03T17:46:18-0400

gunrunnerjohn said:
Welcome to the club. My advice is not to bother trying to fix this particular error right now. I worked on this one as some length, but clearly it's something that got screwed up about three releases ago. Apparently Microsoft has been apprised of this issue and I suspect someday they'll finally fix it. I did all of the suggested fixes and more, none of them eliminated this error.

I have been trying to correct this for a few hours using ChatGPT and nothing has worked. Outside of trying to fix the problem, I was concerned it may cause some problem if left in the current state. Do you know of any issues it may cause?

Restorehealth Error 800F0915

Well-known 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

Well-known member

My Computers My Computers

At a glance

At a glance

aka Mama Glass

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

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 Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Active member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computers

My Computers

My Computers

My Computer

My Computers

My Computer

My Computers

My Computer

My Computers

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer