Windows ADK PreInstallation Environment broken in 20221

%3CLINGO-SUB%20id%3D%22lingo-sub-1714541%22%20slang%3D%22en-US%22%3EWindows%20ADK%20PreInstallation%20Environment%20broken%20in%2020221%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1714541%22%20slang%3D%22en-US%22%3E%3CP%3EIn%26nbsp%3BWindows%20ADK%20PreInstallation%20Environment%20broken%2020221%20some%20components%20are%20broken%2C%20e.g.%26nbsp%3BWinPE-StorageWMI-Package.%20Adding%20the%202%20required%20components%20installs%20without%20error%20when%20building%20a%20custome%20wim.%20However%20the%20module%20of%20Storage%20is%20not%20available%20in%20the%20resultant%20wim.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1740704%22%20slang%3D%22en-US%22%3ERE%3A%20Windows%20ADK%20PreInstallation%20Environment%20broken%20in%2020221%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1740704%22%20slang%3D%22en-US%22%3EThis%20is%20still%20apparent%20in%2020226%20WinPE.%20I%20did%20some%20more%20testing%20and%20it%20looks%20like%20the%20the%20WMIStorage%20module%20is%20not%20properly%20signed%20as%20trying%20to%20import%20the%20module%20results%20in%3A%20Strong%20name%20validation%20failed.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

In Windows ADK PreInstallation Environment broken 20221 some components are broken, e.g. WinPE-StorageWMI-Package. Adding the 2 required components installs without error when building a custome wim. However the module of Storage is not available in the resultant wim.

3 Replies
Highlighted
This is still apparent in 20226 WinPE. I did some more testing and it looks like the the WMIStorage module is not properly signed as trying to import the module results in: Strong name validation failed.
Highlighted
I found a workaround to enable the import of Storage module to load: Adding a DWORD set to 0 for AllowStrongNameBypass in the following registry keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework Assumes a 64 bit WinPE So issue is related to signing of the Powershell Storage module in WinPE or a component it depends on.
Highlighted

This actually turned out to need the key below not the values I mentioned in the previous post.

HKLM\Software\Microsoft\StrongName\Verification\*,*