CoD Modern Warfare 4 PC Security Requirements: TPM 2.0 and Secure Boot

Step 1｜Inspect TPM 2.0 and Secure Boot in Windows

Start with status checks rather than changing firmware.

Time: About 5 minutes · Risk: low

1. Press Windows+R, enter tpm.msc and inspect the status. The ready-for-use message means it is enabled; also confirm Specification Version is 2.0.
2. Run msinfo32 and check BIOS Mode is UEFI and Secure Boot State is On.
3. If using Activision’s Call of Duty Secure Attestation Wizard, obtain it only from the official support page, extract the ZIP and run CODSecureAttestationWizard.exe. Review the reported requirement rather than treating every warning as the same problem.

Step 2｜Use the exact manufacturer’s TPM procedure

Activision distinguishes Intel PTT, AMD fTPM and discrete TPM hardware. The retail CPU minimum alone does not establish TPM support.

Time: About 15 minutes · Risk: medium

1. Back up important data and locate the BitLocker/device-encryption recovery key first. If the key or model-specific procedure is unavailable, stop and ask the maker or administrator. Do not select Clear TPM.
2. For Windows 11, Settings → System → Recovery → Advanced startup → Restart now leads to Troubleshoot → Advanced options → UEFI Firmware Settings where supported.
3. For Windows 10, use Settings → Update & Security → Recovery → Advanced startup → Restart now, then the corresponding recovery options.
4. Following the model’s documentation, locate the applicable option: examples include Intel PTT or Security Device Support, or AMD CPU fTPM under Advanced, Security or Trusted Computing. These names are examples, not a universal BIOS layout.
5. Save using the documented command, restart and check tpm.msc again. F10 is common but not universal.

If the options or supported hardware are unclear, use the PC or motherboard maker’s official guidance before making changes.

Step 3｜Enable Secure Boot only after checking UEFI and GPT

The Windows boot configuration must support the change.

Time: About 15 minutes · Risk: medium

1. Even if you arrived here directly, first confirm UEFI in msinfo32 and GPT for the Windows disk in Disk Management. For MBR or an unknown layout, go to step 4. Stop without backups, recovery keys and the model’s instructions.
2. Enter UEFI using the applicable method in step 2.
3. Use the manufacturer’s documented Secure Boot option and enable it. If it is unavailable, consult the manual instead of guessing which boot keys or CSM setting to change.
4. Save, restart and verify Secure Boot State is On in msinfo32.

A greyed-out option has model-specific causes. Do not change CSM or replace boot keys blindly.

Step 4｜For Legacy or MBR, stop before changing boot mode

Switching mode before the disk and recovery plan are ready can prevent Windows startup.

Time: About 30 minutes · Risk: high

1. Open Disk Management, open Properties for the physical Windows disk and inspect Partition style on Volumes.
2. Even with GPT, record existing boot settings and use model-specific instructions, backups and recovery keys. A work or school PC belongs with its administrator.
3. For MBR, stop settings changes. Do not disable CSM or switch to UEFI first. Record the disk format, PC model and encryption state, and ask the maker about supported conversion and recovery.
4. Microsoft MBR2GPT requires validation, UEFI support and correct post-conversion boot configuration. Suspending BitLocker protection differs from decrypting the volume; do not universally turn encryption off. Follow the maker/administrator’s procedure for protection and protectors with the recovery key available.

MBR2GPT has no conversion-undo function. Do not execute it without a known recovery method, verified backup and any required recovery key. This guide does not provide a one-command conversion shortcut.

Step 5｜Check trusted UAC prompts, firmware and Windows updates

Repeated attestation failures need their exact message, not repeated unrelated BIOS changes.

Time: About 20 minutes · Risk: medium

1. For CODBrokerInstaller.exe or enrollaik.exe prompts triggered by a normal launch from the official launcher, verify publisher and official guidance before approving. Do not approve an unexpected or unidentified executable.
2. If authorization is declined without a visible prompt, inspect Change User Account Control settings and restore notifications to the default level or higher, then relaunch.
3. In tpm.msc, record Manufacturer Version. Activision identifies AMD versions shaped 3.*.0.* as unsupported and directs affected systems to a manufacturer firmware update.
4. For TCG Event Log failure, install applicable Windows updates and restart.

Activision also flags Intel INTC 302.12.*.* and INTC 303.12.*.* firmware as potentially needing an update. Use the exact maker’s current instructions and the backup/key precautions above.

Step 6｜Identify which account requires a phone number

Completing a different account’s verification does not necessarily satisfy the prompt.

Time: About 5 minutes · Risk: low

1. If the game requests Activision-account verification, use official Activision account management to add or verify the requested mobile number.
2. If Steam separately requires phone verification, inspect the correct Steam account’s details and follow its displayed instructions.