A Game Requires TPM 2.0 or Secure Boot: Check Before Changing Firmware

Choose your symptom

• TPM version or status is unknown — Read tpm.msc without clearing the TPM.
• Secure Boot is Off, Unsupported or BIOS Mode is Legacy — Check boot/disk prerequisites before changing anything.
• You lack a recovery key or model-specific instructions — Stop at inspection and ask the PC administrator/manufacturer.
• Windows reports the required state but the game still refuses it — Use that game’s official attestation guidance.

STEP 1: Inspect the current Windows state

1. Press Windows+R, enter tpm.msc and choose OK. Read whether the TPM is ready for use and whether Specification Version is 2.0. Compatible TPM cannot be found can mean it is disabled; it does not alone prove the hardware lacks it.
2. Open Windows+R → msinfo32. Record BIOS Mode and Secure Boot State. The intended state for a game requiring enabled Secure Boot is UEFI with Secure Boot On.
3. Windows 11 eligibility includes Secure Boot capability, which is not the same observation as it currently being enabled. Check the state itself and distinguish the game’s requirement from the OS requirement.

Result and next action: Keep the exact result. If it is unclear, do not guess a firmware switch from a similarly named setting.

STEP 2: Prepare before entering firmware settings

1. Back up important data and confirm access to the correct BitLocker/device-encryption recovery key if encryption is used. Obtain the exact model’s instructions and recovery procedure. If these are unavailable, stop and contact the manufacturer or administrator. Do not choose Clear TPM.
2. Save open work. On Windows 11, the normal route is Settings → System → Recovery → Advanced startup → Restart now. Use the manufacturer’s documented entry route if the screen differs.
3. On the recovery screen, use Troubleshoot → Advanced options → UEFI Firmware Settings → Restart where that option is available. Entering the screen does not require changing a setting.
4. Firmware menus and save/exit controls differ by model. Read and record current settings before any approved change; if unsure, exit without saving changes and seek support.

Result and next action: Do not expose recovery keys in screenshots or support posts. Having a backup is not the same as knowing how this PC will recover from a boot change.

STEP 3: Enable a supported TPM using the model’s instructions

1. Only after preparation, locate the TPM option described by the manufacturer. Microsoft lists menu examples such as Advanced, Security or Trusted Computing; they are not guaranteed menu names.
2. Possible labels include Intel PTT, Intel Platform Trust Technology, AMD fTPM/PSP fTPM, Security Device Support or TPM State. Match the documented setting for your model instead of enabling every similarly named option.
3. Use the model’s save-and-restart procedure, then return to tpm.msc and confirm readiness plus Specification Version 2.0. A save-key example such as F10 is not universal.

Result and next action: If Windows does not return normally or recovery is requested, follow the prepared recovery/manufacturer instructions. Do not clear TPM as a troubleshooting shortcut.

STEP 4: Check boot prerequisites before enabling Secure Boot

1. In Disk Management, identify the disk containing Windows and inspect its Properties → Volumes → Partition style. If it is MBR or the disk/state is uncertain, do not disable CSM or switch boot mode to UEFI; ask the manufacturer or administrator.
2. Only with confirmed compatible UEFI/GPT setup, backups, recovery access and model-specific instructions, enable Secure Boot by that documented route. Record the previous state and verify msinfo32 after restarting. If controls are unavailable, do not delete keys or improvise firmware settings.
3. If MBR-to-GPT conversion is required, review Microsoft’s MBR2GPT prerequisites with the administrator/manufacturer. Conversion and subsequent firmware boot changes need a recovery plan, including encryption handling. This guide does not provide a conversion command or recommend disabling encryption wholesale.

Result and next action: Stop at an unmet prerequisite. A game launch error is not a reason to risk an unbootable Windows installation.

STEP 5: Use the game’s official guidance if checks still fail

1. For the relevant Call of Duty titles, Activision documents CODBrokerInstaller.exe or enrollaik.exe UAC requests during normal official launch/registration. Verify the request’s origin and publisher against the official guidance; a matching filename alone is not authorization to approve an unexpected program.
2. On a stable PC, review Windows Update and restart as required, then recheck the recorded TPM/Secure Boot state before another normal launch.
3. Activision describes an AMD firmware 3.*.0.* registration/compliance issue. If applicable, contact the motherboard/PC manufacturer for the exact supported firmware procedure. Do not flash firmware on unstable power or from an unrelated model’s download.

Result and next action: Provide the error and observed state to official support. Do not weaken UAC, disable anti-cheat or repeatedly approve unexplained prompts to bypass the check.

Keep inspection, enablement and conversion separate

1. tpm.msc and msinfo32 report different properties. TPM version 2.0 is not proof of Secure Boot On; Windows 11 installed is not proof that the game’s attestation passes.
2. Missing recovery access, an unidentified Windows disk, Legacy/MBR, unavailable controls or an unfamiliar firmware screen are stopping conditions. Use model-specific support rather than a generic video for another motherboard.
3. For a managed PC, involve its administrator. Never share the recovery key or attempt to clear/reset security hardware to satisfy a game prompt.

Protect saves and keep changes reversible

• Do not clear TPM, delete Secure Boot keys or switch Legacy/CSM to UEFI by guesswork.
• Preserve data and confirm encryption recovery access before changing firmware.
• Use exact-model firmware instructions; this article does not execute or authorize changes on a managed PC.