Windows ADK for Windows 11 (22H2) updated September 2023

I see that Microsoft has released the new ADK and Windows PE add-on. I don't see it specifically listed in the release notes, but I am assuming that this release likely is updated so that patching Win PE for BlackLotus will no longer be necessary. If anyone beats me to testing this I would love to hear your test results

Thanks, Brink. My apologies. I missed the posting yesterday.

Note the June 2023 signing date.

I just rebuilt the Macrium bootable Rescue Media, using the directions found here...


From the section labeled: Create New Macrium Reflect Rescue Media


I assume the Macrium media builder, downloaded the newest Windows 11 ADK.

The Macrium bootable Rescue media I just created... seems to work.

Windows Server 23H2 ADK. It's not an "updated" 11 22H2 ADK as Microsoft claims. Totally different build number, the same build number as used with Server 23H2.

I got a feeling another ADK is on it's way...
Yes, Microsoft broke VBScript in the new ADK

garlin said:

I got a feeling another ADK is on it's way...
Yes, Microsoft broke VBScript in the new ADK

Click to expand...

Could VBScript be added back like below?

WinPE features are added by mounting boot.wim and running "DISM /Add-Package" from one of the Optional Components (OC) files.

There's an existing Scripting/WinPE-Scripting package in ADK which contains Windows Scripting Host (WSH). But it's normally understood there's basic wscript/cscript support in every default WinPE image.

Forcing IT admins to switch without an official MS announcement and timetable would break countless WinPE automation setups. That's why Michael Niehaus suspects they made an error.

Update - I see that Microsoft updated the notes for the new ADK / Win PE add-on. Bottom line is that the new version is indeed fixed so that it is not susceptible to BlackLotus.

Any idea what to do with this, constantly happening (Server20348, ADK SEP23)? If not, do we know of anyone at MSFT who can support ADK?

Welcome to ElevenForum. Could you provide just a little more information?Here are a few things that I would like to know, but you can provide even more detail if you wish:

1) When you installed the ADK, what options did you choose to install?

2) At the time of the error message, what specific operation(s) are you performing and is the triggering of this error repeatable by doing the same thing every time?

3) What is the goal? In other words, what do you wish to do with the ADK.

4) Since the error is specifically a .NET error, do you have all of the latest updates for .NET installed?

5) Did you have the previous version of the ADK installed on this machine? If so, did it appear to be working properly?

NOTE: I use the ADK for one fairly narrow use, namely, the creation of unattended answer files. Because of that, I am not an ADK expert, but I'll give my best effort to see if I can assist.

hsehestedt said:

Welcome to ElevenForum. Could you provide just a little more information?Here are a few things that I would like to know, but you can provide even more detail if you wish:

1) When you installed the ADK, what options did you choose to install?

2) At the time of the error message, what specific operation(s) are you performing and is the triggering of this error repeatable by doing the same thing every time?

3) What is the goal? In other words, what do you wish to do with the ADK.

4) Since the error is specifically a .NET error, do you have all of the latest updates for .NET installed?

5) Did you have the previous version of the ADK installed on this machine? If so, did it appear to be working properly?

NOTE: I use the ADK for one fairly narrow use, namely, the creation of unattended answer files. Because of that, I am not an ADK expert, but I'll give my best effort to see if I can assist.

Click to expand...

Thank you for the reply.

Here are the answers:


1) When you installed the ADK, what options did you choose to install?
A) Dep tools, ICD, Config Designer, USMT.


2) At the time of the error message, what specific operation(s) are you performing and is the triggering of this error repeatable by doing the same thing every time?

A) Error every time, at WSIM - either select repo or create new repo


3) What is the goal? In other words, what do you wish to do with the ADK.

A) Pretty much what you are doing: built Unattends.


4) Since the error is specifically a .NET error, do you have all of the latest updates for .NET installed?

A) Both the newest 4.81 and the brand new .NET 8rc2 are installed. Problem occured even before 8 was installed


5) Did you have the previous version of the ADK installed on this machine? If so, did it appear to be working properly?

A) Kind of. The same results with 20348 Server and with Preview 25987

Thank you again!

Additional info. Here is the full .Net error message:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.ComponentStudio.Common.FatalErrorException: Exception of type 'Microsoft.ComponentStudio.Common.FatalErrorException' was thrown.
at Microsoft.ComponentStudio.Controls.OpenFolderDialog.OfnHook(IntPtr hdlg, UInt32 uiMsg, UInt32 wParam, IntPtr lParam)
at Microsoft.ComponentStudio.Controls.NativeMethods.GetOpenFileName(OFN& ofn)
at Microsoft.ComponentStudio.Controls.OpenFolderDialog.ShowDialog(IWin32Window owner)
at Microsoft.ComponentStudio.DistributionSharePickerDialog.ShowOpenDialog(IWin32Window owner)
at Microsoft.ComponentStudio.MainForm.OnFileSelectDistributionShare()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.ComponentStudio.Commands.Command.Invoke()
at Microsoft.ComponentStudio.Commands.Command.OnClick(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4645.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
ImgMgr
Assembly Version: 10.0.0.0
Win32 Version: 10.0.20348.1 (WinBuild.160101.0800)
CodeBase: file:///T:/Kits/ADK%2020348/Assessment%20and%20Deployment%20Kit/Deployment%20Tools/WSIM/imgmgr.exe
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4654.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4654.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.ComponentStudio.Controls
Assembly Version: 10.0.0.0
Win32 Version: 10.0.20348.1 (WinBuild.160101.0800)
CodeBase: file:///T:/Kits/ADK%2020348/Assessment%20and%20Deployment%20Kit/Deployment%20Tools/WSIM/Microsoft.ComponentStudio.Controls.DLL
----------------------------------------
Microsoft.ComponentStudio.Command
Assembly Version: 10.0.0.0
Win32 Version: 10.0.20348.1 (WinBuild.160101.0800)
CodeBase: file:///T:/Kits/ADK%2020348/Assessment%20and%20Deployment%20Kit/Deployment%20Tools/WSIM/Microsoft.ComponentStudio.Command.DLL
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4161.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.ComponentStudio.Common
Assembly Version: 10.0.0.0
Win32 Version: 10.0.20348.1 (WinBuild.160101.0800)
CodeBase: file:///T:/Kits/ADK%2020348/Assessment%20and%20Deployment%20Kit/Deployment%20Tools/WSIM/Microsoft.ComponentStudio.Common.DLL
----------------------------------------
Microsoft.ComponentStudio.ComponentPlatformInterface
Assembly Version: 10.0.0.0
Win32 Version: 10.0.20348.1 (WinBuild.160101.0800)
CodeBase: file:///T:/Kits/ADK%2020348/Assessment%20and%20Deployment%20Kit/Deployment%20Tools/WSIM/Microsoft.ComponentStudio.ComponentPlatformInterface.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4380.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4667.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.4161.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I updated ADK, and now X86 is no longer present : only AMD64 and ARM64 are installed.

rpo said:

I updated ADK, and now X86 is no longer present : only AMD64 and ARM64 are installed.

Click to expand...

Yep. That is expected. Did you see the notes regarding this on the page that you downloaded the ADK from?

x86 is dead. Win 10 still has an x86 version, but Win 11 has done away with it.

Thank you. But copype still allows x86 and arm. It's no longer possible to generate a WinPE for 32 bits PCs.

rpo said:

Thank you. But copype still allows x86 and arm. It's no longer possible to generate a WinPE for 32 bits PCs.

Click to expand...

My point was simply that x86 is going away, and that Microsoft notes this in the ADK notes.

malchior43 said:

Any idea what to do with this, constantly happening (Server20348, ADK SEP23)? If not, do we know of anyone at MSFT who can support ADK?

Click to expand...

Just experienced the same issue. What's funny is this is the literal only mention of it on google. And I'm on 24H2. Not awfully promising.

Edit: Welp, guess I was slightly wrong. There's also this Windows Vista post from 2009 with no replies. Which somehow makes the situation even worse lol