How to Enable Secure Boot for Battlefield 2042

If Battlefield 2042 acts like it “requires Secure Boot” (or it won’t launch after a setting change), the usual fix is to match three settings: Secure Boot = ON, your PC boot mode = Windows UEFI, and CSM = OFF. Before you touch BIOS, it also helps to see what Windows is already reporting.

Below is a straightforward checklist that lines up with what you’ll see in many guides, plus the Windows tools you can use to confirm each step.

---

Check your PC’s current Secure Boot state (Windows msinfo32)

Before changing anything, check what Windows reports right now.

1. Press Win + R, type msinfo32, and press Enter.
2. Look for these entries:

• Secure Boot State
• BIOS Mode

What you want to see:

• Secure Boot State should be ON (or enabled).
• BIOS Mode should be UEFI (not Legacy).

If you see Secure Boot state unsupported, don’t panic. It usually means your firmware/boot setup isn’t set up in a way that lets Windows confirm Secure Boot yet. You’ll still need to do the BIOS steps later in this guide.

---

Enable TPM/fTPM in BIOS (before Secure Boot)

Secure Boot and TPM (and sometimes fTPM, which is TPM provided by firmware) are often checked together for newer Windows and game requirements.

1. Reboot your PC.
2. Enter BIOS/UEFI setup (restart, then press a BIOS key like Delete, F2, or F12. The exact key depends on your motherboard).
3. In BIOS, find a security or TPM-related setting and do one of the following:

• Activate TPM
• Or enable fTPM

If you’re not sure where it is, search through BIOS settings for TPM or fTPM.

---

Enter BIOS/UEFI and switch to Advanced Mode (if needed)

Some BIOS screens default to a simple view.

• If you see a “simple” interface, switch to Advanced Mode (or the closest equivalent).
• This is usually where you can find:
• Secure Boot
• UEFI/Windows UEFI mode
• CSM

Once you’re in Advanced Mode, continue with the next steps.

---

Set BIOS mode to Windows UEFI (and confirm it)

Secure Boot requires a UEFI boot setup, and you don’t want your system stuck on a Legacy/CSM-style boot path.

In BIOS/UEFI:

1. Find a setting for Boot mode or Boot options.
2. Set it to Windows UEFI (or the closest option your BIOS offers).
3. Save changes. Some BIOS versions require you to save once before you can adjust other settings.

After that, come back later and confirm the result in Windows using msinfo32.

---

Enable Secure Boot in BIOS/UEFI

Now you can turn Secure Boot on.

1. In BIOS, go to the Secure Boot section (often under Boot, Security, or Authentication).
2. Set Secure Boot to Enabled/On.
3. If your BIOS uses a separate action (like activate), enable it there too.

If your BIOS asks for a “mode,” choose Windows UEFI when you see that option.

---

Deactivate CSM so Secure Boot can work

CSM (Compatibility Support Module) is the “Legacy mode helper” that can interfere with Secure Boot setups.

In BIOS:

1. Find CSM
2. Set CSM to Disabled/Off

If you leave CSM on, you can end up with Secure Boot enabled in BIOS but Windows still not recognizing it correctly, or the game not launching due to a mismatched security/boot setup.

---

Verify Secure Boot is enabled after reboot

Reboot and check again using Windows tools.

1. Boot into Windows.
2. Open msinfo32 again.
3. Confirm:

• Secure Boot State → ON
• BIOS Mode → UEFI

It’s also a good time to re-check TPM after changing TPM/fTPM in BIOS.

Quick TPM check (tpm.msc)

1. Press Win + R
2. Type tpm.msc
3. Press Enter

You should see TPM as enabled/ready (wording varies). It shouldn’t still look disabled/inactive if you just turned it on in BIOS.

---

If Battlefield 2042 still won’t boot: common checks

If everything is enabled and the game still won’t start, don’t assume the BIOS changes “stuck.” Do these quick checks in order.

1. Re-verify Secure Boot + UEFI in Windows

• Open msinfo32
• Confirm Secure Boot State = ON
• Confirm BIOS Mode = UEFI

1. Confirm TPM/fTPM is enabled

• Open tpm.msc
• Make sure it isn’t still disabled/inactive

1. Make sure CSM really is OFF

• If you changed CSM after enabling Secure Boot, check BIOS again.
• If CSM is still enabled, you may be back in a mismatched setup.

1. If the game prompts again

• Some launchers re-check requirements when you click “Play.”
• If the launcher still can’t validate the setup, it will likely keep failing until Windows reports the correct Secure Boot and UEFI state.

If you made BIOS changes and things feel unstable afterward, go back and confirm the trio together:

• Secure Boot = ON
• BIOS/Boot mode = Windows UEFI
• CSM = Disabled

That combination is what the guides keep recommending because it lines everything up.

---

If you see “Secure Boot state unsupported”: what to try next

If msinfo32 shows Secure Boot state unsupported, Windows can’t validate Secure Boot in the current setup. Try this:

1. Go back to BIOS and confirm boot mode

• Set BIOS mode / Boot mode to Windows UEFI
• Avoid Legacy/CSM-style boot mode

1. Disable CSM

• Set CSM = Disabled/Off
• Save and reboot

1. Enable Secure Boot again

• Re-check Secure Boot in BIOS
• Make sure it’s actually enabled/activated

1. Re-check after reboot using msinfo32

• The message should clear once you’re fully in UEFI mode with Secure Boot truly enabled

If it still won’t change, the safest next step is to re-check the full BIOS/Windows setup in this order:

• TPM/fTPM enabled
• Windows UEFI mode
• Secure Boot ON
• CSM OFF

Then reboot and check msinfo32 again.

---

After enabling Secure Boot and confirming it in Windows, try launching Battlefield 2042 again. If it still won’t boot, revisit the troubleshooting section above.