Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security & DevOps Insights

  • Home
  • About
  • Advertise With US
  • Reviews
  • Contact
  • Toggle search form
Home » Windows Server » DISM failed with error 0x800f081f: Source file could not be found
  • Screenshot 2020 05 14 at 19.08.33
    Backup image to TFTP server Network | Monitoring
  • Create your own Network on AWS from Scratch
    VPC, Subnet, NACL, Security Group: Create your own Network on AWS from Scratch [Part 2] AWS/Azure/OpenShift
  • Screenshot 2020 05 13 at 19.23.25
    AWS Command-Line Interface: How to configure AWS CLI [Part 1] AWS/Azure/OpenShift
  • rrd
    How to uninstall the DriveLock Agent from your device Security | Vulnerability Scans and Assessment
  • SSL for Localhost on WAMP
    How to configure SSL for WAMP server Windows Server
  • offloadanapp
    How to Offload Individual Apps on iPhone Mac
  • dfg
    802.1x and EAP Authentication Types Security | Vulnerability Scans and Assessment
  • Dockerxx1
    How to install and uninstall Docker Desktop on Windows 10 and Windows Server Containers

DISM failed with error 0x800f081f: Source file could not be found

Posted on 21/09/202022/02/2025 Christian By Christian No Comments on DISM failed with error 0x800f081f: Source file could not be found
DISM error 0x800f081f

Usually, the DISM failed “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. In this article, we shall discuss “DISM failed with error 0x800f081f: Source file could not be found”. DISM failed with error 0x800f081f. Pleaase see 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.

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, 

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 DISM failed with error 0x800f081f 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 to DISM failed with error 0x800f081f

I resolved this by downloading the Windows 10 ISO from the Microsoft Tech Bench Upgrade Program. Using that as the source for the DISM command 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.

Next step in resolving DISM failed error 0x800f081f is mounting the iso. Once you’ve downloaded the iso, 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 DISM failed 0x800f081f 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 DISM failed with error 0x800f081f issue is to clean up image components. This can be done by running another DISM command. 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 on “DISM failed with error 0x800f081f: Source file could not be found” helpful. If you have any questions about the DISM failed error 0x800f081f, please let me know in the comment session.

5/5 - (1 vote)

Thank you for reading this post. Kindly share it with others.

  • Click to share on X (Opens in new window) X
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on Pinterest (Opens in new window) Pinterest
  • Click to share on Tumblr (Opens in new window) Tumblr
  • Click to share on Telegram (Opens in new window) Telegram
  • Click to share on WhatsApp (Opens in new window) WhatsApp
  • Click to share on Pocket (Opens in new window) Pocket
  • Click to share on Mastodon (Opens in new window) Mastodon
  • Click to share on Bluesky (Opens in new window) Bluesky
  • Click to share on Threads (Opens in new window) Threads
  • Click to share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:Microsoft Deployment Toolkit (MDT), WDS, Windows Deployment Services

Post navigation

Previous Post: Adding a new partition to an existing Linux server
Next Post: NTuser.dat file: How to correctly load Windows Registry Hive

Related Posts

  • group policy 1280x720 1
    Error: The processing of Group Policy failed because of lack of network connectivity to a DC. This may be a transient condition. A success message would be generated once the machine gets connected Windows Server
  • MSIEXEC returned 1602
    Fix MSIEXEC returned 1602: Trellix Setup cannot use this account Windows Server
  • images 8
    Microsoft Direct Access: Now Always On VPN Windows Server
  • 2022 1
    Install Windows Server 2022 on VirtualBox Network | Monitoring
  • Prevent Local Administrators from turning off BitLocker 1
    Prevent Local Administrators from managing BitLocker with the manage-bde command Windows
  • mbamclient
    How to deploy MBAM Client as part of a Windows Deployment Windows Server

More Related Articles

group policy 1280x720 1 Error: The processing of Group Policy failed because of lack of network connectivity to a DC. This may be a transient condition. A success message would be generated once the machine gets connected Windows Server
MSIEXEC returned 1602 Fix MSIEXEC returned 1602: Trellix Setup cannot use this account Windows Server
images 8 Microsoft Direct Access: Now Always On VPN Windows Server
2022 1 Install Windows Server 2022 on VirtualBox Network | Monitoring
Prevent Local Administrators from turning off BitLocker 1 Prevent Local Administrators from managing BitLocker with the manage-bde command Windows
mbamclient How to deploy MBAM Client as part of a Windows Deployment Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

sysadmin top30a

  • Screenshot 2020 05 14 at 19.08.33
    Backup image to TFTP server Network | Monitoring
  • Create your own Network on AWS from Scratch
    VPC, Subnet, NACL, Security Group: Create your own Network on AWS from Scratch [Part 2] AWS/Azure/OpenShift
  • Screenshot 2020 05 13 at 19.23.25
    AWS Command-Line Interface: How to configure AWS CLI [Part 1] AWS/Azure/OpenShift
  • rrd
    How to uninstall the DriveLock Agent from your device Security | Vulnerability Scans and Assessment
  • SSL for Localhost on WAMP
    How to configure SSL for WAMP server Windows Server
  • offloadanapp
    How to Offload Individual Apps on iPhone Mac
  • dfg
    802.1x and EAP Authentication Types Security | Vulnerability Scans and Assessment
  • Dockerxx1
    How to install and uninstall Docker Desktop on Windows 10 and Windows Server Containers

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,836 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory AWS Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Server 2016

Copyright © 2025 TechDirectArchive

 

Loading Comments...
 

You must be logged in to post a comment.