FACEIT "Please enable TPM 2.0" / Attestation Failed — Full Fix (2026)

FACEIT Anti-Cheat shows "Please enable TPM 2.0" or "TPM attestation failed" and won't launch. TPM 2.0 is a hardware security module, and FACEIT has made it mandatory for all players since 25 November 2025. Intel exposes it as PTT, AMD as fTPM. This guide gets it on and attesting correctly, plus the Memory Integrity (Core Isolation) step FACEIT often wants alongside it.

What TPM 2.0 is and why FACEIT needs it

TPM 2.0 is a security module present on most modern boards. Windows and FACEIT AC use it to verify your system hasn't been tampered with. Without it the anti-cheat simply will not start. It is officially supported from Windows 11, and as of 25 Nov 2025 it is a hard FACEIT requirement — old "disable TPM to bypass" tricks no longer work.

Step 1 — check whether you even have TPM

Press Win+R → tpm.msc and maximize the window:

• "The TPM is ready for use" + Specification Version 2.0 → it's on. The error is elsewhere — re-check Secure Boot.
• "Compatible TPM cannot be found" → it's switched off in BIOS (or your board doesn't have it).
• Window won't open / odd state → likely no TPM or unsupported hardware.

Board support: Intel since 6th gen (2015), AMD since X370/B350 (2016–17). On X99 / X79 / LGA 1150 / 1155 / 2011 there is usually no module. To be sure, check your exact motherboard model on the vendor's official spec page — not third-party sites.

Step 2 — enable TPM in BIOS

1. Enter BIOSReboot → press Del/F2 → open the Advanced or Security tab (location varies by board).
2. IntelEnable "Intel Platform Trust Technology (PTT)".
3. AMDEnable "AMD fTPM" / "Security Device Support" → AMD CPU fTPM.
4. Save and re-checkSave and reboot, then open tpm.msc again — it should now show 2.0, ready.

Step 3 — the reset cycle (fixes most AMD "attestation failed")

If TPM is on but FACEIT still says "attestation failed", reset it — this clears roughly 80% of AMD cases.

1. BitLocker? Suspend it first⚠ If you use BitLocker, run admin cmd manage-bde -protectors -disable C: first — otherwise Windows will demand the recovery key on boot.
2. Turn fTPM offBIOS → fTPM = Disabled → save → boot into Windows → reboot.
3. Turn it back onBIOS → fTPM = Enabled → save → boot.
4. Clear the TPMOpen tpm.msc → "Clear TPM" (top-right) → reboot and relaunch FACEIT AC.

Step 4 — the AMD firmware bug (version 3.x)

Open Windows Security → Device security → Security processor details. If Manufacturer Version starts with 3.x (e.g. 3.92.0.5), that is a known fTPM/Pluton bug — only a BIOS update fixes it. Download the latest (or a beta) BIOS for your exact board from the vendor site and flash it, then re-check.

Step 5 — turn on Memory Integrity (Core Isolation / VBS)

At higher trust / ELO, FACEIT also requires Memory Integrity — part of Core Isolation, built on Virtualization-Based Security (VBS). It depends on TPM, Secure Boot and CPU virtualization all being on, which is why it lives in the same conversation as TPM.

1. Turn it onSearch "Core isolation" → Windows Security → turn on Memory Integrity → reboot.
2. Greyed out or won't enable?Click "Review incompatible drivers" — it names the exact .sys blocking it. Remove each owner (its uninstaller or pnputil /delete-driver oemNN.inf /uninstall /force).
3. Option missing entirely?Enable virtualization in BIOS (Intel VT-x / AMD SVM) — Memory Integrity is linked to it.

dTPM vs fTPM

If you have a discrete TPM module on a motherboard header (dTPM) and attestation keeps failing, disable it in BIOS and switch to firmware TPM (fTPM/PTT) instead — it's more reliable and is what FACEIT expects on modern systems.

No TPM at all?

On old platforms (Xeon X79/X99, LGA 2011) there is often no TPM 2.0 natively. Your options: a compatible add-on TPM module if your board has the header, or a newer board/CPU. Pirated or "debloated" Windows also frequently breaks TPM, Secure Boot and Windows Update — if you're on a custom build, install an official Windows image first.

With TPM 2.0 active (and Memory Integrity on if asked), the AC should start. If it now asks for Secure Boot, see our Enable Secure Boot guide; for any other code, the FACEIT Anti-Cheat error fixes page covers it.

FAQ