Well I can’t prove that its broken here. I deployed a Win10 1703 reference image to a 7040 in bios mode and it boots correctly through an pxe boot. I built a UEFI version of Win10 1703 and deployed that to the 7040 in uefi mode. First to the nvme disk and second to a sata ssd. Both booted through pxe to the OS. I tested these configurations with both our production server running FOG 1.4.4 and a dev box I spun up running FOG 1.5.0RC8.
In uefi mode right after iPXE exits and before Windows starts to boot there is some text and a blue banner displayed. I’m a quick reader but its only on the screen for a split second before Windows boots, so I missed even the context of what it said.
On our production server I’m sure I mucked with refind.conf file at some point in time. The 1.5.0RC8 was left as it was when I unboxed it. I did nothing to 1.5.0RC8 other than install it and login to register the test system.
The 7040 has firmware 1.4.5 installed I know there is a later bios release, but that is what was installed on the box. When I registered the system I went into the host configuration and set the exit mode for bios to SANBOOT and uefi to rEFInd.
Now this test may be flawed since I captured and deployed both images (win10 bios and win10 uefi) using our production server (1.4.4) and only used 1.5.0RC8 to pxe boot through. When I setup the test system I didn’t give it a big enough HD to take the 25GB Win10 image. I’ll have to rebuild the test server again to be able to capture the image from our reference VMs. I’ll do that after the holiday.