This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
It does work without any changes if you have been deploying 20H2. Built, captured, and applied with success! You do need the UEFi fix and mdt hotfix for 8456!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 77%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Do you have a link to the required fixes for the UEFI issue?
I found the MDT hotfix...
Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 99%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Are you upgrading your VM to 21H1, and if so, are any of those nasty apps causing any sysprep issues like I'm having from 1703 to 20H2?
Hi, @snork13
Thank you for posting in Microsoft Q&A forum.
Are you testing the 21H1 with MDT and achieve success? congratulations!
And thank you for sharing your experience here.
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 69%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Are you testing without UEFi fix with only hotfix?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 51%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Has anybody had an issue importing Windows 10 21H1 into MDT from the ISO ? I did already convert the .esd to .wim format but I still am not able to do it. MDT version 6.3.8456.1000 and Windows ADK 10.1.19041.1. I exported only Windows 10 Pro index which was 6. When I try to import it into MDT I get "unable to get information for Wim file.
Maybe not related, but just to let things do what they're meant to do, I import the whole ISO and then delete all of the editions except the enterprise one. Takes a whole 2 mins.
How do you import an ISO? You will have to convert .esd to .wim format anyway, otherwise MDT will not recognize it. ISO comes with install.esd file. I have converted the .esd to .wim and I get the error on the import of "Full set of source files" when I try to import the OS. I used the 2009 ADK co convert the .esd file just FYI.
Ok. I should have spelled out... use 7zip to extract the ISO and then import from the extracted folder, the outer folder. It gives me all the editions but I remove the ones I don't want and I've never had an issue this way.
Finally figured it out. For some odd reason I did not use the /compress:max when exporting .esd to .wim. Once I used the /compress:max I was able to import the OS. Thanks for all your comments anyway.