SecureBoot is not enabled. This is how Battlefield 2042 became unplayable.

This has nothing to do with laziness. trying to reframe it as such is just trying to intentionally belittle the player base. doing such a move of requiring changing a setting in the BIOS, since it's not "on" by default for everyone, is a major ask for a game, one that most people won't do. If you post a guide about changing that setting with the warning to "do it at your own risk", then this is not a legitimate ask, and I completely understand the outrage. I also understand my friends who decided to delete the game, and since it doesn't seem like they are going to revert it, then I'll follow as well. I'm by no means happy about it. I loved playing the game, but since my system is older and it's not on by default, I'm not going to risk it for this game. I feel sorry for all the people who already bricked their system because of this, and I hope they'll be able to reverse it, so I don't think anyone should be required to do that. this is basically like updating the system requirements for a product after you as the consumer already bought and used the product, hardly seems fair.

is there any instructions from EA how to enable secureBoot when you have dual boot system? or just go fckurself?

exactly,,   ea please fix game   have been playing for year

yup not starting yup watched the vids  and ya I'm closing my wallet you got BF 6 coming and you expect any of use to purchase it after monkey stunts like this?!  YOU FIX IT !  most of us aren't computer programmers and can't do this if we could we well.   Im not buying anything until from EA until I see a fix. 

Shut up!

As in my experience with messing bios it bricked my bios chip. That's why i highly hate touching anything in bios ever, unless its really 100% needed.

EDIT: BIOS got bricked just by going in there. Was on asus laptop.

Detailed Guide to Enable Secure Boot for Dual Boot Systems

Enabling Secure Boot on a Windows dual-boot system (e.g., Windows + Linux) requires careful steps to avoid boot issues. Secure Boot ensures only trusted operating systems and bootloaders load during startup, but it can interfere with non-Windows OS installations if not configured properly.

Prerequisites

1. UEFI Firmware: Your system must use UEFI (not Legacy/CSM BIOS).
2. Compatible Hardware: Some older hardware may not support Secure Boot.
3. Backup Important Data: Changing boot settings can sometimes cause boot failures.
4. Windows Installed in UEFI Mode: Verify using:

• Press Win + R, type msinfo32, and check "BIOS Mode" (should say UEFI).

Step 1: Check Current Secure Boot Status

1. Open Command Prompt (Admin) and run:

Confirm-SecureBootUEFI

• If it returns True, Secure Boot is already enabled.
• If False, proceed to enable it.

1. Alternatively, check in System Information (msinfo32):

• Look for "Secure Boot State" (should say "On" if enabled).

Step 2: Prepare for Secure Boot (Dual Boot Considerations)

Linux Users: Many Linux distributions (Ubuntu, Fedora, etc.) support Secure Boot, but some (e.g., Arch Linux) may require manual configuration.

Third-Party Bootloaders: Tools like GRUB, rEFInd, or systemd-boot must be signed or use Microsoft's Shim to work with Secure Boot.

Disable Fast Startup (Windows):

• Go to Control Panel > Power Options > Choose what the power buttons do.
• Click "Change settings that are currently unavailable".
• Uncheck "Turn on fast startup" and save.

Step 3: Enter UEFI/BIOS Setup

• Restart your PC.
• Press the UEFI/BIOS key (usually F2, F12, DEL, or ESC).
• Navigate to Boot Settings or Security Settings.

Step 4: Enable Secure Boot

• Locate Secure Boot (may be under Boot, Security, or Authentication).
• Set it to Enabled.
• If prompted, select "Windows UEFI Mode" (not "Other OS").
• Some systems require:
• Reset to Setup Mode (if keys are missing).
• Load Default Keys (restores Microsoft's certificates).
• Save & Exit (usually F10).

Step 5: Verify Secure Boot in Windows

Boot into Windows.

Open Command Prompt (Admin) and run:

Confirm-SecureBootUEFI

• Should now return True.

Step 6: Fixing Dual Boot Issues

For Linux Users

• Ubuntu/Fedora: Should work by default (uses Shim).
• Other Distros: May need to:

1. Install signed bootloader (e.g., shim-signed).
2. Enrol custom keys in UEFI (advanced).

GRUB Issues:

• Reinstall GRUB with Secure Boot support:

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB --no-nvram sudo update-grub

If Windows Boots Instead of Linux

• Use BIOS Boot Menu (usually F12 at startup) to select Linux.
• Set Linux as default in UEFI boot order.

Step 7: Troubleshooting

If PC Won’t Boot After Enabling Secure Boot

• Disable Secure Boot temporarily in BIOS.
• Check if the OS supports Secure Boot (e.g., some Linux distros need extra steps).
• Re-enable Secure Boot after fixing bootloader issues.

"Invalid Signature Detected" Error

• Your bootloader isn’t signed. Solutions:
• Use a signed bootloader (e.g., Shim).
• Disable Secure Boot (last resort).

"Operating System Not Found"

• Ensure CSM/Legacy Boot is disabled in BIOS.
• Reinstall bootloader in UEFI mode.

Conclusion

Enabling Secure Boot on a dual-boot system requires:
✅Confirming UEFI mode
✅ Enabling Secure Boot in BIOS
✅ Ensuring Linux/other OS supports Secure Boot
✅ Fixing bootloader issues if they arise

If done correctly, your system will boot securely while maintaining dual-boot functionality.

this is nothing short of a company extorting money and not allowing you to play the game you've paid hard cash for.

how about realising that what your beloved EA has done is to tell me i have to have secureboot enabled ON MY PC. Did they pay for it, NO, did they build it, NO. They need to enable a roll back NOW or have a class mutiny on their hands.

Having the same issues, even tried to turn on Secure Boot, and had it enabled, only to get the same exact message everyone else has been getting. I just bought this PC in anticipation of the new BF game, but not going to bother buying this new game when I can't even play the old ones. Not going to change my bios again either. I restored my setting back to where they were and I will just uninstall this game, or wait for them to roll back this lousy update. Really dumb, the hoops they make you jump thru these days just to play a freakin game!