Battlefield 6 “Secure Boot” Leak: How the New Anti-Cheat Tech Could Transform Gameplay

Electronic Arts has confirmed that Battlefield 6 will only launch on PCs with Secure Boot and TPM 2.0 enabled, a move tied to the publisher’s new kernel-level “Javelin” anti-cheat system. While the requirement is designed to block rootkits and other low-level exploits, it has ignited debate across the Battlefield community, especially among players running older hardware, Linux-based systems, and handheld devices such as the Steam Deck. The controversy gained momentum after EA updated its support page outlining that Secure Boot must be switched on in UEFI/BIOS before the game will even open. Within hours, Reddit threads exceeded a thousand comments, with many PC gamers reporting error codes during the closed alpha and demanding a more flexible solution. TechPowerUp’s report highlights fears that the Secure Boot mandate will “lock out” perfectly capable rigs built before 2018 or custom dual-boot setups, unless owners flash new firmware or replace motherboards altogether. Battlefield 6 is not alone. Activision has also confirmed that Call of Duty: Black Ops 7 will enforce the same Secure Boot and TPM 2.0 checks when its multiplayer beta drops later this year, signaling an industry-wide pivot toward hardware-bound anti-cheat protections. Security experts note that kernel-level solutions are harder to bypass, but player advocates worry about reduced modding freedom and potential privacy risks from always-on monitoring at the operating-system level. For those determined to join the Battlefield 6 open beta in September, enabling Secure Boot is usually a one-time tweak: • Press DEL, F2, or F12 during startup to enter UEFI/BIOS. • In “Boot” or “Security” menus, switch Boot Mode to “UEFI” if it’s set to Legacy/CSM. • Enable “Secure Boot” and, if prompted, install default platform keys (PK). • Save changes, reboot, and verify in Windows 10/11 by typing “System Information” and checking the Secure Boot State line. A full step-by-step tutorial with screenshots is already live on Windows Central for users unfamiliar with firmware menus. Players on Valve’s Steam Deck face a tougher road; the handheld’s BIOS currently lacks a Secure Boot toggle, meaning Battlefield 6 may remain unplayable on the device at launch unless EA issues a compatibility patch or rewrites its policy. Virtual machine users and dual-boot Linux gamers could also be sidelined, although community-made workarounds may appear as the beta progresses. EA insists that hardened boot-level validation is necessary to “level the playing field,” but backlash shows no sign of cooling. Expect the topic to dominate livestreams, forums, and social media as the first public tests begin next month. For now, the best way to avoid the Secure Boot error screen is a quick trip into BIOS—before the next Battlefield drops you back to the desktop.