UEFI OpROM policies determine whether the firmware initializes network (PXE) or storage controllers before handing control to the operating system. Setting these options correctly ensures that boot devices are recognized in time, prevents delays during POST, and allows for proper network-based installation or rescue environments.
What Are Option ROMs?
Option ROMs, often abbreviated as OpROMs, are small pieces of code embedded within expansion cards such as network interface cards (NICs), RAID controllers, and graphics cards. Their primary purpose is to provide basic initialization and driver services before the main operating system loads its full drivers. In a UEFI environment, these ROMs are executed during the Power-On Self-Test (POST) phase to prepare hardware for booting.
Without OpROMs, many legacy boot methods would fail because the BIOS/UEFI would not know how to communicate with specific hardware devices early enough in the startup sequence. Modern systems rely on these routines to present bootable devices to the user via the boot menu or to automatically attempt to boot from a specified device order.
PXE vs. Storage OpROM Policies
The two most common OpROM policy settings you will encounter in UEFI interfaces relate to Network (PXE) and Storage controllers. These settings control when and how the firmware attempts to launch the respective option ROMs.
PXE OpROM Policy
The PXE (Preboot Execution Environment) OpROM policy dictates whether the network card’s firmware is initialized during POST. When enabled, the system loads the NIC’s option ROM, allowing it to participate in the boot process. This is essential for:
- Network Booting: Allowing the computer to boot an operating system directly from a server over the LAN.
- Rescue Environments: Accessing diagnostic tools or recovery images hosted on a network share.
- Wake-on-LAN: Some implementations require the OpROM to be active for certain power management features.
If you do not need to boot from the network, enabling this can sometimes slow down the POST process slightly, as the firmware must wait for the network card to initialize and check for a boot server. However, on modern high-speed NICs, this delay is often negligible.
Storage OpROM Policy
Storage OpROM policies apply to SATA, NVMe, and RAID controllers. These settings determine if the controller’s firmware is launched to handle boot requests. For example, if you have a hardware RAID array, the RAID controller’s OpROM must be initialized so that the UEFI firmware can see the virtual drive as a bootable device.
In UEFI mode, many modern storage controllers no longer require traditional Legacy OpROMs because they use UEFI drivers (GOP or similar protocols) that are integrated into the motherboard firmware itself. However, some older RAID cards or specific configurations still rely on external OpROMs. If your storage OpROM policy is set incorrectly, you might find that your RAID array does not appear in the boot menu, even though the OS sees it after loading.
How to Configure OpROM Policies
Configuring these settings varies by manufacturer, but the general path is consistent across most major UEFI interfaces like ASUS, Gigabyte, MSI, and Dell.
- Enter UEFI Setup: Restart your computer and press the designated key (usually
Delete,F2, orF12) to enter the BIOS/UEFI setup utility. - Navigate to Advanced Settings: Look for tabs labeled "Advanced," "Boot," or "Peripherals." The exact location depends on your motherboard vendor.
- Locate OpROM Settings: You may find these under "PCI Subsystem Settings," "Network Stack Configuration," or "SATA Configuration."
- Select Policy: Choose between "Enabled," "Disabled," "UEFI Only," or "Legacy Only."
- UEFI Only: Recommended for modern Windows 10/11 installations. It skips the legacy initialization step, speeding up boot times.
- Legacy Only: Required for older operating systems or specialized hardware that does not support UEFI drivers.
- Auto: Lets the firmware decide based on available drivers.
- Save and Exit: Press
F10to save changes and reboot.
If you are troubleshooting a boot issue, ensure that the OpROM for your primary boot device is enabled. For instance, if you are trying to boot from a network drive, verify that the PXE OpROM is enabled. Conversely, if you are installing a new SSD and cannot see it in the boot menu, check the Storage OpROM settings.
Impact on Boot Performance and Compatibility
Enabling unnecessary OpROMs can increase boot time. Each OpROM requires memory allocation and initialization time. On systems with multiple PCIe cards, disabling unused OpROMs (like a secondary NIC you never use) can shave seconds off the POST duration.
Furthermore, compatibility issues often arise when mixing UEFI and Legacy modes. If your system is set to UEFI-only boot mode, attempting to enable Legacy OpROMs may result in errors or prevent the system from booting entirely. Always align your OpROM settings with your overall boot mode configuration.
For users who frequently update their firmware, keeping your UEFI/BIOS up to date is crucial. Newer versions often include improved OpROM handling and bug fixes that resolve boot detection issues. See our guide on Updating the UEFI / BIOS on an ASUS ROG MAXIMUS XIII HERO for detailed instructions on safely updating your firmware.
Troubleshooting Common Issues
If your system fails to boot from a specific device after changing OpROM settings, revert to the previous configuration. Sometimes, the issue is not the OpROM itself but the boot order or secure boot settings. Ensure that Secure Boot is configured appropriately, as it can block unsigned OpROMs.
If you suspect a hardware failure, test the device in another slot or system. In cases where you need to reset your UEFI settings due to misconfiguration, refer to resources like UEFI Password Reset for Gigabyte GA-H61M-S1 Motherboard for general reset procedures applicable to many boards.
Frequently Asked Questions
Does enabling PXE OpROM slow down my boot time?
Yes, slightly. The firmware must wait for the network card to initialize and poll for a DHCP server. On modern systems, this delay is usually less than two seconds, but on older hardware, it can be more noticeable.
Can I boot from a RAID array without a Storage OpROM?
In pure UEFI mode, many modern RAID controllers use built-in UEFI drivers rather than external OpROMs. If your controller supports this, you do not need the OpROM enabled. However, older hardware strictly requires the OpROM to be visible to the firmware.
What is the difference between UEFI Only and Auto for OpROMs?
UEFI Only forces the firmware to use native UEFI drivers, skipping legacy initialization. Auto allows the firmware to load either type depending on what is available. UEFI Only is generally faster and recommended for Windows 10/11.
Why doesn't my network card appear in the boot menu?
The PXE OpROM is likely disabled in the UEFI settings, or the network stack is turned off. Enable both the PXE OpROM and the Network Stack in the advanced settings to make it available for booting.
Is it safe to disable all OpROMs?
It is safe if you only boot from internal drives using native UEFI drivers. However, disabling them will prevent network booting and may hide legacy RAID arrays or older expansion cards from the boot selection menu.