Getting locked out of Multiplayer or DMZ in Call of Duty: Modern Warfare 4 by a "New Key Failed to Generate" or Attestation Failure message is one of the more confusing errors you can hit, because the game itself launches fine. The block happens at the security layer, specifically the RICOCHET Anti-Cheat attestation process that verifies your PC's hardware integrity before letting you into online modes. The fix almost always lives in your firmware or Windows security settings.
Check TPM 2.0 status here
What causes the attestation failure in MW4?
The attestation process checks two hardware security features: Secure Boot and TPM 2.0 (Trusted Platform Module). If either is disabled, misconfigured, or not properly provisioned, the game's security check cannot complete, and the key generation fails. An outdated motherboard BIOS or corrupted Windows system files can also trigger the same result, even when both features appear to be enabled.
Secure Boot and TPM are independent of each other. Confirming one is active tells you nothing about the other, so you need to verify both separately.
How to fix the New Key Failed to Generate error
Work through these fixes in order. Start with the firmware checks before moving to Windows diagnostics, since firmware problems are the most common cause and the easiest to confirm.
Fix 1: Enable Secure Boot in BIOS
Secure Boot is a firmware feature that enforces a trusted startup chain. If it is off, MW4's attestation check will likely fail before it even reaches the TPM.
To enable it:
- Restart your PC and enter the BIOS or UEFI setup. Most systems use Delete, F2, or F10 during POST, but check your motherboard manufacturer's documentation for the exact key.
- Locate the Secure Boot option. Its position in the menu varies by manufacturer.
- Enable Secure Boot, save changes, and restart.
To confirm the status inside Windows without rebooting:
- Press Win + R, type msinfo32, and press Enter.
- Find the Secure Boot State entry.
- Confirm it reads On.
Fix 2: Verify TPM 2.0 is active
Even with Secure Boot enabled, a missing or disabled TPM will still block attestation.
- Press Win + R, type tpm.msc, and press Enter.
- In the TPM Management window, confirm the module is ready for use and that the Specification Version shows 2.0.
If Windows reports no compatible TPM, go back into your BIOS and look for one of these options depending on your hardware:
- Intel PTT (Platform Trust Technology) on Intel systems
- AMD CPU fTPM on AMD Ryzen systems
Enable whichever applies to your CPU, save, and restart.
Fix 3: Update your motherboard BIOS
An outdated BIOS can cause TPM provisioning failures even when the module appears active in Windows. If Secure Boot and TPM 2.0 are both enabled but the error persists, check for a BIOS update.
Before updating:
- Identify your exact motherboard model and current BIOS version through msinfo32 or your manufacturer's support utility.
- Download firmware only from the official manufacturer website.
- Save your BitLocker recovery key if device encryption is active, since firmware updates can trigger a recovery prompt on next boot.
- Do not interrupt the update or remove any USB drive used during the process.
After the update completes, re-enter the BIOS to confirm Secure Boot and TPM 2.0 are still enabled. Firmware updates sometimes reset these settings to their defaults.
Fix 4: Run the Activision attestation check
Once the firmware settings look correct, run Activision's official attestation-checking tool. This verifies whether your system passes the required checks and, where supported, can attempt to generate a new security key. Use only the official tool provided through Activision's support pages. Avoid any third-party utilities that claim to bypass or replicate this process.
If the tool still reports a failure, move on to the Windows-level diagnostics below.
Fix 5: Check TPM attestation status in Command Prompt
Windows includes a built-in command that reports detailed TPM readiness information. Open Command Prompt and run:
tpmtool getdeviceinformation
Look for these two fields in the output:
| Status field | What to look for |
|---|---|
| Ready for Attestation | Should report True |
| Is Capable for Attestation | Should report True |
If either field returns False, the TPM is not ready to complete the attestation check. This narrows the problem to TPM provisioning rather than Secure Boot configuration.
Next, check Windows system files for corruption. Open Command Prompt as an administrator and run:
sfc /scannow
Let the scan finish completely. The System File Checker repairs damaged or missing protected files automatically. If you want to go deeper, also run:
DISM /Online /Cleanup-Image /ScanHealth
This scans the Windows component store for corruption. If DISM identifies issues, a separate repair command may be needed. Restart after both scans complete, then run the attestation check again.
Run SFC to repair system files
Fix 6: Advanced TPM diagnostics in PowerShell
If the error is still present after the steps above, PowerShell can provide more detailed TPM state information. Open PowerShell as an administrator and run:
Get-Tpm
Get-TpmEndorsementKeyInfo
Review the output for signs that the TPM is not ready, provisioning has not completed, or endorsement key information is unavailable.
Two additional commands exist for TPM provisioning:
- Enable-TpmAutoProvisioning
- Initialize-Tpm -AllowClear -AllowPhysicalPresence
After any approved provisioning procedure, restart and recheck TPM status before testing the game again.
Fix 7: Recheck everything and contact support if needed
After completing the relevant steps, run one final check:
- Open PowerShell and run Get-Tpm to confirm the TPM is ready.
- Open Command Prompt and run tpmtool getdeviceinformation to verify both attestation fields show True.
- Run the Activision attestation tool one more time.
If the tool still reports a failure at this point, contact Activision Support directly with your diagnostic results. Repeatedly clearing the TPM or randomizing BIOS settings without a clear diagnosis will cause more problems than it solves.
Quick reference: which fix to try first?
| Symptom | First action |
|---|---|
| Secure Boot shows Off in msinfo32 | Enable in BIOS/UEFI |
| No compatible TPM found in tpm.msc | Enable PTT or fTPM in firmware |
| TPM active but attestation still fails | Run tpmtool getdeviceinformation |
| System files may be corrupted | Run sfc /scannow, then DISM |
| BIOS version is outdated | Download update from manufacturer site |
| TPM provisioning looks incomplete | Use PowerShell diagnostics carefully |
| Attestation fails after all repairs | Contact Activision Support with results |
Does MW4 require Secure Boot and TPM 2.0?
Yes. The attestation process that generates the security key relies on both Secure Boot and TPM 2.0 being active and correctly provisioned. This is tied to the RICOCHET Anti-Cheat system. If your PC was built or configured before these became standard requirements, you may need to make firmware adjustments before MW4's online modes will work. Check Activision's current official system requirements to confirm the exact specifications for your game version.
For other PC setup steps related to these security features, the guide on enabling TPM 2.0 and Secure Boot for MW4 covers the full process in detail.
Once you're past the error and into the game, there's plenty more to work through. The full Modern Warfare 4 strategy guide collection covers everything from reducing visual recoil to specific mission and event challenges.
