DISM error 0x800f0915 usually appears when Windows cannot find the source files it needs to repair an image, install a feature, or complete a servicing task. It often shows up during DISM, Windows Update repair work, or when enabling optional Windows components.
The good news is that this error is usually caused by a source mismatch, missing repair files, or an update component problem rather than a serious hardware failure. In most cases, you can fix it by pointing DISM to the correct Windows source or by repairing Windows Update components first.
What DISM Error 0x800f0915 Means
DISM stands for Deployment Image Servicing and Management. It is the Windows tool used to repair the operating system image and handle features and components stored in that image. Error 0x800f0915 generally means DISM could not complete the requested operation because the files it needed were unavailable, incompatible, or blocked by another servicing issue.
Most Common Causes
- The Windows installation source does not match the version, build, or language of the system.
- Windows Update components are damaged and cannot download repair files.
- The component store is corrupted enough that DISM cannot complete the repair automatically.
- A feature install or cleanup task is being run without the correct source path.
- Temporary servicing files are stuck or partially downloaded.
Try These Fixes in Order
- Run DISM with an explicit repair source from a Windows ISO or installation media that matches your installed version.
- If the error appears during a feature install, make sure the ISO or source files are from the same edition and language as your system.
- Reset Windows Update components so DISM can download what it needs again.
- Run the System File Checker after DISM to verify that protected system files are repaired.
- If the image is still damaged, use an in-place repair install of Windows.
1. Use the Correct Repair Source
The most common reason for 0x800f0915 is that DISM is trying to use a source that does not exactly match your Windows installation. That includes version, build, edition, and language. For example, a Windows 11 ISO will not help if you are repairing a Windows 10 installation, and even different language packs can cause problems.
- Mount a Windows ISO that matches your installed Windows version and edition.
- Open Command Prompt as an administrator.
- Run a command like: DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:X:\sources\install.wim:1 /LimitAccess, replacing X with the mounted ISO drive letter.
- If your ISO contains install.esd instead of install.wim, use the correct file name in the command.
- Wait for the process to finish, then try the repair again if needed.
2. Let DISM Use Windows Update Again
If you previously used the /LimitAccess switch or your system cannot reach Microsoft’s repair content, DISM may fail because it has nowhere else to download replacement files from. Removing the restriction can help if Windows Update itself is healthy.
- Open Command Prompt as an administrator.
- Run: DISM /Online /Cleanup-Image /RestoreHealth without the /LimitAccess switch.
- Wait for the scan and repair to complete.
- If Windows Update starts downloading files, let it finish before trying SFC.
If this still fails, the problem is more likely in Windows Update components or the local servicing cache.
3. Reset Windows Update Components
When Windows Update folders or services are damaged, DISM may not be able to obtain the repair payload it needs. Resetting the update components clears out stuck downloads and reinitializes the services involved in servicing.
- Open Command Prompt as an administrator.
- Stop the relevant services with these commands: net stop wuauserv, net stop cryptSvc, net stop bits, and net stop msiserver.
- Rename the SoftwareDistribution and Catroot2 folders.
- Restart the services with the matching net start commands.
- Run DISM again after the reset.
4. Run System File Checker After DISM
DISM repairs the Windows image. SFC repairs protected operating system files. If DISM completes successfully, running SFC afterward can fix remaining file corruption and confirm the system is stable.
- Open Command Prompt as an administrator.
- Run: sfc /scannow
- Wait for the scan to complete.
- If SFC reports that it found and repaired files, restart when you are done with troubleshooting.
5. Repair Windows with an In-Place Upgrade
If DISM error 0x800f0915 keeps returning even with the correct source and a reset Windows Update cache, the Windows installation itself may be too damaged for normal servicing. An in-place repair install replaces Windows system files while keeping your apps and personal files in place in many cases.
- Download the correct Windows installation media for your version of Windows.
- Run Setup from inside Windows, not from booting the PC.
- Choose the option to keep personal files and apps if it is available.
- Follow the prompts until the repair installation completes.
When the Problem Is Feature-Specific
Sometimes 0x800f0915 appears while enabling a Windows feature such as .NET Framework, Hyper-V, or language packs. In that case, the fix often depends on providing the exact source files for that feature rather than using a general repair command.
- Make sure the feature source comes from the same Windows version and edition.
- Confirm that the language matches if the feature is language-related.
- If the feature was removed by policy or by a cleanup tool, restore the source before trying again.
- Check whether the feature needs a mounted ISO, installation share, or Windows Update access.
How to Narrow Down the Cause
The error message and the command you were running can help you identify the likely cause. If DISM fails only when you use a specific source, the source is probably wrong. If DISM fails even without a source, Windows Update or the component store is more likely to blame. If only one feature fails, the issue is probably tied to that feature rather than the whole system.
What Not to Do
Summary
DISM error 0x800f0915 usually means Windows cannot find the right files to complete a repair or feature installation. The fastest fix is often to use a matching Windows source image, but resetting Windows Update and running SFC afterward are also important steps. If normal repairs fail, an in-place repair install is usually the most reliable next move.