Enter BIOS/UEFI during startup and confirm it worked

Want to open your PC or Mac firmware settings at startup so you can change boot order, enable virtualization, or disable Secure Boot? First, have a wired keyboard or use the built-in one, confirm the exact model, fully shut the system down (not hibernate or Fast Startup), then press the vendor hotkey while powering on. If the hotkey fails, use the operating system to restart into firmware.

Before you start — quick checklist and why each item matters

Start with these checks so you can reach firmware and avoid surprises. Know the model, use a keyboard that initializes early, fully power off, connect AC, and confirm any management or encryption that may block changes.

• Have the exact manufacturer and model or the motherboard model.

• Use a wired USB-A keyboard or the built-in laptop keyboard.

• If you only have USB-C input, bring a passive USB-C to USB-A adapter or a vendor-documented firmware-compatible USB-C keyboard.

• Ensure the system is fully shut down; do not use hibernate or Windows Fast Startup.

• Plug the computer into AC power or ensure the desktop PSU is switched on.

• Know whether the device is managed (MDM), protected by a firmware password, or uses drive encryption such as BitLocker, FileVault, or LUKS.

• Back up important data before changing firmware settings that affect disks (SATA mode, RAID, Secure Boot).

Step-by-step: enter BIOS/UEFI from shutdown or restart (do this now)

If you want to enter firmware from a powered-off state, follow these exact steps in order. If hotkeys fail, use the OS handoff methods shown after the cold-start steps.

1. Fully shut down the system; do not use hibernate or Fast Startup.

2. Connect a wired keyboard directly to the computer; avoid hubs and docks.

3. Power on the system.

4. Immediately use the correct hotkey for your device. Common patterns: single press, repeated taps during the vendor logo, or hold the key while powering on.

5. When a firmware menu appears, stop pressing keys and navigate with the keyboard or mouse if supported.

Expected result: you see a navigable firmware interface labeled "BIOS" or "UEFI" with menus such as Boot, Security, Advanced, and Save & Exit.

From a restart when hotkeys are unreliable, use an OS-initiated handoff.

6. Windows: Open Settings → System → Recovery → Advanced startup → Restart now. After restart choose Troubleshoot → Advanced options → UEFI Firmware Settings → Restart.

Settings → System → Recovery → Advanced startup → Restart now → Troubleshoot → Advanced options → UEFI Firmware Settings → Restart

7. Linux: Prefer a cold shutdown and the hotkey. If you need an OS handoff, use your distribution’s menu or efibootmgr to view and re-order EFI entries.

efibootmgr -v

8. macOS:

• Intel Mac: hold Option at startup for Startup Manager, or Command+R for Recovery.

• Apple silicon: press and hold the power button at startup until Startup Options appear, then choose Options → Continue.

Device map and hotkeys — quick reference by device type and common OEMs

Use this quick map to find the likely hotkey for your system. Try the listed keys in order, and check the vendor support page for model-specific exceptions.

Desktop motherboards and custom builds:

• Most consumer motherboards use Delete or F2 to enter UEFI during POST. Check the motherboard manual for the exact key.

Laptops — common keys (try in order):

• Dell: F2 for setup; F12 for one-time boot menu.

• HP: Esc for startup menu, then F10 for BIOS/UEFI; F9 for one-time boot menu.

• Lenovo: F1 or F2. Many ThinkPad models also have a Novo/Recovery button.

• Asus: F2 for setup; Esc for boot menu.

• Acer: F2 for setup; F12 for boot menu on models that enable it.

• Surface and similar tablets: use a volume + power sequence or a dedicated recovery button; check the manual for the exact combo.

Macs:

• Intel Mac: Option for Startup Manager, Command+R for Recovery (a firmware password may appear first).

• Apple silicon: hold the power button to access Startup Options, then choose Options → Continue for Recovery.

Tablets and 2-in-1s:

• Many use a vendor-specific recovery button or power + volume key combo. Remove docks and external peripherals during tests.

Notes on keyboards and docks:

• Docked keyboards and hubs sometimes initialize after POST. Use a direct system USB port or a simple passive adapter. If a docked keyboard fails, unplug the dock and connect the keyboard directly.

Remote management:

• Intel AMT, iDRAC, iLO and similar controllers provide remote console and firmware access when configured and reachable.

If it didn’t work — prioritized diagnostics and fixes

Work through these checks one at a time and stop when you can enter firmware. Try keyboard, timing, ports, and power-cycling fixes before hardware resets.

1. Switch to a wired keyboard and connect it directly to the computer.

2. Try different key timing: immediate single press, repeated tapping during the logo, or hold the key while powering on for 5–10 seconds.

3. Fully power-cycle: hold the power button until the device is off, wait 5–10 seconds, then power on and try again.

4. Disable Windows Fast Startup or use a full shutdown command.

shutdown /s /t 0

5. Try a different USB port. On older systems, a PS/2 keyboard or a USB-to-PS/2 adapter may work if supported.

6. Remove external USB drives, SD cards, and other bootable media.

7. If you see a firmware password or an MDM lock, follow the vendor’s recovery procedure. Vendors may require proof of ownership.

8. If changing boot options triggers a BitLocker or other encryption recovery prompt, supply the recovery key you exported earlier. Changing SATA/RAID mode also triggers recovery on many encrypted systems.

9. As a last resort, consult the manual for a CMOS/RTC reset procedure and follow it exactly.

How to confirm you are in the firmware interface (what to look for)

To confirm you reached the real firmware, look for labeled menus and keyboard navigation. A splash logo alone is not firmware; the firmware UI accepts input and shows configuration options.

Signs you are in firmware:

• The screen displays menus labeled "BIOS" or "UEFI" and includes Boot, Security, Advanced, or Save & Exit.

• The interface accepts keyboard navigation; many UEFI screens accept mouse input and show an EFI version or firmware build date.

• A vendor splash logo by itself is not firmware. If the system continues to boot to the OS, retry the hotkey or use the OS handoff.

What does not count as firmware:

• OS recovery environments (Windows Recovery or macOS Recovery) are provided by the OS and show options like Reset PC or reinstall. Firmware menus are labeled and sit below those recovery options.

Completion check: once the firmware UI is visible, you should be able to change settings and see Save/Exit options.

OS-based entry methods (Windows, Linux, macOS) and when to use them

Use OS-based entry when hotkeys fail or remote access is not available. These methods ask the OS to reboot into firmware and are more reliable when Fast/Ultra Fast Boot interferes with hotkeys.

• Windows: Settings → System → Recovery → Advanced startup → Restart now → Troubleshoot → Advanced options → UEFI Firmware Settings → Restart.

Settings → System → Recovery → Advanced startup → Restart now → Troubleshoot → Advanced options → UEFI Firmware Settings → Restart

• Linux: Some distributions offer a firmware setup entry in shutdown or boot menus. Use efibootmgr to list and manage EFI boot entries. Prefer a cold shutdown if Fast Boot blocks hotkeys.

efibootmgr -v

• macOS: Intel Macs use Option at startup for Startup Manager or Command+R for Recovery. Apple silicon uses the power-button hold to show Startup Options, then Options → Continue for Recovery.

Safe exit and verification — save vs discard, how to confirm settings took effect

Always confirm what you changed before saving, and check from the OS that the change took effect. If the system won’t boot, restore defaults or follow vendor recovery steps.

• To keep changes, choose Save and Exit, Save Changes and Reset, or an equivalent option.

• To discard changes, choose Discard Changes or Exit Without Saving.

How to verify changes from the OS:

• Boot order: confirm the intended device boots first on the next start or check EFI entries on Linux.

efibootmgr -v

• Secure Boot: on Windows run msinfo32 and look for "Secure Boot State"; on Linux check efivar variables or use mokutil --sb-state where available.

• Virtualization: on Windows check Device Manager or Hyper-V features; on Linux check lscpu or dmesg for CPU virtualization flags.

If the system won't boot after a change:

1. Re-enter firmware and undo the change or choose Restore Defaults / Load Optimized Defaults.

2. If you cannot enter firmware, follow vendor instructions for CMOS/RTC reset or contact vendor support.

3. If BitLocker or another encryptor requests a recovery key, supply the key you exported before changes.

Recovery options if firmware is locked or the system won’t boot after changes

If firmware is locked or the system won’t boot, follow vendor procedures first. Use firmware defaults, recovery keys, and only documented hardware resets for serviceable models.

1. Use the vendor’s documented recovery process for firmware passwords or MDM locks. Vendors may require proof of ownership.

2. Restore firmware defaults from the firmware UI if you can access it.

3. Provide previously exported drive-encryption recovery keys (BitLocker, FileVault, LUKS) when prompted.

4. If the device is unresponsive and you have a desktop or a serviceable model, follow the manual for CMOS/RTC reset and only perform hardware resets described in the manual.

5. If the device is sealed or under warranty, contact vendor support with model, serial number and proof of ownership. Do not attempt intrusive hardware recovery that could void warranty.