Prepare Your PC and Account for Call of Duty TPM 2.0 Requirements
Prepare your PC and accounts now: verify TPM 2.0 and Secure Boot, update firmware and OS, and link and secure your Call of Duty/Activision accounts so anti-cheat checks won't leave you locked out.
Call of Duty’s modern anti-cheat and platform requirements increasingly lean on system attestation, most notably Trusted Platform Module 2.0 (TPM 2.0) and Secure Boot recommendations. This checklist walks through the exact PC and account steps to reduce the chance that anti-cheat will block you from playing or cause progress loss.
1. Verify your system has Trusted Platform Module 2.0
Check whether your machine exposes TPM 2.0 to the OS. On Windows systems, look in the TPM management console or UEFI/BIOS pages to confirm “TPM 2.0” is present and enabled; this is the specific hardware/firmware capability Call of Duty’s modern anti-cheat systems are referencing. If your machine reports TPM 1.2 or “Unavailable,” you will need to enable the platform TPM in UEFI or consider a firmware/motherboard upgrade, games relying on TPM 2.0 will not accept older TPM versions for attestation.
2. Enable TPM in UEFI/BIOS if it’s present but disabled
Many prebuilt PCs and laptops ship with TPM disabled by default. Reboot into UEFI/BIOS and enable the security device labeled TPM, fTPM, PTT, or Intel Platform Trust Technology, these are vendor labels for the same Trusted Platform Module 2.0 capability. Enabling TPM is a low-risk change, but note your UEFI will prompt you to save settings; keep a record of any custom boot options so you can revert if needed.
3. Turn on Secure Boot and confirm a compatible boot mode
Secure Boot complements TPM by ensuring the boot chain is signed and untampered, a configuration anti-cheat systems recommend for stronger attestation. In UEFI/BIOS, set the system to UEFI boot (not Legacy/CSM) and enable Secure Boot; you may need to reset custom boot keys to the factory defaults if you previously used custom signing keys. If your disk uses an MBR partition table, Secure Boot typically requires converting to GPT, plan time to back up and convert to avoid data loss.
4. Update UEFI/BIOS firmware and motherboard drivers
TPM 2.0 and Secure Boot behavior depend on the firmware implementation. Visit your motherboard or laptop vendor and install the latest UEFI/BIOS update and chipset driver, these updates often add or stabilize TPM 2.0 support and resolve Secure Boot quirks. Keep the exact model and BIOS revision number handy; if a firmware update adds TPM 2.0 support, vendors typically list that capability explicitly in release notes.
5. Keep your OS and anti-cheat software up to date
Call of Duty’s anti-cheat systems require modern OS support for platform attestation. Install the latest Windows updates and ensure any kernel-level anti-cheat components are current, many anti-cheat systems install a system driver that checks TPM and Secure Boot state at launch. Reboot after major updates to make sure the anti-cheat driver registers the system’s current security state before launching the game.
6. Link and secure your Call of Duty / Activision account and platform IDs
Platform requirements often extend to account linking and identity verification. Link your Activision/Call of Duty account to the launcher you use (console account, Steam, or other platforms) and enable two-factor authentication on the Activision account to protect progression and purchase data from being accessed if anti-cheat flags account activity. Confirm email and phone details are current so account recovery works quickly if anti-cheat or device attestation causes a temporary block.
7. Prepare a rollback and backup plan before making firm changes
Enabling Secure Boot or updating firmware can change how your OS boots; create a full system backup or image before you modify UEFI/BIOS settings or convert disk formats (MBR→GPT). Keep a recovery USB (Windows installation media or your OEM recovery tool) ready so you can restore if the system won’t boot after changes. Document current UEFI settings and keep bootable media for safe mode and command-line repairs.
8. Troubleshoot common TPM / Secure Boot errors you may encounter
If Call of Duty’s client reports a platform attestation failure, check these common failure points: TPM present but disabled in UEFI, Secure Boot off, disk using legacy MBR, or outdated firmware. If UEFI reports “TPM not found,” verify the platform security setting isn’t set to “Discrete TPM” when you have firmware TPM (fTPM) or vice versa. If you see signed driver errors after enabling Secure Boot, either re-sign or replace unsigned drivers, or revert Secure Boot temporarily while resolving driver signatures.
9. Know your hardware limits and upgrade paths
Older motherboards and pre-2016 systems often lack TPM 2.0 support; some boards accept a discrete TPM module, while others can enable fTPM via CPU/platform microcode updates if the vendor provides a UEFI patch. If your system is several generations old and vendor support is absent, plan for a platform upgrade, motherboard and CPU swaps or a new PC, because anti-cheat attestation relying on TPM 2.0 and Secure Boot can be non-negotiable for modern title compliance.
10. What to expect from anti-cheat checks and how they affect play
Modern anti-cheat uses TPM 2.0 and Secure Boot recommendations to verify system integrity at launch and during play; failing attestation can result in launch blocks, temporary suspensions, or degraded online functionality. After you complete the checklist, TPM enabled, Secure Boot on, firmware and OS updated, accounts linked and secured, expect fewer platform-attestation flags and a smoother first-time launch experience for Call of Duty matches that require those protections.
- Before touching firmware, back up user data and create recovery media to avoid surprises during boot-mode changes.
- Keep vendor model numbers and BIOS revisions written down, support staff will ask for them if you need help.
- If your machine supports fTPM but the OS shows “TPM not ready,” a BIOS update or clearing TPM keys (with a backup) often resolves the issue, proceed cautiously.
Quick practical tips
Conclusion Call of Duty’s move toward TPM 2.0 and Secure Boot–based attestation makes a little firmware work up front a big time-saver at match start: fewer launch errors, fewer account blocks, and a smoother anti-cheat experience. Follow this checklist, verify TPM 2.0, enable Secure Boot, update firmware and OS, secure and link your Activision/Call of Duty accounts, and keep backups, and you’ll minimize the risk of getting locked out when you try to jump into a match. As platform requirements evolve, these hardware and account hygiene steps will keep you ready to play.
Know something we missed? Have a correction or additional information?
Submit a Tip
