Anyone iPXE booting Windows10 ?

[Tribble]

Haven't done win10 deploys yet. Wrestling with secure boot from win10 certified hardware. Its secure boot only on those suckers :-(

but.. What I've found with GPT and EFI, and windows 10 repartitioning may be a help so I'll share it here. Good luck.

INACCESSIBLE_BOOT_DEVICE is typical from invalid settings in the BCD. However you may also get something similar from the EFI boot.
I use linux to clone partitions resize them etc. partclone.ntfsreloc is my good friend. But windows 10 this didnt work. Why? EFI, GPT an Windows Boot Loader.

EFI requires a special partition to find all the files in. This was easy. I thought the partitions GUIDs were easy too. WRONG!
Windows allows you to easily change the GUIDs THESE ARE PARTITION NAMES not the actual partition GUIDs. It was only when I dug deeper into each partition with the linux gdisk tool that I found DIFFERING partition GUIDS!

Now the trick is that while windows doesn't seem to use these partion GUIDs, Windows Boot Loader DOES!!! If I remember it correctly the GUID for the EFI partition is not critical, but the one for the system partition is.

Hope this helps

PaulD

But the thing that really caused me problems was that UEFI requires GPT partitions with unique GUIDs.
Where I thought I was setting the GUID's within windows for the partitions, I was only setting DISKLABELS. It was only when I used the linux gdisk command and specificly dug into the partition for its GPT GUID I found a different set of GUIDs. It looks like the Windows Boot Manager looks for a specific PARTITION BASED GUID not the GUID DISK LABEL.



Windows does this with disk labels. I use a linux based tool gdisk to go past the disklabels and dig deeper and see the true partition GUID. Whilst windows doesn't seem to care about the partition GUID's it is ESSENTIAL to get them right for identifying the boot volume.