If DISM /Online /Cleanup-Image /RestoreHealth returns “The source files could not be found” (often 0x800f081f, 0x800f0906, or 0x800f0907), DISM cannot obtain a compatible repair payload for the Windows component store. It does not usually mean a missing DLL or that Windows is permanently damaged. On Windows 8.1 and 10, try Windows Update first; if that fails, use installation media that matches your edition, architecture, language, release, and preferably build. Windows 7 needs a different repair path.
Before you start
- Back up important files and connect a laptop to power.
- Open Command Prompt with Run as administrator.
- Confirm the Windows version with
winverand the architecture withsysteminfo(or Control Panel → System on older versions). - Leave adequate free disk space. DISM can appear to pause at one percentage; do not interrupt it solely for that reason.
- Temporarily disabling third-party security software is not normally required. Only try it as a targeted troubleshooting step, then re-enable it immediately.
What the error means
Windows has detected component-store corruption or a repairable servicing state, but cannot locate the replacement files. Microsoft associates CBS_E_SOURCE_MISSING and errors such as 0x800f081f with an unavailable or unsuitable repair source. The cause may be broken Windows Update access, missing local payload, an incorrect ISO edition or index, mismatched language or build, blocked enterprise policy, or deeper package corruption.
DISM repairs the component store (the source used by Windows servicing and SFC). SFC repairs protected system files from that store, so running SFC first is not a universal answer to a DISM source error.
Microsoft’s error guidance describes the component-store/source relationship.
Recommended Free Tools
#1 Best Overall
- Comprehensive Solution: This Windows 10 reinstall DVD provides a complete solution for resolving various system issues, including crashes, malware infections, boot failures, and performance slowdowns. Repair, Recover, Restore, and Reinstall any version of Windows.
- USB will work on any type of computer (make or model). Creates a new copy of Windows! DOES NOT INCLUDE product key.
- Windows not starting up? NT Loader missing? Repair Windows Boot Manager (BOOTMGR), NTLDR, and so much more with this DVD. Clean Installation: Allows you to perform a fresh installation of Windows 11 64-bit, effectively wiping the system and starting from a clean slate.
- Step by Step instructions on how to fix Windows 10 issues. Whether it be broken, viruses, running slow, or corrupted our disc will serve you well
- Please remember that this DVD does not come with a KEY CODE. You will need to obtain a Windows Key Code in order to use the reinstall option
Quick repair for Windows 8.1 and Windows 10
- In an elevated Command Prompt, check whether corruption is flagged:
DISM /Online /Cleanup-Image /CheckHealth - Run a deeper scan:
DISM /Online /Cleanup-Image /ScanHealth - Allow DISM to use Windows Update as its source:
DISM /Online /Cleanup-Image /RestoreHealth - When DISM reports The operation completed successfully, run:
sfc /scannow - Restart, then retry Windows Update or the original problem.
/CheckHealth checks whether corruption has already been recorded, /ScanHealth scans for it, and /RestoreHealth scans and repairs where possible. See Microsoft’s DISM command documentation.
- No component-store corruption detected: DISM may not be the cause of the original symptom.
- The component store is repairable: continue with
/RestoreHealth. - The component store cannot be repaired or the source cannot be found: use matching media below.
Repair with a matching Windows ISO
1. Get legitimate installation media
Use Microsoft or your computer manufacturer, not an unofficial ISO or “one-click repair” download. Microsoft provides Windows 10 media at the Windows 10 download page. Windows 8.1 and Windows 7 consumer downloads are more limited; use media that matches your license or manufacturer recovery media.
2. Mount the media
In Windows 10 or 8.1, right-click the ISO and select Mount. Note the new drive letter, for example D:. Windows 7 users should prefer a DVD or trusted manufacturer media; do not install an unverified mounting utility.
3. Check whether it contains WIM or ESD
Inspect D:\sources\ for install.wim or install.esd:
Free tools Windows power users keep installed
One-click scans. No signup required.
dir D:sourcesinstall.*
4. Find the correct edition index
Never assume index 1 is Home or Pro. Query the file you actually have:
DISM /Get-WimInfo /WimFile:D:sourcesinstall.wim
DISM /Get-WimInfo /WimFile:D:sourcesinstall.esd
Choose the index matching the installed edition (Home, Pro, Enterprise, or Education).
5. Run the source-specific repair
For WIM media:
DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:sourcesinstall.wim:INDEX /LimitAccess
For ESD media:
DISM /Online /Cleanup-Image /RestoreHealth /Source:esd:D:sourcesinstall.esd:INDEX /LimitAccess
For example, replace INDEX with 6 if the edition query identifies index 6. Replace D: with your actual drive letter. /LimitAccess tells DISM not to contact Windows Update; it is useful when you deliberately want only the supplied media, but it cannot make an incompatible source valid.
Microsoft also documents using a mounted, known-good Windows directory as a source:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsDISM /Online /Cleanup-Image /RestoreHealth /Source:C:MountWindows /LimitAccess
See DISM image and global syntax and the Cleanup-Image options.
How closely must the source match?
Match the source as closely as possible on all of these:
- Edition (Home, Pro, Enterprise, or Education)
- 32-bit/x86 or 64-bit/x64 architecture
- Display language
- Major release and feature update
- OS build and servicing level, where available
Record the installed build with winver, not just “Windows 10.” A Windows 10 image cannot repair Windows 8.1, and Home media should not be casually used against Pro. A build mismatch can create another servicing error instead of fixing the first one.
If the source command still fails
Verify the path and index
- Mounting can assign a different drive letter than expected.
- Use
install.esdsyntax for ESD andinstall.wimsyntax for WIM. - Include the
wim:oresd:prefix and the correct index. - Use an elevated prompt and check the file with
dir D:sourcesinstall.*.
Try Windows Update without /LimitAccess
If Windows Update is working, run:
DISM /Online /Cleanup-Image /RestoreHealth
Without /LimitAccess, DISM may obtain missing payload from Windows Update. Microsoft describes this behavior at RestoreImageHealth.
Rank #2
- Fresh USB Install With Key code Included
- 24/7 Tech Support from expert Technician
- Top product with Great Reviews
Check servicing policy
On a work-managed computer, Group Policy, WSUS, or an enterprise repair share may control where repair content comes from. Do not change registry or policy settings casually; ask IT for the approved source.
Read the logs
Review:
C:WindowsLogsDISMdism.log
C:WindowsLogsCBSCBS.log
Search for 0x800f081f, CBS_E_SOURCE_MISSING, Cannot repair member file, corrupt, and source. The entries help distinguish a bad path, mismatched payload, pending action, package corruption, or access/storage failure. Microsoft lists these logs in its component-store troubleshooting guidance.
Check the file system
If corruption returns, scan the system volume:
chkdsk C: /scan
For errors requiring an offline repair, schedule:
chkdsk C: /f
CHKDSK checks the file system and disk; it does not supply missing Windows component files.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Run SFC after DISM succeeds
Run:
sfc /scannow
Possible results include no integrity violations, repaired files, files that could not all be repaired, or an inability to start the repair service. If SFC still fails, restart, inspect CBS.log, and run it again. Persistent failure can mean the source still lacks exact required files or that an in-place repair is needed. Microsoft’s workflow is documented at Using System File Checker in Windows.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Windows 7: use a separate repair path
Do not copy the modern Windows 10 workflow blindly to Windows 7. Microsoft’s current image-repair parameter documentation principally covers Windows 8 and later.
- Open an elevated Command Prompt and run
sfc /scannow. - Run Microsoft’s System Update Readiness Tool (CheckSUR) for the installed Windows 7 architecture and service-pack state.
- Restart and retry Windows Update.
- If corruption remains, perform an in-place Windows 7 repair with matching media, provided edition and service-pack requirements are met.
Back up files first. Windows 7 and 8.1 are legacy systems, so official update and media availability is more constrained. Microsoft’s parameter limitations are described at Repair-WindowsImage documentation.
When Windows will not boot: offline DISM
In Windows Recovery Environment (WinRE), use /Image: for an offline installation, not /Online. Drive letters often change in recovery mode:
diskpart
list volume
exit
After identifying the Windows volume and media, a typical command is:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchDISM /Image:C: /Cleanup-Image /RestoreHealth /Source:wim:D:sourcesinstall.wim:INDEX /LimitAccess
Do not assume C: is Windows or D: is the ISO; verify both first. See Microsoft’s online versus offline syntax.
Choose the next step
| Situation | Best next step | Trade-off |
|---|---|---|
| DISM succeeds online | Run SFC and restart | Fastest, least invasive option |
0x800f081f or missing source |
Use matching WIM/ESD or mounted Windows source | Requires compatible media |
| Windows Update is blocked | Use /Source ... /LimitAccess |
Local source must be exact enough |
| Wrong edition or index | Run /Get-WimInfo again |
Usually an easy correction |
| Managed PC | Ask IT for the approved repair source | Local policy changes may be prohibited |
| DISM and SFC both fail | Inspect logs, pending actions, and storage | May require deeper servicing repair |
| Windows works but corruption is severe | Consider an in-place repair installation | Takes longer but may preserve apps and files |
| Windows will not boot | Use WinRE and offline DISM | Drive letters and paths differ |
When to stop troubleshooting
Move to an in-place repair, Reset this PC, clean installation, or qualified IT/professional support when a closely matching source repeatedly fails, CBS logs show extensive package corruption, Windows cannot boot, the drive reports errors, the device is organization-managed, or malware or hardware failure is suspected. DISM addresses Windows image and component-store servicing; it does not automatically repair malware, failing hardware, every boot problem, broken user profiles, or third-party applications.
Standard Windows 10 Home and Pro support ended on August 18, 2026; check Microsoft’s lifecycle page for edition-specific exceptions or extended-support arrangements.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →




