iVentoy stuck on new firmware

[roy]

Hi, I use iVentoy to deploy windows on some machines, but I recently experienced some issues on new firmware. When I select PXE boot in the BIOS iVentoy downloads and then gets stuck and not showing the menu. Originally I used iVentoy version 1.0.21 but also tried 1.0.25 and 1.0.26, this did not make a difference. Also a BIOS update did also not help.

I tried different BIOS settings and different boot files to no avail.
The same config and images still work on the older motherboards, and the logs from both are almost identical.

Machine boots successfully
UEFI version 2.22.189 - 2024 AMI
Motherboard: ASUS Pro WS TRX50-SAGE WIFI

Code:

2026/04/10 10:54:18.808 [TFTP] Parse tftp option(tsize,0)
2026/04/10 10:54:18.808 [TFTP] Parse tftp option(blksize,1468)
2026/04/10 10:54:18.808 [TFTP] Unsupported tftp option windowsize 4
2026/04/10 10:54:18.808 [TFTP] TFTP RRQ client x.x.x.x:1320 download <iventoy_loader_16000_uefi> start ...
2026/04/10 10:54:18.808 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snponly.efi.0
2026/04/10 10:54:18.808 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1320 with blksize 1468, has oack 1
2026/04/10 10:54:18.808 [TFTP] Recv an ERROR opcode pkt from client x.x.x.x:1320.
2026/04/10 10:54:18.919 [TFTP] Parse tftp option(blksize,1468)
2026/04/10 10:54:18.919 [TFTP] Unsupported tftp option windowsize 4
2026/04/10 10:54:18.919 [TFTP] TFTP RRQ client x.x.x.x:1321 download <iventoy_loader_16000_uefi> start ...
2026/04/10 10:54:18.919 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snponly.efi.0
2026/04/10 10:54:18.919 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1321 with blksize 1468, has oack 1
2026/04/10 10:54:18.973 [TFTP] Finished send file to x.x.x.x:1321 with blksize 1468 blks 206
2026/04/10 10:54:22.953 [HTTP] DHCP external subnet mode notify discovery client x.x.x.x ipxe/xx-xx-xx-xx-xx-xx-xx/uefi/mask:m.m.m.m/gw:g.g.g.g/dns:d.d.d.d
2026/04/10 10:54:22.953 [PXE]  Client xx-xx-xx-xx-xx-xx-xx start PXE install in UEFI X64 mode.

Machine boot fails
UEFI version 2.22.1299 - 2026 AMI
Motherboard: ASUS W880-ACE SE

Code:

2026/04/10 10:45:09.454 [TFTP] Parse tftp option(tsize,0)
2026/04/10 10:45:09.454 [TFTP] Parse tftp option(blksize,1468)
2026/04/10 10:45:09.454 [TFTP] Unsupported tftp option windowsize 4
2026/04/10 10:45:09.454 [TFTP] TFTP RRQ client x.x.x.x:1974 download <iventoy_loader_16000_uefi> start ...
2026/04/10 10:45:09.454 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snponly.efi.0
2026/04/10 10:45:09.454 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1974 with blksize 1468, has oack 1
2026/04/10 10:45:09.455 [TFTP] Recv an ERROR opcode pkt from client x.x.x.x:1974.
2026/04/10 10:45:09.764 [TFTP] Parse tftp option(blksize,1468)
2026/04/10 10:45:09.764 [TFTP] Unsupported tftp option windowsize 4
2026/04/10 10:45:09.764 [TFTP] TFTP RRQ client x.x.x.x:1975 download <iventoy_loader_16000_uefi> start ...
2026/04/10 10:45:09.764 [TFTP] DHCP ExternalNet client x.x.x.x should use loader ipxe.x64.snponly.efi.0
2026/04/10 10:45:09.764 [TFTP] Start send file iventoy_loader_16000_uefi to x.x.x.x:1975 with blksize 1468, has oack 1
2026/04/10 10:45:09.800 [TFTP] Finished send file to x.x.x.x:1975 with blksize 1468 blks 206
2026/04/10 10:45:13.858 [HTTP] DHCP external subnet mode notify discovery client x.x.x.x ipxe/xx-xx-xx-xx-xx-xx-xx/uefi/mask:m.m.m.m/gw:g.g.g.g/dns:d.d.d.d
2026/04/10 10:45:13.858 [PXE]  Client xx-xx-xx-xx-xx-xx-xx start PXE install in UEFI X64 mode.

[roy]

Doing some further research, it may have to do with the newer server using an Intel CPU instead of AMD. It seems the newer UEFi firmware does not contain a CMS option wich may be because Intel no longer supports this.

[longpanda]

Is the secure boot option enabled in the BIOS? iVentoy now does not support secure boot, so you need to disable the secure boot option in the BIOS firstly.

[roy]

Is the secure boot option enabled in the BIOS? iVentoy now does not support secure boot, so you need to disable the secure boot option in the BIOS firstly.

Yes, secure boot is disabled.

---

After experimenting with network boot, I found that the motherboard has the same issue with bare metal iPXE and even Windows deployment system.