Update for TPM 2.0 for COD/BF6

Alan J T

Alan J T

😛🖥️⌨️🖱️🎮😛🤐💻🤐🤐🤐🤐🤐🤐
Global Moderator
Joined
Sep 11, 2020
Messages
20,738
MSI have started to release a Patched BIOS for ALL the AM4 Motherboards, this is to remedy the COD/BF6 Game TPM error message.
Please keep an eye on the MSI web page of your motherboard for the BIOS updates.
Before you apply the BIOS Update, you will need to disable TPM in the BIOS to prevent problems with Windows Hello and Windows Activation errors.

--Edit Sept.12--


- Turn off/backup/suspend bitlocker before BIOS flash (if you use the feature)
- Disable TPM in BIOS before BIOS flash
BIOS are available here

MSI Tool Summary - Motherboard

BIOS Update is not mandatory. We recommend to NOT do BIOS update unless you notice issues that could possibly be fixed by BIOS update.
sites.google.com sites.google.com
1757666943697.png

These BIOS are coming straight from MSI, but if you have any concern, wait for official website upload version.
Update BIOS at your own discretion.
If BIOS for your board is not here or on the website, it means it is not ready yet.
Known AMD Limitation
- AMD does not support Ryzen 1000, 2000 TPM update
- AMD B550, A520 + Picasso will not work with TPM-B due to AMD limitation
1759225959055.png


Have put in a request to MSI to verify if we have the correct TPM
As users are reporting, TPM Firmware was updated to 3.94.0.5 and not the latest version 3.94.2.5
I may not have this info till sometime on Monday at the earliest.

EDIT 15-Sep 1500 Hours AU (+10GMT)
BIOS updates for 300, 400 and 500 Series Chipsets on the Support Site will contain TPM Patch 3.94.2.5 when available to download
Check Bios Notes to verify
1757913870888.png


--Edit Sept.30--
AM4 BIOS are all up to date with TPM-B Support
 
Last edited:
Sort by date Sort by votes
OK @Alan J T Just so we are clear. This is my Laptop Raider GE68 HX 14VGG the BIOS is E15M2IMS.713 the one the you are Recommending is Laptop GE68 HX 14VHG and BIOS E15M1IMS.714

I just want to be clear that i would be able to update using this BIOS even though my Motherboard is M2 and the one your suggesting is M1

Kind Regards.
 
Upvote 0 Downvote
Upvote 0 Downvote
1781142686469.png

If this is true, why only COD is getting such report? as long as windows report TPM is working on your PC, it's not a problem of MSI.
Never heard of a specific steps to clear "internal security cache", that sounds like go reinstall your windows and start everything from scratch to me. :nono:
 
Upvote 0 Downvote
Goodspeed said:
https://steamcommunity.com/app/1938090/discussions/0/569288155749074494/
I found this on the Steam forum.
Activision has told a user that "Our studio teams are actively investigating this issue. We do not have an exact time frame. Higher teams are working on a solution.".
It seems like Activision is to be blamed this time.
Click to expand...
The OP shared a manual workaround in the same post which works for him.
For people who encountered "Attestation Failed" it might be worth a try:
https://steamcommunity.com/app/1938090/discussions/0/569288155749074494/?ctp=7#c570414689743374999

Press Win + R
Type services.msc
Find COD.Broker.Service
Open Properties
If it's set to Disabled, change it to Manual
Click Apply
Click Start
Launch the game
 
Upvote 0 Downvote
in the last 5 days been mesaging msi and this is the latest mesage!
Please wait for us and we will release a newer BIOS (add the latest secure boot key) for you to check this issue . Please just wait for our reply !
Last Post: 2026-06-11 14:05:57
 
Upvote 0 Downvote
clumpmasterfun15eb02ee said:
in the last 5 days been mesaging msi and this is the latest mesage!
Please wait for us and we will release a newer BIOS (add the latest secure boot key) for you to check this issue
Click to expand...
They're making a test bios by the sounds of it to see if it will fix the problem for you. Whether it will work or not is a bit of a coin toss, as they can not replicate the actual problem.
 
Upvote 0 Downvote
Its getting so exhausting, feeling like I might need to return the PC to the store and get one with a different motherboard
steamcommunity.com

TPM / Secure Boot “Attestation Failed” – What Actually Works and What Doesn’t (Full Breakdown + Support Response) :: Call of Duty® General Discussions

Call of Duty TPM / Secure Boot Attestation Issue – What actually works and what doesn’t I’m posting this so others don’t waste days chasing random fixes like I did. 🔧 System / context MSI B650M motherboard (latest BIOS AMI 2.62) AMD fTPM enabled Secure Boot enabled Windows 11 fully updated TPM...
steamcommunity.com steamcommunity.com

1781296771264.png
 
Upvote 0 Downvote
Hey everyone, just a quick update. Yesterday, I got my Gigabyte B550 Gaming X V2, and the swap was incredibly smooth. After the frustration with the MSI X570-A Pro—spending a lot and never getting anywhere—this board just worked. BIOS updates were simple, and once updated, TPM 2.0 and Secure Boot were enabled right away—no issues. It passed the Warzone attestation test first try. Just wanted to let you all know—if you’re having similar issues, I really recommend going with a Gigabyte motherboard. It’s been flawless, and it made everything easy. Good luck to everyone else!"
 
Upvote 0 Downvote
130344785156902da said:
Hello, I'm encountering a strange issue. I've already updated to the latest BIOS, and both Secure Boot and TPM are functioning properly. I've reviewed your responses to others and confirmed everything, but unfortunately, this problem still persists:
View attachment 211519

| Motherboard Model: MSI X470 GAMING PRO CARBON | | BIOS Version: 7B78v2J5 (Beta version) | | TPM：3.94.2.5 |
Click to expand...
Did you run it as admin, with right-click on 'CODSecureAttestationWizard.exe', then run as administrator.
 
Upvote 0 Downvote
mannyvolme155202d7 said:
Its getting so exhausting, feeling like I might need to return the PC to the store and get one with a different motherboard
steamcommunity.com

TPM / Secure Boot “Attestation Failed” – What Actually Works and What Doesn’t (Full Breakdown + Support Response) :: Call of Duty® General Discussions

Call of Duty TPM / Secure Boot Attestation Issue – What actually works and what doesn’t I’m posting this so others don’t waste days chasing random fixes like I did. 🔧 System / context MSI B650M motherboard (latest BIOS AMI 2.62) AMD fTPM enabled Secure Boot enabled Windows 11 fully updated TPM...
steamcommunity.com steamcommunity.com

View attachment 211623
Click to expand...
I was told the same by Activision and MSI for my X570-A Pro after a week of file shares. Activision says it's on MSI's end and MSI responded saying that the motherboard is at "end of life" and to not expect further BIOS updates for it as they have no direction from AMD at this time.
 
Upvote 0 Downvote
I managed to fix the issue, but in quite an extreme way. TLDR: I installed Windows on new HDD and it fixed the issue.

I have spent so many hours trying to fix the issue, Activision support and other forums like this have all given me advice. Clearing CMOS on my bios / clearing TPM, reinstalling windows on my existing drive (Windows Reset they call it), reinstalling the game, changing bios settings around secure boot and TPM etc etc.

I eventually decided to format one of my HDDs and do fresh install of windows, with no other drives connected. After fresh install, to my surprise, the "bios" issue is solved :-) .

I then plugged my old HDD and booted back to that which of course still has the problem. I tried to compare a heap of settings in Windows to try and work out what the difference is between the windows installs, but I have no idea. We need Activision to help, but they offer no help. They do admit the issue is on their side and being investigated, but that was more than month ago. They do not publicly admit to the problem, which I guess is affecting thousands of customers.

My expectation for Activision would be first to publicly acknowledge the issue as known issue, and ideally either roll back the change until they can solve it or advise customers what they need to change on their windows install or fix their software. They could start by changing the message from being bios issue ;)
 
Upvote 0 Downvote
duncanmille154002dd said:
I eventually decided to format one of my HDDs and do fresh install of windows, with no other drives connected. After fresh install, to my surprise, the "bios" issue is solved :-)
Click to expand...
Please supply the make and serial number of each drive. It could be firmware-related, controller chip-related, or a mix of both

Pictures of the labels would be excellent if possible, just PM them to me
 
Upvote 0 Downvote
god i don't wanna reinstall the whole windows 11 only for this game, but it looks like it's the only way to fix that, msi z-790 p wifi motherboard, last bios, bf 6 works fine, already tried to clear tpm and others solutions but nothing helps - it's so sad actually
 
Upvote 0 Downvote
Hi everyone,

I've spent the last couple of weeks troubleshooting an issue with my MSI Raider GE68 HX 14VGG (MS-15M2) and thought I'd post everything I've found in case it helps someone else.

The Issue​

Call of Duty would not pass the RICOCHET security attestation despite:

  • TPM 2.0 being enabled
  • Secure Boot enabled
  • UEFI boot enabled
  • BIOS fully updated
  • Windows fully updated
The Call of Duty Attestation Wizard showed TPM and Secure Boot as passing, but the game still failed attestation.

Windows Event Viewer Findings​

After investigating Windows Event Viewer I found TPM-WMI Event ID 1041.

The event reports:

HealthStatus = Possibly attestable

PcrsMatchTcgLog = false

BitMaskOfPcrMismatches = 1

This means Windows can see:

  • TPM is present
  • TPM meets minimum version
  • TPM is responsive
  • EK Certificate is available
  • TCG Log exists
However, Windows detects a mismatch between the TPM Platform Configuration Registers (PCRs) and the Measured Boot (TCG) Log.

Because of this mismatch Windows reports:

HealthStatus = Possibly attestable

instead of a fully successful attestation.

Earlier Secure Boot Event​

I also found Kernel-Boot Event ID 292 several times:

Failed to update the SBAT value in FW

However, Windows later generated TPM-WMI Event 1808 confirming:

  • Windows UEFI CA 2023 installed
  • Microsoft UEFI CA 2023 installed
  • KEK 2023 installed
  • Boot Manager (2023) installed
So the Secure Boot key updates eventually completed successfully.

Everything I Tried​

I went through almost every troubleshooting step I could find, including:

  • Updating BIOS to E15M2IMS.713
  • Performing a completely clean Windows installation
  • Clearing the TPM
  • Reprovisioning the TPM
  • Recreating the AIK certificate
  • Verifying the EK certificate exists
  • Confirming TPM Ready = True
  • Confirming TPM Present = True
  • Confirming TPM Owned = True
  • Confirming Secure Boot = Enabled
  • Switching Secure Boot from Custom to Standard
  • Reinstalling the factory Secure Boot keys
  • Loading BIOS Optimized Defaults
  • Clearing the Windows Update cache
  • Installing every available Windows Update
  • Repairing Gaming Services
  • Running SFC and DISM
  • Comparing measured boot logs
None of these changed the Event 1041 result.

Every boot still reports:

HealthStatus = Possibly attestable

PcrsMatchTcgLog = false

BitMaskOfPcrMismatches = 1

What MSI Asked Me To Try​

MSI support requested that I:

  • Reset Secure Boot to Standard mode
  • Install the factory Secure Boot keys
  • Load BIOS Optimized Defaults
  • Clear the Windows Update cache
  • Provide screenshots of:
    • Event ID 1041
    • Event ID 292
    • Event ID 86
    • Intermediate Certification Authorities
    • Secure Boot settings
    • TPM status
I completed every one of these requests.

The issue remained exactly the same.

MSI's Latest Response​

After reviewing all of the evidence, MSI replied:

"It has been confirmed that the PCR value mismatch issue in Event Viewer 1041 can be resolved through a BIOS update. Please wait for the BIOS to be released."
Click to expand...
They also sent me a follow-up message saying:

"Please don't worry, we will open this ticket for you manually until the new BIOS is ready for the PCR mismatch issue."
Click to expand...
To me, this confirms MSI acknowledge that the PCR mismatch is a firmware (BIOS) issue rather than a Windows configuration problem.

Current System Status​

Everything below is working correctly:

  • TPM Present = True
  • TPM Ready = True
  • TPM Enabled = True
  • TPM Activated = True
  • TPM Owned = True
  • Secure Boot Enabled
  • Secure Boot Active
  • Secure Boot Mode = Standard
  • Factory Secure Boot Keys Installed
  • Windows UEFI CA 2023 Installed
  • EK Certificate Present
The only thing that consistently fails is:

PcrsMatchTcgLog = false

which results in:

HealthStatus = Possibly attestable

Conclusion​

After weeks of testing, clean Windows installs, TPM resets and BIOS changes, nothing changed the PCR mismatch.

MSI have now confirmed they are working on a BIOS update specifically to resolve the Event ID 1041 PCR mismatch and have kept my support ticket open until that BIOS is available.

I'm posting this in case anyone else with an MSI Raider GE68 HX 14VGG (or another MSI laptop) is seeing the same Event ID 1041 or Call of Duty attestation failure.

If anyone else has exactly the same Event 1041 output or has already received the newer BIOS from MSI, I'd be very interested to hear your results.
 
Upvote 0 Downvote
mrhough8158102df said:
Hi everyone,

I've spent the last couple of weeks troubleshooting an issue with my MSI Raider GE68 HX 14VGG (MS-15M2) and thought I'd post everything I've found in case it helps someone else.

The Issue​

Call of Duty would not pass the RICOCHET security attestation despite:

  • TPM 2.0 being enabled
  • Secure Boot enabled
  • UEFI boot enabled
  • BIOS fully updated
  • Windows fully updated
The Call of Duty Attestation Wizard showed TPM and Secure Boot as passing, but the game still failed attestation.

Windows Event Viewer Findings​

After investigating Windows Event Viewer I found TPM-WMI Event ID 1041.

The event reports:

HealthStatus = Possibly attestable

PcrsMatchTcgLog = false

BitMaskOfPcrMismatches = 1

This means Windows can see:

  • TPM is present
  • TPM meets minimum version
  • TPM is responsive
  • EK Certificate is available
  • TCG Log exists
However, Windows detects a mismatch between the TPM Platform Configuration Registers (PCRs) and the Measured Boot (TCG) Log.

Because of this mismatch Windows reports:

HealthStatus = Possibly attestable

instead of a fully successful attestation.

Earlier Secure Boot Event​

I also found Kernel-Boot Event ID 292 several times:

Failed to update the SBAT value in FW

However, Windows later generated TPM-WMI Event 1808 confirming:

  • Windows UEFI CA 2023 installed
  • Microsoft UEFI CA 2023 installed
  • KEK 2023 installed
  • Boot Manager (2023) installed
So the Secure Boot key updates eventually completed successfully.

Everything I Tried​

I went through almost every troubleshooting step I could find, including:

  • Updating BIOS to E15M2IMS.713
  • Performing a completely clean Windows installation
  • Clearing the TPM
  • Reprovisioning the TPM
  • Recreating the AIK certificate
  • Verifying the EK certificate exists
  • Confirming TPM Ready = True
  • Confirming TPM Present = True
  • Confirming TPM Owned = True
  • Confirming Secure Boot = Enabled
  • Switching Secure Boot from Custom to Standard
  • Reinstalling the factory Secure Boot keys
  • Loading BIOS Optimized Defaults
  • Clearing the Windows Update cache
  • Installing every available Windows Update
  • Repairing Gaming Services
  • Running SFC and DISM
  • Comparing measured boot logs
None of these changed the Event 1041 result.

Every boot still reports:

HealthStatus = Possibly attestable

PcrsMatchTcgLog = false

BitMaskOfPcrMismatches = 1

What MSI Asked Me To Try​

MSI support requested that I:

  • Reset Secure Boot to Standard mode
  • Install the factory Secure Boot keys
  • Load BIOS Optimized Defaults
  • Clear the Windows Update cache
  • Provide screenshots of:
    • Event ID 1041
    • Event ID 292
    • Event ID 86
    • Intermediate Certification Authorities
    • Secure Boot settings
    • TPM status
I completed every one of these requests.

The issue remained exactly the same.

MSI's Latest Response​

After reviewing all of the evidence, MSI replied:


They also sent me a follow-up message saying:


To me, this confirms MSI acknowledge that the PCR mismatch is a firmware (BIOS) issue rather than a Windows configuration problem.

Current System Status​

Everything below is working correctly:

  • TPM Present = True
  • TPM Ready = True
  • TPM Enabled = True
  • TPM Activated = True
  • TPM Owned = True
  • Secure Boot Enabled
  • Secure Boot Active
  • Secure Boot Mode = Standard
  • Factory Secure Boot Keys Installed
  • Windows UEFI CA 2023 Installed
  • EK Certificate Present
The only thing that consistently fails is:

PcrsMatchTcgLog = false

which results in:

HealthStatus = Possibly attestable

Conclusion​

After weeks of testing, clean Windows installs, TPM resets and BIOS changes, nothing changed the PCR mismatch.

MSI have now confirmed they are working on a BIOS update specifically to resolve the Event ID 1041 PCR mismatch and have kept my support ticket open until that BIOS is available.

I'm posting this in case anyone else with an MSI Raider GE68 HX 14VGG (or another MSI laptop) is seeing the same Event ID 1041 or Call of Duty attestation failure.

If anyone else has exactly the same Event 1041 output or has already received the newer BIOS from MSI, I'd be very interested to hear your results.
Click to expand...
Hi

I have the same motherboard as you and the same issue, did they give you timeframe on the release of this bios update? I wonder if there is a beta version available that would fix this....
 
Upvote 0 Downvote
grant19912c302b0 said:
Hi

I have the same motherboard as you and the same issue, did they give you timeframe on the release of this bios update? I wonder if there is a beta version available that would fix this....
Click to expand...
Unfortunately no they didnt. They are keeping my Ticket open until a new BIOS is released. I did say I would be happy to try any Beta they released but didnt hear back as yet.
 
Upvote 0 Downvote
Back
Top