ROB RUN Errors and Fixes: Loading, E-Codes, EAC, FPS

ROB RUN will not load — what do you check first?

Three things, in order:

Are the servers up? Maintenance usually lasts 15 minutes to an hour and is announced in the official Discord and Steam forum.
Verify the game files. Steam library → right-click ROB RUN → Properties → Installed Files → Verify integrity of game files.
Restart Steam in online mode and launch the game from your Steam library, never from a shortcut.

That sequence clears the majority of load failures, including E-0124, E-0405 and “Failed to load il2cpp”.

Error codes

Code	Meaning	Fix
E-0101 / E-0110	Cannot connect to the server to download configuration or startup data	Check the connection; make sure normal websites load
E-0102	Data downloaded with errors or blocked, often on guest Wi-Fi or by antivirus	Use a home network, turn off the proxy, pause HTTPS scanning
E-0124	Internal game asset loading error	Verify game files
E-0201	Was running, connection lost and not restored	Check the connection, restart the game
E-0301 / E-0302	Outdated game version	Close the game, restart Steam, update
E-0303 / E-0304	Game data corrupted or mismatched	Wait 10–15 minutes, turn off the proxy, verify files, update
E-0401	Steam account authentication failed	Start Steam in online mode, check the account, restart both
E-0403 / E-0404	Authorization problem (Epic Online Services)	Verify files, add the game to antivirus exceptions, restart the PC
E-0405	Steam not responding or antivirus blocked a system library	Check quarantine, start Steam, verify files, launch from the library
E-0501 / E-0502	Easy Anti-Cheat not running, corrupted or blocked	Launch only through Steam, stop antivirus, verify files, restart
E-0601	Keyboard and mouse not detected, often Remote Desktop or cloud streaming	Connect a physical keyboard and mouse before launch
E-0904	Unexpected internal error	Restart; if it persists, send the error text to support

Stuck on the loading screen

“Preparing shaders” on first launch: give it time. Shaders are built once; if the bar does not move after several minutes, close the game completely and verify the files.
Loading bar frozen after an update: close the game, restart Steam, verify the files, then relaunch. E-0303 and E-0304 are usually this.
Waiting for status information: the client is trying to reach the server. Check that the region is not under maintenance, then reset the network path — turn off any VPN or proxy and run netsh winhttp reset proxy in an administrator Command Prompt.

Easy Anti-Cheat errors

Easy Anti-Cheat (EAC) is kernel-level and it is the reason the game does not run on Linux or Steam Deck through Proton.

Launch only from Steam.
Add the ROB RUN folder to your antivirus exceptions, or at least check the quarantine list.
Verify the game files, then restart the PC — EAC loads at boot.
Never run cheat software: EAC bans are permanent.

Crashes and freezes

Run the game as administrator.
Turn off fullscreen optimizations in the compatibility settings.
Turn off the Steam overlay.
Clear the Steam download cache.
Update Windows and the graphics driver.
Close background apps that hook into games (overlays, capture tools).

Low FPS and stutter

Stutter is worst in crowded places — Looty Bay with 20 players is heavier than an empty settlement.

Below 12 GB of RAM the game runs badly; 16 GB is the recommended spec. Full numbers are on the system requirements page.
Keep the game on an SSD with the required 20 GB free.

Voice chat is silent

Check the microphone permission in Windows and the audio settings in the game. In some regions the voice service needs a VPN, which is a network problem, not a game bug.

How do you contact support?

Support needs your UID, your player name and the approximate time of the problem. Press Esc in game: the UID sits under your character name, with a “Copy UID” button.

Send bug reports with the error code, your CPU and your graphics card. Screenshots or a short video of the steps before the error help more than a description.

Did you lose progress?

Check three things before contacting support: whether a wipe happened, whether you are on the same server, and whether you are logged into the right Steam account. The wipe timer answers the first one.