Clover Bootloader

Hiya,

I am going to install clover bootloader whilst clean installing windows 10 for BIOS UEFI (but the BIOS UEFI are 32-Bit). So after I have set up the partitions (shift + F10 before installing windows) from command prompt - please note the automatic set up of partitions is not working. I will then copy clover bootloader over to the EFI folder on the EFI system partition then set the path for BCD. Then I should be able to start the clean installation process of windows 10 which is 64-bit; hence the need for another bootloader. But my question is this. I have mostly set up the EFI folder contents for clover bootloader. I have all of the directories and files except for these three directories ACPI, ROM and Misc. For these I intend to add them from clover bootloader, but all of these directories have empty files within. My question is this. Will these be enough as this is a clean installation and the respective hardware information, for power, ROM and misc, should be collected and updated whilst installing; or will it? I would rather do this once correctly so am checking this out before.

I don't know about Clover but I use 32 bit rEFInd bootloader to run 64 bit Windows 10 on a system with 32bit EFI (an old 2006 MBP). I've also used 32 bit grub to call 64 bit Linux. Neither required anything apart from the bootloader.

For me Windows would not work properly in pure EFI mode as the firmware doesn't expose correct information to allow sound etc to work. I therefore have hybrid GPT/MBR partition scheme and rEFInd.efi (32 bit) calls the (64 bit) Windows bootloader in legacy BIOS mode which works fine.

Whether Windows will work for you and how well depends though on whether your firmware makes information available to the OS or not - for sure Windows installation will not populate these patch directories for you as they are nothing to do with Windows. Whether Clover would somehow do this IDK.

What system are you trying this on?