same here, if i copy from .1466 \boot \efi \sources\boot.wim \sources\install.wim \bootmgr \bootmgr.efi onto buid .1 iso UEFI boot ok in VmWare. perhaps W10UI.cmd bug ? edit: W10ui with DU Updates excluded , same problem , no uefi boot
can confirm... win10 .1466 and win11 .434 (from uupdump) will not boot in vmware or ventoy on real hardware. Win11 22533 no problems. boots in vmware and ventoy on real hardware win10 .1466 and win11 .434 some efi files got other hash as on older builds. but a replace from old one to new iso does not solve the problem. win10 .1466 and win11 .434 boot/install.wim into .1415 or .376 does boot but does not find any harddisk. so for me it is only working: win10 .1466 and win11 .434 install.wim into .1415 or .376 and it boots and can be installed
The UEFI boot problem with the ISO is caused by the ~ \ efi \ microsoft \ boot \ efisys.bin. After the updates have been integrated using the uup dump script, the file appears to be damaged or Microsoft has generally changed something. Without updates, it works as expected. To solve the problem, you have to recreate the ISO with efisys.bin (perhaps efisys_noprompt.bin too, if you use it) from the 1415 using cdimage.exe. Then the ISO with the 1466 will boot as expected in UEFI mode. BIOS Mode ist not affected.
this method does not work with Windows 11 if I replace efisys.bin and efisys_noprompt.bin from .376 in .434 I got the same error... ISO does not boot
@ts21796354 replaced efisys.bin from build .1415 or .1 doesn't work for me on Vmware. edit: iso need to be rewriten with cdimage with efi bootdata from efisys.bin Works with replace boot.wim + install.wim from build .1466 onto .1 iso build.
I faced the same issue yesterday, not running from ventoy, tried updating ventoy plus changing pen drive as well as tested on different machines. Ended up using Rufus to boot the latest v1466 UUPD iso.
It also works with Windows 11 (22000.434). But after replacing the files you must recreat the ISO with cdimage in order to write the older EFI bootdata in the boot sector of the DVD; Code: cdimage.exe -bootdata:2#p0,e,b"<path>\boot\etfsboot.com"#pEF,e,b"<path>\efi\Microsoft\boot\efisys.bin" -o -m -u2 -udfver102 -lCPRA_X64FRE_DE-DE_DV5 <path> d:\new.iso <path> is the location of the ISO root folder. You must replace it. I testet it with windows 11 (22000.434) and Windows 10 (19044.1466) with efisys.bin from last patch day and with revison 1. Both works finde. Alternativ you can use a tool like PowerISO and replace all files from the 1415 ISO with the files from the 1466 ISO (same with Windows 11). Since the older ISO uses the older efisys.bin for the boot sector it works fine.
I performed an integration with the Jan 2022 updates overview and the serviced image loads fine on legacy/efi virtualbox and on a real physical machine in legacy/uefi mode(asrock H61 motherboard). With the Dec 2021 updates I had an issue seeing storage drives at the partitioning step in uefi mode(legacy mode had no such issues).
w10ui like always. It always worked flawlessly and I had no issues with the iso files. Just the December updates gave me a headache. Now, on 10 21H2 at least, everything works like before.
Ye but that's the thing, I used w10ui and updated everything as before December 2021 - iso boots fine under UEFI and Legacy AND the installer sees all storage drives at partitioning step, whereas before, integrating Dec 2021 updates resulted in iso booting fine in both modes but under UEFI the installer would not see any drives. So, as of now, even without abbodi's mod for skipping updating boot files, everything works fine(for me at least).
Many reported that UEFI boot on vbox and vmware didn't work, on real systems there were mixed results, some had success using rufus but ventoy failed, these are my documented experiences: I've used the same always working FAT32 formatted USB as always for testing.
Well, for me: W10UI v10.15 + Jan 2022 updates + latest Ventoy = booting with no issues Could there be an issue with half the updates still being Nov 2021? Some mismatching going on?
We'll see when the next release preview updates are released, already announced by @abbodi1406 as said mixed results on real hardware, on vmware and vbox all couldn't boot 22000.434 ot 19044.1466 when setup as UEFI. Not updating the ISO boot files bootx64.efi and efisys.bin seems to have solved it for now. 22533.1001 doesn't show this behavior so it probably is a glitch with the .434 and .1466 set of updates.
Does anyone have the es-mx_windows_10_enterprise_ltsc_2021_x64_dvd_f6aaf384.iso es-mx_windows_10_enterprise_ltsc_2021_x86_dvd_93a5debe.iso files for download or links to download those version? The versions for Mexico