Hey, thanks so much for the info, much appreciated. I managed to boot from USB after setting the motherboard options to just 'optimised defaults'. The resultant windows install though, doesn't appear to boot from UEFI, at least there's no UEFI option for it, just something called 'Windows boot manager'. If I allow it to go through to Clover rather than asking the MoBo to list boot options, Clover shows a couple of NTFS partitions such as 'Boot Windows from EFI' but they seem legacy. Not sure what I did wrong here, but will try to persevere a little longer.
Hey, thanks so much for the info, much appreciated. I managed to boot from USB after setting the motherboard options to just 'optimised defaults'. The resultant windows install though, doesn't appear to boot from UEFI, at least there's no UEFI option for it, just something called 'Windows boot manager'. If I allow it to go through to Clover rather than asking the MoBo to list boot options, Clover shows a couple of NTFS partitions such as 'Boot Windows from EFI' but they seem legacy. Not sure what I did wrong here, but will try to persevere a little longer.
The matter is that Windows 10 BCD loader configuration installed in UEFI mode is stored in a separate hidden EFI partition (with the volume of 100 Mb and having FAT32 file system), which the utility bcdedit cannot recognize and therefore it cannot manage the configuration of the boot loader stored there. Copy bootmgr.efi to efi boot bootx64.efi. GPT partitions have GUIDs to be identified as SYSTEM, BASIC, MS_RESERVED in the partition table but the first sector of a GPT partition has the filesystem (FAT32, NTFS) type stored so it can be interpreted by the OS.