PENDING Unable To Capture Windows 11 Using Endpoint Config Manager Capture Media ISO

[KMiller]

I just downloaded Windows 11 yesterday. I built a test Virtual Machine in Hyper-V, put it into "Audit Mode" and made a few customizations. I decided I wanted to capture it and test deployment using EndPoint Configuration Manager.

I downloaded the latest Windows 11 ADK and ADK WinPE Add-On, removed my previous version, rebooted, and installed both ADK and the WinPE Add-On. I rebooted again, went to my Boot images, and updated them successfully. I opened my Endpoint Configuration Manager (showing as version 2107), and navigated to Software Library > Operating Systems > Task Sequences > right-clicked and selected "Create Task Sequence Media". I selected capture media, and created the capture media ISO.

I attached that .ISO to my newly created VM opened the D: drive, and clicked "Launch Media" and immediately received the following error message: "The code execution cannot proceed because VCRUNTIME140_1.dll was not found. Reinstalling the program may fix this problem".

I thought to myself that maybe one of my customizations caused this, so I started over, and just built a fresh Windows 11 Virtual Machine and made zero changes to it. Attached the capture media.iso to it, and attempted to click "Launch Media" again, and received the same error message

A simple search on this reveals the necessity to install Visual C++ Runtime 2015, 2017, 2019, 2022 in both x86 and x64 versions, or copy VCRUNTIME140_1.dll from a working machine to C:\Windows\System32. I opted to install the Visual C++ Runtime libraries, and viola, I was able to click "Launch Media" and begin entering the settings to start my capture process (initiating a sysprep).

I have attached screenshots as well.

Once the sysprep completed, the machine rebooted as expected, and launched into a Windows PreBoot (PE) environment. I saw the status window for "initializing hardware devices" and after a few seconds it failed. I then receive a message saying "Unable to read task sequence configuration disk. For more information, contact your system administrator or helpdesk operator."

 

[hat08]

I'm running into the same issue when trying to capture a Server 2022 image. I've tried both the vmxnet3 and e1000e NICs. Loading winPE from boot media using the same boot image as the capture media works.

SMSTS.log error:
ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM' (0x80070490). Retrying (28)... TSBootShell 2/1/2022 8:44:07 AM 680 (0x02A8)
Volume '\\?\Volume{5ad92ad4-e2b4-48cf-986a-df5e1a3b5a1d}\' not found TSBootShell 2/1/2022 8:44:09 AM 680 (0x02A8)
GetVolumePathForVolumeName(szDeviceVolumeId, rsWin32Path), HRESULT=80070490 (X:\bt\1026714\repo\src\Framework\TSCore\devicepath.cpp,167) TSBootShell 2/1/2022 8:44:09 AM 680 (0x02A8)
DevicePath:eviceNamespaceWin32Path(sDevicePath, rsWin32Path), HRESULT=80070490 (X:\bt\1026714\repo\src\Framework\TSCore\devicepath.cpp,120) TSBootShell 2/1/2022 8:44:09 AM 680 (0x02A8)
DevicePath::ArcToWin32Path(pszBootPath, rsLogicalPath), HRESULT=80070490 (X:\bt\1026714\repo\src\Framework\TSCore\bootsystem.cpp,117) TSBootShell 2/1/2022 8:44:09 AM 680 (0x02A8)
ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM' (0x80070490). Retrying (29)... TSBootShell 2/1/2022 8:44:09 AM 680 (0x02A8)
bGotPath, HRESULT=80070490 (X:\bt\1026714\repo\src\client\TaskSequence\BootShell\configpath.cpp,42) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
ConvertBootToLogicalPath failed after retries. Giving up. TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
GetConfigPathFixedDisk(sArcPath, sWinPEFolder), HRESULT=80070490 (X:\bt\1026714\repo\src\client\TaskSequence\BootShell\configpath.cpp,346) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
Failed to find the current TS configuration path TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
ConfigPath::FindConfigPath(sConfigPath), HRESULT=80070490 (X:\bt\1026714\repo\src\client\TaskSequence\BootShell\bootshell.cpp,654) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
Failed to find the configuration path.
Element not found. (Error: 80070490; Source: Windows) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
Execution failed with error 80070490. TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
hMap != 0, HRESULT=80070002 (X:\bt\1026714\repo\src\Framework\TSCore\environmentscope.cpp,495) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
m_pGlobalScope->open(), HRESULT=80070002 (X:\bt\1026714\repo\src\Framework\TSCore\environmentlib.cpp,335) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
this->open(), HRESULT=80070002 (X:\bt\1026714\repo\src\Framework\TSCore\environmentlib.cpp,561) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (X:\bt\1026714\repo\src\Framework\TSCore\utils.cpp,905) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
GetTsRegValue() is unsuccessful. 0x80070002. TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
End program: TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
Finalizing logging from process 360 TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
Finalizing logs to root of first available drive TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
Successfully finalized logs to X:\SMSTSLog TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
Cleaning up task sequencing logging configuration. TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
TS::Environment::SharedEnvironment.isInitialized() == true, HRESULT=80004005 (X:\bt\1026714\repo\src\Framework\TSCore\tslogging.cpp,694) TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)
TS environment is not initialized TSBootShell 2/1/2022 8:44:11 AM 680 (0x02A8)

 

[hat08]

I also tried building a fresh boot image using WinPE 10.0.22000.1, adding only the vmware vmxnet3 and PVSCSI drivers to it and have the same issue with WinPE not properly initializing hardware.

 

[hat08]

I managed to find a workaround for this. If you build your reference PC using BIOs instead of EFI, it works to capture the image.

 

[Saqib]

I managed to find a workaround for this. If you build your reference PC using BIOs instead of EFI, it works to capture the image.

How do you do it in Hyper-V? Hyper-V let you choose between Gen-1 and Gen-2 when BIOS is offered in Gen-1 and off course it will not have Secure Boot and it does not offer TPM too which are pre requisites for installing Windows 11. I tried installing Windows 11 on Hyper-V Gen-1 VM and got this error.