How to Enable Secure Boot for Battlefield 6: What You Need to Know

Battlefield 6 — like several modern AAA titles with anti-cheat systems — requires Secure Boot to be enabled before you can launch the game. If you're hitting an error message at startup, or you're setting up a new PC and want to get ahead of the requirements, understanding what Secure Boot actually does and how to enable it will save you a lot of frustration.

What Is Secure Boot and Why Does Battlefield 6 Require It?

Secure Boot is a security standard built into your PC's firmware (UEFI) that verifies the software loading during startup is trusted and hasn't been tampered with. It checks digital signatures on bootloaders and system files before Windows even begins loading.

For games using kernel-level anti-cheat software — the type commonly used in competitive shooters — Secure Boot matters because it helps confirm the system environment hasn't been compromised at a low level. Cheating tools and unauthorized software often operate below the OS layer, and Secure Boot closes off some of those entry points.

Battlefield 6 follows the same enforcement pattern seen in titles like Valorant and Call of Duty: if your system doesn't meet the firmware security baseline, the game won't launch. This isn't a bug — it's intentional.

Before You Start: Check Whether Secure Boot Is Already On

Many modern PCs ship with Secure Boot enabled by default, especially systems purchased after 2020. Before diving into BIOS settings, check your current status:

1. Press Windows + R, type msinfo32, and hit Enter
2. In the System Information panel, look for Secure Boot State
3. If it reads On — you're already set
4. If it reads Off or Unsupported — you'll need to take further steps

The Unsupported result is important to flag separately, because it indicates a different problem than simply being disabled.

How to Enable Secure Boot in UEFI/BIOS 🔒

The process is consistent across most systems, though the exact menu layout varies by motherboard manufacturer (ASUS, MSI, Gigabyte, ASRock, Dell, HP, Lenovo, etc.).

Step 1: Enter your UEFI/BIOS Restart your PC and press the firmware key during boot. Common keys include Delete, F2, F10, or F12 — your screen may briefly show which key to press, or check your motherboard or laptop manual.

Step 2: Look for the Secure Boot setting Navigate to the Boot tab or Security tab depending on your firmware. Secure Boot is typically listed under one of these sections. On some systems it's nested under Advanced settings.

Step 3: Enable Secure Boot Toggle Secure Boot from Disabled to Enabled. If the option is grayed out, see the section below.

Step 4: Save and exit Select Save & Exit (often F10), confirm, and let the system reboot normally.

Why Is Secure Boot Grayed Out or Unavailable?

This is where setups diverge significantly. There are two common reasons Secure Boot can't simply be toggled on:

Your Drive Is Using MBR Instead of GPT

Secure Boot requires your Windows installation to be on a GPT (GUID Partition Table) disk, not the older MBR (Master Boot Record) format. Systems set up before Windows 10 — or certain older custom builds — may still be using MBR.

You can check this by:

• Opening Disk Management (right-click Start → Disk Management)
• Right-clicking your primary disk → Properties → Volumes tab
• Look at Partition style — it should say GPT

Windows 10 and 11 include a tool called mbr2gpt that can convert a disk non-destructively, but this carries risk and should be done with a full backup in place.

Your BIOS Mode Is Set to Legacy/CSM

If your firmware is running in Legacy BIOS or has CSM (Compatibility Support Module) enabled, Secure Boot cannot be activated. You'll need to:

1. Switch the boot mode to UEFI
2. Ensure your Windows installation supports UEFI boot (which ties back to the GPT requirement above)

Changing from Legacy to UEFI without the correct partition setup will prevent Windows from booting — so the order of operations matters here.

The Variables That Affect Your Specific Situation 🖥️

Whether enabling Secure Boot takes two minutes or two hours depends on factors specific to your machine:

Dual-boot users running Linux alongside Windows face additional complexity, since Secure Boot interacts with Linux bootloaders differently depending on the distribution and whether Shim/MOK keys are configured.

What "Unsupported" Actually Means

If msinfo32 shows Secure Boot State: Unsupported, your hardware may be too old to support it at all, or the firmware doesn't implement it in a way Windows recognizes. In those cases, simply flipping a BIOS switch won't resolve the problem — the system fundamentally doesn't meet the hardware baseline the game requires.

Some users in this situation have resolved it through a BIOS firmware update from their motherboard manufacturer, which sometimes adds or restores Secure Boot capability. Others have found their hardware simply doesn't support the requirement.

Whether a BIOS update is available, whether it's advisable for your specific board revision, and whether your overall system is worth updating versus replacing — those answers hinge entirely on what you're working with.