As you know, the ban system now is currently mostly targeting the TPM; the solution is to perform a BIOS update and purchase an external DTPM module compatible with your motherboard.
Quick TPM / Attestation Check
Open Command Prompt as Administrator:
Then run:
tpmtool getdeviceinformation
This checks if the TPM is detected and ready.
Then run:
tpmtool comparepcr sha256
This is the most important test.
If you get:
TCG Log and Hardware PCRs match!
your TPM measurements are matching correctly.
If you get multiple PCR mismatch messages, the problem is likely related to TPM attestation / Measured Boot / BIOS, not just Call of Duty.
You can also open PowerShell as Administrator and run:
Get-Tpm
The main values should normally show:
TpmPresent : True
TpmReady : True
TpmEnabled : True
TpmActivated : True
Also run the Call of Duty Secure Attestation Wizard.
If the COD Attestation Wizard says your system is compliant, but:
tpmtool comparepcr sha256
still shows PCR mismatches, then the issue is likely deeper in the BIOS / dTPM attestation path.
I finally found what was causing my COD attestation problem while using a discrete/external TPM.
My setup was passing Secure Boot, TPM 2.0, EK certificate, AIK enrollment, and Windows was showing the TPM as ready for attestation, but COD could still show Failed Attestation Status.
The command that helped me find the real problem was:
cmd//
tpmtool comparepcr sha256
When the issue was happening, Windows showed PCR mismatches.
What I found is this:
Normal Windows Restart
= PCR mismatch
Full shutdown + completely removing power from the PC
= PCR match
After shutting the PC down, turning the PSU off/unplugging it for a short time, then powering it back on, I get:
TCG Log and Hardware PCRs match!
So in my case the issue looks related to how the motherboard BIOS and the external TPM behave during a normal warm restart.
For now, the workaround is simple:
Shut the PC down completely.
Turn off the PSU or unplug the PC.
Wait a little until the motherboard fully loses power.
Power it back on.
Run:
tpmtool comparepcr sha256
If it says:
TCG Log and Hardware PCRs match!
then try COD again.
A normal Restart can make the mismatch come back, so this is more of a workaround than a permanent fix.
Which dTPM should you buy?
Do not buy a random TPM 2.0 module.
The module has to match your motherboard.
Check your motherboard manual or support page and look for:
TPM header type
Pin layout, for example 12-1 pin, 14-1 pin, etc.
SPI support
Official TPM compatibility list
AMD or Intel platform support
The easiest way is to search:
your motherboard model + TPM 2.0 module compatibility
For example, many MSI AM5/B650 boards use an SPI 12-1 pin TPM 2.0 module, and some support modules based on the Infineon SLB9672.
Just because two modules are both TPM 2.0 does not mean they are compatible. The connector and pin layout must match your motherboard.
discord :
7mze
Quick TPM / Attestation Check
Open Command Prompt as Administrator:
Then run:
tpmtool getdeviceinformation
This checks if the TPM is detected and ready.
Then run:
tpmtool comparepcr sha256
This is the most important test.
If you get:
TCG Log and Hardware PCRs match!
your TPM measurements are matching correctly.
If you get multiple PCR mismatch messages, the problem is likely related to TPM attestation / Measured Boot / BIOS, not just Call of Duty.
You can also open PowerShell as Administrator and run:
Get-Tpm
The main values should normally show:
TpmPresent : True
TpmReady : True
TpmEnabled : True
TpmActivated : True
Also run the Call of Duty Secure Attestation Wizard.
If the COD Attestation Wizard says your system is compliant, but:
tpmtool comparepcr sha256
still shows PCR mismatches, then the issue is likely deeper in the BIOS / dTPM attestation path.
I finally found what was causing my COD attestation problem while using a discrete/external TPM.
My setup was passing Secure Boot, TPM 2.0, EK certificate, AIK enrollment, and Windows was showing the TPM as ready for attestation, but COD could still show Failed Attestation Status.
The command that helped me find the real problem was:
cmd//
tpmtool comparepcr sha256
When the issue was happening, Windows showed PCR mismatches.
What I found is this:
Normal Windows Restart
= PCR mismatch
Full shutdown + completely removing power from the PC
= PCR match
After shutting the PC down, turning the PSU off/unplugging it for a short time, then powering it back on, I get:
TCG Log and Hardware PCRs match!
So in my case the issue looks related to how the motherboard BIOS and the external TPM behave during a normal warm restart.
For now, the workaround is simple:
Shut the PC down completely.
Turn off the PSU or unplug the PC.
Wait a little until the motherboard fully loses power.
Power it back on.
Run:
tpmtool comparepcr sha256
If it says:
TCG Log and Hardware PCRs match!
then try COD again.
A normal Restart can make the mismatch come back, so this is more of a workaround than a permanent fix.
Which dTPM should you buy?
Do not buy a random TPM 2.0 module.
The module has to match your motherboard.
Check your motherboard manual or support page and look for:
TPM header type
Pin layout, for example 12-1 pin, 14-1 pin, etc.
SPI support
Official TPM compatibility list
AMD or Intel platform support
The easiest way is to search:
your motherboard model + TPM 2.0 module compatibility
For example, many MSI AM5/B650 boards use an SPI 12-1 pin TPM 2.0 module, and some support modules based on the Infineon SLB9672.
Just because two modules are both TPM 2.0 does not mean they are compatible. The connector and pin layout must match your motherboard.
discord :
7mze