Failed Attestation Status in Call of Duty: Causes & Fixes

1. Why Call of Duty Shows Failed Attestation Status Error？

Secure attestation verifies that Windows started through a trusted chain and that required platform-security features are active. If the attestation is not supported, the current hardware, firmware, or boot configuration may not support the required verification process. Activision uses this signal as part of RICOCHET Anti-Cheat; it is a device-compliance result, not by itself proof of cheating.

⚠ Common reasons for Failed Attestation Status in Call of Duty

• TPM 2.0 is disabled, unavailable, not provisioned correctly, or reported with an older specification version.
• Secure Boot is disabled, the PC boots in Legacy/CSM mode, or the system disk uses MBR instead of GPT.
• UEFI keys are not installed, Secure Boot is in Setup Mode, or custom firmware settings prevent validation.
• The motherboard BIOS/UEFI firmware is outdated and does not expose security measurements correctly.
• Windows or the game client is outdated, game files are damaged, or a required Call of Duty service is disabled.
• A recent hardware, firmware, or boot-configuration change has not been recognized after a full restart.

Before changing anything, press Windows + R, enter msinfo32, and record BIOS Mode and Secure Boot State. Then run tpm.msc and confirm that TPM status is ready for use and Specification Version is 2.0. These checks reveal whether the problem is a missing feature or simply a disabled setting.

2.How to Fix Failed Secure Attestation in Call of Duty？

Fix 1: Run the Official Secure Attestation Wizard

Activision’s Call of Duty Secure Attestation Wizard is the fastest way to identify why the PC is not compliant.

• Close Call of Duty and its launcher, then open Activision’s TPM and Secure Boot support page.

• Download and launch the latest Secure Attestation Wizard. Approve the Windows prompt if the publisher and file source are correct.

  

• Run the scan and note every failed or incomplete item. Use the wizard’s guidance to distinguish TPM, Secure Boot, firmware, or Windows issues.

• After making the relevant correction, fully restart the PC and run the wizard again before launching the game.

Fix 2: Enable TPM 2.0, UEFI, and Secure Boot

This is the primary fix for Failed Attestation Status in Warzone and other current Call of Duty PC releases. BIOS terminology differs by manufacturer, so use your motherboard or laptop manual alongside these steps.

• Save your BitLocker or device-encryption recovery key. Open Settings > System > Recovery > Advanced startup and choose UEFI Firmware Settings, or use the manufacturer’s setup key during startup.

• Set the boot mode to UEFI. If the Windows system disk is MBR, stop here and complete the conversion section below before disabling Legacy/CSM.

  

• Enable the firmware TPM. Look for Intel Platform Trust Technology (PTT), AMD fTPM, Security Device Support, or Trusted Computing.

  

• Enable Secure Boot. If prompted, use Standard mode or install the factory/default Secure Boot keys. Do not clear the TPM.

• Save and restart. In Windows, verify BIOS Mode: UEFI and Secure Boot State: On in msinfo32, then confirm TPM 2.0 in tpm.msc.

If the PC asks for a BitLocker recovery key after firmware changes, enter the key you saved. On a managed work or school device, contact the administrator instead of modifying security policy yourself.

⚡ Bonus: Secure Boot Won’t Enable? Convert MBR to GPT First

Secure Boot requires UEFI boot. A Windows installation that still boots from an MBR system disk commonly depends on Legacy/CSM mode, which can leave Secure Boot unavailable or grayed out. 4DDiG Partition Manager can convert an MBR to GPT without the delete-and-recreate workflow used by basic disk tools.

Note:

Back up important files and connect the computer to stable power before proceeding.

• Install and open 4DDiG Partition Manager. Choose Convert Disk, then Convert MBR to GPT.

  FREE DOWNLOAD

  Secure Download

  BUY NOW
  

• Select the physical disk that contains Windows and the boot partition and click Continue button.

  

• If the chosen disk is the system disk, 4DDiG will download the PE component. After successful download, a prompt window will appear. Ensure there is no unsaved files and power is sufficient or connected well. Click "Sure". The computer will restart and enter the PE environment automatically.

  

• After the program starts in the PE environment, select "Convert MBR to GPT" to proceed.

  

• Select your system disk, click ”Continue”.

  

• After completing conversion, please follow the instructions below to boot your computer, otherwise your computer may not boot properly.

  

Conversion changes the boot layout, not the CPU or TPM hardware. If the motherboard does not support UEFI or TPM 2.0, converting the disk will not make the PC compliant.

💡 Video Guide:

Fix 3: Update Your BIOS

Activision recommends checking for a BIOS firmware update when TPM 2.0 is enabled but Call of Duty still reports a security problem. Firmware updates can improve TPM behavior, Secure Boot key handling, and attestation reporting.

• Find the exact motherboard or laptop model and current BIOS version in msinfo32.

  

• Download the matching update and instructions from the device manufacturer’s official support page.

• Suspend BitLocker if the manufacturer instructs you to, connect AC power, and do not interrupt the update.

• Afterward, recheck TPM, UEFI, Secure Boot, boot order, and default Secure Boot keys because some settings may reset.

Never install firmware for a similar-looking model. A failed or incorrect BIOS flash can make the computer unbootable.

Fix 4: Verify Call of Duty Game Files

If the official wizard passes but the game still shows the old status, repair the local installation and update the launcher.

• Battle.net: select Call of Duty, open the gear menu beside Play, choose Scan and Repair, and start the scan.

• Steam: right-click Call of Duty in Library, open Properties > Installed Files, and select Verify integrity of game files.

  

• Xbox app / Microsoft Store: open the game’s management or repair options and use Verify and Repair when available.

Restart Windows after the repair. Verification replaces missing or modified game files but does not enable TPM or Secure Boot, so it should follow—not replace—the platform-security checks.

Fix 5: Enable COD.Broker.Service

A disabled Call of Duty broker service can prevent the game’s security components from communicating correctly. Service names and availability can vary by game build, so make this change only if COD.Broker.Service appears on your PC.

• Press Windows + R, enter services.msc, and press Enter.

• Locate COD.Broker.Service. Open its properties and check whether the service is disabled or stopped.

• Set Startup type to Manual or the default recommended by the installed game, select Start, and apply the change.

• Restart the launcher and game. If the service is missing, repair the game installation rather than downloading a service file from the web.

Fix 6: Update Windows and Perform a Full Restart

Install pending Windows security and cumulative updates under Settings > Windows Update, then choose Restart. Activision notes that some Trusted Computing Group event-log failures can be corrected by restarting and applying the latest Windows update. Avoid Fast Startup for this test: use Restart so the trusted-boot chain is rebuilt.

Conclusion

To resolve Failed Attestation Status, begin with Activision’s Secure Attestation Wizard and correct the exact item it reports. Most cases come down to TPM 2.0, UEFI, Secure Boot, firmware, or a stale game/service state. When Secure Boot cannot be enabled because Windows boots from an MBR disk, 4DDiG Partition Manager offers a guided MBR-to-GPT conversion before you switch the firmware to UEFI. Back up first, preserve your recovery key, and never clear the TPM casually. Once the wizard passes, verify game files, update Windows, and restart before testing Call of Duty again.