The Windows 10 Enterprise LTSB 1607 boot process appears to be limited to EnterpriseS (Enterprise LTSB) editions, but that doesn't necessarily mean it has to be 21h2. It was just used to bypass the error. You can use other types of ISOs and replace the install.wim file with the one you created. Windows 10 Home 1607, or versions like 1703+, might work.
So I have to copy the boot from the home version 1607, put it in the enterprise folder, and create an ISO? Or do I have to copy the modified install.wim to the home folder and create an ISO? I'm confused.
Copy the install.wim file to the Windows 10 Home 1607 ISO folder. You don't need to copy boot.wim. Basically: install.wim -> copy to -> Windows 10 Home 1607 folder where the ISO was extracted -> Create ISO
Can this version be activated and updated with the latest December patches? Is it the same if I use the Pro version?
as for "windows setup could not configure windows to run on this computer's hardware" error with constructed images when apply-image in hyperv in logs: <z:row Cls="D" Sev="33554432" Maj="Def" Min="Def" LN="249" Fil="" Fun="SysprepSession::Execute" Uid="34537472" Msg="SysprepSession::Execute: Win32 error (126), could not execute actions" PID="2536" TID="2540" Con="" Exe="C:\Windows\system32\oobe\setup.exe" Mod="WinSetup.dll" Err="0" MD="" DT="2026-01-18T08:28:08"/> Image was generalized, but setupcl did not complete successfully." PID="2536" TID="2540" Con="" Exe="C:\Windows\system32\oobe\setup.exe" Mod="WinSetup.dll" Err="2" MD="" DT="2026-01-18T08:28:08"/>
constructed 28000.1 enterpriseg by MUCS (installed by apply image in hyperv; without gailium119's wcp.dll)
reconstruction - 1 to 1 construction - 0 to 1 you can construct with explodesxs, but you will learn to construct with stagesxs