Many online game developers have already introduced mandatory requirements to enable TPM 2.0 and Secure Boot in order to fight cheaters more aggressively at the system boot level. For example, Activision has publicly stated its plans to require TPM 2.0 and Secure Boot on PC in future releases and to test these technologies as part of their anti-cheat systems. Electronic Arts went even further - in its flagship 2025 title, Battlefield 6, players cannot connect to servers at all if these options are disabled. Other developers are expected to follow the same path over time.
At the moment, Rust does not strictly require TPM 2.0 or Secure Boot. However, starting in March 2026, server owners will be able to enable an option that only allows players with TPM 2.0 and Secure Boot enabled to join. It is widely expected that by the end of the year, this will become a mandatory requirement for all players, not just on selected servers.
Why TPM 2.0 and Secure Boot Are Linked to Anti-Cheat
Most cheats in Rust are not simple - they are entire ecosystems involving injectors, custom drivers, modified system libraries, process hiding, virtualization, and low-level system manipulation. The deeper a cheat operates in the system, the harder it is to detect using traditional methods.
What Secure Boot Does
Secure Boot is a UEFI feature that ensures only trusted and properly signed software is loaded during system startup. In simple terms, it helps prevent unauthorized bootloaders or low-level components from running before the operating system starts, significantly reducing the risk of system-level tampering.
What TPM 2.0 Does
TPM 2.0 is a hardware-based (or firmware-based) security module that stores cryptographic keys and participates in integrity checks and trusted boot processes. In plain language, it acts as a “hardware root of trust” that is extremely difficult to fake or bypass using software alone.
Why Anti-Cheat Systems Care
When an anti-cheat system or a game can rely on a clean and trusted boot chain, it becomes much harder for cheaters to load modified drivers before the anti-cheat starts, hide kernel-level modifications, or run suspicious configurations where cheats disguise themselves as legitimate system components. This is exactly why publishers and anti-cheat developers continue to tighten system requirements. In practice, this usually means players start seeing warnings telling them to enable Secure Boot or TPM 2.0, or they lose access to certain game modes or matchmaking features if their system does not meet the requirements.
Does This Mean Rust Will Definitely Enforce These Requirements?
Most likely - yes. Even though Rust already uses a working anti-cheat stack (Easy Anti-Cheat / EAC), Facepunch is clearly moving toward stronger environment verification. Preparing for this scenario in advance makes sense - not only for Rust, but because many modern PC games are heading in the same direction.
What You Actually Gain by Enabling TPM 2.0 and Secure Boot
Pros:
-
Lower chance of anti-cheat or the game flagging your system as an “unsafe configuration”
-
A cleaner and more stable boot environment
-
Your PC meets modern Windows security standards, especially relevant if you already use Windows 11 or plan to upgrade
Cons:
-
You may need to switch BIOS settings from Legacy to UEFI and convert your disk from MBR to GPT
-
Older motherboards may not support TPM 2.0
-
Incorrect BIOS configuration can cause boot issues, so backups and caution are strongly recommended
How to Check If TPM 2.0 and Secure Boot Are Enabled
Checking TPM 2.0
-
Press Win + R
-
Type tpm.msc
-
Check the status and specification version shown in the window
You can also find partial information in Windows Security -> Device Security, but tpm.msc is the most direct method.
Checking Secure Boot
-
Press Win + R
-
Type msinfo32
-
In System Information, find the line Secure Boot State
If it says “Off”, Secure Boot is disabled or your system is not installed in UEFI mode.
How to Enable Secure Boot and TPM 2.0
Exact steps depend on your motherboard manufacturer (ASUS, MSI, Gigabyte, etc.), but the overall logic is usually the same.
Step 1 - Enable UEFI Mode (If Using Legacy / CSM)
-
Enter BIOS / UEFI
-
Disable CSM or Legacy Boot
-
Enable UEFI mode
This may require your system disk to use GPT instead of MBR.
Step 2 - Convert Disk to GPT (If Needed)
If Windows was installed in Legacy mode using MBR, conversion may be required. Microsoft’s built-in MBR2GPT tool is commonly used for this. Always make a backup before proceeding.
Step 3 - Enable Secure Boot
In BIOS / UEFI, this is usually found under:
Boot or Security -> Secure Boot -> Enabled
Sometimes you also need to set “Windows UEFI Mode” or load default Secure Boot keys.
Step 4 - Enable TPM 2.0
TPM may appear under different names:
-
Intel systems - PTT (Platform Trust Technology)
-
AMD systems - fTPM
Look for these options under Security or Trusted Computing in BIOS.
Conclusion
TPM 2.0 and Secure Boot are foundational components of Windows trusted boot security, and they are increasingly mentioned in the context of stronger anti-cheat enforcement in modern games. While Rust does not strictly require them yet, this will likely change in the near future. If you plan to play major PC releases in 2026 and beyond, enabling these features now is a smart move.
And if you want a place where TPM 2.0 and Secure Boot definitely aren’t required - check out CobaltLab! Grab free bonuses and jump into the game right now!
