Deployment Image Servicing and Management (DISM) mounts a Windows image (.wim) file or virtual hard disk (.vhd or .vhdx) for servicing. You can also use the DISM image management command to list the image index numbers, to verify the architecture for the image that you are mounting, to append an image, apply an image, capture an image, and delete an image. Here are some DISM related errors, Failure 5627: How to fix error 0x800f0805, run DISM executable, Error 0xc1420127: The specified image in the specified wim is already mounted for read and write access.
See the following hyperlink for more details on ADK, MDT, Microsoft Endpoint Configuration Manager (SCCM), Intune, Autopilot, and WSUS. Also, see how to configure and deploy Windows using Microsoft Deployment Toolkit, and Windows Deployment Services for Windows 10 (ADK, MDT, and WDS).
The following error “Error 0x800f0830, discard the modified Image and start again: DISM failed, no operation was performed” was prompted because the packages were already installed and as such could not install the packages again.
Microsoft-Windows-xxxxxxxxxxxx-xxxxxxxxx-Package: The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again.
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
In this case, you absolutely have nothing to fix. Simple use the command below to determine if the application has truly been installed.
dism /Image:<MountedDir> /get-features
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.