How to Open BIOS from CMD: A Complete Guide for Windows Users

Accessing your system's BIOS (Basic Input/Output System) — or its modern replacement, UEFI firmware — is something most users rarely need to do, but when you do need it, knowing the right method matters. Using the Command Prompt (CMD) to trigger a BIOS restart is one of the cleaner, more reliable approaches, especially on machines where the traditional key-press method is difficult to time correctly.

What Is BIOS and Why Would You Open It from CMD?

BIOS is the low-level firmware that initializes your hardware before your operating system loads. On most modern systems, this has been replaced or extended by UEFI (Unified Extensible Firmware Interface), which offers a graphical interface and supports larger drives and faster boot times — but the entry point is still commonly called "BIOS" in everyday usage.

You might need to access BIOS to:

• Change the boot order (e.g., to boot from USB)
• Enable or disable Secure Boot or Virtualization
• Adjust CPU, RAM, or fan settings
• Troubleshoot hardware detection issues
• Update firmware

The CMD method is especially useful when your system boots so fast that pressing F2, F10, DEL, or whatever key your manufacturer uses simply doesn't register in time.

Method 1: Using the Shutdown Command in CMD

The most direct CMD approach uses the shutdown command with specific flags to reboot into firmware settings.

Open Command Prompt as Administrator:

• Press Windows + S, type cmd, right-click it, and select Run as administrator

Then type:

shutdown /r /fw /t 0 

What each flag does:

⚠️ This command restarts your PC immediately, so save any open work first.

This method works on Windows 8, 10, and 11 with UEFI firmware. It will not work on older systems running traditional BIOS (non-UEFI), as the /fw flag is only recognized by UEFI-aware versions of Windows.

Method 2: Using bcdedit in CMD

For users who want to schedule a one-time boot into firmware without an immediate restart, bcdedit (Boot Configuration Data editor) offers more control.

bcdedit /set {fwbootmgr} bootsequence {current} 

This is a more advanced approach and is generally only necessary in scripted or enterprise environments. For most users, the shutdown /r /fw /t 0 command is simpler and achieves the same result.

Method 3: PowerShell Alternative (If CMD Isn't Available)

If you prefer PowerShell or CMD isn't accessible, the equivalent command is:

Restart-Computer -Firmware 

This performs the same reboot-to-firmware action as the shutdown command and requires administrator privileges.

What Affects Whether These Methods Work 🖥️

Not every system responds the same way to these commands. Several variables determine whether CMD-based BIOS access will work for you:

Firmware type matters most. The /fw flag only works on systems with UEFI firmware. Older machines — typically those running Windows 7 or earlier hardware — use legacy BIOS, which doesn't support this software-triggered approach. On those systems, you're limited to pressing the correct key during POST (Power-On Self-Test).

Windows version plays a role. This functionality was introduced with Windows 8 alongside UEFI support. Windows 10 and 11 support it reliably; Windows 7 does not.

Administrator privileges are required. Running CMD without elevation will return an "Access Denied" error. The command must be run from an elevated (administrator) session.

Fast Startup can interfere with traditional methods. Windows 10 and 11 use a Fast Startup feature that doesn't fully power down the system. This is part of why the traditional "press F2 at boot" approach sometimes fails — the system doesn't go through a full POST. The CMD method bypasses this entirely by flagging the next boot at the OS level.

Manufacturer key combinations still exist as fallback. If the CMD method doesn't work for any reason, knowing your device's BIOS key is useful. Common ones include:

These can vary even within the same manufacturer's product line based on the specific model and firmware version.

What Happens After the Command Runs

Once you execute shutdown /r /fw /t 0, your system will save a flag to the boot manager telling it to load firmware settings on the very next startup. Your PC restarts and drops directly into the BIOS/UEFI interface — no key timing required.

From there, navigation depends entirely on your firmware. UEFI interfaces are often graphical and mouse-compatible. Legacy BIOS screens are typically keyboard-only with arrow-key navigation. Changes you make don't take effect until you Save and Exit (usually F10 on most systems).

The Variable That Remains

Whether this approach works cleanly on your machine, and what you'll actually need to adjust once you're inside BIOS, comes down to specifics the command itself can't account for — your hardware generation, your firmware version, your Windows build, and what you're actually trying to change once you get there. The path in is consistent; what you do with it depends entirely on what your system's firmware exposes and what your situation actually requires.