Rust Crashing on Startup: Causes, Checks and Fixes (2026)

Few things are as frustrating as gearing up for a wipe, launching Rust, and having the game abruptly close to the desktop or freeze on the splash screen. Because Rust is built on the Unity engine and protected by Easy Anti-Cheat (EAC), startup failures are rarely random. They usually point to a specific bottleneck or conflict between Unity’s memory management, EAC’s kernel-level driver, and your system’s hardware configuration.

When Rust crashes during startup, the timing of the crash is your best diagnostic tool. Crashing instantly when you click “Play” in Steam typically points to an authentication or Easy Anti-Cheat conflict. On the other hand, freezing or crashing to the desktop during the “Loading Bootstrap” or “Loading Assets” phase indicates that the Unity engine is running out of memory or failing to parse corrupted game files. As we head into 2026, Rust continues to push modern PC hardware to its limits, making optimization and stability checks more vital than ever. This guide outlines the most common causes and provides a step-by-step, non-destructive troubleshooting path to help implement a Rust crashing on startup fix for your system.

Likely Causes

Understanding why Rust fails to launch requires isolating the game files, the anti-cheat software, and your Windows operating system. Below is a breakdown of the most common causes, how to identify them, and how difficult they are to resolve.

Fix 1: Verify Integrity of Game Files in Steam

Because Rust receives frequent updates, it is common for local asset bundles to become fragmented or corrupted during the download process. If Unity attempts to load a corrupted file during the startup sequence, it will close the game to prevent memory corruption.

How to check

Open your Steam Library, right-click Rust, and select Properties. Navigate to the Installed Files tab. If your local files are corrupted, this check is the most direct way to identify the issue.

What to do

1. Launch Steam and navigate to your Library.
2. Right-click on Rust and select Properties.
3. Click on the Installed Files tab on the left.
4. Click the Verify integrity of game files button.
5. Wait for Steam to compare your local files with the official manifest. This process can take 5 to 15 minutes depending on your storage speed. If any files fail to validate, Steam will automatically redownload them.

How to undo it

This is a read-only validation process that replaces missing or modified files with official versions. It cannot harm your system or save files, so there is nothing to undo.

Fix 2: Repair or Reinstall Easy Anti-Cheat (EAC)

Rust will not launch without Easy Anti-Cheat running in the background. If the EAC driver is blocked by Windows, has corrupted files, or failed to initialize during a Windows Update, Rust will terminate itself before the main menu loads.

How to check

Navigate to your Rust installation folder (typically C:\Program Files (x86)\Steam\steamapps\common\Rust\). Open the EasyAntiCheat folder. If you see an error window referencing “EAC,” “untrusted system file,” or “driver signature enforcement” upon launching, this fix is highly relevant.

What to do

1. Close Steam completely by right-clicking the Steam icon in your system tray and selecting Exit.
2. Navigate to Steam\steamapps\common\Rust\EasyAntiCheat\.
3. Right-click on EasyAntiCheat_Setup.exe and select Run as administrator.
4. In the setup utility, select Rust from the dropdown menu (if it doesn’t default to it).
5. Click the Repair Service button.
6. Once completed, close the installer, launch Steam as an administrator, and try booting Rust.

How to undo it

If you need to revert this, you can run the same EasyAntiCheat_Setup.exe file and click the Uninstall option, though note that Rust requires EAC to be installed to connect to any secure servers.

Fix 3: Expand the Windows Pagefile (Virtual Memory)

Rust is notorious for its extreme RAM consumption. Even if you have 16GB of physical RAM, Windows can run out of memory addresses during the intensive asset-loading phase at startup. If your virtual memory (pagefile) is disabled or set too low, Unity will crash instantly without showing an error code.

How to check

Press Ctrl + Shift + Esc to open Task Manager, go to the Performance tab, and click Memory. Look at the “Committed” value. If the second number (the limit) is very close to your physical RAM capacity, your pagefile is likely too small.

What to do

1. Press the Windows Key, type “Advanced System Settings,” and press Enter.
2. Under the Advanced tab, click the Settings button in the “Performance” section.
3. Go to the Advanced tab in the Performance Options window and click Change in the “Virtual memory” section.
4. Uncheck the box that says Automatically manage paging file size for all drives.
5. Select your fastest SSD (preferably the one where Rust is installed).
6. Click Custom size and set both the Initial size and Maximum size to 24576 MB (24GB) if you have 16GB of RAM, or 16384 MB (16GB) if you have 32GB of RAM.
7. Click Set, then click OK, and restart your computer to apply the changes.

How to undo it

To revert this change, return to the Virtual Memory settings window, check the Automatically manage paging file size for all drives box, click OK, and restart your PC.

Fix 4: Disable Discord and Steam Overlays

In-game overlays inject code directly into Rust’s graphics rendering pipeline. Because Rust utilizes a highly customized Unity build, these third-party hooks can trigger memory access violations at startup, resulting in an immediate crash to desktop.

How to check

Observe if Rust launches successfully when Discord, GeForce Experience, or Steam are completely closed down. If the game boots fine without them, an overlay conflict is present.

What to do

1. For Steam: Open Steam, go to Settings > In-Game, and toggle off the switch for Enable the Steam Overlay while in-game.
2. For Discord: Open Discord, click the gear icon (User Settings) in the bottom-left corner, scroll down to Game Overlay under “Activity Settings,” and toggle off Enable in-game overlay.
3. For GeForce Experience: Open GeForce Experience, click the gear icon, and toggle off the In-Game Overlay setting in the “General” tab.

How to undo it

You can easily re-enable any of these overlays by returning to the respective settings menus and toggling them back on once you have ruled out overlay conflicts.

Fix 5: Reset the Rust Configuration File (client.cfg)

If you recently modified your graphic settings, resolution, or keybinds, those parameters are saved in a local file called client.cfg. If an invalid value was written to this file, Rust may crash while attempting to initialize the display engine.

How to check

Navigate to Steam\steamapps\common\Rust\cfg\. If you see a client.cfg file that has been modified recently, this could be causing your startup issues.

What to do

1. Close Rust and Steam.
2. Navigate to your Rust installation directory: Steam\steamapps\common\Rust\cfg\.
3. Locate the file named client.cfg.
4. Right-click the file and select Rename. Change the name to client.cfg.old. (This preserves your old settings just in case).
5. Launch Rust. The game will automatically generate a brand-new, factory-default client.cfg file.

How to undo it

If this does not resolve the crash and you want to restore your original settings, delete the newly created client.cfg, and rename client.cfg.old back to client.cfg.

Fix 6: Clear the Steam Download Cache and AppData

Old configuration files, temporary shader caches, and user-profile data stored in your Windows AppData folder can conflict with newer game builds, preventing Rust from initializing properly.

How to check

If you have updated Rust after a long hiatus and it refuses to launch, corrupted cached data is a strong suspect.

What to do

1. Open Steam, click Steam in the top-left corner, and select Settings.
2. Go to the Downloads tab and click Clear Cache next to the “Clear download cache” option. Steam will restart and require you to log back in.
3. Press the Windows Key + R to open the Run dialog box.
4. Type %localappdata% and press Enter.
5. Locate the folder named Facepunch Studios and open it.
6. Delete the Rust folder inside. (This will clear temporary cache files, but not your game files).

How to undo it

Clearing these caches is a standard maintenance practice. The deleted AppData folders will be cleanly recreated the next time you launch the game, so there is no manual undo process required.

Fix 7: Perform a Clean GPU Driver Installation with DDU

A simple driver update sometimes leaves behind orphaned registry keys or conflicting DLLs that cause Unity games to crash during display initialization. A clean installation using Display Driver Uninstaller (DDU) ensures your GPU driver is completely untainted.

How to check

Check your Windows Event Viewer (under Windows Logs > System) right after a crash. If you see warning messages mentioning Display driver nvlddmkm stopped responding and has successfully recovered, your graphics driver is crashing.

What to do

1. Download the latest driver installer for your graphics card from the NVIDIA, AMD, or Intel website.
2. Download the latest version of Display Driver Uninstaller (DDU).
3. Boot Windows into Safe Mode (Hold Shift while clicking Restart in the Start Menu, then go to Troubleshoot > Advanced Options > Startup Settings > Restart, and press 4).
4. Run DDU, select your GPU type (NVIDIA/AMD), and click Clean and restart.
5. Once Windows boots back up normally, run the driver installer you downloaded in Step 1. Select “Custom Installation” and check the box for “Perform a clean installation” if available.

How to undo it

You cannot “undo” a driver wipe, but you can easily reinstall your preferred older driver version using the same installation process if the newest version does not resolve the crash.

If Nothing Works

If you have implemented every Rust crashing on startup fix listed above and the game still refuses to load, the issue may lie in deeper hardware instability or operating system corruption.

• Disable RAM Overclocks (XMP/EXPO): Unity is incredibly sensitive to memory timings. Even if your PC is stable in other games, an unstable XMP/EXPO profile can cause Rust to crash at startup. Enter your motherboard BIOS and temporarily disable XMP or EXPO to see if the game launches.
• Move Rust to an SSD: Rust is not designed to run on mechanical hard drives. Slow read/write speeds can cause the game to time out during asset loading. Ensure Rust is installed on a high-speed SATA or NVMe SSD.
• Analyze the Crash Dumps: You can find specific details about the crash by navigating to %localappdata%\Temp\Facepunch Studios\Rust\Crashes. Open the most recent crash.log file in Notepad to see the exact line of code or DLL that caused the failure. This log can be submitted directly to Facepunch Support for personalized assistance.

FAQ

Why does Rust crash specifically on the “Loading Bootstrap” screen?

The “Loading Bootstrap” phase is when Rust initializes its core engine, loads Easy Anti-Cheat, and allocates system memory. Crashing at this exact moment almost always points to a virtual memory shortage (pagefile size) or EAC failing to verify your operating system’s integrity.

Can Discord or Spotify overlay cause Rust to crash at launch?

Yes. Any software that attempts to draw graphic elements over the Rust window uses a process called DLL injection. If Rust’s Unity engine or Easy Anti-Cheat flags this injection as a security risk or memory conflict, the game will shut down instantly to protect itself.

How do I know if my RAM is causing Rust to crash on startup?

If you run out of physical and virtual memory, or if your RAM has unstable clock speeds, Rust will crash to the desktop without showing an error window. You can check this by disabling XMP in your BIOS or checking Windows Event Viewer for “Event 1000, Application Error” pointing to RustClient.exe.

Do I need to run Rust as an Administrator to fix startup crashes?

Running the game as an administrator can sometimes resolve permission conflicts with Easy Anti-Cheat. However, you must run both Steam and the RustClient.exe as an administrator simultaneously; otherwise, Steam will fail to authenticate your account and throw a launch error.