Battlefield 6 Will Not Launch with Secure Boot Enabled: Check Windows State

For Battlefield 6 still requesting Secure Boot after you enabled it in BIOS, or remaining blocked while Windows reports On. Compare the actual states before toggling settings.

No account needed. Saved only in this browser.

The short answer

Open Windows + R → msinfo32 and confirm BIOS Mode: UEFI and Secure Boot State: On. BIOS Enabled alone is not enough to assess Windows state. Restart after enabling and recheck. If On plus UEFI still fails, record the full error: use the Javelin guide for 94 and EA support for other messages rather than assuming a universal BIOS fix.

Different symptom or still not fixed? Find the next check →
Open My Games →Keep this game’s fixes handy. No account. This browser only.

Key facts

Read in Windows
msinfo32: UEFI / On
Error 94 appears
Check Javelin launch and installation
Before any change
Backup, recovery access and exact-model instructions

Find your symptom

Start with your symptom. Skip steps that do not apply to your setup.

What you seeWhat to checkGo to
BIOS Enabled; Windows not checkedRead msinfo32Step 1
Just enabled or not restartedRecheck after restart and read TPMStep 2
Off, Legacy or UnsupportedStop for model-specific guidanceStep 3
On plus UEFI still blockedUse the full message for escalationStep 4

Fixes, in order

Continue this issue

Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.

Step 1|Read Windows state in msinfo32

Distinguish it from BIOS Enabled.

Time: About 3–5 minutes to read and record · Risk: low

  1. Record the game’s complete message and time. Press Windows + R, enter msinfo32 and open System Information.
  2. Record BIOS Mode and Secure Boot State. For UEFI and On, continue to the restart check.
  3. For Off, Legacy, Unsupported or an unclear result, go to Step 3. Do not switch boot mode or CSM first.

Reading these fields needs no rollback. EA requires Secure Boot for Battlefield 6 on PC.

Step 2|Recheck after restart and read TPM

EA notes that another restart can be needed after enabling.

Time: Duration depends on the task and device · Risk: low

  1. Save work, restart the PC and read both msinfo32 fields again. Do not repeatedly toggle Secure Boot.
  2. Open Windows + R → tpm.msc and record status and Specification Version. EA’s preparation guide also checks TPM 2.0; read only, without clearing or initializing it.
  3. Record not-ready, 1.2 or not-detected results for the manufacturer. Do not speculate and switch TPM types even if On plus UEFI still fails.

A TPM message alone does not prove missing or failed hardware. Specification Version and Manufacturer Version are different.

Step 3|Prepare model-specific help and recovery

Do not fix mismatched states with generic firmware changes.

Time: About 3–5 minutes to read and record · Risk: low

  1. Give the manufacturer your exact PC/motherboard model and Windows readings. Stop here for Legacy, Unsupported or screens that differ from instructions.
  2. Before considering changes, back up important files and confirm access to the BitLocker/device-encryption recovery key from another device. Managed PCs go to their administrator.
  3. Make no change until the exact model’s official procedure and recovery steps are clear. Do not clear TPM, delete Secure Boot keys, convert disks or apply generic BIOS updates.

Never put recovery keys in public screenshots, feedback or support descriptions. Recovery also needs exact-model guidance.

Step 4|Use the remaining message to choose support

No universal fix is verified for every On-plus-UEFI case.

Time: About 3–5 minutes to read and record · Risk: low

  1. For Javelin (94), use its dedicated EA app launch and installation checks. Do not equate it with a Secure Boot fault.
  2. For other messages, give EA the full text, Windows version, model, both msinfo32 fields, TPM state/version and restart result.
  3. Record any settings already changed. Do not add key disclosure, disabled protection or unverified forum boot-mode changes.

Check an actual Javelin error 94

Avoid

  • Do not infer broken keys or a ban from continued failure with On
  • Do not clear TPM, delete Secure Boot keys or apply generic BIOS updates
  • Do not routinely switch Legacy/UEFI or convert disks

Important cautions

    FAQ

    Does BIOS Enabled guarantee Windows shows On?

    Do not assume the readings are identical. Follow EA’s msinfo32 check for BIOS Mode and Secure Boot State, and consult the exact-model manufacturer if they differ.

    What should I change if On plus UEFI still fails?

    No single change is verified for every case. Check the full post-restart message: use Javelin steps for 94 or send EA the recorded states for other messages.

    Sources

    We checked these official pages and wrote the steps in our own words. Follow the publisher’s page if it has changed.

    EA: Battlefield 6 Secure Boot requirementEA: Secure Boot checks and manufacturer guidanceEA: Battlefield 6 error messagesMicrosoft: BitLocker recovery keyBattlefield 6Japanese version of this page