Quick answer (TLDR): "Failed Attestation Status" means RICOCHET Anti-Cheat could not verify that your PC meets Call of Duty's security requirements, so you're locked out of most playlists. To fix it you need to enable TPM 2.0 and Secure Boot in your BIOS and, on many AMD boards, update your BIOS/firmware (older AMD fTPM versions in the 3.x.0.x range fail the check). Run the official Call of Duty Secure Attestation Wizard first — it tells you exactly what's wrong — then enable TPM 2.0, turn on Secure Boot (UEFI boot mode + GPT disk), flash the latest BIOS, and restart. Until you pass, Black Ops 7 limits you to Nuketown 24/7 and Warzone to Battle Royale Casual. Full step-by-step below. For more, see our guide on Warzone & Black Ops 7 'Waiting for Relay' Fix (Season 4.
If you booted up Call of Duty after a season update and got hit with "Failed Attestation Status Applied" or "BIOS Firmware: Update Required" — and suddenly every playlist except one is greyed out — you are not banned, and you didn't do anything wrong. RICOCHET Anti-Cheat's hardware-attestation check simply couldn't confirm your PC's security settings. This guide explains exactly what the error means, why it triggers on season updates, and the precise steps to fix it on both Intel and AMD systems. Updated for Black Ops 7 Season 5 (live as of July 23, 2026).
Call of Duty - Bot Lobby
Get bot lobby in 10 minutes
What is the "Failed Attestation Status" error?
"Failed Attestation Status" is the message Call of Duty shows when RICOCHET Anti-Cheat cannot verify your PC's security configuration with Microsoft. Activision calls this process Remote Attestation, and it runs through Microsoft Azure Attestation (MAA) as part of the game's TPM 2.0 implementation.
Here's the key difference from older anti-cheat checks: instead of asking your PC "are your security features on?" and trusting the answer, Remote Attestation validates those settings through Microsoft's trusted servers. That makes it much harder to spoof — but it also means that if your TPM, Secure Boot, or BIOS firmware isn't in a known-good state, the check fails and the game restricts you.
In Activision's own words from the RICOCHET anti-cheat update:
"Players who fail Microsoft Azure Attestation (MAA) checks will be placed into a separate matchmaking pool. To access all playlists, players must successfully complete the MAA process."
— Call of Duty RICOCHET Anti-Cheat Season 04 Update, callofduty.com/blog
Why does Call of Duty show this error after a season update?
TPM 2.0 and Secure Boot requirements were first added to Call of Duty back in Season 05 of BO7's cycle (August 2025), and they now apply to both Black Ops 7 and Warzone. What changed is enforcement. With Black Ops 7 Season 4 (June 4, 2026), RICOCHET expanded Remote Attestation so that systems failing the Microsoft Azure Attestation check are actively pushed into a separate, restricted matchmaking pool rather than quietly warned. The same enforcement carries forward into Season 5 (launching July 23, 2026) — if you failed in Season 4 and didn't fix it, you will fail again in S5 until the BIOS settings below are corrected.
There are a few common reasons a PC that "worked fine yesterday" now fails:
- TPM 2.0 or Secure Boot is disabled in BIOS (very common on Windows 10 builds and custom PCs).
- Outdated BIOS firmware. This is the big one for AMD users — Activision specifically notes that AMD fTPM software in the 3.x.0.x version range can return an attestation error, and the fix is a BIOS/firmware update.
- Legacy boot configuration — your system is booting in Legacy/CSM mode or your drive uses an MBR partition instead of GPT, both of which block Secure Boot.
- A party member fails. If you queue with friends and even one party member's PC isn't compliant, everyone in the party gets the failed-attestation message.
What happens if you fail attestation?
You are not banned and your account is fine. (If you see playlist restrictions alongside a RICOCHET strike or Communication Ban message, that's a different issue — see the Black Ops 7 Shadowban Guide for that path.) Attestation-only lockouts show no ban notice — just the greyed-out playlists. You're simply moved into a separate matchmaking pool with limited playlist access while you sort out the hardware settings. Per Activision, the restriction is specific:
| Game | What you can still play if attestation fails |
|---|---|
| Black Ops 7 | Nuketown 24/7 only |
| Warzone | Battle Royale Casual only |
| Other CoD titles | Unaffected — TPM 2.0 / Secure Boot are not required |
So if you've noticed you can only load into Nuketown or BR Casual and everything else says the playlist is unavailable, that's the attestation lockout — not a bug, and not a shadowban.
How do you fix "Failed Attestation Status"? (step-by-step)
Work through these in order. The official Secure Attestation Wizard (Step 1) will usually tell you exactly which of the later steps you actually need.
⚠️ Before you touch BIOS: changing UEFI/BIOS settings incorrectly can cause boot failures. Activision's own support article warns that "Activision is not responsible for changes made to your UEFI/BIOS settings." If you're not comfortable in BIOS, check your motherboard manual or ask your hardware vendor. Note your current settings before changing anything.
Step 1 — Run the Call of Duty Secure Attestation Wizard
Activision provides a free Call of Duty Secure Attestation Wizard (`CODSecureAttestationWizard.exe`) that scans your BIOS/security configuration and reports exactly what's non-compliant. Download it from the official Player Support page, extract the .zip, run the .exe, accept the terms, and run the scan.
- System compliant → your PC already meets the requirements; the issue is elsewhere (try clearing the TPM in Step 5, or restart the game).
- System not compliant → the wizard lists each setting that needs fixing (TPM, Secure Boot, GPT, UEFI, BIOS firmware), which maps directly to the steps below.
Step 2 — Check and enable TPM 2.0
First check whether TPM is already on:
- Press Windows key + R, type `tpm.msc`, press Enter.
- If you see "The TPM is ready for use" with Specification Version 2.0, TPM is enabled.
- If you see "Compatible TPM cannot be found," it's disabled in BIOS (or unsupported).
To enable it, reboot into BIOS/UEFI (usually Del or F2 at startup) and turn on the relevant setting:
- Intel CPUs: enable Intel PTT (Platform Trust Technology).
- AMD CPUs: enable AMD CPU fTPM (firmware TPM).
- Discrete TPM: if your board has a physical TPM header/chip, set the TPM device to the dTPM option.
Save and exit, then re-check with `tpm.msc`.
Step 3 — Enable Secure Boot (UEFI boot mode + GPT disk)
Secure Boot has three prerequisites, all of which the wizard checks:
| Requirement | Correct setting | How to check |
|---|---|---|
| Boot mode | UEFI (not Legacy/CSM) | BIOS boot menu |
| Disk partition style | GPT (not MBR) | `diskmgmt.msc` → drive Properties → Volumes tab |
| Secure Boot | Enabled | `msinfo32` → "Secure Boot State: On" |
If your boot mode is Legacy or your disk is MBR, you must convert before Secure Boot will turn on. Windows includes the `mbr2gpt` tool to convert MBR → GPT without data loss, but back up first. Once you're on UEFI + GPT, enable Secure Boot in BIOS, save, and reboot. Confirm with PowerShell: `Confirm-SecureBootUEFI` should return True.
Step 4 — Update your BIOS / firmware (the AMD fix)
This is the step that resolves most stubborn cases, especially on AMD. If the wizard says "BIOS Firmware Update Required" — or you've enabled TPM 2.0 and Secure Boot but Call of Duty still prompts you — your motherboard firmware is too old for attestation.
- Go to your motherboard (or prebuilt/laptop) manufacturer's support page, find your exact model, and download the latest stable BIOS.
- Follow the manufacturer's flashing instructions (most modern boards flash from a USB stick via the BIOS menu).
- AMD users: this specifically updates the fTPM "manufacturing version" out of the problematic 3.x.0.x range that Activision flagged.
After flashing, re-enter BIOS to confirm fTPM/PTT and Secure Boot are still enabled (a BIOS update can reset them to default).
Step 5 — Clear the TPM and re-verify
If everything reads as enabled but the error persists, clearing the TPM forces a fresh set of attestation keys:
- Open `tpm.msc` → on the right, click Clear TPM… and let the PC reboot (you may need to confirm the clear at the BIOS splash).
- After reboot, re-open `tpm.msc` to confirm "The TPM is ready for use."
- In PowerShell, run `Get-Tpm` and check that `TpmReady` and `TpmPresent` are True.
- Make sure Windows is fully updated — a "TCG Event Log Failed" result in the wizard means your Windows build is out of date.
- Relaunch Call of Duty and let the attestation check re-run.
Requirements at a glance
Use this to confirm your hardware even qualifies before you start flashing firmware:
| Component | Requirement |
|---|---|
| Operating system | Windows 10 (version 22H2 or later) or Windows 11 (any version) |
| Intel CPU | 8th Gen or newer (with Intel PTT) |
| AMD CPU | Ryzen 2000 series or newer (with AMD fTPM) |
| TPM | Version 2.0 enabled |
| Boot mode | UEFI |
| Disk | GPT partition style |
| Secure Boot | Enabled |
Windows 11 PCs almost always pass already, because TPM 2.0 and Secure Boot are mandatory for Windows 11 itself. The systems that fail are overwhelmingly Windows 10 builds and older custom rigs where these settings were never switched on.
Call of Duty - Ranked Boost
Get ranked boost in 10 minutes
Who is most affected by failed attestation?
The systems most likely to fail RICOCHET attestation fall into two clear groups:
- Windows 10 custom-built PCs. Steam's PC hardware survey shows that roughly one-third of active PC gamers worldwide still run Windows 10 — the platform where TPM 2.0 and Secure Boot are disabled by default because Microsoft never required them for Windows 10 installation. If you built or bought your PC before the Windows 11 era (pre-2021), there is a very real chance both settings have always been off.
- AMD Ryzen 2000–5000 series boards (2018–2022). Activision specifically identified that AMD fTPM firmware in the 3.x.0.x version range can fail Microsoft's Azure Attestation check even when TPM 2.0 appears enabled in Windows. The firmware fix is a BIOS update from your motherboard maker — see Step 4. This is the single most common cause of "I already enabled TPM and it still fails" reports on AMD boards.
Windows 11 users almost never trigger this error because TPM 2.0 and Secure Boot are mandatory prerequisites for Windows 11 installation — Microsoft enforced what Activision now requires. If you upgraded your existing PC to Windows 11 without a clean install, however, double-check that TPM and Secure Boot are still enabled; the upgrade path occasionally leaves BIOS defaults untouched.
What do the different attestation error codes mean?
The Secure Attestation Wizard can return several specific messages. Here's what each one is telling you: For more, see our guide on Warzone & Black Ops 7 enrollaik.exe Error Fix.
| Wizard message | What it means / fix |
|---|---|
| TPM 2.0: Not Enabled | Turn on Intel PTT / AMD fTPM in BIOS (Step 2). |
| Secure Boot: Not Enabled | Enable Secure Boot in BIOS (Step 3). |
| Boot Partition not set to GPT | Convert MBR → GPT (`mbr2gpt`), then enable Secure Boot. |
| BIOS Boot mode not set to UEFI | Switch from Legacy/CSM to UEFI in BIOS. |
| BIOS Firmware Update Required | Flash the latest BIOS from your board maker (Step 4). |
| Authorization Key Failed | UAC permissions issue — click Generate Key and approve the `enrollaik.exe` prompt. |
| TCG Event Log Failed | Windows is out of date — restart and install the latest Windows update. |
Tips to avoid the error coming back
- Re-check after every BIOS update. Flashing firmware often resets fTPM/PTT and Secure Boot to default — re-enable them or you'll fail attestation again.
- Don't queue with non-compliant friends. One failing party member fails the whole party; have everyone pass attestation solo first.
- Avoid VPN/spoof "easy lobby" tricks in Season 5. With Remote Attestation reading your system state through Microsoft, manipulating matchmaking with sketchy tools is riskier than ever. If you want lower-skill lobbies, do it the safe way (see below).
- Keep Windows current. A stale Windows build is a common cause of the "TCG Event Log Failed" result.
- Troubleshoot other post-update issues separately. If you're also seeing crashes or FPS drops after the same Season 5 update, that's a distinct issue from attestation — see the Black Ops 7 Crashing & FPS Drop Fix.
Once you're back in and able to load every playlist, the grind picks up where it left off — whether that's getting into easier Warzone lobbies or working through the BO7 Prestige system. If you'd rather skip the slog — leveling weapons, climbing ranked, or chasing mastery camos — the Call of Duty boosting services at timesaver.gg are run by pro players and built to save you time.
Check out our Call of Duty services
- CoD Account & Weapon Leveling — skip the grind · level guns and your account fast · handled by pro players
- CoD Bot Lobbies — easy lobbies · rack up kills and complete camo challenges · no VPN spoofing on your account
- CoD Camo Unlocks (BO7) — unlock mastery camos · fast · secure
- All Call of Duty services — every BO7, Warzone and BO6 offer in one place
- BO7 Endgame Guide — what to do once you're back in every playlist
FAQ
Is "Failed Attestation Status" a ban? No. It's a security check, not a punishment. Your account is fine — you're just placed in a restricted matchmaking pool (Nuketown 24/7 in Black Ops 7, Battle Royale Casual in Warzone) until your PC passes the TPM 2.0 / Secure Boot attestation.
I enabled TPM 2.0 and Secure Boot but still get the error — why? Your BIOS firmware is most likely out of date. Update to the latest stable BIOS from your motherboard or system maker (this is the key fix for AMD boards with older fTPM versions in the 3.x.0.x range), then re-enable TPM and Secure Boot afterward, since a BIOS flash can reset them.
Do I need TPM 2.0 and Secure Boot for every Call of Duty game? No. They're required only for Black Ops 7 and Warzone — and the same hardware check applies to mw4 bios firmware update required if you're hitting that error in MW4. Other currently available Call of Duty titles don't require them, though enabling both is recommended for security.
Does this affect console players? No. The TPM 2.0 / Secure Boot attestation applies to PC. Consoles aren't affected, but a PC player who fails attestation can't match with compliant PC or console players.
Will turning on TPM or Secure Boot delete my files? Enabling TPM 2.0 and Secure Boot does not erase data. However, converting your disk from MBR to GPT changes the partition table, so back up important files before running `mbr2gpt`, and always note your current BIOS settings before changing them.
How do I quickly check if my PC is compliant? Run the official Call of Duty Secure Attestation Wizard — it scans your BIOS settings and lists exactly what (if anything) needs to change. You can also spot-check with `tpm.msc` (TPM status) and `msinfo32` (Secure Boot State).
Does a VPN cause the failed attestation error? No — a VPN does not cause attestation to fail. The RICOCHET check reads your local TPM chip, BIOS Secure Boot state, and firmware version through Microsoft Azure; it does not route through your IP or network path. That said, if you have a VPN running and are troubleshooting a stubborn failure after fixing all BIOS settings, disabling it during the in-game attestation pass is a quick variable to eliminate.
The wizard says "System Compliant" but the game still shows the error — what now? Your session token is stale. A cached attestation result from before your BIOS fix can persist in-game even after the hardware now passes. Fix: clear the TPM (Step 5), install all pending Windows updates, fully sign out of Battle.net and the CoD launcher, restart both applications, then launch the game fresh. The attestation re-runs and picks up the compliant state.
Sources: Call of Duty RICOCHET Anti-Cheat Season 04 Update (callofduty.com/blog); Activision Player Support — "Trusted Platform Module (TPM) 2.0 and Secure Boot for Call of Duty" (support.activision.com); callofduty.com Season 5 announcement (July 14, 2026). Current as of Season 5, July 2026. Always follow your hardware manufacturer's official instructions when changing BIOS settings.
