How to fix a Secure Boot failure in WhyNotWin11
Understand the three Secure Boot states, why “Unsupported” usually means Legacy boot, and the safe order of changes to make Secure Boot available.

Secure Boot is one of the Windows 11 requirements that confuses people most. A PC can have Secure Boot switched off and still pass, while another PC with modern hardware fails because Windows reports Secure Boot as "Unsupported". The difference almost always comes down to how Windows was installed, not to the hardware itself.
This guide explains what Secure Boot does, how WhyNotWin11 reads it, what each state means, and the safe order of changes that makes Secure Boot available and enabled. It applies to WhyNotWin11 2.7.0.0 and to PCs running Windows 10 or Windows 11.
What Secure Boot does
Secure Boot is a feature of UEFI firmware. When the PC starts, the firmware checks that each piece of start-up software — the boot loader, and then the parts of Windows that load early — carries a trusted digital signature. If something has been replaced by an untrusted or tampered file, the firmware refuses to run it.
This protects against bootkits and rootkits: malware that hides in the start-up chain, loads before Windows and antivirus software, and is very hard to remove.
How the trust is organised
Secure Boot uses a small set of key databases stored in the firmware:
| Database | Purpose |
|---|---|
| Platform Key (PK) | The top-level key that controls who can change the other databases |
| Key Exchange Key (KEK) | Keys allowed to update the signature databases |
| Allowed signatures (db) | Signatures of boot software that may run |
| Forbidden signatures (dbx) | Signatures that are blocked, such as known vulnerable boot loaders |
Most PCs ship with the manufacturer's Platform Key and with Microsoft's keys in the KEK and db, so Windows boot loaders are trusted out of the box.
Setup mode and user mode
When a Platform Key is installed, the firmware is in user mode and Secure Boot can be enforced. If the keys have been cleared, the firmware is in setup mode, and Secure Boot cannot be turned on until the default keys are restored.
What Windows 11 actually requires
Microsoft's minimum requirement is that the system firmware is UEFI and Secure Boot capable. In other words, Windows 11 needs the PC to support Secure Boot; it does not strictly require it to be switched on at installation time. Turning it on is still recommended for the protection it provides.
How WhyNotWin11 reads Secure Boot
WhyNotWin11 reads the Secure Boot state that Windows records in the registry. Its logic is simple:
- If Secure Boot is enabled, the check passes.
- If Secure Boot is supported but disabled, the check also passes, because the PC is capable.
- If Windows cannot find a Secure Boot state at all, the check fails with "Disabled / Not Detected".
Windows only records a Secure Boot state when it boots in UEFI mode. That is why a PC booting in Legacy mode always fails this line, even if its firmware fully supports Secure Boot.
Step 1: Check your current state
System Information
- Press Win + R.
- Type msinfo32 and press Enter.
- In System Summary, read two lines: BIOS Mode and Secure Boot State.
| BIOS Mode | Secure Boot State | What it means | WhyNotWin11 |
|---|---|---|---|
| UEFI | On | Secure Boot is enabled | Pass |
| UEFI | Off | Capable, but switched off | Pass |
| Legacy | Unsupported | Windows boots through the compatibility path | Fail |
| UEFI | Unsupported | Firmware has no Secure Boot, or it is hidden | Fail |
PowerShell
In an administrator PowerShell window:
Confirm-SecureBootUEFI- True means Secure Boot is on.
- False means the PC boots in UEFI mode but Secure Boot is off.
- An error saying the cmdlet is not supported on this platform usually means Windows is booting in Legacy mode.
Step 2: Prepare
Step 3: Fix the boot mode first (if BIOS Mode shows Legacy)
Secure Boot cannot work in Legacy mode, so this is the most important step for most "Unsupported" results.
Convert the disk from MBR to GPT
UEFI boot requires a GPT system disk. Microsoft's MBR2GPT tool converts the disk without deleting files. Open Command Prompt as administrator and validate first:
mbr2gpt /validate /disk:0 /allowFullOSIf validation succeeds, convert:
mbr2gpt /convert /disk:0 /allowFullOSSwitch the firmware to UEFI
- Restart into firmware setup.
- Find the CSM (Compatibility Support Module) or Boot Mode setting.
- Disable CSM, or set Boot Mode to UEFI only.
- Save and restart.
Windows should start normally. Check msinfo32 again: BIOS Mode should now say UEFI, and Secure Boot State will usually say Off. At this point WhyNotWin11 already passes the Secure Boot line, because the PC is capable.
Step 4: Enable Secure Boot
- Restart into firmware setup again.
- Open the Secure Boot menu, often under Boot or Security.
- If the keys are missing or the firmware reports setup mode, choose Install default Secure Boot keys, Restore factory keys or similar.
- Set Secure Boot to Enabled. On some boards this is done by setting OS Type to Windows UEFI mode.
- Save and restart.
After Windows starts, msinfo32 should show Secure Boot State On, and Confirm-SecureBootUEFI should return True.
Manufacturer-specific notes
Firmware menus vary. These are typical patterns, not exact instructions for every model.
Desktop motherboards
- Secure Boot is often under Boot → Secure Boot or Security → Secure Boot.
- Some boards only show the Secure Boot option after CSM is disabled.
- An OS Type setting may switch between "Other OS" (Secure Boot off) and "Windows UEFI mode" (Secure Boot on).
Branded laptops and desktops
- Look under Security or Boot for Secure Boot and Legacy Support or Boot List Option.
- Some models require an administrator or supervisor password to be set before Secure Boot settings can be changed.
If the screen stays black after disabling CSM
Older graphics cards may lack UEFI firmware support (called GOP). With CSM disabled, such a card shows nothing during start-up.
How to recover
- If the processor has built-in graphics, connect the monitor to the motherboard's video output and change settings from there.
- Reset the firmware to defaults by clearing CMOS, using the jumper or button described in the motherboard manual. This normally re-enables CSM.
- Plan to replace the graphics card with a model that supports UEFI.
Other reasons Secure Boot stays unavailable
| Situation | What is happening | What to try |
|---|---|---|
| Option greyed out | CSM still enabled, or a firmware password is required | Disable CSM; set a supervisor password if required |
| Secure Boot enabled but Windows says Off | Keys missing (setup mode) | Restore default or factory keys |
| PC will not boot with Secure Boot on | Unsigned boot loader or old add-in card firmware | Remove other boot loaders; update card firmware |
| Option missing entirely | Very old firmware | Update the BIOS from the manufacturer |
Dual-boot systems
If you also run Linux or another operating system, check that its boot loader supports Secure Boot. Many current Linux distributions do, using a Microsoft-signed first-stage loader, but older or custom setups may not start once Secure Boot is on.
Re-running WhyNotWin11
After the changes, run WhyNotWin11 again with administrator rights. The Secure Boot line should show Enabled or Supported. Check the Boot Method and Disk Partition Type lines too; they should now read UEFI and GPT.
How Secure Boot fits with other Windows protections
Secure Boot is one layer in a chain of protections that start before Windows and continue after it has loaded.
| Layer | What it does |
|---|---|
| UEFI firmware | Starts the PC and enforces Secure Boot |
| Secure Boot | Allows only trusted, signed boot software to run |
| TPM measurements | Record what loaded so tampering can be detected |
| BitLocker | Releases the drive key only when the start-up chain looks as expected |
| Windows security features | Use the trusted start-up as a foundation |
Because BitLocker relies on the start-up chain looking the same each time, changing Secure Boot or the boot mode can trigger a recovery prompt. That is why suspending BitLocker before changes matters.
Keeping Secure Boot current
Microsoft occasionally updates the forbidden-signatures database (dbx) and Secure Boot certificates through Windows Update to block vulnerable boot software. Keep Windows Update running, and install firmware updates from your PC or motherboard maker when they are offered.
A checklist for a smooth change
- Files backed up to an external drive or the cloud.
- BitLocker recovery key saved and protection suspended.
- Current firmware settings photographed.
- msinfo32 shows BIOS Mode and Secure Boot State before you start.
- Disk converted to GPT if BIOS Mode was Legacy.
- CSM disabled and the PC confirmed to start in UEFI mode.
- Default Secure Boot keys installed if the firmware was in setup mode.
- Secure Boot enabled and confirmed with msinfo32 or Confirm-SecureBootUEFI.
- WhyNotWin11 run again as administrator.
Secure Boot on virtual machines and test PCs
If you test Windows 11 in a virtual machine, Secure Boot is a property of the virtual machine's firmware. In Hyper-V, a Generation 2 virtual machine offers Secure Boot with a Microsoft Windows template. Other virtualisation products have similar settings. WhyNotWin11 run inside the virtual machine reports the virtual firmware's state, so enabling Secure Boot there does not tell you anything about your physical PC.
Signs everything worked
- msinfo32 shows BIOS Mode UEFI and Secure Boot State On.
- Confirm-SecureBootUEFI returns True in an administrator PowerShell window.
- Windows starts without a BitLocker recovery prompt, or you entered the key once and protection is resumed.
- WhyNotWin11 shows Secure Boot Enabled, Boot Method UEFI and GPT Detected.
If Secure Boot State still says Off, return to the firmware and check that the keys are installed and Secure Boot is enabled, not just "available".
Summary
"Unsupported" almost always means Legacy boot. Back up, convert the disk to GPT, switch the firmware to UEFI, restore default keys if needed, and enable Secure Boot. WhyNotWin11 passes as soon as the PC is capable, but turning Secure Boot on gives you the protection it was designed for.
Frequently asked questions
Does Windows 11 need Secure Boot turned on?
The requirement is that the PC is Secure Boot capable. Enabling it is still recommended because it protects the start-up process.
Will enabling Secure Boot erase my data?
No. Turning on Secure Boot does not touch your files. Converting the disk to GPT is the step that deserves a backup, even though MBR2GPT is designed to keep data intact.
Why does WhyNotWin11 pass Secure Boot when it is disabled?
Because WhyNotWin11 checks capability, matching Microsoft's requirement. A supported-but-disabled state proves the PC is capable.
Can I go back to Legacy mode later?
Yes, but a GPT disk will not boot in Legacy mode. Keep the PC in UEFI mode once the disk is converted.
Is Secure Boot the same as the TPM?
No. Secure Boot checks start-up software signatures in the firmware; the TPM stores keys and measurements. Windows 11 needs both, and they are enabled separately.
Why does my firmware ask for a password before changing Secure Boot?
Some manufacturers protect security settings with a supervisor or administrator password. Set one in the firmware's security menu, change Secure Boot, and keep the password somewhere safe.
What is the difference between "Restore factory keys" and "Clear keys"?
Restoring factory keys installs the default Platform Key and Microsoft keys so Windows can boot with Secure Boot on. Clearing keys puts the firmware into setup mode, which disables Secure Boot. For Windows 11, use the restore option.
Can a virtual machine pass the Secure Boot check?
Yes, if the virtual machine uses UEFI firmware with Secure Boot enabled. In Hyper-V that means a Generation 2 virtual machine with Secure Boot turned on in its settings.
Does enabling Secure Boot slow the PC down?
No. The signature checks happen during start-up and do not affect everyday performance.