Rust "EAC: Disconnected" Fix (Easy Anti-Cheat Kicks Explained)

"EAC: Disconnected" in Rust means Easy Anti-Cheat on your PC lost its link with the anti-cheat service while you were joining or playing, so the server dropped you. It is not a ban. In most cases it is fixed on the player's PC by repairing the EAC service, verifying the game files and closing anything that hooks into the game. If every player on one server gets it at once, the server or the EAC backend is the cause, and the owner has a short checklist below.

The EAC messages and what they mean

Rust prints the reason after "Disconnected:" in the console (F1). They are different problems, so read the exact text first.

If you see "Steam Auth Timeout" instead, that is the Steam side of the handshake, covered in the Steam Auth Timeout guide.

Fix 1: Launch Rust the normal way

Rust must start through Steam (or the launcher it opens), which starts EAC first and then the game. Starting RustClient.exe directly from the install folder, or from a shortcut someone made to it, skips EAC, and every server with anti-cheat turns you away with an EAC disconnect. Use Play in Steam.

Restart the PC afterwards if you were running the game the wrong way, since the EAC service may be in a broken state.

Fix 2: Repair the EAC service

1. Close Rust completely.
2. In Steam, right click Rust > Manage > Browse local files.
3. Open the EasyAntiCheat folder and run the setup program in it as administrator.
4. Pick Rust in the list if asked, then click Repair service.
5. Restart the PC and join again.

This clears EAC: Unconnected and most EAC: Disconnected kicks. If the setup program says the service is missing, choose Install instead.

Fix 3: Verify the game files

In Steam: Rust > Properties > Installed Files > Verify integrity of game files. This fixes Client integrity violation and Unknown game file when a file is damaged after an update or a crash during patching. It also removes leftover files from old versions.

If you have ever copied anything into the Rust folder (reshade, config tools, texture packs), delete it. EAC treats any unexpected DLL in the game folder as tampering.

Fix 4: Close what hooks into the game

EAC disconnects players when software reads or writes the game's memory, even harmless software. Close these one at a time to find the culprit:

• RGB, mouse and keyboard tools with macros or game detection.
• Overlays: FPS counters, recording tools, Discord overlay, older versions of hardware monitoring apps.
• Crosshair overlays and screen filters.
• Virtual machines or sandbox tools running in the background.

A clean test is a fresh restart with nothing else open, then Steam and Rust only.

Fix 5: Network and Windows

• VPNs and proxies can cut the EAC connection while the game connection survives, which shows up as EAC: Disconnected a few minutes into a session. Turn them off.
• Firewall and antivirus: allow the Rust folder and the EAC service. Some security suites block the EAC backend after a Rust update changes file hashes.
• Windows updates: EAC expects a reasonably current Windows. Install pending updates and restart.
• Date and time: set them to automatic. EAC uses signed certificates and a clock that is far off breaks them.

When every player gets kicked

If the whole server drops with EAC messages at the same moment, it is not the players' PCs.

1. Check whether EAC is working on other servers. If players get the same kick on big official servers too, the EAC backend is having trouble. It clears on its own, so wait.
2. Check the server is up to date. After a Rust update the client and server must match. An outdated server often shows as a version message, but around force wipe day both errors appear together. See updating on force wipe day.
3. Check server.secure. EAC on the server is controlled by this setting, which should be true on any public server:

server.secure true

Put it in server/<identity>/cfg/server.cfg so it survives restarts. With server.secure false, the server runs without anti-cheat, which is rarely what you want on a server strangers can join.

4. Check for a hitching server. A server that freezes for many seconds during saves or heavy plugin work can drop players with timeout messages, including EAC ones. Watch the console during a kick. The Rust lag and low FPS guide shows how to read server FPS and fix save hitches.

When it is a real ban

A kick that names an EAC ban is a global anti-cheat ban on the Steam account. Server owners cannot lift it, and it affects every server running EAC. Players who believe it is a mistake contact Facepunch support through the official channels.

Running your own server

Most EAC kicks are fixed on the player's PC, but the server side matters too: a server that is current on update day, has server.secure true and does not hitch during saves gives players far fewer kicks. On a GamezServers Rust server the game updates from the panel, server.cfg is in the file manager, and the live console shows each disconnect with its reason as it happens. Saves start at a 300 second interval, which avoids frequent save hitches. If you are setting up a server for your group, see the Rust server for friends page or the Rust game page.

FAQ

Is "EAC: Disconnected" a ban?

No. A ban says so in the message. "EAC: Disconnected" only means the anti-cheat session dropped, and you can rejoin once it is fixed.

Why do I only get EAC kicks on one server?

That server may be hitching or out of date, or your route to it may drop packets. If you get the kick on several servers, the problem is on your PC.

Does reinstalling Rust fix EAC errors?

It can, but repairing the EAC service and verifying files fixes the same things in a few minutes instead of a full download.

Can a server owner turn off EAC?

Yes, with server.secure false, but then there is no anti-cheat on the server. Keep it on for anything public.