@tom-elliott Interesting…enabling Secure Boot did in fact cause the computer to boot to the Windows OS. But it bypassed the FOG menu. It downloaded the NBP successfully, but then loaded Windows.

Disabling Secure Boot caused it to once again boot to the FOG menu, which then timed out, and then hit the rEFInd snag.

Is this model of hardware unable to boot to the FOG server, timeout, and then load Windows?

At this point, it seems it can do either Windows or FOG, but not both together.

@tom-elliott Some further testing:

• Changed to rEFInd Version 10.9. The rEFInd - Initializing screen came up, but then said Scanning for boot loaders; please wait… LT stayed at this screen.

• Changed Host EFI Exit Type for this host to EXIT. Got message
  Chainloading failed, hit ‘s’ for the iPXE shell; reboot in 10 seconds.
  Device would reboot, then do it all over again.

• Changed to rEFInd Version 11.0. Still got the ‘Chainloading…’ message.

• Turned off EXIT for the host. The rEFInd - Initializing screen came up and went to a ‘Scanning for boot loaders; please wait…’ message. It stayed there.

rEFInd just does not want to load Windows for some reason. I saw this thread which referenced a comment on Reddit that non-signed kernels have trouble chainloading to a signed Windows kernel.

Could this be the issue I am dealing with? If so, what can I do to resolve this?

@tom-elliott Yes, I have the scan_delay set to 5. Timeout is also set to 5.

• Started today with rEFInd Version 0.11.04, scanfor set to manual, menuentry for Windows. LT would get to a rEFInd menu, but would fail to load Windows.
  Error: Not Found while loading bootmgfw.efi.

• Changed to rEFInd Version 0.12.0. LT got stuck at rEFInd - Initializing…

• Edited refind.conf to scanfor netboot, internal and disabled manual menu entry. LT got stuck at rEFInd - Initializing…

• Edited boot order of LT to boot to disk first and it loaded the OS.

There seems to be an issue going from pxe boot to hard disk. Once the network boot times out and tries to boot to the hard disk it encounters difficulty at the rEFInd stage.

@sebastian-roth Here’s the menu entry. It’s a Windows 10 image - I just didn’t update the entry name.

Using rEFInd Version 0.11.4.

@sebastian-roth It occurred to me that I was imaging with a golden image that had been created with a vm that used BIOS. I created a new vm using EFI and created a new base image. Reimaged with this image, but it still seemed to get hung up at a rEFInd screen. Later, I saw the OS did end up loading.

Tinkered around with this some as it still seems to get hung up at rEFInd. I edited the scanfor to manual and added a menu entry for Windows. Got this:

@sebastian-roth I updated the firmware on the device, but am still getting the same screen as the previously-posted screenshot.

I spend most of my day yesterday on another matter. Back to work on this issue today.

@tom-elliott I made the suggested changes and ended up with this screen:

Hitting different keys did nothing. It remained stuck on this screen.

@george1421 Tried this, but received same result. Device imaged, but after rebooting brought up the ‘rEFInd - Initializing’ screen.

@sebastian-roth I’m sorry, I am unsure what you mean. Are you saying to configure Option 67 with snponly.efi?