What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The fix is usually outside Battlefield 6. EA’s current guidance requires a compatible PC to boot Windows through UEFI, use a GPT Windows disk, have TPM 2.0 enabled, and report Secure Boot: On. Check those four conditions before changing firmware settings. In particular, do not disable Legacy/CSM on an MBR Windows installation until you have converted it or confirmed the correct recovery procedure.
Battlefield 6 uses EA Javelin Anti-Cheat, which checks the system’s boot-security configuration before launch. Windows 11 by itself does not prove that Secure Boot is enabled. See EA’s Secure Boot requirements and its Battlefield 6 error-code guidance.
As an Amazon Associate I earn from qualifying purchases.
Check your current configuration first
Use Windows to identify the problem before entering UEFI firmware.
1. Check BIOS Mode and Secure Boot State
- Press Windows + R.
- Type
msinfo32and press Enter. - In System Summary, find BIOS Mode and Secure Boot State.
| BIOS Mode | Secure Boot State | What it means |
|---|---|---|
| UEFI | On | The basic Secure Boot requirement is satisfied. |
| UEFI | Off | Enable Secure Boot in firmware. |
| Legacy | Off or unavailable | Windows likely needs an MBR-to-GPT conversion before switching to UEFI. |
| UEFI | Unsupported | Check firmware, motherboard support, and configuration. |
Secure Boot is a firmware feature, not a setting inside the EA app. A PC can support it while running with Secure Boot disabled, Legacy BIOS enabled, or CSM enabled.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
2. Check TPM 2.0
- Press Windows + R.
- Type
tpm.mscand press Enter. - Confirm that the status says The TPM is ready for use.
- Confirm that Specification Version is
2.0.
On Intel systems, the firmware option may be called Intel PTT or Platform Trust Technology. On AMD systems, look for AMD fTPM, Firmware TPM, or TPM Device. TPM and Secure Boot are separate requirements, so enabling one does not automatically enable the other.
3. Check whether the Windows disk is GPT or MBR
- Right-click Start and select Disk Management.
- Find the disk containing Windows, normally Disk 0.
- Right-click the disk label on the left, not the C: partition.
- Select Properties, open Volumes, and check Partition style.
GUID Partition Table (GPT) is compatible with UEFI and Secure Boot. Master Boot Record (MBR) normally must be converted before the existing Windows installation can boot through UEFI.
Case 1: BIOS Mode is UEFI and Secure Boot is Off
Enter the firmware settings from Windows 11:
- Open Settings > System > Recovery.
- Beside Advanced startup, select Restart now.
- Choose Troubleshoot > Advanced options > UEFI Firmware Settings.
- Select Restart.
If UEFI Firmware Settings is missing, restart the computer and repeatedly press the manufacturer’s firmware key. Common keys include Delete, F1, F2, F10, F11, F12, and Esc, but the correct key varies.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →In firmware, aim for this configuration:
- Boot mode: UEFI
- Legacy Boot or Legacy BIOS: Disabled
- CSM/Compatibility Support Module: Disabled
- Secure Boot: Enabled
- Secure Boot mode: Standard or Windows UEFI mode, where available
- TPM, Intel PTT, or AMD fTPM: Enabled
- Boot priority: Windows Boot Manager first
Secure Boot may be under Boot, Security, Authentication, or Advanced. Menu names differ by motherboard and laptop manufacturer. Some firmware requires Install default keys, Restore factory keys, or a BIOS administrator password before Secure Boot can be enabled. Use the manufacturer’s documentation rather than deleting keys or changing unrelated security settings.
Case 2: BIOS Mode is Legacy or the disk is MBR
Do not simply turn off Legacy/CSM. If Windows is installed on an MBR disk, changing the boot mode first can make Windows unbootable.
Before using MBR2GPT: back up important files, save your BitLocker or device-encryption recovery key, confirm the correct disk number, and do not convert a data disk by mistake. Do not run the conversion if validation fails. Dual-boot systems, third-party boot managers, RAID, unusual partition layouts, and disk encryption may require manufacturer or Microsoft-supported recovery guidance.
Validate the Windows disk
Open Windows Terminal, PowerShell, or Command Prompt as administrator. Replace 0 if Windows is installed on another disk:
Rank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
mbr2gpt /validate /disk:0 /allowFullOSContinue only if validation succeeds. If it reports a partition-layout, recovery-partition, or free-space problem, stop and investigate. Do not try random partition commands.
Convert MBR to GPT
After successful validation, run:
mbr2gpt /convert /disk:0 /allowFullOSWhen the conversion finishes:
- Restart into UEFI firmware.
- Disable Legacy/CSM and select UEFI boot.
- Set Windows Boot Manager as the primary boot option.
- Enable TPM 2.0, Intel PTT, or AMD fTPM.
- Enable Secure Boot.
- Save changes and restart.
Microsoft documents MBR2GPT validation and conversion and notes that firmware must be changed to UEFI after conversion. MBR2GPT is not guaranteed to work on every custom disk layout.
Verify the result in Windows
After Windows starts normally, run msinfo32 again. You should see:
- BIOS Mode: UEFI
- Secure Boot State: On
Run tpm.msc and confirm that the TPM is ready for use and reports specification version 2.0. Also confirm that the Windows disk is GPT and that Windows Boot Manager is the active boot path.
Free tools Windows power users keep installed
One-click scans. No signup required.
If Secure Boot is already enabled but Battlefield 6 still reports the error
If msinfo32 shows BIOS Mode: UEFI and Secure Boot State: On, stop repeatedly changing BIOS options. Treat the problem as a boot-chain, firmware, game-file, or anti-cheat detection issue:
- Restart Windows once more.
- Install available Windows updates.
- Update the motherboard or laptop firmware using the official package for the exact model.
- Confirm that Windows is launched through Windows Boot Manager.
- Restart the EA app and Battlefield 6.
- Repair the Battlefield 6 installation through the EA app or the relevant PC storefront.
- Repair or reinstall EA Javelin Anti-Cheat.
EA provides an official Javelin Anti-Cheat installer and troubleshooting route. Select Battlefield 6 in the installer, choose Install, wait for confirmation, restart Windows, and launch the game again. Avoid assuming a fixed executable path because installation locations can vary.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Advanced cases and recovery
Secure Boot is greyed out
Common causes include Legacy/CSM still being enabled, missing factory Secure Boot keys, a required firmware administrator password, outdated firmware, or an incompatible boot configuration. Confirm that the disk is GPT and the system is in UEFI mode first. If the firmware offers it, use the manufacturer’s documented option to restore factory Secure Boot keys.
Rank #3
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
Windows will not boot after enabling Secure Boot
- Return to UEFI firmware.
- Temporarily disable Secure Boot or restore the previous boot setting.
- Confirm that Windows Boot Manager is selected.
- Check that the MBR2GPT conversion completed successfully and that the disk is GPT.
- Use Windows Startup Repair or the manufacturer’s recovery process if Windows still will not start.
Do not repeatedly switch between Legacy and UEFI without confirming the disk and bootloader configuration. Microsoft’s guidance recommends disabling Secure Boot again if Windows cannot boot after the change, then contacting the manufacturer if the issue continues.
BitLocker or device encryption requests a recovery key
Changing TPM, Secure Boot, boot mode, or firmware settings can trigger a recovery prompt on an encrypted PC. Save the recovery key before making changes and suspend protection temporarily through Windows’ supported controls when appropriate. Never clear the TPM casually: doing so can affect encrypted data and stored credentials.
Dual-boot systems and GRUB
Some Battlefield 6 users have reported that the error appears even though Windows reports Secure Boot enabled when Windows is launched through GRUB or another Linux boot chain. This is community evidence, not a confirmed universal EA explanation. As a test, select Windows Boot Manager directly from the firmware boot menu, avoid booting Windows through GRUB or shim temporarily, and check msinfo32 again. See the reported EA forum case for context.
Secure Boot is unsupported
If msinfo32 reports Secure Boot State: Unsupported, or the firmware has no UEFI/Secure Boot support, confirm the motherboard or laptop model and firmware version. Install firmware only from the manufacturer and only for that exact model. If the hardware genuinely lacks the feature, there may be no software fix; Secure Boot is not something a Windows utility can add.
Windows 11’s Secure Boot documentation also discusses Secure Boot certificate changes beginning in June 2026. That transition may matter in device-specific firmware or boot-chain cases, but it should not be assumed to be the cause of this Battlefield 6 error without evidence from the affected PC.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsFinal checklist
- BIOS Mode is UEFI.
- Secure Boot State is On.
- TPM 2.0 is ready for use.
- The Windows disk is GPT.
- Legacy/CSM is disabled.
- Windows Boot Manager is the active boot option.
- EA Javelin Anti-Cheat is installed.
- Windows and motherboard firmware are current.
For additional platform-specific details, consult Microsoft’s guides to Windows 11 and Secure Boot, UEFI and Legacy boot modes, and disabling or recovering from Secure Boot changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
