Rust loads slower than almost any modern game, and some of that is fair — the engine unpacks and warms up tens of thousands of objects. But ten minutes instead of two means a specific cause, and it is almost always one of the six below.
Before fixing anything, know what you are aiming at. These are realistic numbers for a machine with an SSD and 16 GB of RAM:
| Stage | Normal | What is happening |
|---|---|---|
| Launch to main menu | 40–90 s | Asset unpacking, EAC init |
| First join to a server | 2–4 min | Map downloaded and generated locally |
| Rejoining the same server | 40–90 s | Map comes from local cache |
| After a server wipe | 2–4 min | New map, cache no longer valid |
If reaching the menu takes five minutes and rejoining a familiar server takes three, the problem is your system, not the game.
The most common cause and the one you cannot tweak away. Rust reads tens of thousands of small files while loading, and small random reads are exactly where a mechanical drive loses to an SSD by orders of magnitude. In practice: 2 minutes versus 12.
Check it in Task Manager → Performance → your drives. If disk activity sits at 100% while throughput crawls at 3–8 MB/s, you are watching an HDD bottleneck. You can move the library without reinstalling: Steam → Settings → Storage → pick the SSD folder → Move.
Rust can take 12–14 GB while generating a map. On an 8 GB system that means part of the data spills to the page file — that is, to disk — and load times stretch accordingly.
Defender and third-party antivirus scan files as they are read. Rust reads tens of thousands of files during a load, and each one goes through the scanner. That adds minutes for nothing.
Add-MpPreference -ExclusionPath "D:\Steam\steamapps\common\Rust"
Add-MpPreference -ExclusionProcess "RustClient.exe"
Add-MpPreference -ExclusionProcess "EasyAntiCheat.exe"Use your own path — Steam shows it under Manage → Browse local files. Excluding the game folder does not meaningfully lower your protection: those files are still scanned when they are downloaded.
Steam → right-click Rust → Properties → Launch Options:
-high -malloc=system -nolog -window-mode exclusive| Option | What it does |
|---|---|
| -high | High process priority — loading gets CPU time first |
| -malloc=system | System allocator instead of the internal Unity one; noticeably faster loads on most systems |
| -nolog | Skips verbose logging, which is thousands of disk writes per load |
| -window-mode exclusive | Exclusive fullscreen: faster loads and lower input lag |
What not to add: -cpuCount and -maxMem by hand. The engine detects both, and guessed values usually make things worse.
Different problem: the bar stops on "Loading Prefabs" and never moves. That is a fault, not slowness. In order:
%LOCALAPPDATA%\Facepunch\Rust. Settings reset, so copy your client.cfg first.EasyAntiCheat\EasyAntiCheat_Setup.exe from the game folder → Repair.A typical result on an SSD system after all of this: 50–90 seconds to the menu and around two minutes to join a server you have played on before.
Because of the procedural map. Rust does not load a prebuilt level — it generates terrain, vegetation and player structures locally from the server seed. That work lands on your CPU and disk, which is why it takes longer than games shipping fixed levels.
On most systems yes, and noticeably — 20–40% faster to the menu. It makes Unity use the system memory allocator instead of its own. There are no known side effects, and if you see no gain you can simply remove it.
Only as a fix for a hang, not as a speed-up. It wipes all settings including client.cfg, so back the config up first. On a healthy install that folder slows nothing down.
Barely. Once you are off a mechanical drive, most of the remaining time goes to CPU-side unpacking and map generation, not reads. The difference between SATA and NVMe in Rust is a few seconds.