MDT 2013 - import WIM Windows 10 2009 (20H2)

Branko Uzelac 21 Reputation points
2021-01-21T14:27:34.023+00:00

Hello all,
I'm trying to import new WIM file from Windows 10 2009 (20H2) version using latest MDT 2013 (8456) and Windows ADK and PE version 10.1.19041.1. I have update deployment share,reboot PC, but everytime I try to import new WIM file with full set of source files I'm getting following error:

Performing the operation "import" on target "Operating system".
Unable to get information for WIM file D:\win10\Sources\Install.wim.
System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: An attempt was made to load a program with an incorrect format
--- End of inner exception stack trace ---
at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
at Microsoft.BDD.PSSnapIn.ImportOperatingSystem.Import(String sourcePath, String directoryName, Boolean moveDirectory)
Import processing finished.

I tried to download ISO image file couple of times and everytime I export the WIM file from install.esd, I'm always getting the same error. I already reinstall MDT 2013 and install the MDT update even though it's not reflected to my issue (https://support.microsoft.com/en-us/help/4564442/windows-10-deployments-fail-with-microsoft-deployment-toolkit)

Did anybody experience the same issue?
Any advice what would be my next steps.

Microsoft Deployment Toolkit
Microsoft Deployment Toolkit
A collection of Microsoft tools and documentation for automating desktop and server deployment. Previously known as Microsoft Solution Accelerator for Business Desktop Deployment (BDD).
827 questions
Windows 10 Setup
Windows 10 Setup
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
1,901 questions
0 comments
Accepted answer
  1. Simon Ren-MSFT 30,031 Reputation points Microsoft Vendor
    2021-01-22T07:59:52.997+00:00

    Hi,

    Thank you very much for your feedback and sharing. We're glad that the question is solved now. It may help others who have similar issue.

    Based on my experience, it may be that the maximum option in the /Compress argument provides the best compression, but takes more time to capture the image. Recently in all distributions of Windows 8.1, Windows 10, instead of the install.wim file, install.esd is located. The file size with the esd extension is smaller, because it is compressed more strongly (a new type of compression is used). This compression type packs the Windows installation files even more and, as a result, the size of the install.esd file becomes less than the install.wim file by 30%. So we should specify the /compress:max in the dism.exe command.

    Similar thread for your reference:
    How to Extract Install.ESD to Install.WIM (Windows 10/8)
    Please note: The links are not from Microsoft, just for your reference. Thanks for your time.

    Best regards,
    Simon

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Branko Uzelac 21 Reputation points
    2021-01-21T14:56:45.563+00:00

    Okay, don't know why but this command option (bold and italic) for DISM export-image command have resolved my issue:

    D:\win10\sources>dism.exe /export-image /sourceimagefile:install.esd /sourceindex:6 /destinationimagefile:install.wim /compress:max

    I have never used this option before, but if somebody have the same issue, try with approach as I did