DISM Error 0x800f0915: Fix It in Windows

DISM error 0x800f0915 means the Deployment Imaging Service and Management Tool could not complete an operation because the Windows image or component store is corrupted or missing a required file. This usually appears when you run DISM /Online /Cleanup-Image /RestoreHealth and the tool cannot find a valid source to repair from. The fix involves checking your Windows version, using the correct source files (like the install.wim from your own ISO), and cleaning up the component store before retrying.

What Causes DISM Error 0x800f0915

The error code 0x800f0915 translates to CBS_E_INVALID_WINDOWS_IMAGE, which means the Windows image file you pointed DISM to is not a valid or usable Windows image. This happens in a few common scenarios:

You used a /Source path that points to a file that isn’t a Windows image (like a plain folder or a corrupted download).
The install.wim or install.esd file is from a different Windows edition or architecture than your installed system.
The source image itself is corrupted or incomplete because the download was interrupted.
You ran DISM without a /Source flag, and Windows Update is unavailable, so DISM falls back to local files that are also damaged.

Most users encounter this when trying to repair Windows 10 or Windows 11 after running sfc /scannow and being told that corrupt files were found but could not be fixed. DISM is the next step, and this error blocks that repair.

How DISM Repair Actually Works

DISM (Deployment Image Servicing and Management) is a command-line tool that services Windows images and the component store. When you run /RestoreHealth, it scans the component store for corruption and replaces damaged files with good ones. It needs a source—either Windows Update or a local image file—to copy healthy versions of system files from.

The component store (located at C:\Windows\WinSxS) is a central repository of all Windows components. If files in this store are damaged, any attempt to repair or update Windows can fail. DISM is designed to fix the store itself, but it cannot conjure files out of thin air; it must pull them from a trusted source. If the source is invalid, you get 0x800f0915.

There is a common misconception that running DISM with no /Source always works because it uses Windows Update. That is only true if Windows Update is fully functional and can reach Microsoft’s servers. In many repair scenarios, Windows Update is exactly what is broken, so DISM fails with this error.

Step-by-Step Fix for 0x800f0915

Follow these steps in order. Stop when the error no longer appears.

Check your Windows version and edition. Press Win + R, type winver, and note the version number (e.g., 22H2) and edition (Home, Pro, etc.). You need this to download the correct ISO.
Download the correct Windows ISO. Go to Microsoft’s official software download page and download the Windows 10 or Windows 11 ISO that matches your version and edition. Do not use a random third-party site.
Mount the ISO. Right-click the ISO file and choose Mount. Note the drive letter it gets (e.g., E:).
Find the install image. Open File Explorer, go to the mounted drive, and look in the sources folder. You will see either install.wim or install.esd.
Identify the correct index number. Open Command Prompt as Administrator and run:
dism /Get-WimInfo /WimFile:E:\sources\install.wim (or .esd). Look for the index that matches your edition (e.g., “Windows 11 Pro”).
Run DISM with the source. Replace E with your drive letter and N with the index number:
dism /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim:N /LimitAccess
The /LimitAccess flag prevents DISM from contacting Windows Update, forcing it to use only your local source.
If that fails, extract the image first. Some users find that pointing directly to the .wim works, but if not, extract it to a folder:
dism /Export-Image /SourceImageFile:E:\sources\install.wim /SourceIndex:N /DestinationImageFile:C:\repair\install.wim
Then use C:\repair\install.wim as your source.
If you still get 0x800f0915, clean the component store. Run dism /Online /Cleanup-Image /StartComponentCleanup first, then retry the restore command. This removes old versions of updated components, which sometimes clears the corruption.

Common Mistakes That Keep the Error Coming Back

Using the wrong edition. If your system is Windows 11 Home and you use a Pro ISO, DISM will reject it. Always match the edition exactly.
Using a .esd file when you need .wim. Some ISOs contain install.esd, which is compressed. DISM can usually read it, but if it fails, converting it to .wim with the export command above often solves it.
Not running as Administrator. DISM requires elevated privileges. Right-click Command Prompt and choose Run as administrator.
Skipping the /LimitAccess flag. Without it, DISM may try Windows Update first, fail, and then fall back to the local source—but sometimes it just fails outright. Forcing local-only avoids that confusion.
Using a corrupted download. If the ISO itself is damaged, no amount of retrying will help. Re-download it, and verify the SHA-1 hash if you know how.

What to Do If the Error Persists

If you have followed all the steps above and still get 0x800f0915, the component store may be too damaged for an online repair. Your options are:

Run DISM from Windows Recovery Environment (WinRE). Boot from the Windows installation USB, choose Repair your computer, then Troubleshoot > Command Prompt. From there, run DISM against the offline Windows installation. The command is different because the OS is not running:
dism /Image:C:\ /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim:N
Note that the drive letters may be different in WinRE; use diskpart or dir to find the correct ones.
Use the “Repair install” (in-place upgrade) method. Mount the ISO, run setup.exe, and choose Keep personal files and apps. This reinstalls Windows while preserving your data and often fixes deep corruption without losing anything.
Back up and do a clean install. This is the last resort. If the system is so damaged that even an in-place upgrade fails, a clean installation of Windows is the only reliable fix. Back up your files first.

Preventing DISM Errors in the Future

Once you have fixed the error, take steps to avoid it recurring:

Keep Windows Update enabled and run it regularly. Most corruption comes from interrupted updates.
Do not force-shut down your PC during updates. Let updates finish, even if it takes a while.
Run sfc /scannow occasionally, but do not rely on it alone—DISM is the repair tool for the component store.
If you use disk cleanup, do not delete the Windows Update cache unless you are sure updates are not pending.
Consider creating a system restore point before major changes, so you can roll back if something goes wrong.

Frequently Asked Questions

Can I use a Windows ISO from a different version (e.g., 21H2 vs 22H2)?

Yes, but only if the base version is the same or newer. For example, if you have Windows 11 22H2, you can use a 23H2 ISO as a source, but not a 21H2 one. The source must be at least as new as your installed version, and the edition must match. If you are unsure, download the exact ISO for your version from Microsoft’s site.

Why does DISM say “source files could not be found” even though I mounted the ISO?

This usually means the path is wrong or the file name is different. Check that the drive letter is correct (it may not be E:), and confirm whether the file is install.wim or install.esd. Also, if you are using a USB drive instead of a mounted ISO, the path will be different.

Is it safe to use a third-party tool to repair Windows instead of DISM?

No. Third-party repair tools are not officially supported and can make things worse. Stick with DISM and SFC, or use the Windows built-in reset and recovery options. If you need more help, use Microsoft’s official support channels.

Will this error go away if I just restart my PC?

No. A restart will not fix corrupted system files. The error is persistent because the component store is damaged. You must run the repair commands with a valid source as described above.

Can I run DISM from Safe Mode?

Yes, you can run DISM in Safe Mode, but it is not necessary. If you are in Safe Mode, make sure you are connected to the internet or have a local source available. The same commands work, but some services are disabled, so it is usually better to run it in normal mode unless normal mode is not booting.

What is the difference between /RestoreHealth and /ScanHealth?

/ScanHealth only checks the component store for corruption and reports whether it is repairable. It does not fix anything. /RestoreHealth actually performs the repair. Always run /ScanHealth first to confirm there is a problem, then run /RestoreHealth to fix it.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →