CoD Attestation Fails on MW4 Beta Despite TPM 2.0

Even when a PC checks all the usual “secure” boxes, Activision’s attestation flow can still fail—because the last step isn’t about TPM or Secure Boot. A recent reproduction on a Razer Blade 16 running Windows 11 showed TPM 2.0 and Secure Boot passing, while the overall attestation ended with an error tied to CODBrokerInstaller.exe and Windows permissions.

What the test found: TPM 2.0 and Secure Boot pass, attestation still fails

In a case reproduced using Activision’s official Secure Attestation Wizard, two core requirements were detected correctly: TPM 2.0 was available and Secure Boot was enabled. The PC also booted into Windows 11 in UEFI mode, and the wizard flagged neither of those prerequisites as problematic.

However, the final attestation result still failed. The wizard reported: “Proof requirement not met.” The tool pointed to CODBrokerInstaller.exe as the reason, stating that the application did not receive the required permission. Because of that, the system was only labeled “temporarily compliant,” not fully verified.

How to separate the problem: firmware checks vs. the CODBrokerInstaller step

This specific failure mode is important because it helps distinguish two categories of issues:

TPM 2.0 / Secure Boot configuration: In the reproduced case, both were recognized successfully by the wizard.
Registration/authorization step: The failure happened later, during the CODBrokerInstaller.exe permission step inside the attestation process.

That means users encountering the “proof requirement not met” style outcome shouldn’t automatically assume their BIOS or TPM/Secure Boot setup is wrong—at least not in this scenario.

CODBrokerInstaller permissions: check UAC first

Activision’s guidance for the CODBrokerInstaller-related error centers on Windows User Account Control (UAC). The installer component needs the appropriate permission while registration runs as part of attestation.

UAC steps to try before re-running the wizard

Check the current Windows UAC setting.
If no UAC prompt appears, set UAC to the standard level or to “Always notify.”
Restart Call of Duty (so the attestation components reinitialize cleanly).
Run the attestation wizard again after those changes.

What happened in the reproduced case

On the test system, UAC was already set to the Windows default when the wizard was first run, yet no prompt appeared for CODBrokerInstaller.exe. After switching UAC to “Always notify,” the tester ran the flow again and initially hit the same failure at the same step.

So while UAC is the first thing to check for this specific error message, the reproduced results also suggest it may not be the only factor in every setup.

When a firmware issue might still matter

If the wizard’s messaging explicitly points toward firmware problems rather than CODBrokerInstaller permissions, then BIOS-level or TPM firmware updates could become relevant. In the reproduced scenario, though, the wizard’s stated cause was the permission shortfall for CODBrokerInstaller.exe.

Why this matters for Modern Warfare 4 (even though the bug isn’t confirmed)

Activision has stated that TPM 2.0 and Secure Boot are PC requirements for Modern Warfare 4. While it’s not fully documented whether the beta uses the exact same downstream attestation steps seen in other titles, the structure of the process makes it realistic that MW4’s verification includes a similar “after prerequisites, then register/authorize” phase.

That’s why the test is still useful: it demonstrates that even a correctly configured system can fail attestation during the final permission/registration step—despite showing green checks for TPM and Secure Boot.

Quick takeaways for MW4 pre-checks

Passing TPM 2.0 and Secure Boot does not guarantee successful attestation if the later CODBrokerInstaller.exe permission step fails.
For this error type, start by checking Windows UAC settings and re-launching Call of Duty before re-running attestation.
The CODBrokerInstaller permission issue wasn’t confirmed as an MW4-only bug in this report, but MW4 still requires TPM 2.0 and Secure Boot, making the risk of a similar failure path plausible.