BIOS & UEFI,
option by option.
The setup screen is the one place where a wrong click can leave a machine that does not boot, with no operating system available to undo it. Every vendor renames the same options, so this reference is organised by what the option gates rather than by the label you happen to see.
Two rules before you change anything.
In the firmware screen there is no undo — there is only what you remember.
Windows can roll a driver back because it kept the previous copy. The setup utility keeps nothing. The moment you press the wrong option and save, the machine either boots differently or does not boot, and the only record of the old value is the photograph you took.
So: photograph every screen you change before changing it, and change one option per visit. If something goes wrong, that photograph is the difference between a two-minute recovery and a reinstall.
- BitLocker is the trap. Several options below — TPM, Secure Boot, CSM — can make the recovery key mandatory on the next boot. If the drive is encrypted and you do not have the key, do not touch them.
- Getting in without guessing. In Windows: Settings → System → Recovery → Advanced startup → Restart now → Troubleshoot → UEFI Firmware Settings. That route is the same on every machine, unlike the Del/F2/F10/F12 lottery at power-on.
- A password on the setup itself is a different thing from a Windows password. Forget the supervisor password on some boards and the firmware is bricked to changes, not to Windows.
- «Optimized Defaults» is a real escape hatch. It is usually the fastest way back from a machine that stopped booting after you experimented — it does not touch your data.
The options.
Each entry names the concept first and then the labels it hides under. Search the page for the wording your screen actually uses.
Secure Boot
- What it is
- A signature check performed by the firmware before it hands control to the bootloader. Its only job is to refuse bootloaders that are not signed by a certificate the platform trusts.
- What changes
- On, it blocks operating systems and boot media that are not signed — some Linux installers, older recovery USBs, a dual-boot set up years ago. Off, Windows 11 keeps running but loses the attestation some anti-cheat and enterprise tools demand, and BitLocker's protection becomes dependent on a separate policy.
- Risk
- Careful Turning it off on an encrypted drive can trigger a BitLocker recovery prompt at the next boot. Have the key before you test it.
Boot mode: UEFI against Legacy / CSM
- What it is
- Whether the firmware boots the modern way (reading an
EFIfolder from a GPT-partitioned disk) or emulates the old BIOS (MBR disks, option ROMs). «CSM» is the compatibility module that provides that emulation. - What changes
- This is the option that makes a working Windows «disappear». Windows installed in UEFI mode will not boot in Legacy mode and the other way round; the disk is untouched, the firmware simply stops finding the bootloader. It also caps you at one 4K monitor without a proper GOP driver, and it is why the drive sometimes vanishes from the boot list entirely.
- Risk
- Expensive Not data loss — but a machine that looks dead until someone puts the mode back, which is hard to diagnose precisely because the drive is still listed in the firmware.
TPM — Security Device Support, fTPM, AMD fTPM, Intel PTT
- What it is
- The chip (or firmware feature) that holds keys bound to this machine. «Discrete TPM» is a physical part; «fTPM» and «PTT» are the same interface implemented inside the CPU or chipset, which is why the label depends on your vendor.
- What changes
- Disabled, anything sealed to it stops working: BitLocker, Windows Hello, and the credential guard that protects saved tokens. Windows 11 also stops reporting the device as compliant. Enabling a cleared TPM is harmless; disabling one that keys are already sealed to is where the recovery prompt comes from.
- Risk
- Expensive The one firmware option that can lock you out of your own data permanently if the drive is encrypted and the recovery key is not somewhere else.
Virtualisation — Intel VT-x, AMD-V, SVM Mode
- What it is
- The CPU feature that lets a hypervisor run guest operating systems. Firmware label varies wildly: SVM on AMD boards, VT-x or «Intel Virtualization Technology» on Intel, «Virtualization» under an Advanced or CPU page.
- What changes
- Off, Hyper-V, Virtual Machine Platform, Windows Sandbox, WSL2, Docker Desktop and every third-party emulator refuse to start. On, nothing visible changes at all except those tools begin working. It has no meaningful effect on gaming performance on a current machine.
- Risk
- Reversible The least dangerous option on this page. One reboot and it is applied either way.
VT-d / AMD-Vi — IOMMU
- What it is
- The companion feature that lets a virtual machine own a physical device directly — GPU passthrough, NVMe passthrough — instead of going through the host.
- What changes
- Off, device assignment cannot work and VMs see emulated hardware. On, you gain the possibility and, in rare configurations with certain chipsets, lose the ability to use an older PCIe device in the host. For anyone not running a hypervisor it does nothing.
- Risk
- Reversible Leave it alone unless you are building a passthrough VM.
Fast Boot
- What it is
- The firmware skipping parts of initialisation — USB stack training, memory retraining, some POST checks — so the machine reaches the bootloader sooner. Not the same thing as Windows' own «Fast startup», which is a hibernation of the kernel session.
- What changes
- Enabling it can make the setup key press impossible at power-on, a USB keyboard unresponsive until Windows loads, and a bootable USB never offered. When you cannot get into the firmware «for no reason», Fast Boot is the usual answer.
- Risk
- Careful Annoying rather than destructive: the Advanced-startup route above reaches the firmware regardless of how fast the machine boots.
XMP, DOCP, EXPO — the memory profile
- What it is
- A pre-tested overclock stored in the memory module's own chip. Intel calls the standard XMP; ASRock and some AMD boards label it DOCP; DDR5 AMD boards call it EXPO. Out of the box, memory runs at the slow JEDEC speed, not the speed on the box.
- What changes
- Enabling it raises frequency and tightens timings to the module's advertised values. If the kit, the motherboard and the CPU memory controller do not agree, the machine fails to boot or restarts during training — and the fix is to clear CMOS, which is why this is the entry that needs a photograph.
- Risk
- Careful Recoverable, but the recovery may mean opening the case or shorting the jumper. Enable one profile level at a time, not the top one by default.
SATA mode — AHCI against RAID / Intel RST / IDE
- What it is
- How the storage controller presents its disks. AHCI is the plain standard. RAID and «Intel RST / VMD» put the disks behind the vendor's controller driver. IDE is a legacy compatibility mode.
- What changes
- Switching the mode after Windows is installed produces the most dramatic failure available here: an
INACCESSIBLE_BOOT_DEVICEstop, because the storage driver Windows loaded no longer matches the controller it is talking to. The disk is fine. The boot is not. - Risk
- Expensive Only change it with a plan to get Windows into safe mode first, or with the vendor's driver ready. On many OEM machines RST is on by default and turning it off is what breaks the system.
Above 4G Decoding / Resizable BAR / Smart Access Memory
- What it is
- Letting the CPU address the graphics card's whole frame buffer at once instead of a 256 MB window. «Resizable BAR» is the PCIe mechanism; «Smart Access Memory» is AMD's marketing name for it; «Above 4G Decoding» is the firmware prerequisite.
- What changes
- On supported GPU and CPU pairs, a free frame-rate improvement in some games and worse performance in a few others. If it is already enabled by default on an OEM board there is usually no reason to touch it.
- Risk
- Careful Enabling Resizable BAR without CSM disabled, or on an older GPU, can stop the machine posting at all. Same recovery as XMP.
Boot order / Boot option #1
- What it is
- The sequence the firmware tries when looking for a bootloader. «Boot option #1» is the first one it attempts, and it is a different setting from the one-time boot menu key.
- What changes
- Nothing about the disk, only which one is tried first. A USB stick left in the machine while you were reinstalling something can quietly become the first entry, and «Reboot and select proper boot device» is what that looks like from the outside.
- Risk
- Reversible The safest thing to change. If the machine stops booting after you reordered, put the Windows entry back — or just remove the USB drive.
Load Optimized Defaults / Restore Defaults / Clear CMOS
- What it is
- The factory configuration for the firmware. Inside the setup it is a menu item; outside it is the jumper or the coin-cell battery that empties the settings from a powered-down board.
- What changes
- Everything on this page returns to its vendor default at once — which is exactly why it is the recovery for a machine that stopped posting after an experiment. It does not touch the disk. It can reset the system clock, drop your boot order, disable XMP, and on some boards clear a stored supervisor password (which is the intended way back from forgetting one).
- Risk
- Careful Reversible in the sense that you can reconfigure again — but if you had undocumented firmware settings for a specific device, those notes are gone too.
Adjacent screens.
Firmware changes surface as operating-system errors, which is why this page is read next to these two.
Driver errors, translated
What «this device cannot start» and Code 43 actually claim, and the four buttons that get confused.
Read the reference every appWhat this dialog box is asking
The recovery and signature prompts that appear when a boot setting has gone wrong.
Read the reference the productToolTip AI Aura
Vendor setup utilities label the same option four different ways across four generations of board. The radar reads whatever the screen in front of you says.
Read about Aura the libraryAll guides
One hundred and fifty-six entries across thirteen families of screen, each with the same three fields.
Back to the indexThere is no «BIOS screen». There are two hundred.
Award, the reference here covers what the options do. It cannot cover the exact wording your board's firmware uses, or the setting a small vendor invented last year. That is the screen the application is built for.
Get ToolTip AI on Microsoft Store