bootpick beta

Tested computers and systems

Every computer and operating system bootpick has actually been run on, with the details that matter when something does not work: firmware, disks, boot loaders and how each system is started.

Computers

MachineFirmwareDisksStatusNotes
Laptop, AMD Ryzen 7 4800HInsyde UEFI 2.7NVMe + SATA, GPTWorksMouse and touchpad through the firmware's own pointer drivers. Secure Boot off. The HDMI output stays dark until the operating system starts: the firmware only drives the built-in screen.
QEMU q35OVMF (EDK2)FAT folders as disksWorksStock OVMF has no USB mouse driver; bootpick loads the bundled EDK2 ones from \EFI\bootpick\drivers\.

Systems started by bootpick

SystemLoaderStatusNotes
WindowsWindows Boot ManagerWorksStarted directly; no menu in between.
Pop!_OS 24.04 (COSMIC)systemd-boot 249WorksThe entry is passed with LoaderEntryOneShot; the systemd-boot menu can be hidden from the app.
Ubuntu (encrypted disk)shim + GRUBWorksThe system disk is encrypted; GRUB lives on a separate, unencrypted /boot partition, so its menu can still be hidden.
elementary OSshim + GRUBWorksInstalled in a folder called "ubuntu" on its own EFI partition; bootpick shows its real name and logo. GRUB kept on the EFI partition, hidden from the app as well.

The settings app was used on Pop!_OS 24.04 (COSMIC, Wayland) and on elementary OS, both editing the same installation.

Tried it on something else? Open an issue with the computer model, firmware vendor (shown in \EFI\bootpick\bootpick.log), the systems you start and whether the mouse worked, and it will be added here.

Last updated: 10 November 2026