[UPDATE] Battlefield 6 Update: On Secure Boot & Cheats

1. You Give Up a Chunk of System Freedom
   Secure Boot only allows booting OS loaders signed with keys stored in your motherboard firmware.
   If you want to run unsigned OSes, custom kernels, or older hardware drivers, Secure Boot will block them unless you manually manage keys (which is not beginner-friendly).
   Dual-booting Linux or other alternative OS setups becomes harder — sometimes impossible without disabling Secure Boot or manually signing bootloaders.
2. It Normalizes Publisher Control Over Your Firmware
   Once you flip it on “just for one game,” you’ve accepted that publishers can dictate your BIOS settings.
   That sets a precedent: today it’s Secure Boot, tomorrow it might be firmware updates, mandatory fTPM, or restrictions on hardware mods.
   The more people comply, the easier it is for companies to justify more invasive requirements.
3. It Can Break Existing Configurations
   If your system drive is MBR (not GPT), enabling Secure Boot means converting it — a risky process if you don’t know what you’re doing.
   Some older GPUs, capture cards, or PCIe devices don’t play nice with Secure Boot.
   You might suddenly find certain unsigned drivers, modding tools, or even older software failing to load.
4. It Expands the “Walled Garden” Effect
   PCs have traditionally been open platforms. Secure Boot (when controlled by someone else’s keys, like Microsoft’s or your OEM’s) makes your hardware behave more like a console.
   Over time, this could mean your hardware only boots OSes or drivers approved by a small set of corporate signers.
5. It Doesn’t Stop All the Threats They Claim
   Publishers pitch Secure Boot as an anti-cheat silver bullet. It’s not.
   It stops some kernel-level cheats, but game cheats can still run from user-mode or from external devices — as people already proved in the Battlefield 6 beta.
   You end up giving up control without a guarantee of a cheat-free experience.

Bottom Line
Enabling Secure Boot isn’t automatically bad — some people run it daily without issue.
But the concerns are:

• Loss of control over your own firmware and boot options.
• Potential hardware/software compatibility issues.
• Normalization of corporate control over what your PC can run.