You probably noticed that Microsoft release a new version of Windows ADK for Windows 11 last month (May 2022), the 22H2 version. One major change in this version compared to the 21H2 version of the kit is that x86 boot images are no longer included. In this post you learn about what this means for ConfigMgr and MDT Lite Touch environments.
Update August 16, 2022: ConfigMgr 2111 and later versions now officially support Windows ADK for Windows 11 22H2.
Update October 5, 2022: There is now a fix available for the MDT Lite Touch script issue. Thank you, Daniel, for bringing that to my attention. See the official docs here for a workaround: https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md
Below is the new content inside the Windows Preinstallation Environment folder:
What's new in Windows ADK for Windows 11 22H2
According to the official documentation covering the new features for the 22H2 version, Microsoft only mentions improvements for the Windows Performance Recorder (WPR) and Windows Performance Analyzer (WPA). The what's new information don't even mention the fact the x86 boot images are removed from WinPE, but there is a note about the on the Download and install the Windows ADK page.
When doing a file comparison between 21H2 and 22H2 I did notice there was a new optional component for WinPE: The winpe-hsp-driver.cab file. This seems to be support for the new Microsoft Pluton Processor. Below is a listing of the new files in 22H2 (when installing only the OSD components and WinPE):
.\assessment and deployment kit\imaging and configuration designer\x86\hwreqchk.dll
.\assessment and deployment kit\windows preinstallation environment\amd64\winpe_ocs\winpe-hsp-driver.cab
.\assessment and deployment kit\windows setup\amd64\sources\background_cli.png
.\assessment and deployment kit\windows setup\amd64\sources\hwreqchk.dll
.\assessment and deployment kit\windows setup\amd64\sources\windlp.dll
.\assessment and deployment kit\windows setup\amd64\sources\asz\arunimg.dll
.\assessment and deployment kit\windows setup\amd64\sources\asz\arunres.dll
.\assessment and deployment kit\windows setup\amd64\sources\asz\spwizres.dll
.\assessment and deployment kit\windows setup\amd64\sources\replacementmanifests\fsdepends-replacement.man
.\assessment and deployment kit\windows setup\amd64\sources\replacementmanifests\nchostagent-replacement.man
.\assessment and deployment kit\windows setup\amd64\sources\replacementmanifests\systemsettings_handlers_cortana-replacement.man
.\assessment and deployment kit\windows setup\amd64\sources\replacementmanifests\updateagent-replacement.man
.\assessment and deployment kit\windows setup\amd64\sources\svr\arunres.dll
.\assessment and deployment kit\windows setup\amd64\sources\svr\background_svr.png
.\assessment and deployment kit\windows setup\amd64\sources\svr\spwizres.dll
.\assessment and deployment kit\windows setup\arm64\sources\background_cli.png
.\assessment and deployment kit\windows setup\arm64\sources\hwreqchk.dll
.\assessment and deployment kit\windows setup\arm64\sources\windlp.dll
.\assessment and deployment kit\windows setup\arm64\sources\asz\arunimg.dll
.\assessment and deployment kit\windows setup\arm64\sources\asz\arunres.dll
.\assessment and deployment kit\windows setup\arm64\sources\asz\spwizres.dll
.\assessment and deployment kit\windows setup\arm64\sources\replacementmanifests\fsdepends-replacement.man
.\assessment and deployment kit\windows setup\arm64\sources\replacementmanifests\systemsettings_handlers_cortana-replacement.man
.\assessment and deployment kit\windows setup\arm64\sources\replacementmanifests\updateagent-replacement.man
.\assessment and deployment kit\windows setup\arm64\sources\svr\arunres.dll
.\assessment and deployment kit\windows setup\arm64\sources\svr\background_svr.png
.\assessment and deployment kit\windows setup\arm64\sources\svr\spwizres.dll
.\assessment and deployment kit\windows setup\x86\sources\background_cli.png
.\assessment and deployment kit\windows setup\x86\sources\hwreqchk.dll
.\assessment and deployment kit\windows setup\x86\sources\windlp.dll
.\assessment and deployment kit\windows setup\x86\sources\asz\arunimg.dll
.\assessment and deployment kit\windows setup\x86\sources\asz\arunres.dll
.\assessment and deployment kit\windows setup\x86\sources\asz\spwizres.dll
.\assessment and deployment kit\windows setup\x86\sources\replacementmanifests\fsdepends-replacement.man
.\assessment and deployment kit\windows setup\x86\sources\replacementmanifests\systemsettings_handlers_cortana-replacement.man
.\assessment and deployment kit\windows setup\x86\sources\replacementmanifests\updateagent-replacement.man
.\assessment and deployment kit\windows setup\x86\sources\svr\arunres.dll
.\assessment and deployment kit\windows setup\x86\sources\svr\background_svr.png
.\assessment and deployment kit\windows setup\x86\sources\svr\spwizres.dll
Note: Funny enough, Microsoft didn't even update the installer to reflect that x86 boot images (including the 32-bit ARM boot image) are no longer installed. See below screenshot.
ConfigMgr Support
First of all, ConfigMgr 2111 now supports the 22H2 version of Windows ADK for Windows 11. If you upgrade Windows ADK to this version in your ConfigMgr environment, ConfigMgr won't be able to reload or update the x86 boot image anymore. Not the end of the world if you don't need it, but still.
The official docs: Support for the Windows ADK in Configuration Manager.
Note: Upgrading to Windows ADK to 22H2 technically works for an existing ConfigMgr setup, even though it obviously won't be able to upgrade the x86 version of the boot image.
MDT Lite Touch Support
Like ConfigMgr 2203, MDT Lite Touch does not have official support for the new ADK either. In fact, MDT, which has not been updated since 2020, don't even have official support for anything Windows 11, even though it happens to work just fine.
In my testing the x64 22H2 boot image does not seems to work with MDT Lite Touch, even if following the instructions later in this post to prevent the Deployment Workbench from crashing. When starting an MDT Lite Touch Deployment using Windows 11 ADK 22H2 the HTA-based wizard is not very happy.
Update: A fix for the script issue is now available, see the official docs here for a workaround: https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md
If you upgrade Windows ADK to 22H2 on your MDT server, the Deployment Workbench will crash once you click on the Windows PE tab in the deployment share properties. To prevent that from happening, simply copy in the x86 boot image structure from an earlier version of the ADK to the install folder.
I think I've found a solution. When I installed the ADK for Windows 11 22H2 with the WinPE add-on for Windows 11 2004, I did not get the script errors in the task sequence. Hope this helps.
I have a stupid question but I'm wondering why I don't find any clue.
How about the Windows 11 ADK compatibility with Windows 10 deployment?
Context : MECM 2207 and no need for Windows PE x86 anymore.
There is the good old Windows 10 ADK 2004, but what is the best choice when deploying both Windows 10 and Windows 11 ?
Windows ADK for Windows 11 21H2 and Windows ADK for Windows 11 22H2 are both supported to deploy Windows 10 and Windows 11. Most of our customers are currently Windows ADK for Windows 11 21H2 for their Windows 10 deployments. That being said, good old Windows ADK 2004 will happily deploy Windows 10 and Windows 11 as well. Microsoft just doesn't list that as being supported.
The javascript error can be fixed by editing the WinPE unattend xml and adding a synchronous command to update a registry value as seen here: https://github.com/MicrosoftDocs/memdocs/blob/main/memdocs/configmgr/mdt/known-issues.md
Thanks for the update! I'll update the post.
Ok, I fixed it myself – uninstalled the ADK, installed an older one, created the x86 boot image and then reinstalled the Windows 11 ADK…
Hi Johan,
I was just wondering if you (or anyone else) has installed a new CM Server with the latest ADK.
As you note, in this case there is no X86 boot image – normally not such a problem since we don't really need it…
Except when setting up a PXE server – without the x86 boot image, PXE boot does not work.
Is there any known workaround?
tnx,
Nick
I got PXE to work via the native responder, but it's easier to just stick to Windows ADK for Windows 11 21H2 for now. Well tested, and works fine when deploying both Windows 10 22H2 and Windows 11 22H2.
I can't fix the Windows PE tab crash on the latest kit version. I guess my copy of x86 from the Windows 10 version isn't old enough? I tried copying it over but no dice. Tried making empty x86 folder. Tried turning off x86 etc.
I see this error often on Google but no official Microsoft solution.
Feel I have no choice but to start all over from scratch again but I don't feel confident that anything will be different.
You can add a x86 boot image structure from an earlier version of the ADK, and MDT will be happy. For now I recommend staying away from ADK 22H2 in MDT Lite Touch.
@Johan: did you know that Microsoft is deprecating use of boot.wim from WDS?
https://docs.microsoft.com/en-us/windows/deployment/wds-boot-support
Hi Joshua,
The article is a bit misleading, it's the support for running setup.exe from a boot image with is being deprecated. Something you should never do anyway. Support for normal boot image use (MDT/ConfigMgr, custom OSD) is still in there.
/ Johan
ADK 10.0.22621.1. still has the issue of the Dot3Svc not starting. It says
> net start dot3svc
The Wired Autoconfig Service could not be started.
More help is available by typing NET HELPMSG 3523.
> net helmpsg 3523
The *** service could not be started.
> netsh lan show interfaces
The following helper DLL cannot be loaded: DOT3CFG.DLL
The following command was not found: lan show interfaces.
Any fix for this yet?
Hi Mike,
Not that I know of. Would recommend filing a support case with Microsoft on this (and please reply back here when it's solved)
Johan,
It's a bug. Here is what I had to do to get it working again.
802.1X is not working properly with Windows 11 ADK – OSCC
Hi Mike, thanks for the update. Much appreciated.
I'm still getting the script error when the deployment wizard loads. Anybody find a fix for this? I can ignore the error and continue as usual however…
Hi Tony,
Unfortunately no, not yet at least. I recommend staying away from Windows 11 ADK 22H2 for now.
I'll definitely stay away from W11ADK 22H2. Thanks!!
I ran into both of the above issues with MDT this week. I was drawn to 22H2 PE because the old 2004 PE build doesn't seem to support AMD's 6000 series USB4 controller…at least I was unable to get it working with any of HP's or AMD's provided chipset drivers. 22H2 works, but has the issues above. What I found is script error during the workflow can be ignored, it seems to only effect the workflow UI, fonts look odd, error messages can't be shown, but the workflow will complete if you close the error. The MMC error message can… Read more »
Thanks for the info. Windows ADK for Windows 11 21H1 should have the same hardware support. So maybe use that one until Microsoft fixes the HTA component in 22H2.
ADK 22H2 HTA fix for MDT
https://learn.microsoft.com/en-us/mem/configmgr/mdt/known-issues
I found myself on vacation and going through my LinkedIn list and clicking on one of your posts as I am wont to do. But, like a bag of Jay's Potato chips, you can't eat just one. So I noticed the previous and next post buttons and proceeded to binge. I realized that not all articles were relevant to my interests (most were). It would have been nice to have the previous and next post buttons on the top so that I could skip back to past articles I may have missed and not have to scroll to the bottom… Read more »
Hi John,
It's a good idea, but I couldn't find a setting for having the previous/next buttons show up on the top of the page. Myself I usually search (even my own blog).
Do you think there will be any future for MDT? Probably not….,right?
I don't know at this point.
I think eventually CM/AutoPilot (provisioning) will take its place.
there is also a problem when importing windows 10 22h2 to deploymentshare
mdt recognize it as windows 10 unknown and there is an error when trying to create task sequence with this version of windows.
Thanks for the update!