How To Enable Secure Boot For Battlefield 6

It's a frustrating experience: you're ready to play, but Battlefield 6 stops you with a Secure Boot is Not Enabled error. This is a security check enforced by EA's Anti-Cheat, which requires a trusted system environment to stop cheaters. Don't worry, this is a common issue with a clear solution. In this guide, you'll learn how to enable Secure Boot for Battlefield 6, explaining the settings you need to change within your PC's firmware so you can get back to the game.

Why Battlefield 6 Now Requires Secure Boot

If you're wondering why this setting is suddenly mandatory, it's not just a decision by EA. This requirement is part of a larger, industry-wide shift in how developers combat cheating. For years, anti-cheat software has been in a cat-and-mouse game with cheat developers. As soon as an anti-cheat program was updated, cheaters would find ways to bypass it. Many modern cheats operate at the "kernel-level" (the deepest layer) of Windows, allowing them to load before the game's anti-cheat even starts. This makes them effectively invisible.

To fight this, games like Battlefield 6 and Valorant (with its Vanguard anti-cheat) are now leveraging security features built directly into your PC's hardware. They need to create a trusted environment to ensure the game and its anti-cheat system haven't been tampered with. This is where Secure Boot and TPM come in:

• Secure Boot acts as a security guard before Windows loads. It checks the digital signature of every piece of software trying to boot, from your drivers to the Windows kernel itself. If it finds a piece of unsigned code (like a cheat-loading rootkit), it blocks it from running.
• TPM (Trusted Platform Module) acts as a hardware-level safe. It holds cryptographic keys and can verify (or attest) that your system is in a clean, untampered state.

By requiring these two features, EA ensures that its anti-cheat is loading on a system that is verifiably clean. This isn't to make life difficult for players. Instead, it's a necessary technical step to block cheats at their foundation and, in the long run, provide a fairer, more stable playing field for everyone.

Preparing Your System for the Fix

Preparation is essential before working with your PC's firmware. You'll be changing sensitive settings that control how your computer boots. A few minutes of precaution can prevent hours of frustration. Here is what to do.

Critical: Check for BitLocker Encryption

If you use BitLocker drive encryption (common on Windows 10/11 Pro), you must find and save your 48-digit Recovery Key. Enabling TPM or Secure Boot changes your system's hardware fingerprint. BitLocker will see this as a security threat and lock you out on the next boot, demanding the key. You can typically find it saved to your Microsoft account.

Check for BIOS/FirmLoop Updates First

If your PC is a few years old, the TPM or Secure Boot options might be hidden, mislabeled, or entirely missing. A simple BIOS update often fixes this. Visit your motherboard manufacturer's support website (like ASUS, MSI, or GIGABYTE), find your specific model, and check for the latest BIOS/Firmware. Updating (following the official instructions carefully) can make the required settings magically appear and save you a lot of trouble.

Create a Windows Restore Point

As a final safety net, create a restore point. This saves the current state of your system files and registry. Click the Start button, type Create a restore point, and select the top result. In the "System Protection" tab, click "Create...", give it a name (e.g., "Before BIOS changes"), and click OK. This gives you a quick way to rewind if Windows acts strangely after the reboot.

Verifying Your System's Current State

Let's diagnose the problem. We need to check what Windows currently sees.

1. Press the Windows Key + R to open the "Run" dialog.
2. Type msinfo32 and press Enter.
3. The System Information window will open. Look for two specific lines: BIOS Mode and Secure Boot State.

Your goal is to have BIOS Mode set to UEFI and Secure Boot State set to On.

If BIOS Mode says Legacy, you have a more complex issue. You must address this first. See the Handling the 'Legacy' & CSM Complication section below.

Accessing the Command Center: Your BIOS/UEFI

The required settings are not exposed within the Windows OS. Configuration must be done directly in the system's BIOS/UEFI firmware.

• Restart your computer.
• As it is booting up (on the black screen with the motherboard logo), repeatedly press the correct key to enter the setup.

This key is different for each manufacturer. Here are the most common ones:

The First Component: Enabling the TPM (fTPM/PTT)

Once you are in the BIOS, your first task is to find and enable the TPM (Trusted Platform Module). This is a security feature that Secure Boot relies on.

• Look for menus named Security, Advanced, Peripherals, or CPU Configuration.
• The setting is rarely called "TPM." You are looking for: Intel PTT (Intel Platform Trust Technology) or AMD fTPM (AMD Firmware TPM).
• Set this option to Enabled.

The Second Component: Activating Secure Boot

Now for the main setting. This is usually in its own menu.

• Look for a menu named Boot, Security, or Secure Boot.
• Find the main Secure Boot option and set it to Enabled.

What If Secure Boot is Grayed Out or "Not Active"?

This is a very common problem. If you enable Secure Boot but it still shows as Not Active, you need to install the default security keys.

1. In the same Secure Boot menu, look for an option like Key Management.
2. Find the setting named Restore Factory Keys, Install Default Secure Boot Keys, or Reset to Setup Mode.
3. Select this option and confirm. The status should change to Active or Enabled, and the keys will show as Installed.

Handling the "Legacy" & CSM Complication

If msinfo32 showed your BIOS Mode as Legacy, you cannot enable Secure Boot. You must be in UEFI mode.

• CSM: In your BIOS, find an option called CSM (Compatibility Support Module) or Legacy Boot. You must Disable this.
• GPT Disk Warning: UEFI mode requires your Windows drive to use the GPT partition style. The older Legacy mode used MBR. If you disable CSM and Windows will not boot, it is because your drive is still MBR. You will need to use a tool (like Windows' mbr2gpt.exe) to convert your drive, which is an advanced process. Back up all your data before attempting this.

Finalizing and Confirming the Fix

You've changed the settings, now it's time to save and check your work.

1. Navigate to the Save & Exit tab in your BIOS.
2. Select Save Changes and Restart (or press the F10 key).
3. Your computer will reboot.
4. Once in Windows, it's a good idea to open msinfo32 one more time.
5. Confirm that Secure Boot State now reads On.

Launch Cleared

With BIOS Mode as UEFI and Secure Boot State as On, you have successfully secured your system. EA Anti-Cheat will now recognize your PC as compliant, and the Secure Boot Is Not Enabled error will be gone. Check the graphics settings in the game to match the capabilities of your hardware, and adjust everything to your preferences for a comfortable game. You are clear to launch Battlefield 6.

FAQ

What is Secure Boot Battlefield 6 and why does the game require it?

Secure Boot is a firmware feature that verifies trusted boot components, and Battlefield 6 uses it to reduce low level cheat vectors and improve launch integrity on PC.

How to enable Secure Boot for Battlefield 6 if the BIOS reads Legacy/CSM?

Switch the system to a true UEFI boot with a GPT system disk, then enable TPM 2.0 and install default Secure Boot keys so the state reads active in Windows.

Why do I get EA Secure Boot Battlefield 6 message on launch even after I enabled it?

This usually means keys are missing or CSM remains on. Restore factory keys, set mode to Standard or Windows UEFI, update firmware, then verify msinfo32 shows Secure Boot On.

Can I play without Secure Boot on PC 2025?

If the requirement is enforced you will not pass the integrity check. Enable UEFI, TPM 2.0 and Secure Boot so the game can launch normally on Windows.