DISM Error 0x800f0915: How to Fix It on Windows 11

DISM error 0x800f0915 usually means Windows could not get the repair files it needed to complete RestoreHealth.

That is why running the same command again and again often changes nothing.

When this error appears, I would treat it as a repair-source problem first. Let Windows try its normal online source once. If that fails, verify that the component store is repairable, then give DISM a Windows source that actually matches the installation you are repairing.

The important part is not downloading any random Windows ISO. The edition, release, architecture, language, image format, and image index all matter.

Start With the Normal Online Repair

Open Terminal (Admin) or Command Prompt (Admin) and run:

DISM /Online /Cleanup-Image /RestoreHealth

Windows normally uses its configured servicing sources and can contact Windows Update for repair content.

Microsoft’s current repair guidance still recommends running DISM before System File Checker because DISM can provide the files SFC needs to repair protected Windows components.

If the command finishes successfully, run:

sfc /scannow

Restart Windows afterward.

If 0x800f0915 returns, stop repeating RestoreHealth and find out whether the image is actually repairable.

Official Microsoft reference:
https://support.microsoft.com/en-us/windows/experience/backup-recovery/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files

Check the Component Store Before Downloading Anything

Run:

DISM /Online /Cleanup-Image /CheckHealth

CheckHealth is quick. It reports whether Windows has already marked the component store as corrupted and whether that corruption can be repaired.

For a deeper scan, run:

DISM /Online /Cleanup-Image /ScanHealth

There are three useful outcomes.

No corruption detected

If DISM says the component store is healthy, reconsider why you are running RestoreHealth.

The original Windows problem may be somewhere else.

The image is repairable

This is the situation where a matching local source makes sense.

The image is non-repairable

Ordinary source commands may not be enough. Back up important files and consider a Windows repair reinstall later in this article.

Make Sure Windows Update Is Not the Real Problem

Before moving to an ISO, check:

Settings > Windows Update

Install pending updates and restart.

Also confirm that:

• the PC has working internet access
• Windows Update itself is not showing an error
• a VPN is not blocking Microsoft services
• a proxy is not misconfigured
• the date and time are correct

When Windows Update is broken, DISM may be unable to obtain repair content through the normal online route.

If Windows Update itself is stuck or repeatedly failing, use How to Clear Windows Update Cache and Fix Update Problems before assuming the ISO is the only solution.

The ISO Must Match the Windows Installation Closely

This is where many DISM source repairs go wrong.

Press:

Windows + R

Enter:

winver

Note the Windows release and build.

Then open:

Settings > System > About

Check:

• edition
• system type
• Windows version

For example, note whether you are using Windows 11 Home or Pro and whether the PC is x64 or Arm64.

Download Windows installation media only from Microsoft:

https://www.microsoft.com/software-download/windows11

Use media that matches the Windows installation as closely as possible.

A mismatched source can still mount normally and look valid in File Explorer while DISM rejects it as unsuitable repair content.

Mount the ISO and Look Inside the Sources Folder

After downloading the ISO:

1. Open File Explorer.
2. Locate the .iso file.
3. Right-click it and choose Mount.
4. Note the drive letter Windows assigns.

I will use D: in the examples below.

Your PC may use another letter.

Open:

D:\sources

Look for one of these:

install.wim

or:

install.esd

Do not assume every Windows ISO uses install.wim.

The image type changes the source syntax you use later.

Find the Correct Edition Inside the Image

A Windows ISO can contain several editions.

Do not copy an image index from a YouTube video or another PC.

If the ISO contains install.wim, run:

DISM /Get-WimInfo /WimFile:D:\sources\install.wim

If it contains install.esd, run:

DISM /Get-WimInfo /WimFile:D:\sources\install.esd

DISM will list the images stored in the file.

Look for the edition that matches your installed Windows edition.

You may see output similar to:

Index : 1
Name  : Windows 11 Home

Index : 6
Name  : Windows 11 Pro

Those numbers are only examples.

Use the index displayed by your own ISO.

Microsoft’s DISM documentation specifically supports inspecting Windows image files to determine which indexes and editions they contain.

Run RestoreHealth With the WIM Source

Suppose:

• the ISO is mounted as D:
• it contains install.wim
• your matching Windows edition is index 6

Use:

DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:6 /LimitAccess

Replace:

• D: with your ISO drive letter
• 6 with the correct index from your own image

/LimitAccess tells DISM not to contact Windows Update and to rely on the source you supplied.

That is useful when the whole reason you are using an ISO is that the online servicing path already failed.

If the ISO Uses install.esd

Use the same logic but change the source type.

For example:

DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:D:\sources\install.esd:6 /LimitAccess

Again, the index number is only an example.

Use the edition index reported by your own DISM /Get-WimInfo command.

What a Source Failure Usually Tells You

If the local-source command still fails, the result is more useful than simply saying “DISM is broken.”

Recheck these items:

Wrong edition
A Home installation should not be repaired with a Pro image index.

Wrong architecture
x64 and Arm64 media are not interchangeable.

Wrong image type in the command
Use wim: with install.wim and esd: with install.esd.

Wrong drive letter
The mounted ISO may be E: or another letter instead of D:.

Wrong image index
Never assume the index number.

Media does not match the installed Windows release closely enough
Download fresh official media instead of reusing an old ISO.

The component store has deeper damage
At some point an in-place repair becomes safer than forcing more DISM commands.

Do Not Add /LimitAccess Without a Valid Local Source

/LimitAccess prevents DISM from contacting Windows Update.

That is useful only when you have already supplied a valid source.

Running a command that blocks Windows Update without giving DISM usable repair files can leave it with nowhere to obtain the components it needs.

Microsoft documents /Source as the location of known-good repair files and /LimitAccess as the option that prevents online repair from contacting Windows Update.

Run SFC After DISM Finally Succeeds

When DISM reports:

The restore operation completed successfully.
The operation completed successfully.

run:

sfc /scannow

DISM repairs the Windows image that SFC can use as a source for protected system files.

If SFC itself fails with a Windows Resource Protection message, use Windows Resource Protection Error: How to Fix It rather than starting the entire DISM procedure again.

When an In-Place Repair Is the Better Next Step

There is a point where more DISM experimentation stops adding value.

I would consider a Windows repair reinstall when:

• CheckHealth reports non-repairable corruption
• a correctly matched source still cannot repair the image
• Windows Update and servicing are both badly damaged
• several Windows components are failing
• DISM repeatedly returns source or servicing errors after the source has been verified

Windows 11 now provides a less disruptive repair option under:

Settings > System > Recovery

Look for:

Fix problems using Windows Update

and:

Reinstall now

When available, this reinstalls the current Windows version while preserving apps, files, and settings.

For the full process, see Reinstall Your Current Version of Windows to Repair System Files.

Avoid the Common DISM Source Mistakes

The most damaging mistakes with 0x800f0915 are usually not complicated.

They are things like:

• using an old ISO simply because it is already on the PC
• assuming every ISO contains install.wim
• copying somebody else’s image index
• using /LimitAccess before confirming the source
• downloading modified installation media from an unofficial website
• running RestoreHealth ten times without changing the repair source
• moving straight to a clean installation when an in-place repair is still available

For this error, precision matters more than the number of fixes.

If the online repair cannot obtain the files it needs, give DISM a known-good source that matches the Windows installation. If even that source fails after you have verified the edition, architecture, image type, and index, move to a repair reinstall instead of piling more commands onto a damaged servicing stack.