@robbit @Sebastian-Roth I have experienced the same issue with the same laptop. Running FOG 1.5.9. Until now, we have a mix of UEFI and BIOS computers with a huge variety of brands, form factors, and NICs that have had no problems imaging with FOG. Our Windows DHCP server with appropriate scope policies hands out the proper boot file and imaging just happens. With this model, it was taking 50 minutes (on a network with a 10G backbone and 1G to the endpoint) just to download bzImage. I tried the NVME fixes and the alternative init.xz files, but that did nothing. However, creating a DHCP scope policy (based on MAC address, as I only have one of these machines) that handed out snponly.efi as the boot file for this machine (instead of ipxe.efi) completely and immediately solved this issue for me. Just wanted to post this, as I came across this unsolved thread in my attempts to find a solution. Hopefully it can help someone else.

@robbit @Sebastian-Roth I have experienced the same issue with the same laptop. Running FOG 1.5.9. Until now, we have a mix of UEFI and BIOS computers with a huge variety of brands, form factors, and NICs that have had no problems imaging with FOG. Our Windows DHCP server with appropriate scope policies hands out the proper boot file and imaging just happens. With this model, it was taking 50 minutes (on a network with a 10G backbone and 1G to the endpoint) just to download bzImage. I tried the NVME fixes and the alternative init.xz files, but that did nothing. However, creating a DHCP scope policy (based on MAC address, as I only have one of these machines) that handed out snponly.efi as the boot file for this machine (instead of ipxe.efi) completely and immediately solved this issue for me. Just wanted to post this, as I came across this unsolved thread in my attempts to find a solution. Hopefully it can help someone else.