A boot menu is a firmware-provided selection screen, opened with a hotkey during startup, that lets the user choose which device starts the computer this one time, for example a USB drive, an optical disc, a second disk or a network boot. In the Boot & firmware stage of operating systems, it sits between the power-on self-test and the bootloader, and it overrides the stored boot order without changing it.
On modern PCs, the boot menu is a view of the UEFI boot manager, which lists the boot entries stored in firmware memory. It is the standard way to install or repair an operating system, run a live USB or start diagnostic tools while leaving the permanent configuration intact.
How the boot menu works in UEFI firmware
After POST finishes, the firmware briefly checks for a hotkey before it follows the configured boot order. If the boot menu key is detected, the firmware pauses and displays every bootable option it knows, so the user can select one with the arrow keys and Enter.
In UEFI systems, each option corresponds to a Boot#### variable stored in nonvolatile memory (NVRAM), containing a description and a device path to an EFI executable. The permanent sequence is stored in the BootOrder variable, while a one-time choice is expressed through the BootNext variable, which the firmware consumes and deletes after a single use.
Removable media without a dedicated entry are handled through the fallback path \EFI\BOOT\BOOTX64.EFI on 64-bit x86 systems. This is why a correctly prepared USB stick appears in the boot menu even though no boot entry was ever created for it.
The table below lists the main firmware elements that the boot menu reads or changes.
| Element | Stored where | Role |
|---|---|---|
| Boot#### entry | UEFI NVRAM variable | Describes one bootable target and its path |
| BootOrder | UEFI NVRAM variable | Permanent priority list of entries |
| BootNext | UEFI NVRAM variable | One-time override, cleared after use |
| Fallback loader | EFI system partition on removable media | Allows booting media without an entry |
| Legacy device list | Compatibility support module | Lists BIOS-style boot sectors when CSM is enabled |
Boot menu keys and ways to open it
There is no universal boot menu key. Each manufacturer chooses its own, and the key is usually shown briefly on the startup logo screen. The window for pressing it can be under one second on systems with fast boot enabled.
| Platform | Common key | Note |
|---|---|---|
| Dell and Lenovo PCs | F12 | Some Lenovo laptops also have a small recovery button |
| HP PCs | Esc, then F9 | Esc opens a startup menu with further options |
| ASUS systems | F8 or Esc | Desktop boards and laptops often differ |
| MSI and ASRock boards | F11 | Shown on the motherboard splash screen |
| Intel-based Mac | Hold Option | Opens the Startup Manager |
| Apple silicon Mac | Hold the power button | Opens startup options instead of a key menu |
Windows also offers a software route. Holding Shift while selecting Restart opens the advanced startup environment, where Use a device sets a one-time boot target. On Linux, the efibootmgr utility can set BootNext directly, which is practical on remote machines without keyboard access.
Boot menu compared with related concepts
The boot menu is often confused with other startup screens. The key distinction is who displays the menu and what it selects: the firmware chooses a device or loader, while a bootloader chooses an operating system or kernel.
| Concept | Shown by | What it changes |
|---|---|---|
| Boot menu | Firmware | One-time choice of boot device or entry |
| Boot order | Firmware setup utility | Permanent device priority |
| Firmware setup | Firmware | All settings, including Secure Boot and CSM |
| Bootloader menu | GRUB or Windows Boot Manager | Choice of operating system or kernel |
| PXE boot | Network interface firmware | Loads a boot image from a network server |
A bootloader menu such as GRUB appears only after the firmware has already selected a disk. Changing a GRUB default therefore never affects which USB device the firmware tries first.
Practical use and settings that affect the boot menu
The boot menu is the safest way to start an installer or rescue system, because nothing is permanently changed if the attempt fails. Several firmware and operating system settings decide whether a device appears and whether it boots.
- Secure Boot blocks loaders that are not signed with a trusted key, so some Linux tools or older utilities fail with a security violation message.
- With CSM enabled, the same USB stick may appear twice, once as a legacy entry and once with a UEFI prefix; the choice decides the installation mode.
- Fast boot settings may skip USB initialization, so external keyboards and drives can be ignored until the setting is relaxed.
- Windows Fast Startup performs a partial hibernation, so pressing the key after a normal shutdown may not work; a full restart avoids this.
Common problems and fixes
When the boot menu does not behave as expected, the cause is usually a timing, mode or media problem rather than a hardware fault. The table maps frequent symptoms to their likely causes and fixes.
| Symptom | Likely cause | Fix |
|---|---|---|
| Menu never appears | Fast boot or Fast Startup skips the key check | Use a full restart or the Windows advanced startup route |
| USB drive is missing | Media lacks a UEFI loader or uses an unsupported format | Recreate the media with a FAT32 EFI partition |
| Security violation message | Loader not trusted by Secure Boot | Use signed media or adjust Secure Boot deliberately |
| Installed system will not start | Installer ran in legacy mode on a UEFI disk | Reinstall after choosing the UEFI entry |
Understanding it simply
A boot menu is like asking a taxi driver to take a different route just for today. Normally the computer starts from its main disk, following a fixed list. Pressing a special key at power-on shows a short list of everything it could start from instead.
The user picks a USB stick or another disk, and the computer starts from it once. The next time, it returns to its usual habit automatically. Nothing in the settings has to be changed back.
Applied in practice
An IT technician in a small accounting office needs to replace the failing system disk of a desktop PC and reinstall the operating system. She writes the installer to a 16 GB USB stick, plugs it in, performs a full restart and presses F12 when the manufacturer logo appears.
The boot menu lists the internal disk, the network adapter and the stick twice: once as a legacy entry and once with a UEFI label. She chooses the UEFI entry, so the installer creates a GPT disk layout that works with Secure Boot. After installation, the PC starts from the new disk automatically, because the stored boot order was never modified, and the stick can be removed without any cleanup in the firmware settings.