A practical troubleshooting guide for cases where a USB installation drive, recovery drive, or rescue flash drive does not appear in the BIOS/UEFI boot menu.
If the BIOS or UEFI boot menu does not show your flash drive, the most common reason is a mismatch between the USB drive format and the firmware boot mode. A modern UEFI computer usually expects a USB drive prepared as GPT with FAT32. Older BIOS systems usually expect MBR with Legacy or CSM boot enabled.
The flash drive was created for Legacy BIOS, but the PC is set to UEFI only, or the opposite.
Very commonSome rescue tools, Linux images, and older installers do not boot while Secure Boot is enabled.
CommonThe firmware may not initialize a front-panel port, hub, docking station, or some USB 3.x controllers early enough.
Easy to testThe problem can look slightly different depending on the motherboard, laptop brand, and firmware interface. Usually you will see one of these symptoms:
CSM is enabled.A flash drive is not listed in the boot menu just because files were copied to it. The firmware must recognize a valid boot structure, a compatible partition scheme, a supported file system, and a boot mode that matches the current BIOS/UEFI configuration.
| Cause | What it means | Recommended fix |
|---|---|---|
| Wrong partition scheme | GPT USB is used on a Legacy-only PC, or MBR USB is used on a UEFI-only configuration. |
Recreate the USB drive with the correct target system. |
| Unsupported file system | Some UEFI firmware cannot boot from NTFS without a helper loader. |
Use FAT32 for UEFI when possible. |
| Secure Boot restriction | The bootloader on the USB drive is not trusted by the firmware. | Disable Secure Boot temporarily or use a signed image. |
| Fast Boot enabled | Firmware skips some USB initialization during startup. | Disable Fast Boot in UEFI settings. |
| Bad USB creation method | The ISO was copied as normal files instead of being written as a bootable drive. | Use Media Creation Tool, Rufus, Ventoy, or another reliable writer. |
| Port or hub problem | The USB controller is not available before the operating system loads. | Use a direct USB 2.0 port or a rear motherboard port. |
Before you change firmware options, confirm that the USB drive itself is usable and that you are opening the correct boot menu.
The fastest reliable fix is to recreate the bootable USB drive. For Windows installation media, the safest options are Microsoft Media Creation Tool or Rufus. For diagnostic tools and Linux images, use the tool recommended by the image developer.
GPT; Target system: UEFI; File system: FAT32 when available.
MBR; Target system: BIOS or UEFI-CSM; File system: FAT32 or NTFS, depending on the image.
| Computer type | Firmware mode | USB partition scheme | Best file system |
|---|---|---|---|
| Modern Windows 11 PC | UEFI only | GPT | FAT32 |
| Most Windows 10 laptops | UEFI, sometimes CSM | GPT for UEFI, MBR for Legacy | FAT32 preferred |
| Old BIOS desktop | Legacy BIOS | MBR | FAT32 or NTFS |
| Mixed rescue toolkit | Depends on target PC | Use the writer’s recommended mode | Depends on toolkit |
Many boot menu problems come from a simple mode mismatch. A USB drive prepared for UEFI may not appear when the firmware is forced into Legacy mode, and a Legacy-only USB may be hidden when UEFI-only boot is selected.
Restart the computer and press the setup key. Common keys are Del, F2, F10, or Esc. On Windows 10 and Windows 11, you can also use the advanced startup path:
UEFI or UEFI only.CSM, if available.CSM, Legacy Support, Launch CSM, UEFI/Legacy Boot, or Boot Mode.
Secure Boot allows the firmware to start only trusted bootloaders. Official Windows 10 and Windows 11 installation media normally works with Secure Boot enabled. Some older Windows images, Linux distributions, antivirus rescue disks, cloning tools, and custom PE environments may require Secure Boot to be disabled temporarily.
Some systems do not initialize every USB controller before the operating system starts. This is especially common with front-panel connectors, USB hubs, docking stations, adapters, and certain USB 3.x controllers on older motherboards.
If you are trying to install or repair Windows, use official installation media whenever possible. A Windows ISO can be written incorrectly if you only copy the ISO file itself to the flash drive. The USB drive must contain boot files in the correct structure.
For most users, Microsoft Media Creation Tool is the simplest way to create a Windows installation USB that works on UEFI systems. It automatically prepares the drive with the required boot files.
For a current Windows 10 or Windows 11 PC, select GPT and UEFI. If the Windows image contains a file larger than 4 GB and FAT32 is not possible, Rufus may create an NTFS-based UEFI boot method. This works on many PCs, but some restrictive firmware setups may not show it until Secure Boot is disabled.
If the basic fixes do not help, the problem may be caused by firmware bugs, old BIOS versions, corrupted NVRAM entries, or a USB drive layout that the motherboard cannot parse.
Load default firmware settings, save, restart, then configure only the required options again: USB Boot, UEFI or Legacy, and Secure Boot.
If the motherboard or laptop is old, a firmware update may improve USB boot compatibility. Download firmware only from the official manufacturer website and follow the exact instructions for your model.
If the flash drive has an unusual partition layout, old boot records, or hidden partitions, wipe it before writing the image again. In Windows, you can use DiskPart:
DiskPart commands — this erases the selected USB drivediskpart
list disk
select disk X
clean
exit
X with the correct USB disk number. The clean command removes partition information from the selected disk. Selecting the wrong disk can erase an internal drive.
Use this table to choose the fastest next step based on what you see.
| What you see | Most likely cause | Try this first |
|---|---|---|
| USB works in Windows but not in Boot Menu | Not created as bootable media | Recreate the USB using Media Creation Tool or Rufus. |
| Only Windows Boot Manager appears | USB boot disabled or UEFI-only filtering | Enable USB boot and recreate the drive as GPT + UEFI. |
| USB appears only in Legacy mode | Drive was created as MBR/Legacy | Use Legacy/CSM or recreate as GPT + UEFI. |
| USB appears but does not boot | Secure Boot or corrupted image | Disable Secure Boot temporarily or write the ISO again. |
| USB appears on another PC only | Port, firmware, or compatibility issue | Try another port, another flash drive, or update BIOS/UEFI. |
Recreate the USB drive for the correct boot mode, connect it directly to a reliable USB port, open the one-time Boot Menu, and check UEFI/Legacy, Secure Boot, and USB Boot settings. In most cases, the problem is solved by matching GPT + UEFI or MBR + Legacy/CSM to the target computer.