Since Microsoft don't officially support Windows 11 Deployments with MDT, nor supporting any Windows ADK version newer than Windows ADK for Windows 10, version 1809 (build 17763), it's up to the OSD community to make it work. On the good side, with millions of MDT downloads during the years, you're not exactly alone 🙂
NOTE: Build 26100 (24H2 ADK) does work with MDT, with the workarounds listed in this post, but has known PowerShell and servicing bugs. For now, I recommend sticking with ADK 22H2 build 22621.
Food for thought
As of this writing, the by Microsoft only supported deployment solution for Windows 11 is ConfigMgr, but if you don't mind a few tweaks, you can absolutely make MDT work for Windows 11, and even use the latest Windows ADK (Windows ADK for Windows 11 24H2). .
Fun fact: You can deploy Windows 11 just fine with an older ADK version too, but you will find that the native driver and chipset support is not the best. I recommending using at least Windows ADK for Windows 11 22H2 (Build 22621).
Issue #1 – WinPE x86 is Missing
The fact that Microsoft no longer includes the 32-bit (x86) version of WinPE is not exactly new, it was removed already in Windows ADK for Windows 11 22H2 (Build 22621), but MDT expects to find an x86WinPE_OCs folder structure in the Windows ADK installation folder. If MDT can't find that, the console crashes with an exception:
System.IO.DirectoryNotFoundException. Could not find a part of the path 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs'.
Solution: Create an empty x86\WinPE_OCs folder structure in the Windows ADK folder. MDT don't care about the content; it just looks for the folder 🙂 Here is a PowerShell snippet.
$OCx86Path = "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs"
New-Item -Path $OCx86Path -ItemType Directory -Force
Issue #2 – Generating Catalog Files will Fail
If you try generating a catalog for a WIM image using the latest Windows ADK, MDT will crash with this lovely error message:
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.ComponentStudio.ComponentPlatformInterface, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
This is due to the fact that the latest Windows ADK is the first version to include architecture specific versions of Windows System Image Manager (WSIM). Earlier versions only had x86 versions.
Solution: Edit the C:\Program Files\Microsoft Deployment Toolkit\Bin\DeploymentTools.xml file and provide the %RealPlatform% value for the imgmgr.exe tool. Thank you L. Ozon for providing this elegant workaround. Below is what the edited line should look like:
<tool name="imgmgr.exe">%ADKPath%\Deployment Tools\WSIM\%RealPlatform%</tool>
I've been tasked with updating a new environment to generate Windows 11 25H2 gold images; but I'm running into an issue during the sysprep phase that I've not seen on our older versions of Windows 11. I've also been unable to find out anything about this error on google either. I'm seeing sysprep fail with the following lines in the setupact.log file SYSPRP GeneralizeForImaging called for WaaSMedic SYSPRP GeneralizeForImaging called for WaaSMedic cv=h71KqkdooEuJsOL4.0 SYSPRP GeneralizeForImaging called for WaaSMedic failed to create WaaSRemediationAgent hr=0x80070422[gle=0x00000057] The setuperr.log file contains 4 lines of BCD errors and the WaasMedic one. I suspect this is… Read more »
I have not seen this issue when Internet access is blocked for the VM used for build and capture. So, try that. See this post: https://www.deploymentresearch.com/block-internet-access-to-a-hyper-v-vm/
Can I please have the mdt 8456? Is not available anymore to download.
You can still find MDT on the wayback machine (Internet archive), https://web.archive.org/web/20240315155222/https://download.microsoft.com/download/3/3/9/339BE62D-B4B8-4956-B58D-73C4685FC492/MicrosoftDeploymentToolkit_x64.msi
Thank you very much!
Hm, are you sure the link works? All i get is error 503.
Worked for me just now (January 29,2026)
LTI deployment issue with windows recovery. When deploying an edition of windows (pro, home, enterprise, etc.) from install.wim, it uses the winre.wim file for the specific edition, which doesn't include any drivers for the hardware (or virtualization platform, especially if you're using a different virtualization platform). What that means is that due to missing drivers, Windows Recovery may not be able to access the various devices due to missing drivers. The solution is: Determine the index for the specific edition in install.wim that will be deployed, and mount it In the mount folder, locate "Windows\System32\Recovery\Winre.wim" and mount it to another… Read more »
I keep getting this. Boot into pxe, the wizard starts and as it looks like its applying custom settings, it throws out the same erroe each time. I'm using the latest adk, mdt, win pe. I am testung with an hp zbook fury 16 g9 laptop but have a fee varieties of zbooks (not yet tested). I found the latest driverpack and imported into mdt and regenerated the boot image. I restarted wds, i removed boot image and reloaded, just keep getting this. It will not move past this. Please help. I'm pulling my hair out in frustration.
Try using drvload.exe with the driver, and then run wpeinit.exe… Good for verifying the right driver is added.
Having updated to Windows ADK 24H2 (Build 26100) and matching PE Components to deply Windows 11 24H2, the task sequence works but we get a warning with the message: Unable to locate the Results.xml file needed to determine the deployment results. (This may be the result of mismatched script versions. Ensure all boot images have been updated.) I've deleted and regenerated boot images and made sure WDS is using them. I don't seem to be able to find much, if anything, on the internet with people experiencing this issue. The file it looks for appears to be in the c:\windows\temp… Read more »
Sorry, nothing that rings a bell
Sadly this fix doesn't work anymore with the latest current version. You get the same message but this fix doesn't work anymore.
Sorry for the very late reply…. I've been successful with Windows ADK 24H2, are you still seeing this issue?
This is what worked for me in version ADK 10.1.26100.2454 (December 2024). I added the following to the DeploymentTools.xml <tool name="imgmgr.exe">%ADKPath%\Deployment Tools\WSIM\amd64</tool> <tool name="imagecat.exe">%ADKPath%\Deployment Tools\WSIM\amd64</tool> Full XML <?xml version="1.0" encoding="utf-8" ?> <Kits> <ADK> <tool name="bcdboot.exe">%ADKPath%\Deployment Tools\%RealPlatform%\BCDBoot</tool> <tool name="bcdedit.exe">%ADKPath%\Deployment Tools\%RealPlatform%\BCDBoot</tool> <tool name="bootsect.exe">%ADKPath%\Deployment Tools\%RealPlatform%\BCDBoot</tool> <tool name="dism.exe">%ADKPath%\Deployment Tools\%RealPlatform%\DISM</tool> <tool name="imagex.exe">%ADKPath%\Deployment Tools\%RealPlatform%\DISM</tool> <tool name="wimgapi.dll">%ADKPath%\Deployment Tools\%RealPlatform%\DISM</tool> <tool name="wimgapi.dll.mui">%ADKPath%\Deployment Tools\%RealPlatform%\DISM\en-us</tool> <tool name="oscdimg.exe">%ADKPath%\Deployment Tools\%RealPlatform%\OSCDIMG</tool> <tool name="wdsmcast.exe">%ADKPath%\Deployment Tools\%RealPlatform%\WDSMCast</tool> <tool name="wdsmcast.exe.mui">%ADKPath%\Deployment Tools\%RealPlatform%\WDSMCast\en-us</tool> <tool name="winpe.wim">%ADKPath%\Windows Preinstallation Environment\%RealPlatform%\en-us</tool> <tool name="imgmgr.exe">%ADKPath%\Deployment Tools\WSIM\amd64</tool> <tool name="imagecat.exe">%ADKPath%\Deployment Tools\WSIM</tool> <tool name="imagecat.exe">%ADKPath%\Deployment Tools\WSIM\amd64</tool> <tool name="scanstate.exe">%ADKPath%\User State Migration Tool\%RealPlatform%</tool> <tool name="loadstate.exe">%ADKPath%\User State Migration Tool\%RealPlatform%</tool> <tool name="bootmgr">%ADKPath%\Windows Preinstallation Environment\%RealPlatform%\Media</tool> <tool name="etfsboot.com">%ADKPath%\Deployment Tools\%RealPlatform%\OSCDIMG</tool> <tool name="efisys.bin">%ADKPath%\Deployment Tools\%RealPlatform%\OSCDIMG</tool> <tool name="efisys_noprompt.bin">%ADKPath%\Deployment Tools\%RealPlatform%\OSCDIMG</tool> </ADK>… Read more »
I have a problem deploying the image as shown in the picture. I am not sure what went wrong. Please help me.
I'll need a bit more information to help with that.
– If you press F8, does the machine have an IP address?
– What version of Windows ADK are you using?
– Can you reproduce the issue in a virtual machine?
– If you press F8, does the machine have an IP address?
Yes, i check cmd: ipconfig /all and i have ip.
– What version of Windows ADK are you using?
ADK 10.1.26100.2454
ADK WinPE 10.1.26100.24.54
MDT 6.3.8456.1000
– Can you reproduce the issue in a virtual machine?
I can fix on production.
I use windows 11 Pro 24H2
Might be worth trying an older, and more tested, ADK like the 22H2 version.
Thanks for all of the detailed guides. Ive just started working with 24H2, and with the new ADK and MDT. I've noticed the LiteTouch boot image (without drivers) is over 600mb in size, and thus exceeding the 500MB boot device and crashes the whole sequence. Any ideas how to resolve the LiteTouch file size?
There is no 500 MB limit that I'm aware of… we have customers with MDT boot images in the 700-800 MB range using it for all sorts of hardware. I've ever only seen an issue like that when deploying a VM that is configured for dynamic memory (don't). What errors are you seeing?
It appears you are correct. I was reviewing logs and it appeared the Lite Touch boot device was failing. I ended up finding that even though BitLocker was turned off, that there's a second setting for drive encryption that has to be turned off as well. Once that was turned off, all went well.
Should say I added a command to run ltiboostrap in a step, but it doesn't autologin to even get to that.
ADK 10.1.26100.2454, w24h2, able to build image. when deploying it stalls after OS deploy, before StateRestore. Sticks me on admin login page, if i login, I can run the LTIBootStrap.vbs file that is sitting in C root, image installs everything remaining, joins domain and ends on login screen, ready for use. Can't figure why it's stalling, any help would be appreciated. I can't seem to remedy getting past it stalling. Have plenty of auto logins, drivers are updated. I ran into this with the previous adk 10.18362.1 so thought updating adk would fix. Nope.
Only thing that comes to mind is a GPO that breaks the process.
I looked deeper and it was the wim. Had some lingering provisioned apps. I removed from wim, re-sysprepped and worked.
Thx
I am experiencing the same issue. Can you tell me the provisioned Apps that were removed.