> like this well enough to prefer a 32GB FAT32 volume for EFI, so there's enough space for some Live Linux distributions, along with all the boot files I can m

> like this well enough to prefer a 32GB FAT32 volume for EFI, so there's enough space for some Live Linux distributions, along with all the boot files I can muster Great idea, so it's always there when you need it! > Under the latest Windows 10 GPT scheme, the MSR by default now extends from sector 34 to the first sector of your system volume, and for performance your system volume is hopefully aligned at a location such as 8192, although 1024 was common for a while. So all these sectors are now well spoken-for. This is fairly recent and until then sectors 34 through 8191 for instance were being unused by Windows 10, out-of-partition, and unallocated by default. It must be very recent because it never happened to me. If it did, I would just move the MSR. I guess Microsoft is just trying to use the leftovers to be less intrusive? But with a large enough EFI, I don't really care. > Revocation of previous Microsoft-signed Linux keys Use your own keys! Don't depend on someone else's keys! > Take a look at what might be happening/proposed with SYSTEMD for booting and with the proper input plus great care a new Linux bootloader could arise to overcome remaining obstacles It has already happened: I follow the Arch way of a "fat" EFI payload using systemd EFI stuff: so I have a kernel + initrd (+ cmdline) in one EFI file - and no need for a bootloader anymore, as the UEFI can directly boot this EFI payload. Sign this file with your own keys (MOK) and you're king of your castle > There simply needs to be a single Microsoft-signed bootloader that can boot any Linux, or Windows, from a user-configurable menu A menu is a waste of time. I keep my EFI payload on the EFI partition. I never need to change the kernel cmdline. One less piece of software (a good thing as grub2 had recent vulnerabilities) > Along these lines a focused amount of work needs to be done with UEFI Shell programs, and that might be all it requires There are a few good ones, that can help you in case of problems - but booting a live distribution is almost faster. Your idea of keeping it right in the EFI partition is great - we simply need to change our habits and create larger EFI partitions. It's the ideal place to put it, as Windows or anything else won't dare touch it there. > So it looks like Microsoft is still lying at least about one of the most important things. Maybe - but we don't really need them with MOK keys and the systemd EFI stub.