When Windows says secure boot is not enabled, the problem is usually not Windows itself. The cause is often a mix of BIOS settings, a TPM check, or the system’s boot configuration after a firmware change, drive swap, or dual-boot install.
CompTIA A+ Certification 220-1201 & 220-1202 Training
Master essential IT skills and prepare for entry-level roles with our comprehensive training designed for aspiring IT support specialists and technology professionals.
Get this course on Udemy at the lowest price →Quick Answer
“Secure boot is not enabled” usually means Windows detects that your PC is booting in Legacy mode, Secure Boot is turned off in UEFI firmware, or the bootloader is incompatible. The safest fix is to confirm the boot mode first, back up important data, convert the system disk to GPT if needed, then enable Secure Boot in firmware and verify the state in Windows 10 or 11.
Quick Procedure
- Check whether Windows is booting in UEFI or Legacy mode.
- Confirm whether Secure Boot is currently off.
- Back up important files before changing firmware or partition settings.
- Convert the system disk from MBR to GPT if Secure Boot cannot be enabled.
- Open BIOS or UEFI setup and disable Legacy boot or CSM.
- Turn on Secure Boot, save changes, and restart.
- Verify Secure Boot State in Windows Security or System Information.
| Primary Issue | Secure Boot is disabled or unavailable in firmware as of November 2026 |
|---|---|
| Common Cause | Legacy BIOS mode, MBR disk layout, or bootloader conflict as of November 2026 |
| Typical Windows Versions | Windows 10 and Windows 11 as of November 2026 |
| Key Tools | System Information, PowerShell, diskpart, MBR2GPT as of November 2026 |
| Firmware Setting | Secure Boot, UEFI mode, and CSM/Legacy Boot controls as of November 2026 |
| Best Outcome | Secure Boot State shows On in Windows after reboot as of November 2026 |
Secure Boot is a firmware-level protection that helps Windows verify trusted boot components before the operating system loads. It shows up most often during startup, installation, or security validation after a firmware update, hardware upgrade, or dual-boot change.
The important part is to diagnose the cause before touching the machine’s firmware. A warning is not always the same as an error, and a compatibility issue is not always a failure; those differences matter because the wrong fix can break the boot configuration and leave the system unbootable.
This guide focuses on Windows 10 and Windows 11 systems, especially after motherboard changes, drive replacements, or BIOS settings changes. The goal is simple: identify what is blocking Secure Boot, fix it without data loss, and verify that Windows accepts the new security state.
What Secure Boot Does And Why Windows Cares
Secure Boot is a firmware feature in the UEFI startup process that helps stop unsigned or tampered bootloaders from loading. It checks digital signatures on boot components before the operating system starts, which reduces the risk of rootkits and early-stage malware.
Microsoft documents Secure Boot as part of the Windows trust chain, and the official guidance explains that Windows uses it with UEFI firmware and trusted keys to validate boot files. See Microsoft Learn and the UEFI specifications at UEFI Forum for the underlying model.
Windows cares because Secure Boot supports device security checks, BitLocker trust decisions, and compatibility validation. The feature is not just a checkbox in a settings screen; it is part of the system’s startup integrity chain.
Secure Boot, TPM, UEFI, and Legacy BIOS are not the same thing
These terms are often mixed together, but they do different jobs. A TPM check verifies the presence and status of the Trusted Platform Module, while Secure Boot verifies boot signatures, UEFI is the modern firmware environment, and Legacy BIOS is the older startup method.
- Secure Boot controls what bootloaders can start.
- TPM supports device identity, measured boot, and BitLocker features.
- UEFI is the firmware mode where Secure Boot usually works.
- Legacy BIOS usually prevents Secure Boot from being enabled.
For broader device and hardening context, Microsoft’s Windows security guidance is useful, and the NIST Cybersecurity Framework remains the most common reference for layered endpoint protection. In practical terms, Secure Boot protects the start of the chain, not the whole chain.
Common Symptoms And When The Error Appears
The error often appears in Windows Security, System Information, or during an operating system installation check. You may see messages such as “Secure Boot State: Off,” “Legacy Mode,” or a warning that the device does not meet security requirements.
It often shows up after a Windows update, a motherboard firmware update, a new SSD install, or a move between dual-boot configurations. A system that booted normally for months can suddenly report that secure boot is not enabled if the firmware settings were reset or the disk layout changed.
Some users disable Secure Boot on purpose. Gaming anti-cheat setups, Linux dual-boot environments, and enterprise imaging policies can all lead to Secure Boot being turned off intentionally.
Secure Boot errors are usually configuration problems, not hardware failures. That distinction saves time, because a good diagnosis can prevent unnecessary drive replacements or reinstallations.
Common indicators include Legacy Mode, CSM Enabled, or a Secure Boot State: Off result in Windows tools. Those clues tell you where to look: Windows, the firmware, or the bootloader.
Prerequisites
Before making changes, collect the basics. This reduces the chance of losing access to Windows or changing more settings than necessary.
- Administrator access to Windows.
- Physical or remote access to the PC’s BIOS or UEFI setup.
- A current backup of important files.
- Knowledge of whether the machine is used for dual boot, encryption, or enterprise management.
- Access to the motherboard or PC manufacturer’s support page.
- Optional but useful: a Windows recovery drive or installation media.
Warning
Do not change BIOS settings blindly. A wrong firmware change can stop the machine from booting, especially if the current boot configuration depends on Legacy mode or a custom bootloader.
If you are preparing for entry-level support work, this is the kind of hands-on troubleshooting covered in IT support training and in the CompTIA A+ Certification 220-1201 & 220-1202 Training path. It is also a common task in computer and network administration roles where a technician has to fix startup issues without touching user data.
How Do You Check Whether Secure Boot Is Actually Off?
You check Secure Boot status in Windows first, because the firmware menu is not the best place to start. The quickest method is System Information, which shows whether the machine is in UEFI or Legacy mode and whether Secure Boot is enabled.
- Press Windows key + R, type
msinfo32, and press Enter. - Find BIOS Mode and Secure Boot State in the summary pane.
- Note whether BIOS Mode says UEFI or Legacy.
- Open Windows Security and check Device Security for additional status details.
- If needed, open PowerShell as Administrator and run
Confirm-SecureBootUEFI.
If PowerShell returns True, Secure Boot is enabled. If it returns False or an error, the system either has Secure Boot disabled or is not booting in the correct firmware mode.
Microsoft documents the Confirm-SecureBootUEFI command in Microsoft Learn. That makes it a clean verification method when the GUI is ambiguous.
Verify Your Boot Mode And Firmware Support
BIOS Mode tells you whether Windows is booting in UEFI or Legacy mode. If it says Legacy, Secure Boot usually cannot be turned on until the boot mode is changed.
To confirm firmware support, open msinfo32 and look for the Secure Boot State line. If the machine says UEFI but Secure Boot is unavailable or unsupported, the firmware may need an update or the platform may not support it at all.
That distinction matters because some systems support UEFI without fully supporting Secure Boot. Older hardware can sometimes boot Windows just fine but still lack the key management or firmware hooks needed for Secure Boot.
| UEFI | Usually means Secure Boot can be enabled if the bootloader and disk layout are compatible. |
|---|---|
| Legacy | Usually means Secure Boot cannot be enabled until the system is converted to UEFI boot. |
For general Windows deployment compatibility, Microsoft’s hardware and boot guidance at Microsoft Learn explains why GPT and UEFI are the modern standard. If the machine is old enough to lack firmware support, the real fix may be a platform upgrade rather than a setting change.
Convert A Legacy Installation To UEFI When Needed
Secure Boot often stays unavailable if Windows was installed on an MBR disk using Legacy boot. In that case, the system may need to be converted to GPT so the firmware can boot in UEFI mode.
You can check the disk style in Disk Management or by using diskpart. In an elevated Command Prompt, run diskpart, then list disk; if the system disk does not show a GPT asterisk, it is likely using MBR.
- Back up important files and create a recovery plan.
- Open an elevated Command Prompt.
- Run
mbr2gpt /validate /allowFullOSto check whether conversion is possible. - If validation succeeds, run
mbr2gpt /convert /allowFullOS. - Reboot into firmware settings and switch the boot mode from Legacy to UEFI.
- Enable Secure Boot after confirming the conversion completed successfully.
Microsoft’s official documentation for MBR2GPT is the right reference for prerequisites and edge cases: Microsoft Learn. The tool is designed to convert the system disk without a full reinstall, but only when the disk and partition layout meet the rules.
Do not skip the backup step. Partition conversion is usually safe when done correctly, but a bad power event or a pre-existing disk problem can still create Data Loss.
Enter BIOS Or UEFI Setup Safely
Most systems let you enter firmware setup with a function key during startup. Common keys include F2, F10, F12, Esc, or Delete, but the exact key depends on the manufacturer.
Windows also provides a route through Advanced Startup. From Settings, open Recovery, choose Advanced startup, then select UEFI Firmware Settings if the option is available.
Before changing anything, record the current values or take photos of every firmware page you touch. That habit matters because some changes are not obvious once you have left the menu.
Change one firmware setting at a time. If the system stops booting, you will know exactly which change caused the problem.
This is also where good website administration and workstation support habits overlap with system administration. The same discipline used to document server changes should apply to a desktop’s boot configuration.
Enable Secure Boot In The Firmware Settings
Secure Boot is usually found under the Boot, Security, or Authentication menus. On many systems, the toggle remains hidden or grayed out until UEFI mode is active and Legacy boot or CSM is disabled.
- Enter the firmware setup menu.
- Set Boot Mode to UEFI.
- Disable CSM or Legacy Boot if it is enabled.
- Locate the Secure Boot option and switch it to Enabled.
- If prompted, load factory keys or restore default Secure Boot keys.
- Save changes and reboot.
On some systems, Secure Boot will not activate until the firmware uses standard keys instead of custom keys. That is why the “restore factory keys” option matters on certain motherboards and laptops.
After reboot, return to Windows and check whether Secure Boot State changed to On. If it did not, the firmware may not have saved the setting, or another boot option is still forcing a Legacy path.
Fix Common Firmware Roadblocks
One of the most frustrating cases is a Secure Boot option that exists but cannot be changed. That usually means the firmware is still in Legacy mode, CSM is still active, or the motherboard wants a specific admin password before exposing the setting.
Some vendors also hide Secure Boot until you clear custom keys or restore default keys. That is especially common on systems that were previously used in a custom-boot or enterprise-managed environment.
If the menu looks wrong or the option vanished after a failed change, update the BIOS or UEFI firmware from the motherboard or PC manufacturer’s support site. A firmware bug or outdated version can block the setting even when the hardware supports it.
Note
Updating firmware can solve Secure Boot problems, but it can also reset BIOS settings and change the boot configuration. Record the old values first so you can restore storage mode, fan settings, and boot order if needed.
For firmware best practices and update guidance, vendor documentation is the source of truth. If you are working with Microsoft-based endpoints, also check the platform vendor’s support pages before touching any security-related setting.
Handle Dual-Boot, Linux, And Third-Party Bootloaders
Dual-boot systems are a common reason Secure Boot fails to turn on. Even if Windows is compatible, a non-Microsoft bootloader can interfere with the chain of trust.
Some Linux distributions support Secure Boot through shim and signed kernels, while others need custom configuration. If the machine uses an older installer, an unsigned kernel, or a custom GRUB setup, Secure Boot may refuse to start that boot path.
Boot managers, disk encryption tools, and recovery partitions can also complicate the startup chain. If the system is trying to load a third-party entry before the Windows Boot Manager, Secure Boot may flag the configuration as untrusted.
- Make sure Windows Boot Manager is first in the boot order.
- Disable or remove unsupported boot entries that you no longer need.
- Confirm that any Linux loader is Secure Boot compatible.
- Check whether encryption or recovery software installed its own boot option.
For Linux compatibility details, see the Arch Wiki Secure Boot overview and official distro documentation. For enterprise risk context, the CIS Benchmarks are useful when standardizing boot settings across fleets.
How Do You Confirm The Fix In Windows?
You confirm the fix by verifying that Windows now reports Secure Boot as enabled. The simplest check is msinfo32, where Secure Boot State should read On.
Open Windows Security and check Device Security. A clean status there usually means the firmware change is being recognized correctly by the operating system.
Then restart the machine normally at least once or twice. A successful cold boot matters because a configuration that only works after one restart is still unstable.
- Open
msinfo32again. - Confirm BIOS Mode says UEFI.
- Confirm Secure Boot State says On.
- Restart the PC and test a full boot cycle.
- Check BitLocker or other security tools for warnings after the change.
Microsoft’s documentation for BitLocker and device protection is useful here because firmware changes can affect the way protected drives respond. If BitLocker is enabled, expect a recovery prompt only if the platform sees the change as significant.
What If Secure Boot Still Won’t Turn On?
If Secure Boot still refuses to enable, return to the basics. The machine may still be booting partly in Legacy mode, or the firmware may not have accepted the last setting change.
Resetting BIOS settings to defaults can clear a hidden conflict, especially after a failed firmware experiment. If the system has a corrupted or unusual boot entry, a default reset can restore the expected path.
Also check for pending firmware updates, chipset drivers, or motherboard utilities from the vendor. Some boards require a firmware refresh before Secure Boot becomes available or stable.
If the menu layout is unfamiliar or support status is unclear, contact the PC or motherboard manufacturer. That is the right move when the system is obscure, older, or built with nonstandard firmware options.
When Secure Boot will not turn on after a clean UEFI conversion, the problem is usually firmware support, stale keys, or an incompatible boot entry—not Windows itself.
Best Practices To Prevent The Error In The Future
The best prevention is to install Windows on GPT with UEFI from the start. That setup avoids most Secure Boot compatibility problems and makes future recovery easier.
Keep firmware updated, but document every BIOS or UEFI change during upgrades. A short note about what changed, when it changed, and why it changed can save hours later.
Avoid unnecessary bootloader changes unless they are required and understood. Custom dual-boot entries, old recovery tools, and ad hoc firmware changes are the fastest way to create a startup problem.
- Prefer UEFI and GPT on modern Windows deployments.
- Keep firmware and motherboard documentation handy.
- Back up before partition or firmware changes.
- Verify Secure Boot after any storage, boot, or OS upgrade.
This is the same kind of disciplined process used in network and system administration. It also comes up in support roles where technicians need to know what does a systems administrator do: they diagnose, document, and change only what is necessary.
Why This Matters For IT Support And Certification Prep
Secure Boot troubleshooting is a practical support skill, not an abstract theory topic. It touches startup behavior, firmware navigation, Windows security, disk partitioning, and recovery planning in one workflow.
That is why this task fits naturally into the hands-on troubleshooting work covered in CompTIA A+ Certification 220-1201 & 220-1202 Training. A technician who understands BIOS settings, TPM check results, and boot configuration changes can solve issues that look more serious than they are.
It also overlaps with broader computer and network administration responsibilities. Whether you are supporting a single laptop or a room full of endpoints, the ability to diagnose Secure Boot issues quickly saves time and prevents data loss.
For career context, the U.S. Bureau of Labor Statistics reports strong demand across computer support and systems-related roles as of November 2026. Salary data varies by role and region, but the technical skill set around startup integrity, system hardening, and secure deployment is consistently valued.
Key Takeaway
Key Takeaway
- Secure Boot is not enabled usually means the PC is in Legacy mode, Secure Boot is turned off, or the bootloader does not match the firmware’s trust rules.
- BIOS settings should be checked before making changes, because UEFI mode and Secure Boot settings are tightly linked.
- A failed TPM check is not the same problem as Secure Boot, but both can affect Windows security validation.
- Converting the disk to GPT and correcting the boot configuration are often required before Secure Boot can be turned on.
- Verification matters: Windows should show Secure Boot State On after a clean reboot, not just once in firmware.
CompTIA A+ Certification 220-1201 & 220-1202 Training
Master essential IT skills and prepare for entry-level roles with our comprehensive training designed for aspiring IT support specialists and technology professionals.
Get this course on Udemy at the lowest price →Conclusion
The most common causes of the Secure Boot error are Legacy boot mode, missing firmware support, disabled Secure Boot, or a bootloader conflict. The right order is always the same: diagnose first, switch to UEFI if needed, enable Secure Boot, then verify the result in Windows.
Secure Boot is a security feature, not just a Windows checkbox. It helps protect the earliest stage of startup, where rootkits and unauthorized bootloaders try to gain control before the operating system can defend itself.
If your firmware menus do not match the general steps, check the motherboard manual or the OEM support site before making more changes. For support professionals, that habit is part of solid troubleshooting; for learners, it is exactly the kind of practical skill that builds confidence in real Windows environments.
CompTIA® and Security+™ are trademarks of CompTIA, Inc. Microsoft® is a trademark of Microsoft Corporation.