Rust Easy Anti-Cheat (EAC) Error: How to Fix It

Published

On this page

Rust’s Easy Anti-Cheat error almost always comes from the EAC kernel driver itself — corrupted, blocked, or out of sync with Windows’ security settings — not from anything wrong with your Rust install or your account. Rust runs EAC as a low-level kernel driver enabled by default on every official server, which makes it more sensitive to Secure Boot, TPM, and driver-signing settings than anti-cheat in most other games.

Rust Easy Anti-Cheat (EAC) Error: How to Fix It

This covers the most common Rust EAC failures — “EAC timed out,” failure to start, and kernel driver errors — in the order most likely to fix them.

1. Repair Easy Anti-Cheat from the Rust install folder

Start here. It’s Facepunch’s own first recommendation and fixes most driver/service corruption without touching your Rust files.

  1. Open your Rust install folder (Steam default: ...\steamapps\common\Rust\EasyAntiCheat).
  2. Right-click EasyAntiCheat_Setup.exe → Run as administrator.
  3. Select Rust from the list and choose Repair Service.
  4. Relaunch Rust through Steam.

2. Check Secure Boot and TPM 2.0

Facepunch has been rolling out Secure Boot and TPM 2.0 requirements through EAC in phases during 2026, starting with servers explicitly tagged secure and expanding from there. If you can’t connect to a tagged server, or get a hardware-security-related EAC error, this is almost certainly why.

  1. Press Win + R, type msinfo32, press Enter.
  2. Confirm Secure Boot State: On and BIOS Mode: UEFI.
  3. Press Win + R, type tpm.msc, press Enter — it should show TPM 2.0, ready for use.
  4. If either is off, enable it in your motherboard’s BIOS:

Older guidance to disable Secure Boot for EAC issues is outdated for Rust specifically — Facepunch is moving toward requiring it, not avoiding it, so try enabling it before you try disabling anything.

3. Run Rust and EAC as administrator

The EAC kernel driver needs elevated permissions to install and load correctly.

  1. Right-click EasyAntiCheat_Setup.exe → Properties → Compatibility.
  2. Check Run this program as an administrator → Apply.
  3. Do the same for the Steam shortcut.
  4. Relaunch Rust.

4. Check antivirus and firewall blocks

EAC’s kernel-level hooks are a common false-positive target for security software.

  1. Check your antivirus’s quarantine list for anything related to EasyAntiCheat and restore it if found.
  2. Add the Rust install folder and its EasyAntiCheat subfolder as exclusions.
  3. Confirm your firewall (Windows Firewall or third-party) allows both RustClient.exe and the EAC service through — an “EAC timed out” error is frequently a blocked connection rather than a broken install.

5. Confirm the Easy Anti-Cheat service is running

  1. Press Win + R, type services.msc, press Enter.
  2. Find EasyAntiCheat.
  3. Right-click → Properties → set Startup type to Automatic, then Start.
  4. Reboot and relaunch Rust.

6. Verify game files and check Memory Integrity

  1. In Steam, right-click Rust → Properties → Local Files → Verify integrity of game files.
  2. Check Windows’ Memory Integrity (Core Isolation) setting under Windows Security → Device Security — a conflict here between HVCI and EAC’s kernel driver can trigger startup errors on some systems. Toggle it off, reboot, and test if you’re stuck after every other step.

7. Clean reinstall of Easy Anti-Cheat

For errors that survive everything above, reinstall EAC specifically.

  1. From the EasyAntiCheat folder, run EasyAntiCheat_Setup.exe as administrator.
  2. Choose Uninstall for Rust.
  3. Reboot.
  4. Relaunch Rust — EAC redeploys automatically on the next launch.

Rust’s kernel-level EAC makes it stricter about Secure Boot, TPM, and driver signing than most anti-cheat. Repair first, confirm your hardware-security settings are on rather than off, and the reinstall in step 7 handles whatever’s left.

Frequently asked questions

Why does Rust keep giving an Easy Anti-Cheat error?

Rust runs EAC as a kernel-level driver enabled by default on every official server, so any corruption in the driver, a Secure Boot/TPM mismatch, or a blocked service will stop the game from connecting. Running the EAC repair tool from your Rust install folder fixes most cases.

Does Rust require Secure Boot and TPM 2.0 now?

Facepunch is rolling this out in phases through 2026 — first as a requirement on servers explicitly tagged secure, with a wider rollout planned. If you can't connect to a secure-tagged server, check that Secure Boot and TPM 2.0 are both enabled in your BIOS.

What does 'EAC timed out' mean in Rust?

It means the Easy Anti-Cheat client couldn't complete its verification handshake with the server in time, usually from a stalled EAC service, a network/firewall block, or an out-of-date anti-cheat driver. Restarting EAC via a repair and confirming your firewall allows Rust through usually clears it.

Why did Rust's EAC error start after a Windows update?

Windows updates can change security features like Memory Integrity (HVCI) or reset driver signing enforcement, and EAC's kernel driver is sensitive to both. Re-enabling Secure Boot/TPM if they were affected and re-running EAC's repair tool usually resolves it.

Is disabling Secure Boot a fix for Rust EAC errors?

It used to help on older EAC builds that predated hardware-security requirements, but Rust is moving the opposite direction — Facepunch is enabling Secure Boot and TPM 2.0 requirements, not removing them. Try repairing EAC and confirming Secure Boot/TPM are on before disabling anything.