“The source files could be found” error, after running the “DISM /Online /Cleanup-Image /RestoreHealth” command, is a common problem on Windows 10 and 8 based computers. ( DISM’s source files could be found error codes: 0x800f081f or 0x800f0906 or 0x800f0907 )
The error “The Sources files could not be found files” in DISM tool, is commonly caused because of the following reasons:
Reason 1. DISM tool cannot find online (in Windows Update or WSUS) the files needed to perform the repair, when using this command: “DISM /Online /Cleanup-Image /RestoreHealth”
Reason 2. You have specified a wrong Windows Image (install.wim) file as the repair source, when using this command: “DISM /Online /Cleanup-Image /RestoreHealth /Source“
Reason 3. The install.wim or the install.esd file, that you ‘re using as a repair source, contains multiple install.wim files. (DISM /Online /Cleanup-Image /RestoreHealth /Source)
- FIX DISM 0x800f081f Error in Windows 10/8
- How to Extract Install.ESD to Install.WIM (Windows 10/8)
- How to Extract an INSTALL.WIM file that contains several INSTALL.WIM files.
In this troubleshooting guide you will find several methods to resolve the following DISM errors: “The Source Files Could not be Found”, “0x800f081f”, “0x800f0906”, “0x800f0907”.
How to FIX: DISM /RestoreHealth Could not Find Source Files to Repair Windows 10 or Windows 8/8.1.
Method 1. Clean and Analyze the WinSXS folder.
The Windows Component Store folder, aka WinSXS (C:\Windows\winsxs), contains all the files needed during servicing operations in Windows, such as the installation of updates, hotfixes, etc. Additionally, the WinSXS folder, contains all the files needed for a Windows installation or repair.
In time, the size of WinSXS folder becomes large or corrupted, because of updates and new features that are added to the installation, so it needs cleaning before running the DISM tool. To do that:
- DISM /Online /Cleanup-Image /StartComponentCleanup
- SFC /SCANNOW
- DISM /Online /Cleanup-Image /AnalyzeComponentStore
- SFC /SCANNOW
3. Restart your computer.
4. After the restart, open command prompt (as admin) again and run DISM.
- DISM /Online /Cleanup-Image /RestoreHealth
Method 2. Specify an alternative Repair Source in DISM by using the /Source switch.
By default DISM looks online to find the required files to repair the Windows Image. But in most cases, this doesn’t work, so you need to specify a local source for the known good files by using the /Source switch.
Requirements: To accomplish this task you need the install.wim file (X:\sources.install.wim), from a Windows installation media (USB, DVD or ISO), that has the same Windows version, edition and language with the installed version.
If you don’t own a Windows installation media (USB, DVD or ISO), then you can obtain one, by using these options:
- Option A. Download Windows by using the Media Creation tool, or
- Option B. Download Windows in a ISO file by using the Windows ISO Downloader tool, by following the instructions on this article: How to Download Any Version of Windows or Office w/o a Product Key (Legally & Free)
1. If you have used the Media creation tool (option A), to download Windows 10, then you may need to extract the according to your Windows version install.wim file, from the install.esd file (X:\sources\install.esd), by using these instructions: How to Extract Install.ESD to Install.WIM (Windows 10/8)
2. If you have used the Windows ISO Downloader tool (option B), to download Windows 10/8 ISO, then you may need to extract a Windows Image (according to the installed Windows version) from the install.wim file (X:\sources\install.esd) file, by using these instructions: How to Extract an INSTALL.WIM file that contains several INSTALL.WIM files.
To specify an alternative Repair Source in DISM:
- DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\install.wim file:1 /LimitAccess
* Note: Replace the “X” drive letter according to your case. For example, if the Windows installation media is at drive “D”, then the command will be:
- DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess
6. Be patient until DISM repairs the Windows image component store.
7. When the operation is completed, you should be informed that the “operation is completed successfully”. *
* Note: If the DISM tool fails again with “Error 0x800f081f: The Sources files could not be found”, then read this guide before proceeding to the rest methods. The problem has – probably – occurred because the install.wim file, contains multiple install.wim files.
8. Finally, to complete the repairs run the sfc /scannow command:
- SFC /SCANNOW
9. When the SFC scan is completed successfully, you ‘re done!
Method 3. Specify an alternative Repair Source by using Policies or Registry.
1. Attach the Windows installation media on your system.
1. Copy the install.wim file from the Windows installation media (e.g. (X:\sources.install.wim) to the C:\ drive (root folder).
2. According to your Windows version (Pro or Home), follow the instructions below to specify the C:\install.wim file, as the default source to repair the Windows Image.
2A. Windows 10 Pro & Windows 8/8.1 Pro
– Specify DISM /Source in Local Group Policy Editor:
3. In Group Policy Editor navigate (from the left side) to:
- Computer Configuration > Administrative Templates > System
4. At the right pane open the “Specify settings for optional component installation and component repair” setting.
5. Apply the following settings:
1. Check Enabled
2. At “Alternate source file path” type: wim:C:\install.wim:1
3. Check Never attempt to download payload from Windows Update
6. Click OK and close Policy Editor.
7. Restart your computer.
8. After the restart, run the “DISM /Online /Cleanup-Image /RestoreHealth” command again.
10. When the repair is completed, then undo the changes in Policies.
2B. Windows 10 Home & Windows 8/8.1 Home
– Specify DISM /Source in Windows Registry:
3. At the left pane, navigate to this key:
4. Right click at Policies key and select New > Key
5. Give at the new key the name: Servicing
6. Highlight the Serving key.
7. Right click at the right pane and choose New > Expandable String Value
8. Give at the new value the name: LocalSourcePath
9. Double click at “LocalSourcePath” and at the value data box, type: wim:C:\install.wim:1
10. Click OK.
11. Right click again at the right pane, and choose New > DWORD (32-bit) Value.
12. Give at the new value the name: UseWindowsUpdate
13. Double click at “UseWindowsUpdate” and at the value data box, type: 2
14. Click OK
* 2 = Do Not use Windows Update
15. Close registry editor and restart your computer.
16. After the restart, run the “DISM /Online /Cleanup-Image /RestoreHealth” command again.
17. When the repair is completed, then undo the changes in Windows Registry.
Method 4. Fix DISM Source Files Cannot be Found Error with Windows Repair Upgrade.
The other method to fix DISM errors is to perform a repair upgrade of Windows 10.
Step 1. Repair/Upgrade Windows 10 by using the Media Creation Tool.
1. Download and run the media creation tool according to your OS Version.
2. Accept the License Terms.
3. Choose the option Upgrade this PC now and press Next.
4. Wait until Windows is upgraded.
Step 2. Use DISM and SFC tools to complete repairs.
– After Windows upgrade:
- DISM /Online /Cleanup-Image /StartComponentCleanup
- Dism /Online /Cleanup-Image /RestoreHealth
- sfc /scannow
Method 5. Fix DISM errors by examine the CBS.LOG file.
(UPDATED on 17/5/2017)
After it’s execution, DISM creates a log file named “CMS.log” at “C:\Windows\Log\CBS” directory (e.g. C:\Windows\Log\CBS\ CBS.log), that captures any issues found, when DISM command tool is executed.
So, the last method to fix DISM’s “Source Files Cannot be Found” error, is to examine the CBS.LOG file, in order to find out and remove the installed package(s) that causes the problem.
Step 1. Examine DISM’s log file (CBS.LOG).
1. Navigate to C:\Windows\Log\CBS directory and open the CBS file.
2. Using the Find tool (View > Find), search for “Checking System Update Readiness”.
3. Now look under the “Checking System Update Readiness” line, to find out the corrupted package(s). *
* e.g As you can see at the below screenshot, the corrupted package is named: “Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0”
4. Once, you find out, the name of the corrupted package, then continue to the next step.
Step 2. Remove the corrupted package’s registry entry.
IMPORTANT: Before you continue to modify the registry, first take a backup. To perform a registry backup:
a. From the main menu, go to File & select Export.
b. Specify a destination location (e.g. your Desktop), give a filename (e.g. “RegistryBackup”) and press Save.
3. From the left pane navigate and select this key:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
5. With the Component Based Servicing key highlighted, go to Edit > Find (from the menu) and search for the corrupted package name in the registry. To do that, just copy and paste in the search box, the name of the corrupted package from the CBS.LOG. (e.g. “Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0“)
6. At this occasion, the name of the corrupted package was found at the following two (2) registry locations/keys:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
7. Now, for safety reasons, backup all the registry key(s) you found, by right-clicking on each of them (on the left pane) and choose Export. *
* Note: Save the registry keys on your desktop, in order to easy import them backup if something goes wrong. (Double click at the exported key(s) and Merge).
8. Then, assign full control permissions, to the all key(s) you found, to Administrators. To do that:
1. Right click on each key and select Permissions.
2. Highlight Administrators, place a check mark on Full Control checkbox and click OK.
9. Finally, delete all the registry key(s) you found. (Right click on each key and Delete)
10. Close Registry Editor.
Step 3. Move the corrupted packages to other location on disk.
1. Navigate to C:\Windows\Servicing\Packages folder.
2. Now find and move to your desktop, all the packages that their name begins with the name of the damaged package in the CBS.LOG.
e.g. At this occasion I found (and moved to my desktop) the following four (4) files, that their name begins with the name of the corrupted package: Microsoft-Windows-TestRoot-and-FlightSigning-Package
3. Restart you computer.
4. Run the “DISM /Online /Cleanup-Image /RestoreHealth” command again.
5. If DISM is completed without errors, then proceed and delete permanently the exported registry key(s) and the moved packages from your desktop.
Good luck! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.