This means FACEIT needs TPM 2.0 enabled and working, and yours is off or cannot attest. Enabling it and clearing the attestation issue fixes it. Jump to your situation below or work through the methods in order.
FACEIT Anti-Cheat requires TPM 2.0, and pairs it with Secure Boot for boot attestation. You will see TPM 2.0 required if it is off, or TPM attestation failed if it is on but cannot produce a valid, trusted report. To enable it, turn on TPM 2.0 in BIOS (Intel PTT or AMD fTPM), with Windows in UEFI mode on a GPT disk. Then confirm it works: tpm.msc should say the TPM is ready and Specification Version 2.0, and in Windows Security, Device Security, Security processor details, Attestation should read Ready. For attestation failures, the common fixes are to switch from a discrete TPM (dTPM) to firmware TPM (fTPM) in BIOS, update your motherboard BIOS (AMD boards reporting version 3.*.0.* have a known TPM issue fixed by a BIOS update), and, if you use a self-signed boot loader, boot Windows directly from Windows Boot Manager via the boot menu, since self-signed loaders break attestation. Once TPM 2.0 is enabled and attesting, FACEIT lets you connect.
TPM 2.0 is a security chip that signs a measured record of your boot. FACEIT requires it, with Secure Boot, so it can verify a tamper-proof report that no unauthorized software loaded. TPM 2.0 required means it is off; attestation failed means it is on but cannot produce a trusted report.
Enabling TPM 2.0 in BIOS fixes the requirement, and confirming attestation Ready in Windows Security fixes the rest. Attestation failures usually come from a discrete TPM, an out-of-date BIOS, or a self-signed boot loader, each with a direct fix.
“TPM required is easy, just enable it, Intel PTT or AMD fTPM, in UEFI on a GPT disk. Attestation failed is the interesting one, because TPM is on but cannot give FACEIT a clean report. Nine times out of ten switching from a discrete TPM to firmware fTPM fixes it, and on AMD boards showing version 3-point-something a BIOS update is the known cure. And if someone is dual-booting with a self-signed loader, that breaks attestation, so boot Windows directly from Windows Boot Manager. Check attestation reads Ready in Windows Security and you are done.”
tpm.msc
FACEIT requires TPM 2.0. Enable it in BIOS (Intel PTT or AMD fTPM) with Windows in UEFI on a GPT disk, and confirm in tpm.msc it is ready and version 2.0. For TPM attestation failed, switch from dTPM to fTPM, confirm Attestation reads Ready in Windows Security, update the BIOS (AMD version 3.*.0.* has a known fix), and boot Windows directly if you use a self-signed loader.
If attestation still fails after fTPM and a BIOS update, clearing the TPM in tpm.msc (back up BitLocker keys first) and re-enabling it can restore a clean attestation state. You can also submit your error to us for a tailored fix.
