Windows Server

DISM failed with error 0x800f081f: The source file could not be found, no operation was performed

Usually, the “0x800f081f” error is caused by incorrectly configured system settings or irregular entries in the Windows registry. But in this case, this error message states that the DISM tool was unable to find the files required to fix the Windows image in their default location.

Here are some related contents, see how to fix error 0xc1510114: The wim file needs to be remounted, Error 0x80070002: When trying to mount an image file, Error code 15601: How to resolve DISM unspecified error when removing preinstalled packages, Error 0xc1420127: The specified image in the specified wim is already mounted for read and write access, and Error 740: Elevated permissions are required to run DISM.

This means the source files could not be found” even with the correct ISO, source files, and the right path. I also got this error without having any dependency issues. Below is the error log prompted when I tried adding packages to the Windows Image (WIM).
- Error: 0x800f081f
- DISM failed. No operation was performed.
- For more information, review the log file.
- The DISM log file can be found at C:\windows\Logs\DISM\dism.log

To resolve this issue, you have to either run a component clean up and then an SFC Scan or provide DISM with a location that contains the files it needs to attempt the image repair.

Solution: I resolved this by downloading the Windows 10 ISO from the Microsoft Tech Bench Upgrade Program and using that as the source for the DISM command Visit the following Tech Bench and download the iso file again. You can use this alternative link too.

Alternatively, the Windows 10 2004 language ISO can be downloaded from the following website https://my.visualstudio.com or from https://www.microsoft.com/vlsc, which is Volume Licensing Service Center as well.

Once the iso is downloaded, mount it. ( Right-click at the iso file > click Mount ) and extract the needed package (FoD) you wish to add to your install.wim file (windows image). See this article on how to add packages to the Windows image (install.wim) file.

Now, when you try to add the package again with the right PackageFamilyName (UWP), you should get the following message below that the installation was successful.

Deployment Image Servicing and Management tool
Version: xxxxxxx

Image Version: xxxxxx

Processing 1 of 1 - Adding package Microsoft-OneCore-DeveloperMode-Desktop-Package~31bf3856ad364e35~amd64~~10.0.19041.1
[==========================100.0%==========================]

If the following step mentioned above do not work, you should perform the following steps below.
1: Analyse the Component: Before proceeding to start the component clean, first analyze it to see if there are errors. Here is the command to achieve this. MountZ here is the mounted directory.

dism /Image:G:\Path-to-the-mounted-wim-file\<MountedZ> /Cleanup-Image /AnalyzeComponentStore >>G:\path-to-the-text-fileoutput\AnalyzeCompStore.txt

2: Clean the Components File: The first way to tackle this issue is to clean up image components. This can be done by running another DISM command. Use use the command below to resolve issues with the install.wim file.

dism /Cleanup-Image:G:\path-to-mounted-wim-file/StartComponentCleanup /ResetBase

Note: Also try to see if there are dependencies that is needed for the the package you are adding. If this is not meant, this could also result to issue.

I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x