Categories About Us Contact Us Become a Member

How to fix RICOCHET TCG Event Log Failed in Call of Duty

This means your Windows build is out of date, so the trusted boot log the attestation check reads is invalid. Updating Windows resolves it. Jump to your situation below or work through the methods in order.

By Neeraj Singh ~5 min Updated Jun 2026 84% found this helpful
Error message
TCG Event Log Failed. Secure Attestation Wizard result.
Summary

A TCG Event Log Failed result in the Call of Duty Secure Attestation Wizard means your Windows build is out of date, so the TCG (Trusted Computing Group) event log that records your trusted boot measurements is not in a state RICOCHET's attestation can validate. TPM and Secure Boot may be enabled correctly, but the boot log itself fails the check. The fix is straightforward: fully update Windows, including all pending quality and cumulative updates, then restart so the boot log is rewritten cleanly, and re-run the Secure Attestation Wizard. If it still reports the TCG log after updating, running the built-in Windows system repairs (sfc /scannow and DISM) rebuilds a corrupted boot measurement log. Because this is a Windows-update problem rather than a hardware one, it usually clears without any BIOS changes.

What this error means

The TCG event log records the measurements taken during a trusted boot, and RICOCHET's attestation reads it to confirm your PC booted in a known-good state. A TCG Event Log Failed result means that log is invalid, which the Secure Attestation Wizard ties to an out-of-date Windows build.

Updating Windows fully and restarting rewrites the boot log so it passes. If a stale or corrupted log persists after updating, the Windows system-file repairs rebuild it. No BIOS change is normally needed for this specific result.

Common causes

Windows is missing quality or cumulative updates.
The trusted boot log is stale after a firmware or setting change.
A corrupted boot measurement log.
The PC was not restarted after a recent update.
Expert insight

“TCG Event Log Failed sounds scary but it is usually the easiest one, your Windows is just behind. The event log is the record of your trusted boot, and if Windows is out of date the attestation cannot trust it. So I run Windows Update until there is nothing left, restart so the log gets rewritten, and re-run the wizard. If it is stubborn, sfc and DISM rebuild the log. You almost never need to touch the BIOS for this one.”

How to fix it

Method 1

Fully update Windows

1Install every pending update in Settings, Windows Update, including optional quality updates.
2This is the fix the Secure Attestation Wizard points to for a TCG log failure.
3Continue to the restart.
Method 2

Restart and re-run the wizard

1Restart the PC so the trusted boot log is rewritten cleanly.
2Run the Secure Attestation Wizard again.
3Relaunch Call of Duty.
Method 3

Rebuild a corrupted boot log

1If the wizard still flags the log, repair Windows from an admin Command Prompt:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
2Restart afterwards.
3Re-run the wizard.
Method 4

Confirm TPM and Secure Boot are still on

1Verify with
tpm.msc
msinfo32
that TPM reads 2.0 and Secure Boot State is On.
2A firmware update can reset these.
3Re-enable them if needed, then retry.

A TCG Event Log Failed result in the Secure Attestation Wizard means Windows is out of date. Fully update Windows, restart so the boot log is rewritten, and re-run the wizard. If it persists, rebuild the log with sfc /scannow and DISM. Confirm TPM 2.0 and Secure Boot are still enabled.

Frequently asked questions

What does TCG Event Log Failed mean?
It means the trusted boot log RICOCHET's attestation reads is invalid, which the Secure Attestation Wizard attributes to an out-of-date Windows build. TPM and Secure Boot can be on, but the boot log itself fails.
How do I fix the TCG Event Log error?
Fully update Windows with all pending quality and cumulative updates, restart so the boot log is rewritten, and re-run the Secure Attestation Wizard. If it persists, run sfc /scannow and DISM to rebuild the log.
Do I need to change BIOS settings?
Usually not. TCG Event Log Failed is a Windows-update problem, so updating Windows and restarting fixes it. Only confirm TPM 2.0 and Secure Boot are still enabled if a recent firmware update reset them.
Why does an old Windows build cause this?
The TCG event log records your trusted boot measurements, and an out-of-date Windows can produce a log the attestation cannot validate. Updating brings the boot components in line so the log passes.
What is the TCG event log?
It is the Trusted Computing Group log of measurements taken during a trusted boot, stored so a verifier can confirm the PC started in a known-good state. RICOCHET's attestation checks it as part of verifying your system.
It still fails after updating, what now?
Restart to rewrite the log, then run sfc /scannow and DISM to repair a corrupted log. Confirm TPM 2.0 and Secure Boot remain enabled, then re-run the Secure Attestation Wizard.

Still not working?

If the wizard clears TCG but you are still restricted, the remaining fault is usually TPM, Secure Boot or firmware related, so work through the Failed Attestation steps next. You can also submit your error to us for a tailored fix.

Was this fix helpful? Thanks for your feedback!