callofduty[.]com/blog/2025/08/call-of-duty-black-ops-6-ricochet-anti-cheat-season-05
I don't know if anyone is planning on playing Battlefield 6, the open Beta or the regular version -- if so, they've announced that their anti-cheat requires both Secure Boot & a TPM turned on. And with the announcement, several sites have posted articles on turning on Secure Boot if it's not enabled on your PC/laptop. Problem is, those tutorials may not go far enough, be misleading, &/or be just plain inaccurate, which is why I'm posting this.
I recommend HWiNFO [hwinfo[.]com] to check whether the device boots using UEFI or Legacy booting -- it's on the first screen of the window, & it'll also show if Secure Boot is enabled [it can be turned on in the BIOS but not enabled]. I'm using an AMD Ryzen CPU & it's built-in TPM. In HWiNFO it's shown under Motherboard -> SMBIOS DMI -> TPM. You can also type msinfo32 in the Run box, find the TPM status in Settings, or run tpm.msc.
If you're booting UEFI but Secure Boot is off or not enabled it's turned on in the BIOS setup menus for your device. Usually you can get into that setup menu by repeatedly pressing a hot key when the device is first started from a power off state. Usually that hot key is F2 or Delete, but it can be any other usually F key, or may not in fact exist. You can get into the BIOS settings from Windows Settings Recovery, rebooting the system to get the same boot menu that you get when Windows won't start 3 or 4 times in a row.
The manufacturer of the motherboard or device *may* have a manual available, and if so, it **may** cover Secure Boot. And it should be a straightforward switch to turn it on. However, you need to follow through to make sure it's enabled once you're back in Windows... with Gigabyte, and maybe some other brands of motherboards, the next part is a PITA. To actually enable Secure Boot you have to set it to custom & (re)load the factory keys, which means a restart where the BIOS resets itself to its defaults. That means you have to know every one of the very many settings in the BIOS to put things back.
The Nightmare scenario is if your PC/laptop uses Legacy booting, which is entirely possible if you upgraded Win7 or 8 to Win10, and still possible, though unlikely, if you installed Win10 fresh. In that case the easiest fix is to turn on UEFI booting in the BIOS, boot to Windows setup files on a USB stick [that you created with Rufus], and install Windows fresh, wiping your previous partition(s).
Otherwise you have to do 3 things: make sure the hard disk(s) have GPT partitions, make sure the EFI boot files are on a FAT32 partition, and in the BIOS, turn off Legacy [it may be called CSM] booting, turn UEFI booting on, and select the EFI boot loader. Generally all requirements have to be met at once or the system will not boot into Windows. If the BIOS sees a GPT partition on the boot drive it will often jump into UEFI mode on it's own, and if the EFI boot files are not there, fail to boot. If the BIOS is set to UEFI but doesn't see the EFI boot files on a FAT32 partition, because you didn't tell it to look there or that partition &/or the EFI boot files don't yet exist, it will fail to boot.
You can create a FAT32 partition and then add EFI [& optionally Legacy] boot files to it using the Windows tool BCDBoot. Afterward Windows *should* continue to boot in Legacy mode. Am Important Note: BCDBoot does not always work -- the boot files it creates may or may not start Windows. You can use the Windows tool or a partitioning app like AOMEI Partition Assistant [IMHO preferred] to convert an MBR hard disk/SSD to GPT. Another Important Note: you *may* find that not every partition on the hard disk/SSD survived intact. You can create the FAT32 partition, add EFI boot files, and convert the disk to GPT after booting to a Windows To Go drive.
I have installed Windows fresh to create the FAT32 partition with EFI boot files, then replaced the Windows partition with a backup of the old working Windows partition. In my experience that may or may not work. I have basically cloned individual partitions to a VHD [Virtual Hard Disk], converted that VHD from MBR to GPT, then cloned them back *after* converting the original disk to GPT. That has worked.