W10UI should be taking care of it for you, but this can happen if setup.exe and setuphost.exe in the <iso>\sources directory do not match versions correctly. In previous versions of Windows you apply the SDU .cab file to the ISO and then had to copy setup.exe from the boot.wim back to the <iso>\sources directory. 24H2 added new requirement of also copying setuphost.exe from boot.wim as well.
Vbox doesn't want to run 24H2, i still can't t install 26100.xxxx on it. Lemme test on the latest version. EDIT: still the same, i somewhere on their forum read they consider 24H2 IP and block it, should soon be unblocked i guess.
I've managed to install 24H2 26100.1742 ISO on Vbox 7.0.20 using default settings. This is on a i7 8550u Laptop with 16GB RAM
It has been this way since a long time, i just use VMWare, vbox is just for x86 tests which vmware refuses to run
Me too i managed to install 26100.1742 without any problems on VB 7.1.2. Only with the last iso's test 26100.2033 i build yesterday... it refuse it
Could it be something with newer features like SecureBoot or TPM? Maybe VB still only supports the old SecureBoot signature. I have no problems booting a 26100.1 ISO in EFI mode, under VB 5.2.45. Edit: Complete.
So i have the same problem when i use the mvs LTSC 26100.1742 (fr-FR) version as a base to build the LTSC 26100.2033 (fr-FR) and i tested it on vmware 17.5.2 this time (see image) i think 26100.1742 can not be used as base (i've not tested with 26100.1 OEM)
i use these updates: ..\26100_Updates_x64\defender-dism-x64-241004.cab ..\26100_Updates_x64\windows11.0-kb5043080-x64_LCU_1742.1.10.msu ..\26100_Updates_x64\windows11.0-kb5043939-x64_PSFX_OOBE_1588.1.1.msu ..\26100_Updates_x64\windows11.0-kb5044030-x64-ndp481_CU_9277.2.msu ..\26100_Updates_x64\windows11.0-kb5044284-x64_LCU_2033.1.20.msu ..\26100_Updates_x64\windows11.0-kb5044612-x64_DUSafeOS_2003.1.1.cab ..\26100_Updates_x64\windows11.0-kb5045520-x64_DUSources_2033.cab my config W10UI 10.47: set "Target=%~dp0_WorkDir" :: updates location :: leave it blank to automatically detect the current script directory set "Repo=%~dp026100_Updates_x64" :: dism.exe tool custom path (if Host OS is Win8.1 or earlier and no Win10 ADK installed) set "DismRoot=dism.exe" :: enable .NET 3.5 feature set Net35=1 :: optional, custom "folder" path for microsoft-windows-netfx3-ondemand-package.cab set "Net35Source=%~dp0_WorkDir\sources\sxs\" :: Cleanup OS images to "compress" superseded components (might take long time to complete) set Cleanup=1 :: Rebase OS images to "remove" superseded components (warning: break "Reset this PC" feature) :: require first to set Cleanup=1 set ResetBase=1 :: update winre.wim if detected inside install.wim set WinRE=1 :: Force updating winre.wim with Cumulative Update regardless if SafeOS update detected :: auto enabled for builds 22000-26050, change to 2 to disable :: ignored and auto disabled for builds 26052 and later set LCUwinre=0 :: Expand Cumulative Update and install from loose files via update.mum :: applicable only for builds 26052 and later set LCUmsuExpand=0 :: update ISO boot files bootmgr/memtest/efisys.bin from Cumulative Update set UpdtBootFiles=1 :: 1 = do not install EdgeChromium with Enablement Package or Cumulative Update :: 2 = alternative workaround to avoid EdgeChromium with Cumulative Update only set SkipEdge=0 :: do not install Edge WebView with Cumulative Update set SkipWebView=0 PS the W10UI log produce no errors (i check each time)
Homebrew boot.wim 26100.1 from UUP dump works fine with the latest updates, so this is the workaround Something is wrong with setup.exe, maybe it's newer in msft iso
I did select to update the bootfiles, will test without updating them, andy managed to get it running on the latest vbox it seems.