A new Windows 11 22H2 release of the ADK appeared a couple of days ago, and it didn’t take long for some to notice an issue with it:

It turns out that the VBScript.dll just isn’t there. It could probably be added back (ideally from a matching Windows 11 build 25398 media) and re-registered, but that’s kind of challenging to do, so in the meantime if you are using something that needs VBScript in Windows PE (e.g. MDT), you might want to stick with the older release of the ADK.

If you happen to be using Tanium Provision, we use PowerShell for almost everything, but had one VBScript that was used in Windows PE to find and launch our PowerShell script. That obviously broke too. Contact your TAM to get an updated Windows PE generation script (ADKPrep.ps1) that addresses this by eliminating the VBScript and using only PowerShell.

We’ll see if this was done on purpose or not — likely related to the work going on to make VBScript an optional feature. There’s always a chance Microsoft will address this with another updated release.