Rust crashing to desktop, hanging on a black screen, or refusing to launch is almost always fixable — and on this game the prime suspect is nearly always Easy Anti-Cheat (EAC), with corrupted files, GPU drivers, and overlays close behind. This guide runs through the fixes in the order most likely to get you back on the beach. It’s written for the PC (Steam) version; Rust Console Edition is a separate product and these steps don’t apply to it.
First, check your RAM — Rust is memory-hungry
Rust’s official Steam requirements are 12 GB RAM minimum, 16 GB recommended (ignore third-party sites claiming 10 GB — they’re wrong), with an SSD effectively required to avoid brutal load times. Rust is genuinely RAM- and CPU-heavy, so running it on 8 GB, on a hard drive, or with a misconfigured pagefile is a real cause of crashes and stutter. If you’re at or below the minimum, that’s your first answer.
“EasyAntiCheat is not installed” / EAC won’t start
This is the single most common launch blocker. EAC ships inside the Rust install folder:
- Run the EAC installer from the game folder. Right-click Rust in Steam → Manage → Browse local files, open the
EasyAntiCheatfolder, and run the setup — on the current build it’sEasyAntiCheat_EOS_Setup.exe(older installs useEasyAntiCheat_Setup.exe; use whichever is present). Choose Repair, with Rust selected in the dropdown. - Run the EAC setup and the game as Administrator — this clears many “not installed” cases.
- Full EAC reinstall: delete the entire
EasyAntiCheatfolder in the Rust directory, then Verify integrity of game files in Steam to re-download a clean copy. - Always launch Rust from Steam, never the .exe directly — EAC doesn’t load otherwise.
Verify your game files (the universal first step)
Steam → right-click Rust → Properties → Installed Files → Verify integrity of game files. This fixes corrupted or missing files behind a huge share of crashes, “unknown file version,” and launch failures. Run it before anything more drastic.
Black screen on launch / crash to desktop
- Toggle fullscreen ↔ windowed (Alt+Enter). A black screen on launch is usually a temporary display-mode glitch that this clears.
- Clean-install your GPU drivers. Outdated or faulty drivers are a leading launch-crash cause — use the vendor’s clean-install option (or DDU) and reboot.
- Remove ReShade. ReShade has been banned since January 2025 — EAC will refuse to start if it’s present. Delete all ReShade DLLs and config from the Rust folder, then verify files.
- Add a Defender/antivirus exclusion for the Rust folder — AV occasionally flags the Rust or EAC executable.
- Disable overlays — the Steam overlay, GeForce Experience/NVIDIA App, and Windows Game Bar all hang or crash Rust for some players.
Memory, runtimes, and admin rights
- Let Windows manage your pagefile (virtual memory) and reboot — a mis-set pagefile causes out-of-memory crashes and stutter on a RAM-heavy game like Rust. There’s no magic size to set; automatic is the safe choice.
- Run Rust (and Steam) as administrator and keep Windows updated — repeatedly cited for EAC service-start failures.
- Repair the Visual C++ Redistributables and DirectX runtime if launch crashes persist — a standard fix for “stopped working” errors.
Is EAC the culprit? A diagnostic test
Facepunch documents a supported way to launch the non-EAC client to test whether EAC itself is causing your crash. Note this is a diagnostic only — with EAC disabled you can’t join normal multiplayer servers, so it’s purely to confirm the crash is EAC-related. The exact steps are on Facepunch’s support site (search “Launching Rust with EAC disabled”); follow their procedure rather than a guessed one. If Rust runs fine without EAC, focus on the EAC reinstall steps above.
Crashing only on one server?
If Rust runs fine on most servers but crashes on one — or everyone on it is rubber-banding — that’s the server, usually a plugin conflict or a host running out of memory, not your client. If it’s your own server, our Rust server troubleshooting docs cover the server-side fixes. An oversold or underpowered box crashes under a full pop with Oxide plugins loaded — running on properly resourced Rust server hosting with guaranteed RAM and high-clock CPU keeps it stable through wipe-day rushes. While you’re at it, our free Rust tools and server-status checker are handy.
If your problem is getting kicked or disconnected rather than crashing, see our Rust connection & EAC error guide.
Frequently asked questions
Why does Rust keep crashing on startup?
Most often a broken Easy Anti-Cheat install, corrupted game files, or outdated GPU drivers. Repair EAC from the EasyAntiCheat folder (run as admin), verify your game files in Steam, clean-install your GPU drivers, and remove ReShade if you have it (it’s banned and blocks EAC).
How do I reinstall Easy Anti-Cheat for Rust?
Open Rust’s local files (Steam → Manage → Browse local files), go into the EasyAntiCheat folder, run the setup (EasyAntiCheat_EOS_Setup.exe on current builds) as administrator, and choose Repair with Rust selected. For a full reinstall, delete the EasyAntiCheat folder and verify your game files in Steam.
How much RAM does Rust need?
Officially 12 GB minimum and 16 GB recommended, with an SSD strongly recommended. Rust is RAM- and CPU-heavy, so 16 GB and letting Windows manage your pagefile will resolve a lot of crashing and stutter on lower-spec systems.
Why does Rust launch to a black screen?
Usually a display-mode glitch or a GPU driver issue. Press Alt+Enter to toggle fullscreen/windowed, clean-install your GPU drivers, verify game files, and disable overlays. Removing ReShade and adding an antivirus exclusion for the Rust folder also resolves it for some players.
Ready to play?
Run your own Rust server with XGamingServer
Spin up an always-on Rust server your friends can join in minutes — no port-forwarding, no tech headaches.
