After being imaged, Win10 won't UEFI boot, will Legacy boot
Relatively new to FOG, been tinkering with it the past few weeks.
(Running FOG 1.5.9)
I am able to PXE boot using UEFI on a Lenovo T14. I captured my golden image successfully.
I tried to deploy my T14 image to another T14. It successfully deploys (I think).
When I reboot the system, it refuses to boot unless I change UEFI to Legacy boot. Then it jumps into Windows and appears happy.
I’d like to skip the step of changing the settings in the firmware if possible. I have another model, a T480 that seemed to take the image and boot via UEFI just fine.
What am I missing?
Thanks in advance!
@george1421 Scratch that. I was confused about how this works, my apologies.
The Windows 10 installation I used to create my image is using an MBR, aka Legacy boot.
Thanks again for the quick reply.
@george1421 Thank you for the reply George! I suppose that’s why I’m a bit confused.
I will try to rip the image again. (Making sure to UEFI boot to PXE)
I will post after I try deploying again.
@mmarquis What you are saying is inconsistent with the way fog works.
If you capture a uefi image and deploy it to another uefi image it will boot. FOG does not change the disk structure, like from uefi to bios. If you have to switch the target computer into bios (legacy) mode then your captured image was from a bios based computer. At the heart of it fog just moves partitions to raw data files on the fog server and then from the raw data files on the server to the new target computer. It doesn’t change the format of the media.
FWIW uefi and bios partition tables are laid out differently.
Just to add a layer of confusion here. The mode that image capture happens is not related to or has an impact on the target computer disk structure.
For example I can have a UEFI computer and UEFI disk structure. I can boot the computer in bios mode and capture and deploy that UEFI disk as long as the target computer is configured for UEFI when it boot, it will see the hard drive and boot.