Windows 11 Deployment – Using MDT 8456 with Windows ADK 23H2 (Build 25398)

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 🙂

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 23H2). In general, I don't recommend using the latest ADK due to the fact it's built on Windows, Server 23H2 instead of Windows 11, but sure, if you absolutely want to, you can.

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 – VBScript is Broken

While VBScript is announced to be deprecated it's going to be around for a good while longer. You'll be surprised how many scripts, and installers using it. VBScript was not removed from the latest ADK, Microsoft accidentally broke it, and issued a fix for that quite quickly. Here is a post on how to fix VBScript in the latest ADK: https://www.deploymentresearch.com/fixing-vbscript-support-in-windows-adk-sep-2023-update-build-25398

Issue #2 – 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 x86\WinPE_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 🙂

Creating the empty x86\WinPE_OCs folder structure.

Issue #3 – 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: Copy the x64 (amd64) WSIM files to the C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\WSIM folder.

WSIM Files from the amd64 folder copied on level up.
About the author

Johan Arwidmark

5 1 vote
Article Rating
Subscribe
Notify of
guest
3 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Ahmed
Ahmed
26 days ago

Thanks Johan for sharing the informative article,

I have a question regarding your recommendations about using at least Windows ADK for Windows 11 22H2 (Build 22621), does this version support DART integration tool, also does it will work fine for deploying Windows 11 23H2 and Windows 10 22h2?

Thanks,

Petri
Petri
30 days ago

Got the same and googled a bit and found this article. This made Catalog to work


>