Battlefield 6 Secure Boot and Javelin Anti-Cheat Error Fix

Battlefield 6 requires Secure Boot and TPM 2.0 to be enabled so EA Javelin anti-cheat can run — if either is off, or Windows is booting in Legacy mode, Javelin refuses to start and the game closes the moment you launch it. The Error 7 and Error 1053 messages both point at the same root cause: the anti-cheat could not verify a trusted boot path. This guide checks Secure Boot and TPM in Windows first, enables them in BIOS, then covers the Javelin-specific repairs (the anti-cheat installer, overlays, and the Legacy-mode edge case).

This is a boot-path requirement, not a hardware-power requirement. A brand-new gaming PC can fail it and a seven-year-old one can pass.

Step 1 — Check what Windows already reports

Do this before touching BIOS — half the time only one setting is actually missing, and you avoid a needless reboot into firmware.

Check Secure Boot:

1. Press Windows + R, type msinfo32, press Enter.
2. Read two rows: Secure Boot State and BIOS Mode.

What msinfo32 shows	What it means	What to do
Secure Boot State: On, BIOS Mode: UEFI	Correct	The problem is Javelin itself — jump to step 4
Secure Boot State: Off, BIOS Mode: UEFI	Just needs enabling	Enable Secure Boot in BIOS (step 3)
Secure Boot State: Unsupported, BIOS Mode: Legacy	Windows installed in legacy mode	Convert to GPT first (step 5)
Secure Boot State: Off, BIOS Mode: Legacy	Same as above	Convert to GPT first (step 5)

Check TPM:

1. Press Windows + R, type tpm.msc, press Enter.
2. Look for “The TPM is ready for use” and Specification Version: 2.0.
3. “Compatible TPM cannot be found” means it is disabled in BIOS, not physically absent — enable it in step 2.

Step 2 — Enable TPM 2.0 in BIOS

The setting is rarely labelled “TPM”. Look for the vendor name:

• AMD systems — AMD fTPM or AMD CPU fTPM, under Advanced → AMD fTPM configuration or Trusted Computing.
• Intel systems — Intel PTT (Platform Trust Technology), under Advanced → PCH-FW Configuration or Trusted Computing.
• Discrete TPM module — if your board has a physical TPM header, set Security Device Support to Enable and select the discrete option.

Save, reboot, and re-check tpm.msc. Vendor-specific menu paths:

• Enable TPM in ASUS BIOS
• Enable TPM in MSI BIOS
• Enable TPM in Gigabyte BIOS
• Enable TPM in ASRock BIOS

Step 3 — Enable Secure Boot in BIOS

Only enable Secure Boot after confirming BIOS Mode reads UEFI in msinfo32. Enabling it on a Legacy-mode Windows install leaves the machine unbootable until you switch it back.

1. Enter BIOS and switch to Advanced mode if your board opens in a simple view.
2. Find Secure Boot under Boot or Security.
3. Set OS Type to Windows UEFI mode.
4. If Secure Boot shows “Not active” with keys missing, use Restore Factory Keys or Install Default Secure Boot Keys.
5. Set Secure Boot to Enabled, then disable CSM (Compatibility Support Module) — Secure Boot cannot be active while CSM is on. Save and exit.

Vendor walkthroughs:

• Enable Secure Boot in ASUS BIOS
• Enable Secure Boot in MSI BIOS
• Enable Secure Boot in Gigabyte BIOS
• Enable Secure Boot in ASRock BIOS

Step 4 — Secure Boot is on but Javelin still errors (Error 7 / 1053)

If msinfo32 says Secure Boot State: On and tpm.msc says ready, but Battlefield 6 still throws a Javelin anti-cheat error, work through these in order:

1. Reboot fully — a cold boot, not a fast-startup resume. Javelin reads boot state captured at power-on, so a hybrid-shutdown resume can carry a stale reading.
2. Repair the anti-cheat installer. In your Battlefield 6 install folder (Steam: steamapps/common/Battlefield 6, or the EA app install path), find EAAntiCheat.Installer.exe, right-click Run as administrator, select Battlefield 6 from the drop-down, and click Update (or Repair). This reinstalls the Javelin service cleanly and fixes most Error 7 / 1053 loops.
3. Repair the game files. In the EA app, select Battlefield 6 → Manage → Repair. On Steam, use Properties → Installed Files → Verify integrity.
4. Close conflicting background apps before launching: RGB/lighting software, fan-control and overclocking tools (MSI Afterburner, Riva Tuner), monitoring overlays, audio-modifier apps, and macro tools. Javelin flags software that hooks into games or reads memory.
5. Install the latest Microsoft Visual C++ Redistributable from Microsoft’s official site — a missing or outdated runtime is a documented cause of Error 7/1053.
6. Update your GPU driver and Windows. A clean current driver from NVIDIA, AMD, or Intel removes a common launch-failure variable.
7. Disable any VPN or proxy while testing — some block the anti-cheat’s initial handshake.

Step 5 — If BIOS Mode says Legacy

Windows is installed on an MBR disk, so Secure Boot cannot be enabled until the disk is converted to GPT. Microsoft’s mbr2gpt does this in place, without reinstalling:

mbr2gpt /validate /allowFullOS
mbr2gpt /convert /allowFullOS

Run both from an elevated command prompt, /validate first. If validation fails, stop — do not run the conversion. After it succeeds, enter BIOS, switch boot mode from Legacy/CSM to UEFI, then enable Secure Boot.

Back up anything important first. The conversion is generally reliable, but it modifies the partition layout of your boot drive.

The AMD fTPM stutter caveat

Worth knowing before you flip fTPM on: some Ryzen systems develop a periodic system-wide stutter after enabling AMD fTPM, caused by the firmware TPM’s periodic access to SPI flash. It shows up as a brief freeze every few minutes, in games and on the desktop alike.

AMD fixed this in an AGESA update, so the answer is to update your motherboard BIOS to a version carrying that AGESA or newer. If your board has a discrete TPM header module, using that instead of fTPM sidesteps the issue completely — full detail in the AMD fTPM stutter fix.

Why Battlefield 6 requires this at all

Secure Boot and TPM 2.0 are not there to check your hardware is fast enough. They let EA Javelin verify a chain of trust: that the firmware loaded a signed bootloader, that the bootloader loaded a signed kernel, and that no unsigned driver was inserted underneath Windows.

That matters because the most capable cheats load below the game — as kernel drivers or bootkits — where a user-mode anti-cheat cannot see them. Requiring a verified boot path removes the easiest place to hide. The broader explanation is in why anti-cheat needs Secure Boot and TPM, and the trade-offs of kernel-level anti-cheat generally are in is kernel-level anti-cheat safe. Call of Duty imposes the same requirement — see the Modern Warfare 4 Secure Boot and TPM fix for the Ricochet equivalent.

Related guides

• Why Anti-Cheat Needs Secure Boot and TPM
• Is Kernel-Level Anti-Cheat Safe?
• Modern Warfare 4 Secure Boot and TPM 2.0 Fix
• Best Battlefield 6 Settings for FPS
• Battlefield 6 Stuttering Fix