shutdown /r /fw. This command triggers an immediate system restart and forces the computer to enter the BIOS/UEFI setup utility instead of loading the operating system. It is the fastest method for users who need quick access to firmware settings without manually pressing keys during startup or navigating through complex Windows recovery menus.
The Command Line Method
The most efficient way to access UEFI firmware from within a running Windows session is via the built-inshutdown utility. This tool supports specific flags that alter the behavior of the shutdown process. By combining the reboot flag with the firmware flag, you instruct the hardware to halt normal boot procedures and jump straight to the configuration screen.
To execute this, open the Start menu, type cmd, right-click on Command Prompt, and select Run as administrator. In the elevated window, type the following command and press Enter:
shutdown /r /fw
The system will immediately begin shutting down. Unlike a standard restart, which loads Windows again, this sequence tells the motherboard to intercept the boot process. You will see a brief black screen followed by the UEFI/BIOS interface. Note that this requires administrative privileges because it alters the fundamental state of the machine's power cycle. If you do not have admin rights, the command will fail with an access denied error.
Alternative GUI Path via Settings
If you prefer not to use the command line, Windows provides a graphical pathway to achieve the same result. This method is useful if you are unfamiliar with command syntax or if the/fw flag is somehow disabled in your specific build, though this is rare in modern versions of Windows 10 and 11.
Navigate to Settings > Update & Security (on Windows 10) or System > Recovery (on Windows 11). Look for the Advanced startup option and click Restart now. The computer will reboot into a blue menu titled "Choose an option." From there, select Troubleshoot, then Advanced options, and finally UEFI Firmware Settings. Clicking Restart here performs the exact same action as the command line method.
This path is particularly helpful when troubleshooting issues that prevent normal booting, such as those described in our guide on UEFI Laptop Won't Boot to Windows: C: Drive Changed, where accessing firmware settings is crucial for verifying drive detection.
Why Use the Command Line?
While the GUI method works well, the command line offers distinct advantages for advanced users and IT professionals. First, it is significantly faster. There is no need to navigate multiple layers of menus or wait for the "Choose an option" screen to load completely. Second, it allows for scripting. You can include theshutdown /r /fw command in batch files or PowerShell scripts to automate firmware updates or configuration changes across multiple machines.
Additionally, some systems may have the "Fast Startup" feature enabled by default. Fast Startup can sometimes interfere with the timing required to catch the key press for entering BIOS (like F2 or Del) during a cold boot. Using the /fw flag bypasses these timing issues entirely because the OS explicitly requests the firmware interface before the bootloader takes over.
However, be aware that this method does not work if Windows fails to load properly. If your system is stuck in a boot loop or crashes before reaching the desktop, you cannot run any commands. In such cases, you must rely on hardware keys or the Windows Recovery Environment (WinRE), which can be accessed via installation media or forced shutdowns. For more information on handling boot failures, see our article on Windows 11: Laptop Shows 'No Bootable Drives' After Restart; Apps Stopped Responding.
Troubleshooting Common Issues
Some users report that the command does not work or that the system boots back into Windows anyway. This is usually due to one of two reasons. First, ensure you are running the command prompt as an administrator. Second, check if your motherboard manufacturer has disabled the ability to jump to UEFI from Windows via software. This is uncommon but can happen on older or highly customized enterprise boards. Another issue arises if you have dual-boot configurations. Entering UEFI firmware settings will allow you to change the boot order, which might affect which operating system loads next. Be careful not to disable Secure Boot unless necessary for compatibility with other operating systems or older hardware drivers. Incorrectly changing these settings can lead to boot failures similar to those discussed in Unable to boot Windows 10 after converting MBR to GPT on HDD - Tech Support. Finally, remember that once you are in the UEFI interface, you can exit without saving changes if you simply want to verify settings. However, if you modify anything, ensure you save your changes before exiting, as improper configuration can render the system unbootable.Frequently Asked Questions
Can I use this command on Windows 7?
No, the /fw flag was introduced in Windows 8.1 and later versions. Windows 7 does not support direct jumping to UEFI from the command line. You must use the traditional method of pressing a key like F2, F10, or Del during the POST phase.
Will this command delete my data?
No, entering the UEFI firmware interface does not erase any files or partitions. It only changes the low-level hardware settings. Your operating system and personal data remain intact on the storage drives.
What if I miss the UEFI screen and boot into Windows?
If the system boots into Windows despite using the command, it likely means the firmware setting to allow OS-initiated entry was disabled by the manufacturer. In this case, you must use the Settings > Recovery method or restart normally and spam the BIOS key during startup.
Does Fast Startup affect this command?
Fast Startup generally does not block the /fw command because it forces a full shutdown rather than a hibernation-like state. However, if you experience issues, disabling Fast Startup in Power Options can ensure a clean handoff to the firmware.
How do I know if I am in UEFI or Legacy BIOS?
The interface design varies by manufacturer, but modern UEFI interfaces often support mouse input and graphical layouts. Legacy BIOS is typically text-only with keyboard navigation. If you see options like "Secure Boot" or "Boot Order" with a graphical list, you are likely in UEFI mode.