BF6 Secure Boot Error: 7 Fixes That Actually Work in 2026

The "Secure Boot is not enabled" error stops Battlefield 6 from launching because the game detects that your platform security doesn't meet EA Javelin anti-cheat requirements — it checks for a UEFI boot chain with Secure Boot and related protections, and in most cases the fix is a 15-minute BIOS change rather than anything wrong with the game. The annoying part is the opportunity cost: every evening you spend in BIOS menus is an evening of Season 4 XP you don't earn, which is exactly why some players hand the grind off to a BF6 weapon leveling boostfrom $19.99 while they sort their rig out.

Let me be blunt about the ceiling here, because a lot of guides won't: on PC there are no workarounds — Battlefield 6 won't launch unless Secure Boot is enabled. This is a design decision, not a bug. EA's position is that Secure Boot lets Javelin-supported games detect and remove bad actors, resulting in fewer cheaters. So the goal isn't to bypass the check — it's to make your system pass it as quickly as possible.

Quick-fix checklist (best to worst time-to-value)

Run these in order. I've ranked them by how many players they fix per minute spent.

1. Confirm what's actually broken with msinfo32 — 2 minutes, tells you which of the three requirements is failing.
2. Enable Secure Boot in BIOS in the correct order — 15 minutes, fixes the clear majority of cases.
3. Restore factory Secure Boot keys if the setting reads "Inactive" — 5 minutes.
4. Convert your boot drive from MBR to GPT with mbr2gpt — 20–30 minutes, needed if you're on Legacy/CSM.
5. Verify TPM 2.0 and update chipset/ME firmware — 20 minutes, the fix for the newer post-update wave.
6. Remove or update an incompatible kernel driver — 10 minutes, if you're getting a Security Violation notice instead.
7. Repair the install and the anti-cheat service — 15–40 minutes depending on your connection.

Do steps 1–3 before you touch anything destructive. Roughly speaking, if msinfo32 already shows UEFI mode, you can skip the partition conversion entirely and save yourself half an hour.

1. Diagnose first: msinfo32

Press Win+R and run msinfo32. You want BIOS Mode reading UEFI and Secure Boot State reading On. If it says Legacy, you'll need to convert to UEFI; if it already says UEFI, skip ahead. Also check your disk: open diskmgmt.msc, right-click Disk 0, then Properties and the Volumes tab to see whether the partition style is GPT or MBR.

This step costs two minutes and decides whether your evening is a 15-minute job or a two-hour one. Skipping it is the single most common time-waster I see in forum threads.

2. Enable Secure Boot — order matters

The fastest route into firmware: open the Start menu, click the Power icon, hold Shift and click Restart, then choose Troubleshoot, Advanced options, UEFI Firmware Settings, and Restart.

Once you're in, sequence matters. Community guides converge on this order: disable CSM, enable TPM, set OS Type to Windows UEFI Mode, and enable Secure Boot last. Why last? Enabling it too early can cause a black-screen boot failure. If that happens, a CMOS clear or GPU bypass gets you back — unpleasant but recoverable.

Verdict: highest value fix on the list. Most modern boards pass immediately afterwards.

3. Secure Boot shows "Inactive"? Restore the keys

This one catches people out. The toggle says Enabled, the game still refuses. If Secure Boot is listed as "Inactive", go to Key Management and restore factory keys to activate it. If the option is locked or greyed out, resetting Secure Boot keys to defaults or setting a BIOS admin password can unlock it, and brand-specific steps vary by motherboard.

4. MBR to GPT conversion

If msinfo32 said Legacy, your drive is almost certainly MBR. The boot drive must use GPT rather than the older MBR format, and Microsoft's mbr2gpt command converts it without data loss. Back up your data first anyway — the tool is reliable, but boot-layer changes deserve a safety net.

Time-vs-value: 20–30 minutes, and it's the only path forward for Legacy installs. Compare that to a clean Windows reinstall in UEFI mode, which is a 2–4 hour job. Try the conversion first.

5. TPM 2.0 and the post-update attestation wave

Here's the part that isn't fully settled. Check TPM by running tpm.msc and confirming TPM 2.0 is active. But since early September 2026, a smaller group of players report the error appearing on systems that were previously working fine — one report describes BF6 refusing to launch with the Secure Boot message after a September 4, 2026 update despite Secure Boot State showing On, UEFI mode, GPT, TPM 2.0 initialised, and updated BIOS and Intel ME/PTT firmware. Digging further, the same troubleshooting turned up broken TPM attestation with no Intel EK manufacturer certificate.

To be clear: that is a user report under investigation, not a confirmed developer-acknowledged bug. If you're in this bucket — older chipset, firmware-based TPM (Intel PTT / AMD fTPM), everything green in Windows — updating chipset and management-engine firmware is the lever worth pulling, and after that it's a support ticket rather than more BIOS roulette.

6. Security Violation instead of Secure Boot?

Different message, same family of problem. Javelin also blocks specific kernel drivers: players report a Security Violation notice stating that EA AntiCheat detected an incompatible driver and asking them to update or disable it, with error 119 — in that example an EVGA kernel driver. Read the path in the message, update or uninstall that utility, reboot, relaunch. This is confirmed behaviour by design, not a glitch.

7. Repair the install and anti-cheat service

Last on the list because it's the lowest hit rate for this specific error. Once your hardware configuration is correct, verify game files and reinstall the anti-cheat service if errors persist, and repair the game or EA App if needed.

If nothing works

Two honest outcomes exist. First, hardware limits: some older motherboards support UEFI but lack Secure Boot or key management, and if that's your board the error will persist even after switching to UEFI and converting to GPT — leaving compliant hardware or an upgrade as the only options. Second, an unresolved backend or firmware edge case, which belongs in a ticket. EA's Battlefield 6 technical issues forum exists specifically for connectivity, performance and crash problems, and it's the fastest way to find out whether others share your exact chipset.

Console players seeing something similar aren't imagining it either — PS5 users have reported update 1.000.009 downloading correctly but failing to install with error CE-100095-5, which appears to affect multiple consoles and may relate to the update package itself.

Quick answers

Is the Secure Boot requirement ever going away? Unlikely. EA mandates Secure Boot on PC for anti-cheat integrity, meaning your PC needs Secure Boot and TPM 2.0 enabled to run the game. Treat it as permanent and configure once.

Will enabling Secure Boot break my other games or dual boot? Standard Windows setups are fine. Dual-boot and unsigned-driver setups are where friction appears, since Secure Boot checks the digital signature of software trying to boot and blocks unsigned code. Plan around your Linux bootloader before flipping it.

How much progress am I losing while I'm locked out? During an active phase, quite a lot — the Top Gun phase is live now, with Tidal Strike scheduled as the final phase on September 15, and event windows don't pause for your BIOS. If your XP looks wrong after you get back in, that's a separate issue covered in our BF6 weapon XP not tracking fixes.

Bottom line

Ranked purely on time-to-value: diagnose with msinfo32, enable Secure Boot in the CSM-then-TPM-then-Secure-Boot order, restore factory keys if it reads Inactive. That sequence resolves most cases inside 20 minutes. Partition conversion is worth the extra half hour; a full Windows reinstall almost never is until you've exhausted firmware updates. And if your board genuinely lacks Secure Boot support, no guide on the internet can fix that — budget for hardware instead of hours.

The frustrating math is that a lockout during a limited-time phase costs you progression you can't earn back later, and mastery grinding is 10+ hours per weapon at normal pace. If you'd rather not lose the phase while you're troubleshooting firmware, our Battlefield 6 weapon leveling servicefrom $19.99 can keep the mastery grind moving, and BF6 bot lobbiesfrom $14.99 are there for when you're back online and want to make up ground fast.