Random Number GodsRNG · Enemy Territory · Battlefield · D&D
Friday BF64 + Sunday D&D

Check the calendar. ET pubs running the new Frostbite rotation all week.

Failed Attestation Status despite everything passing – TPM, Secure Boot, AIK, COD Broker all OK (9800X3D / MSI X870E) HELPPP!!!!!

preview

Hey everyone,

I’ve been trying to solve this for hours and I’m running out of things to check, so I’m hoping someone here has dealt with the same situation.

I’ll give the full context because I don’t want to hide anything.

A while ago I got banned from COD after using an Unlock All tool. I know that was stupid and I’m not trying to defend using it. At this point I just want to play COD normally again without cheats, unlock tools or anything like that.

Since then I rebuilt the PC software side, reinstalled Windows, and changed some hardware/firmware identifiers while troubleshooting. After getting everything running again, COD launches perfectly fine, but when I try to enter certain playlists I get:

“You are under Failed Attestation Status. This playlist is currently unavailable.”

The weird part is that basically every attestation test I can find says the PC is fine.

My system:

* Ryzen 7 9800X3D
* MSI MPG X870E EDGE TI WIFI
* BIOS 1.A20
* Windows 10 Pro 22H2
* Build 19045.7663
* UEFI boot
* Secure Boot enabled
* Physical/discrete TPM 2.0 installed
* Infineon SLB9670
* TPM firmware 7.63.3353.0
* COD tested on both Battle.net and Steam

I originally used AMD fTPM, but I later installed a discrete Infineon TPM and selected it in the BIOS.

Windows correctly detects the new TPM:

Manufacturer: IFX
Manufacturer Version: 7.63.3353.0
Specification Version: 2.0
Status: The TPM is ready for use

tpmtool getdeviceinformation gives:

TPM Present: True
TPM Version: 2.0
TPM Manufacturer: Infineon

Is Initialized: True
Ready For Storage: True
Ready For Attestation: True
Is Capable For Attestation: True
Clear Needed To Recover: False
TPM Has Vulnerable Firmware: False
Is Locked Out: False

Get-Tpm gives:

TpmReady: True
TpmEnabled: True
TpmActivated: True
TpmOwned: True

ManufacturerIdTxt: IFX
ManufacturerVersion: 7.63.3353.0
AutoProvisioning: Enabled
LockedOut: False

The Endorsement Key certificate is also present and valid.

It identifies as:

TPMModel=SLB 9670 TPM2.0
TPMManufacturer=IFX

and the EK certificate is issued by:

Infineon OPTIGA(TM) RSA Manufacturing CA 035

Secure Boot is definitely enabled:

Confirm-SecureBootUEFI

returns:

True

msinfo32 shows:

BIOS Mode: UEFI
Secure Boot State: On

One weird thing is:

PCR7 Configuration: Binding Not Possible

although I understand that this does not necessarily mean attestation itself is broken.

I also restored the Secure Boot factory keys in the MSI BIOS:

Security → Secure Boot → Custom → Key Management → Restore Factory Keys

Then changed Secure Boot back to Standard.

Secure Boot still reports True afterwards.

The official Call of Duty Secure Attestation Wizard 1.1.3 says:

System compliant

TPM 2.0 passes.

Secure Boot passes.

There is no “Generate Key” button because the Wizard does not detect an Authorization Key failure.

I checked the COD Broker Service as well.

It exists:

COD.Broker.Service

and while COD is running:

Status: Running
StartType: Automatic

(I tested both Manual and Automatic.)

The broker log says:

Enroll AIK result 0.

I went further and manually tested Microsoft AIK enrollment:

certreq.exe -EnrollAIK -machine -config ""

This succeeds completely.

Result:

PkiStatus(0): SCEPDispositionSuccess
EnrollStatus(1): Enrolled
The operation completed successfully. 0x0
Submit(ChallengeAnswer): OK
HTTP/1.1 200 OK

Microsoft actually issues a new AIK certificate successfully.

I checked the Microsoft Platform Crypto Provider too:

certutil.exe -csp "Microsoft Platform Crypto Provider" -key

and I have:

ActivisionAIK
TestAIK-...
TestAIK-...

So ActivisionAIK exists as well.

I also checked Windows logs immediately after reproducing the Failed Attestation error.

Code Integrity only shows:

Code Integrity will enable WHQL driver enforcement for this boot session.

TPM events show:

The TPM was successfully provisioned and is now ready for use.
The TBS device identifier has been generated.

There are no TPM, TBS, Secure Boot or Code Integrity errors at the time COD rejects the playlist.

Measured Boot logs are also being created normally under:

C:\Windows\Logs\MeasuredBoot

The newest logs are generated after every reboot.

Things I have already tried:

* TPM 2.0 enabled
* switched from AMD fTPM to discrete TPM
* Secure Boot enabled
* CSM/legacy boot not being used
* UEFI boot
* restored Secure Boot factory keys
* switched Secure Boot Custom → Standard afterwards
* fully updated Windows
* latest relevant drivers
* COD Secure Attestation Wizard
* COD Broker Service running
* Broker set to Manual
* Broker set to Automatic
* Scan and Repair
* reboot/cold boot
* manual AIK enrollment
* tested BattleNet
* installed the game again on Steam and tested there

Steam gives the exact same Failed Attestation Status, so it doesn't seem to be a Battle.net-specific problem.

The thing that confuses me most is that the actual Microsoft AIK infrastructure accepts this TPM:

IFX-KeyId-...
microsoftaik.azure.net
HTTP 200 OK
Enrolled

and even COD's own Broker reports:

Enroll AIK result 0

yet the game still considers the machine to have failed attestation.

I have already submitted the Activision TPM Diagnostic Report for systems that pass the Wizard but still fail in-game.

I’m not trying to bypass the attestation checks. I’m trying to figure out why the machine passes every official test but the game still rejects it.

Has anyone had this exact combination?

Especially interested if you have:

* Ryzen 7000/9000
* MSI X870/X870E
* an Infineon SLB9670 discrete TPM
* Wizard = System Compliant
* Ready For Attestation = True
* AIK enrollment = HTTP 200
* but COD still gives Failed Att