This error occurs when the FACEIT Anti-Cheat is unable to verify the integrity of your TPM (Trusted Platform Module) 2.0. This is typically caused by a configuration issue or the use of unverified software during the boot process.
We’ve identified and documented four common causes for this issue:
Case 1: Playing from an Internet Cafe Using CCU Cloud Update
A known interaction between CCU Cloud Update and TPM functionality can sometimes cause this error.
Please reach out directly to CCU Cloud Update support. They’ll guide you through the necessary steps to restore proper TPM functionality.
Case 2: Faulty Discrete TPM (dTPM) Module
If your motherboard has a discrete TPM (dTPM) module installed, it might be the source of the problem. You can check if you have dTPM in your BIOS, where you enabled TPM, the settings menu may present a choice between "dTPM" (discrete) and "fTPM" (firmware).
We recommend switching to firmware-based TPM (fTPM). This simple change often resolves issues associated with discrete TPM modules.
Case 3: Interference from Old GRUB Versions
Older versions of the GRUB bootloader may sometimes interfere with TPM attestation, leading to this error.
- Test the Bootloader: Try booting directly into Windows using your motherboard's boot menu (often accessible by pressing F10, F11, or F12 during startup, depending on your manufacturer), bypassing GRUB.
- Verify the Fix: If the TPM error is resolved when booting directly into Windows, then upgrading GRUB to its latest version should fix the issue permanently.
Case 4: Self-Signed Boot Loaders
Self-signed boot loaders are not allowed and will cause TPM attestation to fail. While standard boot loaders from major distributions (like Ubuntu or Fedora) are generally permitted, custom or self-signed versions will trigger this error.
If you cannot avoid using a self-signed boot loader, you must bypass it to use the FACEIT Anti-Cheat:
Solution: Boot Windows directly through your motherboard’s boot menu.
How to do it: Restart your computer and tap the boot menu key (typically F8, F10, F11, or F12) during the startup splash screen. Select Windows Boot Manager from the list to bypass the custom loader and launch Windows directly.
Case 5: Other Scenarios (General Troubleshooting)
If the above cases don’t apply, updating your motherboard’s BIOS can often resolve TPM errors.
To do so, follow these steps carefully:
- Identify Your Motherboard Model:
- Press the Windows key.
- Type msinfo32 and press Enter.
- In the System Information window, locate "BaseBoard Manufacturer" and "BaseBoard Product" Note these details.
- Find BIOS Updates:
- Open your web browser and search for: bios update [your motherboard model] (e.g., "bios update ASUS ROG Strix Z490-E Gaming").
- This search should lead you to the support page of your motherboard's manufacturer website, where you can find the latest BIOS updates and instructions.
💡 Pro Tip: Always double-check that you’re using the correct update for your motherboard model. Keeping your firmware up-to-date ensures your TPM and other system components run smoothly.