Clover EFI Bootloader

Clover EFI Bootloader is the boot menu that appears before any operating system starts, and its claim is that it can start almost any of them. It lives on the small system partition every modern disk carries, or on a USB stick.

When the computer powers on, it scans the drives, finds every system installed and shows them as icons on a themed screen. Pick one and it boots. On firmware too old for modern booting it can emulate the newer standard itself, so a machine from a previous generation boots the same way as a new one.

Its best-known use is the one that made it famous, and it should be named plainly. Clover EFI Bootloader is one of the two main tools for starting macOS on a PC that was not made to run it, the setup known as a Hackintosh. It works by presenting that system with the hardware details it expects.

That use runs outside the licence terms of macOS, and the community around it has largely moved to the newer OpenCore loader, which Clover now incorporates parts of. It also boots Windows and Linux, side by side, which is the use that sits entirely within the rules.

The sections below cover the boot menu, the configuration file, the drivers and patches, multi-booting, and the honest picture of where the project stands.

The boot menu

The Clover EFI Bootloader menu is the part everyone sees. Every bootable system on every connected drive appears as an icon, with its name, and the arrow keys or the mouse choose between them. After a timeout the last system chosen boots on its own, so a machine that usually starts one system needs no attention. A long list scrolls when the screen is small, and custom entries add systems the scan does not find or rename the ones it does. For a stick that boots any of many installers from a menu, a multi-boot USB tool is the simpler cousin, without the patching.

The look is fully themeable. Themes change the background, the icons, the fonts, the animations and the mouse pointer, and a theme manager installs them from a large shared collection. From the same menu, a key saves the original firmware tables for later study and another saves the graphics firmware.

An EFI command shell opens for anyone who needs to work below the operating system.

The configuration file

Everything Clover EFI Bootloader does is set in a single configuration file, a structured text file kept in its folder on the system partition. It sets the boot timeout and the default system, the screen resolution, the theme, the hardware details reported to the operating system, the patches applied at boot, and the drivers loaded. Getting this file right is most of the work of a Clover setup, and the reason guides for particular motherboards are shared so widely.

The file can be edited by hand, and a graphical configurator exists for those who would rather not. Settings can also be changed from the boot menu itself for a single boot, which is how a setting is tested before it is written to the file.

A bad edit can stop a machine from booting through Clover, so keep a known-good copy and a second way to boot before changing it.

Drivers and boot-time patches

Clover EFI Bootloader loads its own firmware drivers before any system starts, for reading file systems the firmware does not understand, handling memory layouts, and emulating missing firmware services. Those drivers sit in a folder beside the configuration file and are chosen per machine.

Patches modify the operating system or its tables as it loads, adjusting the descriptions of hardware so a system recognises parts it would otherwise ignore. That is the machinery behind the Hackintosh use, and it is also why the configuration is specific to each motherboard and graphics card.

Recent releases fold in components from the OpenCore project, which brought new settings into the configuration and changed how memory is handled at boot.

Multi-booting Windows and Linux

The everyday, uncontroversial use of Clover EFI Bootloader is a single menu for several systems. Install Windows and a Linux distribution on the same machine, or on separate drives, and Clover offers both at startup, with the last choice remembered. Because it reads the system partition directly, it finds the boot files of each without manual entries in most cases.

For a machine that only runs Windows and Linux, though, the menus built into those systems or a simpler tool do the job with far less setup. For managing the Windows boot menu itself and repairing a system that will not start, EasyBCD is the more direct tool.

Clover earns its place where the firmware is old, the systems are unusual, or the boot screen should look a particular way.

Putting it on a stick or a disk

Clover EFI Bootloader is usually placed on a USB stick first, to test a machine without touching its disk, and moved to the system partition of the internal drive once it boots reliably. The stick needs the right partition layout and file system for the firmware to see it. Rufus prepares a stick with the layout firmware expects, and the Clover files are then copied into its EFI folder. On a stick, a bad configuration means nothing worse than a reboot, which is why every guide tests there first.

Once it works from the stick, the folder is copied to the internal drive’s system partition. The firmware is then told to boot it, from its own menu or through an option in Clover that writes a boot entry.

Where the project stands

Clover EFI Bootloader is still developed, with releases arriving through the year, but its position has changed. The community that made it famous has largely moved to OpenCore for booting macOS, preferring that loader’s stricter design, and Clover now borrows parts of OpenCore to keep up. The newest versions of macOS have also dropped support for the processors a PC uses, which narrows the Hackintosh use toward its end.

What remains is a capable, deeply configurable boot manager with a long history and a large base of shared configurations, and a multi-boot menu for unusual setups. The configuration file asks for patience and the setup for a careful, tested approach.

Conclusion

Clover EFI Bootloader suits people who want one themed boot menu for several systems, owners of older machines whose firmware predates modern booting, and the tinkerers who build unusual setups and share their configurations. Its scanning, its themes and its single configuration file make it one of the most flexible boot managers there is.

It asks for patience, its configuration is specific to each machine, and its most famous use is outside the rules and fading. Test on a stick, keep a working copy of the configuration, and use the simpler tools when the job is only Windows and Linux.