I wonder if booting this way will circumvent the certificate signing when booting in UEFI mode:
https://github.com/pbatard/uefi-ntfs
"UEFI:NTFS is a generic bootloader, that is designed to allow boot from an NTFS partition, in pure UEFI mode, even if your system does not natively support it.
However, this is not possible because Microsoft have arbitrarily decided that they would not sign anything that is GPLv3 under the false pretence that it would force them to relinquish their private signing keys.
What this means is that, unfortunately, UEFI:NTFS cannot be submitted to Microsoft for Secure Boot signing, as it will be automatically rejected, and you currently are left with no choice but to have Secure Boot disabled for UEFI:NTFS to run."
Here is the EFI image containing the drivers and binaries as a FAT EFI image:
https://github.com/pbatard/rufus/tree/master/res/uefi
https://github.com/pbatard/uefi-ntfs
"UEFI:NTFS is a generic bootloader, that is designed to allow boot from an NTFS partition, in pure UEFI mode, even if your system does not natively support it.
However, this is not possible because Microsoft have arbitrarily decided that they would not sign anything that is GPLv3 under the false pretence that it would force them to relinquish their private signing keys.
What this means is that, unfortunately, UEFI:NTFS cannot be submitted to Microsoft for Secure Boot signing, as it will be automatically rejected, and you currently are left with no choice but to have Secure Boot disabled for UEFI:NTFS to run."
Here is the EFI image containing the drivers and binaries as a FAT EFI image:
https://github.com/pbatard/rufus/tree/master/res/uefi