Battlefield 6 Anti-Cheat Secure Boot Error EA Javelin TPM Required

What is the Battlefield 6 Secure Boot Error?

Battlefield 6 uses EA's Javelin anti-cheat system, which operates at the kernel level to prevent cheating. When you launch BF6, Javelin verifies that your system has UEFI Secure Boot and TPM 2.0 enabled before allowing the game to start. If either is missing or disabled, the game displays "Secure Boot is not enabled" or "Anti-cheat error: platform security requirements not met" and refuses to launch.

This is not a bug — Javelin requires Secure Boot to verify that no unauthorized code (bootkits, rootkits, or cheat drivers) has modified the boot chain. TPM 2.0 provides hardware-backed attestation that the system is in a trusted state. Most PCs built after 2016 support both features, but they may be disabled in BIOS by default.

When does it occur?

• At game launch — BF6 closes immediately with an anti-cheat error dialog
• After a BIOS reset or CMOS clear that reverted Secure Boot settings
• On PCs where Windows was installed in Legacy/CSM mode with an MBR disk
• After upgrading a motherboard without reconfiguring UEFI settings
• On systems where Secure Boot is enabled but the OS boot mode is incompatible

Common causes

• Secure Boot is disabled in BIOS/UEFI firmware settings
• TPM 2.0 is not enabled or not present on the motherboard
• CSM (Compatibility Support Module) is enabled, which disables Secure Boot
• Windows was installed on an MBR-partitioned drive instead of GPT
• The motherboard firmware is outdated and has Secure Boot implementation issues
• Third-party software or custom drivers have placed unsigned components in the boot chain
• The BIOS OS Type is set to "Other OS" instead of "Windows UEFI Mode"

Step-by-step fixes

1. Check your current Secure Boot status — Press Win+R, type msinfo32, and press Enter. Look for "Secure Boot State" — it should say "On". Also check "BIOS Mode" — it must say "UEFI" (not "Legacy"). If Secure Boot is Off or BIOS Mode is Legacy, proceed to the next steps.

1. Enable Secure Boot in ASUS BIOS — Restart and press Del or F2 to enter BIOS. Go to Boot > CSM > set Launch CSM to Disabled. Then go to Boot > Secure Boot > OS Type and set it to Windows UEFI mode. Set Secure Boot State to Enabled. Save and exit (F10).

1. Enable Secure Boot in MSI BIOS — Enter BIOS with Del. Go to Settings > Advanced > Windows OS Configuration > set BIOS UEFI/CSM Mode to UEFI. Navigate to Settings > Security > Trusted Computing and enable Security Device Support (TPM). Then go to Settings > Security > Secure Boot and set Secure Boot to Enabled. Save and exit.

1. Enable Secure Boot in Gigabyte BIOS — Enter BIOS with Del. Go to BIOS > CSM Support and set it to Disabled. Navigate to BIOS > Secure Boot > Secure Boot Enable and set to Enabled. For TPM, go to Peripherals > Trusted Computing 2.0 and enable it. Save and exit.

1. Enable Secure Boot in ASRock BIOS — Enter BIOS with F2 or Del. Go to Boot > CSM and set it to Disabled. Navigate to Security > Secure Boot and set it to Enabled. For TPM, go to Security > Intel Platform Trust Technology or AMD fTPM and enable it. Save and exit.

1. Convert MBR disk to GPT (if BIOS Mode shows Legacy) — If your Windows was installed in Legacy mode, you must convert the boot disk from MBR to GPT. Open Command Prompt as administrator and run mbr2gpt /validate /disk:0 to check compatibility, then mbr2gpt /convert /disk:0 to convert without data loss. After conversion, enter BIOS and switch boot mode from Legacy to UEFI.

1. Enable TPM 2.0 — In BIOS, look for Intel PTT (Platform Trust Technology) under Security or Advanced > Trusted Computing, or AMD fTPM under AMD CBS > PSP Configuration. Enable the appropriate option for your CPU platform. Verify in Windows by pressing Win+R and typing tpm.msc — the TPM version should show 2.0.

1. Update motherboard BIOS firmware — Visit your motherboard manufacturer's support page, download the latest BIOS version, and flash it using the built-in BIOS update tool (e.g., ASUS EZ Flash, MSI M-Flash, Gigabyte Q-Flash). Outdated firmware can have broken Secure Boot implementations that Javelin rejects.

If it still doesn't work

If Secure Boot and TPM are both enabled but BF6 still won't launch, verify that no unsigned drivers are breaking the Secure Boot chain by running bcdedit /enum in an elevated Command Prompt and checking that testsigning is set to No. If you previously enabled test signing for modding or custom drivers, run bcdedit /set testsigning off and restart. For systems that genuinely lack TPM 2.0 or Secure Boot support (motherboards from before 2013), the only option is a hardware upgrade — Javelin does not offer a bypass. Check the EA Help page for BF6 system requirements for the latest compatibility updates.