@george1421 So, I am an idiot.

What was happening here is I deployed the old BIOS image, which blew away the GPT designation, and then when I created and captured the new image, the Windows installer never re-applied the GPT. I manually went in with diskpart, wiped the drive, applied GPT, rebuilt the image, captured, deployed, and voila! It boots now.

Jokes on me for trusting the Windows installer I guess.

Thanks for your input George! It actually helped a lot.

@george1421 So, I am an idiot.

What was happening here is I deployed the old BIOS image, which blew away the GPT designation, and then when I created and captured the new image, the Windows installer never re-applied the GPT. I manually went in with diskpart, wiped the drive, applied GPT, rebuilt the image, captured, deployed, and voila! It boots now.

Jokes on me for trusting the Windows installer I guess.

Thanks for your input George! It actually helped a lot.

@george1421 Hi George, Thanks for the reply!

The first images I deployed were BIOS based, but then I realized my mistake and built & captured an image from the offending laptop directly (which is UEFI only) and that also does not boot. I did try the Windows recovery and the tools could not fix the boot problem.

Is there something I need to set on the FOG end to force it into UEFI-based capture? I couldn’t find anything to do that and from what I read elsewhere on the forum here it seemed like FOG figures it out automatically.

Is this a function of incorrect partition format (MBR vs GPT) or is there more going on that differentiates BIOS vs UEFI images where FOG is concerned?

Hello folks,

I have an issue that started out looking like the UEFI boot issues a bunch of people were having, but I think it might be something different.

We recently got some new HP laptops (very generically called HP Laptop 15z) that do not have legacy boot options. I was able to find info and reconfigure my FOG to boot consistently into PXE, and both capture and deploy tasks seem to complete successfully, but after a deploy, if I let it chain load, rEFInd goes to it’s “about” screen. If I disable netboot and force it to boot from HD, it complains that there is no OS.

I’ve tried all the other exit types as well and none will boot the HD.

I’ve tried this with both old images (Win 10 1809) that have worked flawlessly and new ones (W10 20H2) created on the new hardware.

Specs:

• FOG 1.5.8
• DHCP is a Win2008 server with 66 pointing to FOG IP and 67 set to snponly.efi
• I’m using persistent groups plugin
• I have a custom init but it’s just replacing the register script with a simpler one that only asks the questions we need

I dunno if those last two are even useful or relevant but I’m grasping at straws here. I don’t know what I did to have the system just completely unable to find the OS.

Any insight is appreciated.