Find the message on your screen, then work through its fixes in order. Every fix is labelled Official (Facepunch, Easy Anti-Cheat, Steam, Microsoft, GPU vendors) or Community-reported, with its source.
· 140 errors and problems · Free to use and share
Searches the message, other wordings, error codes, where it shows and why it happens.
Do this first
The steps that fix the most problems, quoted from the entries they come from. Try them in order before you look for your exact error.
Check it is not an outage
Check whether it is widespread: try a second server, and look at the Rust General Discussions board or Rust's official X account for an outage. If many players have it, wait. Community
Repair EAC: open ...\steamapps\common\Rust\EasyAntiCheat\, type EasyAntiCheat_EOS_Setup.exe repair in Explorer's address bar, press Enter and allow the admin prompt (only a console window flashes; there is no repair window any more). Official
If it still fails, do a fresh install: Library → right-click Rust → Manage → Browse local files, close Steam's window, delete the whole Rust folder, then install Rust again from Steam. Official
Also seen asStartup error: Steam not open?Are you connected to Steam? Is it running?[Steamworks.NET] SteamAPI_Init() failed. Is Steam running?Steam must be running to play this game
Where you see it
A startup error shown as Rust opens, before the main menu.
Why it happens
Rust could not talk to the Steam client it was launched from: Steam is closed, out of date, on a beta build, or Rust's files are damaged.
What to do, in order
Close Rust and Steam completely, open Steam again, then launch Rust from your Steam Library (not from RustClient.exe).OfficialSource 1
Restart your PC if restarting Steam did not help.OfficialSource 1
In Steam, open Steam → Check for Steam Client Updates, install any update and let Steam restart.OfficialSource 1
Opt out of the Steam client beta: Steam → Settings → Interface → Client Beta Participation → No beta chosen, then restart Steam.OfficialSource 2
Verify Rust's files: Steam → Library → right-click Rust → Properties → Installed Files (older Steam and Facepunch's articles: Local Files) → Verify integrity of game files.OfficialSource 3
If it still fails, do a fresh install: Library → right-click Rust → Manage → Browse local files, close Steam's window, delete the whole Rust folder, then install Rust again from Steam.OfficialSource 4
Caveats
Exact Facepunch wording is "Steam not open?". The aliases come from players (2026-01-30 Steam thread, paraphrased) and an old output_log line; "Steam must be running to play this game" is a generic Steamworks message and was NOT found quoted for Rust in any source checked, so treat it as a likely variant only. Facepunch's article describes the beta setting as Steam → Settings → "Beta participation" → "NONE - opt out"; current Steam UI (per Steam Support) is Settings → Interface → Client Beta Participation → "No beta chosen". A reply in the 2026 thread also notes this happens if you launched the Rust SDK/staging app instead of Rust.
On launch, if ReShade files are present in the Rust folder.
Why it happens
Facepunch banned ReShade in Rust from January 13, 2025; Rust refuses to start while ReShade is installed in its folder.
What to do, in order
Open the Rust folder: Steam → Library → right-click Rust → Properties → Installed Files (older Steam and Facepunch's articles: Local Files) → Browse.OfficialSource 1
Delete ReShade's files: dxgi.dll, d3d9.dll, d3d11.dll or opengl32.dll (whichever ReShade added), reshade.ini, and the reshade-shaders folder.OfficialSource 1
Verify files so Steam restores anything removed by mistake: Properties → Installed Files (older Steam and Facepunch's articles: Local Files) → Verify integrity of game files.OfficialSource 1
Relaunch Rust; if it still shows the error, open a ticket with Facepunch support.OfficialSource 1
Caveats
Only delete the files ReShade put there; deleting other DLLs from the Rust folder breaks the game (verification will restore them). ReShade is banned for fair-play reasons, so there is no supported way to keep it.
Also seen asrust-unity 6000.3.15x1-11_d4a0e1288074rust unity 6000.3.15x1-13_a91cf34396eeRust - Unity 6000.x popup"utility 6000" pop-up
Where you see it
A small Unity popup (window title is Rust plus the Unity build string), shown on launch or while joining a server, followed by the game closing.
Why it happens
The text is Rust's Unity 6 engine build identifier, not an error code; the popup only says Rust crashed. Reported triggers include damaged local cfg or bundles data, an NVIDIA App DLSS override or Smooth Motion forced on Rust, and an out-of-date Windows build.
What to do, in order
Verify Rust's files first: Steam → Library → right-click Rust → Properties → Installed Files (older Steam and Facepunch's articles: Local Files) → Verify integrity of game files.OfficialSource 1
Turn DLSS/DLAA off in Rust's graphics settings and test again.CommunitySource 2
If you use the NVIDIA App, remove any DLSS override ("latest DLSS") and Smooth Motion set for Rust, then test again.CommunitySource 3
Check your Windows version (Win+R → winver); Rust on Unity 6 needs Windows 10 21H1 (build 19043) or newer, so install pending Windows updates.OfficialSource 4
Back up the cfg folder somewhere outside the Rust folder, then delete the cfg and bundles folders in the Rust folder (Library → right-click Rust → Manage → Browse local files).CommunitySource 5
Verify files again so Steam re-downloads bundles (a large download) before you launch.OfficialSource 1
If it keeps crashing, collect the newest .dmp from %LOCALAPPDATA%\Temp\Facepunch Studios LTD\Rust\crashes and output_log.txt from the Rust folder and open a Facepunch ticket.OfficialSource 6
Caveats
The build string changes between Rust updates (x1-11, x1-13…); it does not mean you are banned (a 2026-10-16 thread asked this; replies say it is only the Unity version). No Facepunch article covers this popup. The cfg/bundles reset is community-reported: the original Reddit report (kept as source) could not be re-fetched on 2026-10-30 because Reddit blocked access, but the same steps were suggested on Steam on 2026-10-01 and a cfg-folder reset fixed a related loading crash for several players; at least one 2026-10-16 player says cfg reset, verify and reinstall did not help. Raising the page file helped one 2026-09-05 player once and then stopped helping. The DLSS-override fix was reported by two players in the 2026-09 thread. The Windows-version link is inferred: Unity 6.3's player requires Windows 10 21H1+ and Facepunch announced that minimum, but no source ties this popup to it directly.
A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:
Launch and crashesOfficial sources
Also seen asUnityCrashHandler64.exeRust closes to desktop with no error
Where you see it
The last lines of Rust's output log (or a crash-handler window) after the game closes unexpectedly.
Why it happens
Rust's engine (UnityPlayer) crashed and the Unity crash handler wrote a report; the line itself does not say why.
What to do, in order
Note what you were doing and when, then verify Rust's files in Steam.OfficialSource 1
Open %LOCALAPPDATA%\Temp\Facepunch Studios LTD\Rust\crashes, sort by Date modified and keep the newest .dmp file.OfficialSource 2
Copy output_log.txt from the Rust install folder (default C:\Program Files (x86)\Steam\steamapps\common\Rust).OfficialSource 3
Do a clean graphics-driver install with your GPU vendor's own installer option (see the GPU-driver entry).OfficialSource 4
Open a Facepunch support ticket with the .dmp, output_log.txt and your PC specs from dxdiag (Win+R → dxdiag → Save All Information).OfficialSource 5
Caveats
Exact log text quoted in a 2025-06-08 Microsoft Q&A thread, path shown as AppData/Local/Temp/Facepunch Studios LTD/Rust/Crashes. Facepunch says it fixed EAC blocking crash dumps in September 2026 and since October 2026 uploads crashes to its backend automatically. Do NOT delete UnityCrashHandler64.exe: some Russian-language threads suggest it, but the crash handler only reports crashes. Community suggestions in that Q&A thread (manual 8000–16000 MB page file, '-windowed -noborder') are unverified; '-windowed' and '-noborder' are not Unity player arguments.
Grab the latest .dmp from %LOCALAPPDATA%\Temp\Facepunch Studios LTD\Rust\crashes.OfficialSource 2
Grab output_log.txt from the Rust install folder.OfficialSource 3
If support asks, test with RustClient.exe (Rust without EAC) to see whether the crash still happens before the main menu.OfficialSource 4
Open a ticket with Facepunch with both files and a description of what you were doing, before looping through reinstalls.OfficialSource 2
Caveats
Facepunch's article also says to type %AppData% and then go to \Local\Temp\…, but %AppData% opens the Roaming folder; %LOCALAPPDATA%\Temp (or %TEMP%) reaches the right place. RustClient.exe without EAC can only join unsecure servers; use it only as a test.
Also seen asFaulting application name: RustClient.exeRust.exe caused an Access Violation (0xc0000005) in module UnityPlayer.dllCrash in UnityPlayer.dllRust has stopped workingApplication has stopped working
Where you see it
Windows Event Viewer (Windows Logs → Application) after Rust closes, or a Unity crash report.
Why it happens
Rust's engine crashed reading or writing memory it shouldn't. It names where it crashed, not why; graphics drivers, damaged files, overlays, unstable overclocks or memory faults are common culprits.
Close overlays and monitoring tools (Discord overlay, MSI Afterburner/RivaTuner, recording software) and test again.OfficialSource 2
Do a clean graphics-driver install (NVIDIA: Custom (Advanced) → Perform a clean installation; AMD: AMD Cleanup Utility; Intel: clean-installation checkbox).OfficialSource 3
Remove CPU/GPU/RAM overclocks and test at stock settings.OfficialSource 2
Run Windows Memory Diagnostic (Start → mdsched) to rule out RAM errors.OfficialSource 2
Send the .dmp and output_log.txt to Facepunch support.OfficialSource 4
Caveats
Event Viewer text quoted from a 2026-05-31 Steam thread (RustClient.exe/UnityPlayer.dll version 6000.3.15.51057). Modern Windows rarely shows the old "has stopped working" dialog; Rust usually just closes. Do not download UnityPlayer.dll from DLL sites; verify files instead.
Also seen as...\Rust\UnityPlayer.dll is either not designed to run on Windows or it contains an error. Error status 0xc0e90002Bad Image 0xc000012f
Where you see it
A Windows dialog as Rust starts, naming a DLL in the Rust folder.
Why it happens
Windows could not load a game DLL because the file on disk is damaged, incomplete or was altered (for example by antivirus or a failing drive).
What to do, in order
Verify Rust's files in Steam so the damaged DLL is replaced.OfficialSource 1
Check Windows Security → Virus & threat protection → Protection history for a block or quarantine of that file.OfficialSource 2
Check the drive for errors: This PC → right-click drive → Properties → Tools → Error checking.OfficialSource 3
If it persists, do a fresh install of Rust.OfficialSource 4
Run sfc /scannow from an administrator Command Prompt to repair Windows system files.OfficialSource 5
Caveats
Wording: the 2026-08-16 Steam report is in Russian (error status 0xc0e90002); the English sentence above is Windows' standard Bad Image text, translated, not quoted from a Rust player. The 0xc000012f alias is a common Bad Image status but was not seen in a Rust report. The reporter had already verified files and installed VC++ redistributables without success; no resolution was posted.
Failed to initialize player. Details: Failed to initialize graphics. Make sure you have DirectX11 installed, have up to date graphics card and have not disabled 3D acceleration in display settings. InitializeEngineGraphics failed
Launch and crashesOfficial and community sources
Also seen asFailed to initialize playerInitializeEngineGraphics failedFailed to create D3D11 deviceGraphics device is nullDirectX 11 / D3D11 GPU required
Where you see it
A Unity dialog right after the Rust splash, before the main menu.
Why it happens
Unity could not create a Direct3D device: the GPU or driver lacks DirectX 11 support, the driver is broken, a graphics injector (ReShade) is loaded, or a forced graphics launch option no longer works.
What to do, in order
Remove graphics launch options you added (Library → right-click Rust → Properties → General → Launch Options) and test.CommunitySource 1
Remove ReShade or other graphics injectors from the Rust folder, then verify files.OfficialSource 2
On laptops, make sure Rust runs on the dedicated GPU, not integrated graphics.OfficialSource 4
Do a clean driver install with the vendor's installer (NVIDIA clean installation, AMD Cleanup Utility, Intel clean install).OfficialSource 5
Caveats
Main wording quoted from a ReShade-forum Rust report; "InitializeEngineGraphics failed" also appears in Rust Steam threads (2017, 2023). "Failed to create D3D11 device", "Graphics device is null" and "D3D11 GPU required" are Unity log/dialog wordings that were NOT found in a current Rust report; listed as aliases only. A 2017 Steam thread says removing a forced DirectX 9 launch option fixed it after Rust dropped DX9. The dedicated-GPU step comes from Facepunch's Garry's Mod article, applied by analogy. Do not install old DirectX 9 (June 2010) runtimes for Rust; Facepunch's DirectX-runtime article is about Garry's Mod.
d3d11: failed to create 2D texture ... D3D error was 887a0005
Launch and crashesOfficial sources
Also seen asDXGI_ERROR_DEVICE_REMOVEDd3d11: failed to create staging 2D texture [887a0005]Rust.exe is not respondingThis application is not responding
Where you see it
In output_log.txt when Rust freezes on a loading screen or after a few minutes of play, often followed by "not responding".
Why it happens
0x887A0005 means the graphics driver stopped responding or was reset (Windows' Timeout Detection and Recovery), so Rust lost its GPU device. Causes include driver faults, unstable GPU clocks or overheating.
What to do, in order
Update or clean-install your graphics driver with the vendor's own option (NVIDIA: Perform a clean installation).OfficialSource 1
AMD users: run AMD Cleanup Utility (preferably in safe mode), then install the current driver.OfficialSource 2
Intel Arc users: use the clean-installation checkbox in Intel's driver installer.OfficialSource 3
Remove GPU overclocks or undervolts and test at stock clocks.OfficialSource 4
Collect output_log.txt and the latest .dmp and send them to Facepunch support.OfficialSource 5
Caveats
Microsoft defines DXGI_ERROR_DEVICE_REMOVED 0x887A0005 as the GPU being removed or the driver upgraded/reset; TDR fires when the GPU hangs longer than 2 seconds. Do NOT edit TdrDelay/TdrLevel registry keys: Microsoft documents those for testing and debugging, and raising them hides hangs rather than fixing them. Log lines quoted from 2026-04-13 (RTX 2060) and 2026-09-14 (RTX 5060 Ti) Steam threads; neither had a confirmed fix. In the 2026-09-14 report '-force-d3d12' caused a different crash ('Kernel WaveSpectrum not found in WaterSystem').
Also seen asSystem out of memoryOut of memorySystem.OutOfMemoryExceptionYour system is low on virtual memoryThe paging file is too small for this operation to complete
Where you see it
A fatal dialog or log line, usually while loading a map or prefabs on joining a server.
Why it happens
Windows could not give Rust more memory: physical RAM plus page file was used up, often because the page file is capped or very small, the PC is near the 12 GB minimum, or integrated graphics is taking system RAM.
What to do, in order
Close browsers, Discord and other heavy apps before launching Rust.CommunitySource 1
Set the page file back to automatic: Advanced System Settings → Performance Settings → Advanced → Virtual memory Change → tick Automatically manage paging file size for all drives → OK, then restart.OfficialSource 2
Make sure the system drive has plenty of free space so Windows can grow the page file.OfficialSource 3
Lower texture quality and other memory-heavy settings.CommunitySource 4
Check your PC against Rust's minimum: 12 GB RAM, a dedicated GPU from the GTX 1060 / RX 470 class, SSD highly recommended.OfficialSource 5
Caveats
Exact text quoted from a 2025-10-25 Steam report (Ryzen 5600G iGPU, 16 GB). Other wordings are Windows/.NET standard messages, not confirmed in a 2026 Rust report. Microsoft: the commit limit is RAM plus all page files; with no page file it is slightly below installed RAM. A huge manual page file is not a fix for too little RAM (several 2026 threads tried 30–48 GB with no change). Avoid 'RAM cleaner' or 'memory booster' tools. Launch options like -maxMem= are not documented by Facepunch or Unity.
The code execution cannot proceed because steam_api64.dll was not found. Reinstalling the program may fix this problem.
Launch and crashesOfficial sources
Also seen assteam_api64.dll is missingsteam_api64.dll not foundUntrusted system file ...\Rust\steam_api64.dll
Where you see it
A Windows dialog when Rust starts.
Why it happens
Rust's Steamworks DLL is missing or blocked, usually because antivirus quarantined it as a false positive or the install is incomplete.
What to do, in order
Check Windows Security → Virus & threat protection → Protection history and restore/allow the file if Rust's steam_api64.dll was quarantined.OfficialSource 1
Verify Rust's files so Steam restores the DLL.OfficialSource 2
If your antivirus keeps removing it, add the Rust folder as an exclusion in that antivirus (not a full disable).OfficialSource 3
If it still fails, do a fresh install of Rust.OfficialSource 4
Caveats
The dialog wording is Windows' standard missing-DLL message; no 2026 Rust player quote of it was found. Facepunch's Steam article covers the same cause for a missing executable. Never download steam_api64.dll from DLL-download websites; files from them can be wrong versions or malware, and a replaced Steam DLL can also be flagged by EAC (the 'Untrusted system file' variant is an EAC message, covered in the EAC section).
Also seen asSmart App Control has blocked part of this appSome features of RustClient.exe may not work because the publisher of GameAssembly.dll could not be verifiedWindows Defender flags GameAssembly.dllFailed to load mono
Where you see it
On launch, usually right after a Rust update, sometimes after a Windows security popup about GameAssembly.dll.
Why it happens
Rust's compiled game code (GameAssembly.dll) was blocked or quarantined by Windows Security or another antivirus, so the game cannot load it.
What to do, in order
Click Learn more on the Windows popup, or open Windows Security → Virus & threat protection → Protection history, to see what was blocked.OfficialSource 1
If GameAssembly.dll from the Rust folder was quarantined, restore it from Protection history.OfficialSource 2
Verify Rust's files so Steam replaces anything removed.OfficialSource 3
If your antivirus keeps flagging it, exclude only the Rust folder rather than turning protection off.OfficialSource 4
Caveats
Reported on Steam 2026-10-01 (Windows 11) and 2025-04-10 (verify fixed it). Microsoft says Smart App Control blocks files that are not validly signed; Microsoft does not recommend turning it off, and turning it off has historically been one-way without reinstalling Windows, so do not. Treat a block as a possible false positive only if the file is Rust's own and Steam verification restores it. 'Failed to load mono' is the pre-IL2CPP form of this error from older Rust builds (2018–2020 reports); current Rust uses GameAssembly.dll/IL2CPP.
No 2026 Rust-specific report of this dialog was found; it is included because it is a common Windows launch error and the fix is Microsoft's. Get the redistributable only from Microsoft; never from DLL-download sites. Installing it will not fix crashes that are not about these DLLs (a 2026-08-16 Bad Image reporter tried it without effect).
Also seen asWindows 10 not supportedRequires a 64-bit processor and operating system
Where you see it
Rust fails to start or crashes on startup on an older Windows build or a 32-bit system.
Why it happens
Since the 2026 Unity 6 upgrade Rust needs at least Windows 10 version 21H1 (build 19043); the Steam store now lists Windows 11 64-bit as the minimum, and 32-bit Windows is not supported.
What to do, in order
Press Win+R, type winver and check your Windows version and build.OfficialSource 1
Install all Windows updates (Settings → Windows Update) so you are at least on Windows 10 21H1 (build 19043).OfficialSource 2
Plan a move to 64-bit Windows 11: it is the store's listed minimum and Windows 10 support ended on October 14, 2025.OfficialSource 3
Caveats
Facepunch (May 2026): "The minimum required version will be ... Windows 10 Version 21H1 (Build 19043) or newer". Unity 6.3 player docs say the same. Store page read 2026-10-30 lists OS: Windows 11 64bit (minimum and recommended), 12 GB RAM, GTX 1060 / RX 470 / Arc A580, DirectX 11, 45 GB, SSD highly recommended. Whether Rust still runs on fully-updated Windows 10 was not tested; players report it does, but it is below the published minimum and no longer receives Windows security updates without ESU. Secure servers additionally require TPM 2.0 and Secure Boot (EAC section).
Crash or freeze while loading into a server ("Spawning World", "Preparing prefabs" / "Cleaning Up")
Launch and crashesOfficial and community sources
Also seen asStuck on Preparing prefabsHangs at Cleaning Up 1616/5040Crashes on Spawning WorldCrash on Loading with new NVIDIA driver
Where you see it
On the server-loading screen, often after a GPU driver or Rust update.
Why it happens
Usually a damaged local Rust config or cache, a GPU feature forced on Rust (DLSS, driver overrides), or a driver that misbehaves with the current Rust build; in October 2026 several RTX 50-series owners reported hangs after a new NVIDIA driver.
What to do, in order
Turn DLSS off in Rust's graphics settings, join once, then turn it back on if wanted.CommunitySource 1
Close Rust, back up and delete the cfg folder in the Rust folder (some players also cleared maps and ai), then verify files.CommunitySource 1
Clean-install the current driver with the vendor tool (NVIDIA: Custom (Advanced) → Perform a clean installation).OfficialSource 3
AMD: run AMD Cleanup Utility in safe mode, reboot, install the current Adrenalin driver.OfficialSource 4
Intel Arc: run the driver installer and tick the clean-installation checkbox.OfficialSource 5
If it started with a brand-new driver, roll back to the previous driver and report it to Facepunch with your output_log.txt.CommunitySource 6
Caveats
Deleting cfg fixed the Spawning World freeze for several players (2025-10 to 2026-06 thread; 2026-08-01 RTX 5080 thread), but not everyone. The RTX 5060 reports (2026-10-27, 2026-10-29) name drivers 621.01 (problem) and 617.42 (rolled back, still failed for that user); those driver numbers and any NVIDIA acknowledgement could NOT be confirmed from NVIDIA release notes. DDU (Display Driver Uninstaller) is widely recommended by players but is a third-party tool; vendors' own clean-install options are preferred. Avoid 'driver updater' apps.
Rust crashes or freezes at startup with an overlay running
Launch and crashesOfficial and community sources
Also seen asDiscord overlay crashMSI Afterburner / RivaTuner (RTSS) crashGeForce Experience / NVIDIA App overlay crash
Where you see it
Rust hangs on its first loading screen or crashes soon after launch while overlay or monitoring software runs.
Why it happens
Overlay and monitoring tools inject into the game's rendering; some versions conflict with Rust's engine or with EAC.
What to do, in order
Fully exit MSI Afterburner and RivaTuner Statistics Server (system tray), then launch Rust.CommunitySource 1
Turn off the Discord in-game overlay and the NVIDIA App/GeForce overlay and test again.OfficialSource 2
Disable other recording, 'performance booster' or system-monitor software while testing.OfficialSource 3
If Rust works without them, re-enable one at a time to find the culprit, or update it.OfficialSource 4
Caveats
No current Rust-specific Facepunch article on overlays; the named list (Discord Overlay, RivaTuner/MSI Afterburner) is from Facepunch's Garry's Mod start-up article, and Steam Support lists recording software and performance boosters as interfering programs. A 2017 Rust thread fixed a startup hang by changing RTSS settings. EAC can also refuse some tools; EAC messages are covered separately.
Also seen asBlack screen when joining a serverScreen is black when tabbed in, UI visible
Where you see it
Rust starts (music may play) but the screen stays black, at the menu or while loading into a server.
Why it happens
Usually a display-mode/resolution mismatch, an overlay, or a graphics-driver problem; while loading, it can also be the same causes as loading-screen crashes.
What to do, in order
Start Rust windowed once by adding -screen-fullscreen 0 to Launch Options, fix the resolution in Options, then remove it.OfficialSource 1
Close overlays (Discord, RTSS/Afterburner, NVIDIA App) and test.OfficialSource 2
Clean-install your graphics driver with the vendor's option.OfficialSource 4
Caveats
No Facepunch article covers it; Rust black-screen threads checked (2019, 2026-02, 2026-05-31) had no confirmed fix posted. -screen-fullscreen 0 is a documented Unity player argument; whether Rust honours every Unity argument is Assumed, not tested. Black screen while loading on RTX 50 cards: see the loading-crash entry. Alt+Tab / Alt+Enter tips are common, but in the Rust threads checked Alt+Tab did not help.
Extra options can work around a problem for testing, but stale ones from old guides are a common cause of launch failures.
What to do, in order
When troubleshooting, first clear the Launch Options box completely and test with nothing in it.CommunitySource 1
To test whether the DirectX path is the problem, try -force-d3d11 on its own, then remove it after testing.OfficialSource 2
For true exclusive full screen, -window-mode exclusive is the documented Unity option; remove it if Rust crashes or ignores it.OfficialSource 2
Caveats
Unity documents -force-d3d11, -force-d3d12, -force-vulkan, -window-mode exclusive|borderless, -screen-fullscreen 0|1, -force-gfx-direct and -disable-gpu-skinning for players; whether Rust passes each through is Assumed. Players report -window-mode exclusive being ignored (2019) or crashing (2017), and -force-d3d12 / -force-vulkan crashing in 2026. -gc.buffer is a Rust console setting used by players; no Facepunch documentation was found, and a 2026-07-19 bug report says it is no longer honoured (capped near 2008 MB) since the 17 July 2026 build. -maxMem, -malloc=system, -cpuCount, -exThreads, -high, -windowed, -noborder and -useallavailablecores are NOT documented by Unity or Facepunch for Rust; a 2026-10-16 reply says most launch options 'were disabled a while back' (unverified). Do not copy long launch-option lists from videos.
Rust crashes on launch on Apple Silicon Macs after the June 18, 2026 update
Launch and crashesCommunity reports
Also seen asEXC_BAD_ACCESS (SIGSEGV) in libanybrainSDK.dylibanybrain::HardwareInfoMac::calcDeviceId()
Where you see it
macOS crash report shortly after Rust opens, before or at the main menu.
Why it happens
A crash in an anti-cheat/analytics library on Apple Silicon (M1–M4) Macs introduced with the June 18, 2026 build.
What to do, in order
Update Rust; players report the August 7, 2026 update fixed it.CommunitySource 1
If it still crashes, send the crash report to Facepunch support.CommunitySource 1
Caveats
Rust's store page lists macOS Monterey (12) and Apple M1 as minimum. Facepunch support's reply quoted in the thread suggested enabling Rust under System Settings → Privacy & Security → Accessibility; the player said it did not help. Rolling back via Steam betas let players reach the menu but not join live servers ('Wrong Connection Protocol').
Connecting to a serverOfficial and community sources
Also seen asSteam Auth TimeoutDisconnected due to error: Steam auth timeoutRejecting connection - Steam Auth Timeout (server console)
Where you see it
On the disconnect screen while joining a server, usually after the connection screen has started.
Why it happens
The server asked Steam to confirm your login ticket and Steam did not answer in time. When it hits many players at once it is a Steam-side outage (Facepunch has said such waves followed Steam's weekly maintenance and were beyond its control), and nothing on your PC will fix it.
What to do, in order
Check whether it is widespread: try a second server, and look at the Rust General Discussions board or Rust's official X account for an outage. If many players have it, wait.CommunitySource 2
Fully close Rust and Steam, relaunch Steam, then launch Rust from the Steam library.OfficialSource 3
In Steam, choose Steam > Check for Steam client updates, and install any update.OfficialSource 3
Opt out of Steam client betas: Steam > Settings > Beta participation > "No beta chosen" / "NONE - opt out", then restart Steam.OfficialSource 3
Restart your router/modem, and test on a wired connection if you are on Wi-Fi.OfficialSource 4
Verify Rust's files: right-click Rust > Properties > Installed Files (older Steam and Facepunch's articles: Local Files) > Verify integrity of game files.OfficialSource 5
If it still happens on every server, do a fresh install (delete the Rust folder, then reinstall from Steam).OfficialSource 6
Caveats
The Facepunch steps above come from its 'Steam not open & startup errors' article; Facepunch has no article on Steam Auth Timeout itself, so they are applied here because both are Steam-session problems. The outage statements are quoted by PCGamesN from Rust's official X account, not read from X directly. A widely copied 'fix', raising server.connectiontimeout, is a server setting for admins, not something a player can change. Reinstalling during a Steam outage wastes time: check for a wave first.
Connecting to a serverOfficial and community sources
Also seen asKicked: Steam Auth FailedSTEAM auth failed
Where you see it
On the disconnect screen when connecting, sometimes on one server only while others work.
Why it happens
Steam rejected or could not validate the login ticket the server checked. Reports cluster on days when Steam's backend has problems; a single server affected for many players points to that server's own link to Steam.
What to do, in order
Try another server; if others work and many players report the same server, it is the server's problem. Tell its staff and wait.CommunitySource 1
Fully restart Steam and launch Rust from the Steam library.OfficialSource 3
Verify Rust's files in Steam (Properties > Installed Files (older Steam and Facepunch's articles: Local Files) > Verify integrity of game files).OfficialSource 4
If it persists everywhere, reinstall Rust (one player reported a reinstall fixed it).CommunitySource 1
Caveats
Exact wording confirmed from player reports on the Steam forum (2025 and 2026). No official Facepunch or Valve article describes this message; treat the cause as community-reported. Contact the server's staff if only their server fails.
Connecting to a serverOfficial and community sources
Also seen asSteam: AuthTicketCanceledSteam Status "AuthTicketCanceled"Auth ticket canceledSteam Auth Ticket Cancelled
Where you see it
On the disconnect screen or in the F1 console, often mid-game, sometimes for several players at once.
Why it happens
Steam told the server that the login ticket for your session was cancelled (AuthTicketCanceled is one of the Steam authentication responses Facepunch documents). It usually follows your Steam client losing its connection, or a Steam-side hiccup; several players dropped at once means it was not your PC.
What to do, in order
Reconnect; it is often a one-off.CommunitySource 2
If it repeats, fully restart Steam and launch Rust from the Steam library.OfficialSource 4
If it repeats, work through Steam's network checklist: router reboot, wired connection, firewall.OfficialSource 5
Caveats
The response name comes from Facepunch's Steamworks documentation; the documentation lists the value but gives no description, so the plain-language cause is community-reported. The 'Kicked: Steam: AuthTicketCanceled' form is quoted in a server owner's post.
Also seen asSteam: LoggedInElseWhereSteam: NoLicenseOrExpiredSteam: VACCheckTimedOutSteam: AuthTicketInvalidSteam: AuthTicketInvalidAlreadyUsedSteam: UserNotConnectedToSteamSteam: PublisherIssuedBanKicked: Steam: Unresponsive
Where you see it
On the disconnect screen or in the F1 console, with a Steam authentication code after "Steam:".
Why it happens
The server passes on Steam's own authentication answer. The names are Steam's: e.g. LoggedInElseWhere (the account is in use in another session), NoLicenseOrExpired (this account does not own Rust, e.g. a family-shared copy), UserNotConnectedToSteam (your Steam client is not signed in online).
What to do, in order
Fully restart Steam (close it, relaunch it) and launch Rust from the Steam library.OfficialSource 2
For NoLicenseOrExpired: play on the Steam account that bought Rust; family-shared copies are not allowed.OfficialSource 3
For any other code: restart Steam and Rust, then check your connection with Steam's network checklist.OfficialSource 4
Caveats
Only 'Steam: AuthTicketCanceled' (separate entry) and 'Steam: Unresponsive' were seen in player reports with the 'Kicked: Steam:' prefix; the other names are taken from the Steamworks AuthResponse enum Facepunch documents and were NOT found in a player report, so their exact on-screen form is unconfirmed. The meanings given are plain readings of Steam's response names (the Facepunch page has no descriptions). PublisherIssuedBan relates to a publisher (Facepunch) game ban: see the 'Publisher Banned' entry. Reasonable but unsourced advice (Assumed): for LoggedInElseWhere, close Rust and Steam on any other PC using the same account; for UserNotConnectedToSteam, take Steam out of Offline Mode.
Connecting to a serverOfficial and community sources
Also seen asYou are not whitelistedNot whitelistedKicked: Whitelist
Where you see it
On the disconnect screen immediately after connecting to a private or whitelisted server.
Why it happens
The server only lets in Steam accounts its staff have added. Rust has no built-in whitelist, so this comes from a server plugin and the wording is whatever that server set.
What to do, in order
Check the server's website or Discord for how to apply for whitelist access.OfficialSource 1
Ask the server's staff to add your Steam64 ID, and send them the exact kick text.CommunitySource 2
Caveats
Facepunch's wiki confirms vanilla Rust has no whitelist (servers use an Oxide/uMod plugin, or set server.maxplayers 0 and use skipqueue). The message shown is the example default of one whitelist plugin; others differ. Nothing on the player's PC can fix it. Lone Wolf Rust is not a whitelisted server; its entry checks are the FIREWALL (see the VPN and staging entries).
Connecting to a serverOfficial and community sources
Also seen askicked: Wrong Connection Protocol: Client update required!Wrong connection protocol: Client update requiredtheir protocol is X not Y (server console)
Where you see it
On the disconnect screen right after clicking Join, typically on or just after a Rust update day.
Why it happens
Your copy of Rust is older than the server's. The server compares version (protocol) numbers and refuses an older client.
What to do, in order
Close Rust and let Steam finish downloading the Rust update; restart Steam if no update appears.CommunitySource 1
Launch "Rust", not "Rust - Staging Branch".OfficialSource 4
Opt out of Rust betas: right-click Rust > Properties > Betas > None, then verify files.OfficialSource 4
Verify Rust's files: Properties > Installed Files (older Steam and Facepunch's articles: Local Files) > Verify integrity of game files.OfficialSource 5
Caveats
Exact text confirmed in a 2023 Steam thread quoting the server log. Facepunch's article does not name this message; its beta/staging steps are applied because a beta or staging client runs a different build. If you are fully updated and still get this, the server may be on a newer staging/test build than release.
Wrong Connection Protocol: Server update required!
Connecting to a serverOfficial and community sources
Also seen asConnection error, server update requiredserver update requiredwrong connection protocol - server update required
Where you see it
On the disconnect screen right after clicking Join, usually just after a Rust update.
Why it happens
The server is running an older build than your client. After a Facepunch update each community server has to update itself, and until it does, updated players cannot join.
What to do, in order
Wait: the server's owner has to update it. Check the server's Discord or website for an update notice.CommunitySource 1
Make sure you are not on a beta or Staging Branch build that is newer than release (Properties > Betas > None).OfficialSource 3
If every server says this, verify your files, since you may be on the wrong branch.OfficialSource 4
Caveats
Nothing on the player's PC can update the server. Do not roll back or try to downgrade your client. Contact the server's staff if it stays down long after an update.
Also seen asClient update required!Server update required!
Where you see it
On the disconnect screen when a Staging Branch (or beta) client tries to join a release server, or the reverse.
Why it happens
Steam lists two separate games, "Rust" and "Rust - Staging Branch". Staging runs a test build, so its version usually does not match release servers and the server refuses the connection; staging also has far fewer servers.
What to do, in order
Close Rust - Staging Branch and launch "Rust" from your Steam library.OfficialSource 1
In Rust > Properties > Betas, make sure no beta is selected, then verify game files.OfficialSource 1
For Lone Wolf Rust, always use the main client: the FIREWALL does not allow the Staging Branch.OfficialSource 2
Caveats
Which suffix appears (client vs server update required) depends on which build is newer; that follows from how the protocol check works and was not observed for staging specifically, so treat it as Assumed. Lone Wolf's FIREWALL blocks the Staging Branch whatever the message says; the exact wording of the FIREWALL's own kick was not confirmed.
Connecting to a serverOfficial and community sources
Also seen asConnection attempt failedStuck on "Connecting"
Where you see it
On the main menu a few seconds after trying to join, before any loading screen.
Why it happens
Your client never got an answer from the server: the server may be starting up, restarting, full of junk traffic, or unreachable from your network (VPN, firewall, router).
What to do, in order
Wait a minute or two and try again; a server that is still starting gives this.CommunitySource 1
Try a different server. If all fail, the problem is on your side.CommunitySource 2
Update your antivirus/firewall and test with the firewall briefly off; if that fixes it, add an allow rule for Rust instead of leaving it off.OfficialSource 3
Connect directly: from the main menu press F1 and type client.connect IP:PORT (BattleMetrics lists a server's IP and port).OfficialSource 3
If you host the server on your own network, connect with its LAN address (or localhost on the same PC) rather than your public IP.CommunitySource 4
Caveats
Exact text confirmed in a 2015 Steam thread ('There is no message saying "failed to join". It should be "Connection attempt failed"'). Facepunch's 'No servers showing' article is about the browser, but its VPN, router, firewall and direct-connect steps apply. Do not leave Windows Firewall or antivirus disabled; test briefly, then make an exception. If you host on a home network, Steam's 'Required Ports' page lists the ports Steam itself needs; the game port (Rust default 28015) must also be forwarded.
On the disconnect screen, during play or while loading in.
Why it happens
The server stopped hearing from your client (or you from it) for too long. It is usually packet loss or a dropped connection between you and the server; if a whole server drops at once, it is the server or its host.
Test on a wired connection instead of Wi-Fi or powerline.OfficialSource 3
Turn off VPNs, proxies, download accelerators and other programs Steam lists as interfering.OfficialSource 4
Verify Rust's files if it happens on every server.OfficialSource 5
Caveats
The message wording is confirmed from a December 2024 Steam thread; that thread has no replies and no confirmed fix (the poster had already verified files, reinstalled Rust and Steam and tried other servers). If a whole server drops at once, it is the server or its host: tell its staff. The Steam Support network articles are general Steam connectivity guidance, not Rust-specific. Changing Steam's 'server browser pings per minute' does not affect an established connection.
Connecting to a serverOfficial and community sources
Also seen asKicked: UnresponsiveDisconected : UnresponsiveKicked: Steam: Unresponsive
Where you see it
On the disconnect screen, typically shortly after joining or while the game hitches at the end of loading.
Why it happens
The server decided your client had stopped responding: either your game froze (for example a long hitch while loading) or your connection stopped delivering data for a while.
What to do, in order
Reconnect once; the answer marked correct on the Steam forum says the kick happens when the game freezes and the server treats you as inactive.CommunitySource 2
Restart your router and test on a wired connection.OfficialSource 3
Make sure Windows manages the pagefile automatically (Advanced System Settings > Performance > Advanced > Virtual Memory > Automatically manage), then restart.OfficialSource 4
No official article explains this kick; the cause is community-reported. Facepunch's pagefile article is about performance problems in general and is included because a frozen client is one reported trigger, not because Facepunch links it to this message. If several players are kicked as unresponsive at the same moment, it is the server; tell its staff.
Connecting to a serverOfficial and community sources
Also seen asPacket FloodingKicked: Packet Flooding: Client CommandDisconnected: Packet Flooding
Where you see it
On the disconnect screen during play, sometimes for several players at the same moment.
Why it happens
The server received far more packets of one type from you in one second than its limit allows, and kicked you to protect itself. Normal players hit it when packets pile up and arrive in a burst: after a network stall on your side, or after the server itself froze for a few seconds.
What to do, in order
Reconnect. If several players were kicked at the same moment, the server stalled; tell its staff.CommunitySource 1
If it is only you, again and again, restart your router and test on a wired connection.CommunitySource 2
Close bandwidth-heavy programs (downloads, streaming uploads) while playing.OfficialSource 4
Caveats
The limit is a server setting (server.maxpacketspersecond_tick, default 300 per a server host's reading of the server code); only the server admin can change it. Common advice to verify files or clear Steam's download cache does not address the cause. The 'Client Command' variant has been reported when a server's plugins or version were out of date. No official Facepunch article covers this kick.
Connecting to a serverOfficial and community sources
Also seen asDisconnected: Invalid Packet: Player TickKicked: Invalid Packet: Client ReadyDisconnected: invalid packet: user information
Where you see it
On the disconnect screen while joining or shortly after; the part after 'Invalid Packet:' names the message the server rejected.
Why it happens
The server could not read a message your client sent. It shows up in waves after updates when client, server or server mods do not match, and can also come from a server-side bug.
What to do, in order
Make sure Rust is fully updated, then verify your files.OfficialSource 4
Try another server: if only one server does it, it is that server's build or plugins.CommunitySource 3
Report the full text (including the part after 'Invalid Packet:') to the server's staff.CommunitySource 2
Caveats
Exact text confirmed in Steam threads (2015 wave after a patch; 2018 'Player Tick' variant). No official article covers this.
Also seen asKicked: RPC Error in RPC_WantsMountKicked: RPC Error: OnProjectileAttackKicked: RPC Error in ItemCmd
Where you see it
On the disconnect screen right after doing something specific (mounting a vehicle, shooting, moving an item).
Why it happens
The server hit an error while processing an action you took and dropped you. The name after 'RPC Error' is the server function that failed. It is almost always a server-side bug, often in a plugin or an out-of-date mod framework, not your PC.
What to do, in order
Reconnect and avoid repeating the exact action that triggered it.CommunitySource 1
Report it to the server's staff with the full message and the time it happened.CommunitySource 2
Caveats
Do not reinstall Rust for this; the fault is on the server. Server admins find the cause in the server log just before the kick.
Also seen asDisconnect: Too many Connections from this IP
Where you see it
On the disconnect screen when connecting, sometimes after being dropped from a server and trying to rejoin.
Why it happens
The server limits how many connections it accepts from one IP address. You can hit it if your previous session has not been cleared yet, or if several people in your home (or behind the same carrier-grade NAT) are connecting at once.
What to do, in order
Wait a few minutes before reconnecting so the old session times out.CommunitySource 1
If others in your household play the same server, tell its staff that you share an IP.CommunitySource 1
Caveats
Exact text confirmed from a January 2024 Steam thread; the thread has no confirmed fix and the cause above is an inference from the message (Assumed). Restarting the router to get a new IP is sometimes suggested but was not confirmed to help. Contact the server's staff if it persists.
Connecting to a serverOfficial and community sources
Also seen asServer is fullKicked: Server FullQueue
Where you see it
On the connecting screen (queue position shown) or back on the main menu when the server has no free slot.
Why it happens
Every slot is taken. Rust places joining players in a connection queue that shows how many are ahead of and behind you; you join when a slot frees.
What to do, in order
Stay on the queue screen rather than re-clicking Join, which can lose your place.CommunitySource 2
If you were bounced to the main menu, press F1 and read the last console line to confirm it was a full server.OfficialSource 1
Join another server, or try again off-peak.OfficialSource 1
Caveats
Facepunch's own source is a 2013 news post from before the queue existed. Queue-skip is a server feature (built-in skipqueue list or plugins); a player cannot skip a queue themselves.
On the disconnect screen with no useful reason, e.g. after a kick, a ban, a restart or a wipe.
Why it happens
The server closed your connection without passing a reason the client could show. Common causes are a staff kick, a plugin kick (whitelist, VPN blocker, anti-cheat plugin), or the server shutting down for a restart or wipe.
What to do, in order
Wait a minute and try to rejoin: if you are banned or blocked, the real reason usually shows on the second attempt.CommunitySource 1
If it repeats, ask the server's staff: the kick reason (whitelist, VPN blocker, anti-cheat plugin) is in the server's console.CommunitySource 2
Connecting to a serverOfficial and community sources
Also seen asKicked for disallowed VPN / ProxyVPN / proxy detected
Where you see it
On the disconnect screen immediately after connecting to a server that blocks VPNs, such as Lone Wolf Rust.
Why it happens
The server checks your IP address and refuses connections that look like a VPN, proxy or hosting provider. Servers do this because VPNs make banned players' alt accounts harder to catch. The wording depends on the server's plugin.
What to do, in order
Turn off your VPN or proxy app completely (disconnect it, do not just pause it), then reconnect.OfficialSource 1
After disabling the VPN, exit and restart Steam (Steam's own advice for any interfering program).OfficialSource 2
On Lone Wolf Rust, GeForce NOW and ShadowPlay are allowed. If you genuinely need a VPN, open a VPN exception ticket in our Discord. Exceptions aren't given for ping, because a VPN doesn't improve it.OfficialSource 5
If you are not using a VPN and still get it, send the exact message to the server's staff; some ISP or mobile addresses get flagged by mistake.CommunitySource 4
Caveats
Lone Wolf Rust's FIREWALL requires connecting without a VPN (published FIREWALL page). The exact text of Lone Wolf's own FIREWALL kick was NOT confirmed. 'Kicked: VPN is Blocked' is another server's message as reported in 2025. A VPN does not lower ping in Rust; do not rely on one to 'fix' connection errors.
Disconnected by VAC: You cannot play on secure servers
Connecting to a serverOfficial sources
Also seen asVAC banned from secure serverSecure connection failedA connection to the VAC servers could not be madeNo Steam logon
Where you see it
These are Valve Anti-Cheat messages from VAC-secured Steam games; players sometimes search them when Rust kicks them.
Why it happens
VAC is Valve's anti-cheat. Rust uses Easy Anti-Cheat, not VAC, so a Rust kick does not come from VAC; but servers can read your account's VAC history from Steam and refuse you because of it.
What to do, in order
In a VAC game, follow Steam's steps: restart, remove programs that modify game files, repair the Steam Service.OfficialSource 1
For 'Secure connection failed', check your firewall/router ports and close interfering background programs.OfficialSource 2
For Lone Wolf Rust: an account may have at most one VAC ban, and it must be 3+ years old.OfficialSource 3
Caveats
If you saw a message like this in Rust, re-read the exact text: Rust's anti-cheat messages begin with 'EAC' and belong to the EAC section. Rust does not use VAC (community statements agree; Facepunch's anti-cheat support section covers EAC only). Lone Wolf's FIREWALL rule on VAC bans is published on its FIREWALL page; the kick text it shows was not confirmed. Steam Support cannot remove a VAC ban; a ban is not a connection error.
Connecting to a serverOfficial and community sources
Also seen asReceiving Data
Where you see it
On the loading screen after connecting, where the progress stops at 'Receiving Data'.
Why it happens
Your client is waiting for the server to send the world and your player. Reports point to network trouble, a networking utility on the PC, or a server-side problem with the player's position or the map.
What to do, in order
Restart your router and test on a wired connection.OfficialSource 3
Exit download accelerators, traffic-shaping or VPN software, then restart Steam (reboot if the program needs it).OfficialSource 4
If only one server does it, tell its staff: an Oxide admin suggested the spawn area or map can be at fault, or the server may be on a different Rust branch.CommunitySource 2
Caveats
No official article covers this. The 2015 Steam thread confirms the symptom ('LOADING- RECIEVING 6576 / 12511' frozen) but has no fix in its first page. Claims that getting killed while stuck lets you respawn were seen only in search summaries and are not included.
Connecting to a serverOfficial and community sources
Also seen asSpawning World
Where you see it
On the loading screen near the end of joining, with the counter stalled or the game going 'Not Responding'.
Why it happens
The client is creating the server's objects in your game. Large or changed maps, damaged local map or config files, low memory, and graphics settings have all been reported as causes.
What to do, in order
Wait a few minutes before cancelling; on big servers this step can be slow, and cancelling can crash the game.CommunitySource 1
Turn off DLSS in Rust's video settings, join, then turn it back on once you are in.CommunitySource 2
Make sure Windows manages the pagefile automatically, then restart.OfficialSource 3
Close Rust and delete the downloaded maps in the Rust folder's 'maps' subfolder so the map downloads fresh.CommunitySource 2
Deleting the 'cfg' folder is also suggested, but it resets your settings and binds: back it up first. Downloaded maps re-download automatically, so deleting them is safe.
On the loading screen while joining, before 'Spawning World', or as a crash right after warmup finishes.
Why it happens
The client is loading and preparing the game's assets. Slow drives, low memory or a too-small pagefile, outdated GPU drivers and damaged files are the commonly reported causes.
What to do, in order
Let it finish: Facepunch's wiki warns that without an SSD you should expect longer than average load times.OfficialSource 5
Make sure Windows manages the pagefile automatically, then restart the PC.OfficialSource 2
If it never finishes, do a fresh install of Rust, ideally on an SSD.OfficialSource 4
Caveats
Facepunch's wiki install page (source 4) says an SSD is highly recommended at minimum spec and required at recommended spec. Cancelling and rejoining to 'skip' warmup is a widely shared tip, but the same guides warn it causes stutter and crashes; not recommended. Old advice to launch with DirectX 9 is obsolete.
Buying and Installing RustFacepunch Rust Wiki (wiki.facepunch.com, community-editable) · accessed 30 Oct 2026
Couldn't Download Level
Connecting to a serverOfficial sources
Also seen asDownload map file <URL> (console line)
Where you see it
On the disconnect screen when joining a server that uses a custom map.
Why it happens
The server uses a custom map that your client must download from a web address, and the download failed: the host is down, your VPN/antivirus/DNS blocked it, or the domain is blocked in your country.
Open F1, copy the URL from the 'Download map file' line, download it in a browser, and put the .map file in the Rust folder's 'maps' subfolder.OfficialSource 1
Check your antivirus's web/network protection is not blocking the download.OfficialSource 1
Allow Rust.exe and RustClient.exe in Windows Firewall.OfficialSource 1
If the download page itself fails, tell the server's staff: the map host is down.OfficialSource 1
Caveats
From Facepunch's wiki (community-editable). The wiki also suggests switching DNS to Cloudflare or Google; that is a reasonable step but changes system settings, so try the others first. In countries where a file host is blocked, the wiki suggests a VPN, which will conflict with servers that block VPNs (Lone Wolf included).
The Steam Servers are currently unavailable. Please try again later.
Connecting to a serverOfficial sources
Also seen asThe Steam Servers are too busyError Code 53
Where you see it
In the Steam client when trying to launch, update or join, before Rust connects to any server.
Why it happens
Steam itself cannot reach Valve's servers: maintenance, an outage, or a local program/network blocking Steam.
What to do, in order
Wait and retry; Steam may be under maintenance.OfficialSource 2
Change Steam's Download Region (Settings > Downloads).OfficialSource 1
Disable or exit programs Steam lists as interfering (VPNs, some firewalls, P2P clients, IP filters), then restart Steam.OfficialSource 3
Restart your router; test with a wired connection.OfficialSource 4
Caveats
Exact message text from Steam Support. While Steam is unreachable, Rust cannot authenticate with any server either, so expect Steam Auth Timeout/Failed until it recovers. Steam Support also says some university/business networks and proxies block Steam's ports.
Also seen asEAC Authentication TimeoutEAC Authentication timed outAuthenticationFailed
Where you see it
On the disconnect screen while joining an EAC-secured server, usually within seconds of connecting.
Why it happens
The server did not receive anti-cheat authentication from your client, so EAC could not authenticate your connection. The usual reasons are EAC not running (Rust not started through Steam), a damaged EAC install, or something blocking EAC's traffic.
What to do, in order
Close Rust completely and wait up to 10 minutes before relaunching, so EAC can refresh its cache.OfficialSource 1
Launch Rust only from your Steam library, not from a desktop shortcut or RustClient.exe.OfficialSource 1
Verify Rust's files: Steam library > right-click Rust > Properties > Installed Files ("Local Files" in Facepunch's article) > Verify integrity of game files.OfficialSource 2
Repair EAC: open ...\steamapps\common\Rust\EasyAntiCheat\, type EasyAntiCheat_EOS_Setup.exe repair in Explorer's address bar, press Enter and allow the admin prompt (only a console window flashes; there is no repair window any more).OfficialSource 1
Restart your PC and power-cycle your router/modem.OfficialSource 1
Install all pending Windows updates and restart.OfficialSource 1
Update your antivirus, and test once with it temporarily disabled; turn it back on straight after the test.OfficialSource 1
Delete RustClient.exe.eac from ...\steamapps\common\Rust\EasyAntiCheat\ if it exists.OfficialSource 1
Open output_log.txt in the Rust folder, look near the bottom for applications EAC lists as "forbidden", and close them in Task Manager.OfficialSource 3
Do a fresh install: delete the whole Rust folder, then install Rust again from Steam.OfficialSource 4
Caveats
Facepunch's article (updated 2026-07-30) no longer has a separate EAC connectivity-check step that older copies quoted on Steam. Epic's developer docs list launching the client without the anti-cheat bootstrapper as one of the most common causes. Turn antivirus back on after the test; if it was the cause, add an exclusion rather than leaving it off. Contact Facepunch support with output_log.txt attached if every step fails.
Also seen asDisconnected - EAC : Client Integrity ViolationClientViolationClientIntegrityViolated
Where you see it
On the disconnect screen when joining or shortly after joining a server.
Why it happens
Usually your local Easy Anti-Cheat files did not update correctly or have become corrupt. It is a check on your own machine and on its own puts no ban on the account.
What to do, in order
Open the Rust folder (Steam > right-click Rust > Properties > Installed Files (older Steam and Facepunch's articles: Local Files) > Browse) and delete the whole EasyAntiCheat folder.OfficialSource 1
Exit Steam completely, then right-click your Steam shortcut and choose Run as administrator.OfficialSource 1
Verify Rust's files from the Steam library so Steam downloads the EAC folder again.OfficialSource 1
If it persists, make sure Rust is fully updated in Steam (one player fixed it with a pending update).CommunitySource 3
Caveats
Epic's docs say a client violation is enforced on the player's own machine and creates no sanction against the account. Several players in the Steam thread fixed it with Verify alone.
Also seen asDisconnected: EAC: DisconnectedDisconnected: EAC
Where you see it
On the disconnect screen after connecting to, or while playing on, an EAC-secured server.
Why it happens
Your connection to Easy Anti-Cheat's back-end servers is not working, so the game server cannot confirm EAC is running and disconnects you. EAC is also not loaded if Rust was not started from Steam.
What to do, in order
Close Rust and start it from your Steam library, not from the game folder.OfficialSource 1
Allow HTTP/HTTPS (ports 80 and 443) to client.easyanticheat.net in your firewall and antivirus.OfficialSource 1
Then work through the EAC Authentication Timeout steps (wait 10 minutes, verify, repair EAC).OfficialSource 2
Caveats
Facepunch's article was last updated 2023-05-26; the host name and ports are as it gives them. If many players are kicked at once, the problem may be EAC's or the server's, not yours.
Sources
EAC: DisconnectedFacepunch Studios (Rust Support) · accessed 30 Oct 2026
Also seen ascould not resolve the address download.eac-cdn.com
Where you see it
In an Easy Anti-Cheat dialog at launch, before the main menu.
Why it happens
Your PC could not resolve download.eac-cdn.com, the address EAC downloads its module from.
What to do
Open Command Prompt and run ipconfig /flushdns, then restart Rust.OfficialSource 1
Caveats
The flush is the only fix Facepunch gives. Epic's docs separately say that when the EAC module cannot be downloaded because of a connection problem or firewall, the bootstrapper falls back to a 'null client' and you will then be kicked from secure servers (see the NullClient entry). Checking that no DNS filter or firewall blocks download.eac-cdn.com follows from this but is not a documented step.
Sources
Network DNS ErrorFacepunch Studios (Rust Support) · accessed 30 Oct 2026
Last resort only: import GlobalSign's "CodeSign" and "EV CodeSign" root certificates from GlobalSign's own site.OfficialSource 1
Caveats
Facepunch's article dates from 2022-08-11 and its GlobalSign link now redirects to GlobalSign's root-certificates page. Take certificates only from GlobalSign or Windows Update, never from a third-party download or 'fix' pack, since a planted root certificate lets an attacker sign malware.
Also seen asStart Service Failed (1053)Start Service Failed (1058)Start Service Failed (1450)ERROR_ACCESS_DENIEDERROR_SERVICE_REQUEST_TIMEOUTERROR_SERVICE_DISABLEDERROR_NO_SYSTEM_RESOURCES
Where you see it
In an Easy Anti-Cheat dialog at launch; the number in brackets is the Windows error code.
Why it happens
The EAC Windows service could not be started. For codes 5, 1053, 1058 and 1450 Facepunch's causes are an out-of-date Windows or antivirus wrongly treating the EAC-protected game as malicious.
What to do, in order
Note the number in brackets; for 31 or 1056 use those entries instead.OfficialSource 1
Install all Windows updates and restart.OfficialSource 1
Add the Rust folder and C:\Program Files (x86)\EasyAntiCheat_EOS\ as exclusions in your antivirus (do not uninstall it).OfficialSource 2
Repair the service from an Administrator Command Prompt: cd "C:\Program Files (x86)\EasyAntiCheat_EOS", then EasyAntiCheat_EOS.exe repair, then echo %ERRORLEVEL% (0 means it worked).OfficialSource 3
Caveats
Facepunch also links a Windows hotfix (KB2922790); that link now redirects to an unrelated servicing page and the hotfix is for long-unsupported Windows versions, so it is left out. Code 1058 means the service is disabled; do not set unrelated services to Automatic with registry edits from tutorials.
Windows cannot load any kernel-mode driver. Facepunch calls this system-level corruption, for example a rootkit or an old antivirus that did not uninstall cleanly.
If the error stays, back up your files and reinstall Windows, as Facepunch recommends.OfficialSource 1
Caveats
Facepunch says this is 'most often irreversible without re-installing Windows'. Facepunch only names the cause. If an old antivirus was removed, its vendor's official removal tool may clean up what is left; this is not documented.
Also seen asTest signing modeKernel Driver Test Signing mode is not supported
Where you see it
In an Easy Anti-Cheat dialog at launch.
Why it happens
Windows is in kernel driver test-signing mode, which EAC does not support. It is usually left on by an old unsigned driver (for example an old sound card) or by a tool that needed it.
What to do, in order
Open Command Prompt as Administrator, run bcdedit /set testsigning off, and restart.OfficialSource 2
Check that the 'Test Mode' watermark is gone from the bottom-right of the desktop.OfficialSource 2
Replace any unsigned driver with a signed one from the device maker's website, or contact the maker.OfficialSource 1
Caveats
Never turn test signing ON (or run bcdedit /set nointegritychecks on) as an 'EAC fix'; some guides do. Microsoft notes BCDEdit changes can make a PC unbootable and need a restart. If the command says the value is protected by Secure Boot policy, test signing is not your problem.
Plug in a mouse of another brand and start Rust again.OfficialSource 1
Caveats
There is no driver or firmware workaround; the brands are banned outright. Facepunch's article lists Razer, Logitech, Corsair, SteelSeries, Zowie, HyperX and Asus as working.
Also seen asSecure tagTPM and Secure Boot requiredadditional requirements
Where you see it
In the server browser on servers with the "Secure" tag; clicking one shows what it requires and whether your PC supports it.
Why it happens
From March 2026 servers can choose to require TPM 2.0 and Secure Boot through EAC. Phase one is select servers only; Facepunch says a global requirement will follow and will be announced in the monthly devblog.
What to do, in order
Press Win+R, run tpm.msc and check it says "The TPM is ready for use" (Specification Version 2.0).OfficialSource 1
Press Win+R, run msinfo32 and check "Secure Boot State" is On.OfficialSource 1
If TPM is off, enable it in the BIOS/UEFI: AMD fTPM ("Firmware TPM") or Intel PTT, then save and exit.OfficialSource 1
If Secure Boot is off, set Secure Boot to Enabled (mode Standard) in the BIOS/UEFI, then save and exit.OfficialSource 1
If Secure Boot is greyed out, the PC boots in Legacy/CSM mode; on Windows 10 the disk may need converting from MBR to GPT (Microsoft's MBR2GPT) before switching to UEFI. Read your motherboard's manual first.OfficialSource 1
In an Administrator PowerShell, run tpmtool getdeviceinformation and check TPM Present, Version 2.0, Is Initialized and Ready For Attestation; run get-tpm and if AutoProvisioning is false, run Enable-TpmAutoProvisioning and restart.OfficialSource 3
Update Windows and the BIOS if any value is still wrong.OfficialSource 3
Caveats
Status as of 2026-10-30: Facepunch's article (updated 2026-09-11) still describes phase one (select servers); no global date was found in the devblogs read. Shipshape says over 80% of players have TPM hardware but just under 60% have Secure Boot on. Hardware from before about 2016 may lack both. A BIOS change can stop the PC booting; Facepunch's fix is 'Load Optimised Defaults'/CMOS reset. Switching Legacy to UEFI without converting the disk is what makes Windows unbootable. Ignore older guides that tell you to DISABLE Secure Boot for EAC: secure servers now require it on. The heading is descriptive; the exact server-browser wording was not seen.
Boot validation failed: Measured bootlog not found
Easy Anti-CheatOfficial sources
Where you see it
As the kick reason when joining a server that requires TPM and Secure Boot.
Why it happens
Windows did not generate the measured boot log EAC needs to check your PC's state, or it was removed after boot.
What to do, in order
Check TPM and Secure Boot are both enabled (tpm.msc, msinfo32).OfficialSource 1
Run tpmtool getdeviceinformation in an Administrator PowerShell and check Ready For Attestation is true.OfficialSource 1
Caveats
EAC's article names only the cause and 'make sure both TPM and Secure Boot are properly enabled'. A full restart before retrying is reasonable but not documented. Tools that clean or delete Windows logs may remove the boot log.
As the kick reason when joining a server that requires TPM and Secure Boot.
Why it happens
The events in your boot log do not match what was measured into the TPM during boot; something removed or changed boot-log events, or extended the TPM without logging it.
What to do, in order
Check TPM and Secure Boot are both enabled (tpm.msc, msinfo32).OfficialSource 1
Install all Windows updates and update the BIOS/UEFI to the latest version from your motherboard maker.OfficialSource 1
If it persists, contact your TPM/motherboard manufacturer, as EAC suggests, or Facepunch support.OfficialSource 1
Caveats
EAC's article explains the meaning only; the steps are its general TPM troubleshooting. A full restart and removing boot-level tools (boot managers, boot tweakers) follow from the meaning but are not documented. A PCR mismatch can also be what tampering looks like, so do not use 'TPM spoofer' or 'boot log fixer' tools: that is anti-cheat circumvention.
Unable to verify Secure Boot. Event missing from measured bootlog
Easy Anti-CheatOfficial sources
Where you see it
As the kick reason when joining a server that requires Secure Boot.
Why it happens
The measured boot log has no event confirming Secure Boot is on. Your firmware should add it at boot, so this usually means old firmware or Secure Boot not actually on.
What to do, in order
Run msinfo32 and check "Secure Boot State" is On.OfficialSource 2
Update your BIOS/UEFI to the latest version for your motherboard.OfficialSource 1
In the BIOS, set Secure Boot to Enabled and, if asked, Secure Boot Mode to Standard, then save.OfficialSource 2
Also seen asDisconnected: EAC BannedKicked: EAC: BannedPermanentBannedTemporaryBannedEasy Anti-Cheat banBanned by EAC
Where you see it
On the disconnect screen whenever you try to join an EAC-secured server.
Why it happens
Your Steam account has been game-banned through Easy Anti-Cheat for a cheating-related violation. Bans can apply hours or days after the detection, even while you are offline.
What to do, in order
If you believe it is wrong, read EAC's account suspension policy and use EAC's ban appeal form (it asks for a Reference ID).OfficialSource 2
Facepunch Support cannot overturn, review or speed up EAC bans; a ticket there will not lift it.OfficialSource 1
Secure your Steam account (new password, Steam Guard), whatever the outcome.OfficialSource 1
Caveats
This is not a technical error, and no repair, reinstall or verify removes it. Facepunch support cannot overturn, review or speed up EAC bans. A stolen or shared account is not an exemption. A new account to get around the ban is ban evasion and gets banned too. Facepunch's separate 'Ban Second Chances' policy (bans older than 8 months, no hardware ban or repeat offence) allows buying Rust on a new account; it lifts nothing. Avoid 'unban' and 'HWID spoofer' services, which are scams and evasion. Using another account to play is ban evasion (Facepunch), and on Lone Wolf Rust it means a permanent, unappealable ban of all your accounts. The 'EAC Banned' string comes from the Facepunch article; an EAC disconnect is a different error (covered elsewhere).
Also seen asError: Unknown file versionUnknown game fileFatal Application Exit - Unknown Game File (mscorlib.dll)Game executable invalidUnknown file version
Where you see it
In an Easy Anti-Cheat dialog at launch, naming the file that failed.
Why it happens
EAC found a game file that was modified and does not match the expected version, usually changed by the player or other software, or left over from a broken update.
What to do, in order
Close Rust, then verify files: Steam → Library → right-click Rust → Properties → Installed Files (older Steam and Facepunch's articles: Local Files) → Verify integrity of game files.OfficialSource 1
Remove any mods, ReShade or injected files you added to the Rust folder, then verify again.OfficialSource 2
If it returns, do a fresh install: delete the Rust folder and reinstall from Steam.OfficialSource 3
If verify reports all files valid and it still happens, test the hardware (EAC suggests a Prime95 stress test), since failing RAM/CPU can corrupt files.OfficialSource 2
Caveats
Facepunch says Verify is the usual fix for 'Unknown file version'. In Steam the button is now under Properties > Installed Files. A plain Steam uninstall does not remove every Rust file, which is why Facepunch prefers a fresh install.
Also seen asLaunch Error: Easy Anti-Cheat is not installedEasyAntiCheat_EOS_Setup won't openLaunch Error: EasyAntiCheat_EOS_Setup
Where you see it
In a launch-error dialog when starting Rust from Steam.
Why it happens
The EAC Windows service is not installed, which the EAC driver needs to load. The install may have failed when Rust was installed, or something blocked it.
What to do, in order
Verify Rust's files in Steam, then try launching again.OfficialSource 2
Open ...\steamapps\common\Rust\EasyAntiCheat\Settings.json and copy the productid value.OfficialSource 1
Open Command Prompt as Administrator and cd into ...\steamapps\common\Rust\EasyAntiCheat\.OfficialSource 1
Run EasyAntiCheat_EOS_Setup.exe install <productid>, then echo %ERRORLEVEL%; 0 means it installed.OfficialSource 1
If the setup will not run at all, restart your PC and router, check your Windows account is allowed to install software, and try again.CommunitySource 3
Caveats
EAC's install command is generic; the Rust paths are from Facepunch's articles. The Settings.json location is EAC's statement for any game and was not checked against a Rust install. In the January 2024 Steam thread the poster confirmed a restart of PC and router fixed a setup that would not run. A different Steam thread suggests LockHunter-type tools to force-delete EasyAntiCheat_EOS.sys; prefer a reboot or EAC's own repair/uninstall commands.
Also seen asError 30005 - Create File Failed With 32Error Code: 30005 (CreateService failed with 1072)30005
Where you see it
In an Easy Anti-Cheat launch-error dialog; the game never starts.
Why it happens
The EAC service could not start the game, most often because another program had locked an EAC file on disk.
What to do, in order
Restart the PC; EAC calls this the simplest fix.OfficialSource 1
If it keeps happening, add EasyAntiCheat_EOS.exe (folder C:\Program Files (x86)\EasyAntiCheat_EOS\) to the exclusions in Windows Security or your antivirus.OfficialSource 1
Repair the EAC service from an Administrator Command Prompt: cd "C:\Program Files (x86)\EasyAntiCheat_EOS" then EasyAntiCheat_EOS.exe repair.OfficialSource 2
Repair from Rust's folder too (EasyAntiCheat_EOS_Setup.exe repair in ...\Rust\EasyAntiCheat\) and verify Rust's files.CommunitySource 3
Caveats
A 2022 Rust Steam post fixed it by force-deleting EasyAntiCheat_EOS.sys with LockHunter; that is risky and not recommended; restart instead. A 2024 Steam thread shows players disabling Memory Integrity and Hardware-enforced Stack Protection for 30005 with no confirmed result: don't. If it persists, Facepunch support may ask for EAC logs from %AppData%\EasyAntiCheat\.
Sources
Error 30005Easy Anti-Cheat (Epic Games) · accessed 30 Oct 2026
Disconnected: EAC: Anti-cheat client protection not active (NullClient)
Easy Anti-CheatOfficial and community sources
Also seen asNullClientAnti-cheat client protection not active
Where you see it
On the disconnect screen when joining any EAC-secured server.
Why it happens
The EAC bootstrapper could not load the anti-cheat module and started in fail-safe 'null client' mode. The usual reasons are that it could not download the module (connection or firewall) or that the game runs on a platform with no EAC module, such as Wine/Proton for Rust.
What to do, in order
Close Rust and start it from the Steam library.OfficialSource 2
Turn off any VPN, proxy or DPI-bypass tool (for example GoodbyeDPI) and relaunch.CommunitySource 3
Allow EAC through your firewall/antivirus (ports 80/443) and flush DNS with ipconfig /flushdns.OfficialSource 4
Delete the EasyAntiCheat folder inside the Rust folder and verify files so it downloads again.CommunitySource 3
Check the bootstrapper log %AppData%\EasyAntiCheat\anticheatlauncher.log for the reason and include it in a support ticket.OfficialSource 1
Caveats
The Steam thread (2024 to 2026) reports mixed fixes: joining through Steam > View > Game Servers, reinstalling the Epic Games launcher, and in 2026 removing GoodbyeDPI or a VPN. None is confirmed by Facepunch. On Linux/Steam Deck this is expected: Rust has no Proton EAC module (see the Linux entry).
Network DNS ErrorFacepunch Studios (Rust Support) · accessed 30 Oct 2026
Kicked: EAC: Heartbeat timed out
Easy Anti-CheatOfficial sources
Also seen asHeartbeatTimeoutEAC: Heartbeat lost
Where you see it
As the kick reason in the middle of a session, often after minutes or hours of normal play.
Why it happens
Anti-cheat data stopped flowing for a long time after you were authenticated. Epic gives server performance problems (messages arriving very slowly or not at all) as the most common cause; on the player's side packet loss can do it too.
What to do, in order
Rejoin; if only one community server does it, tell its admin (it is usually server-side).OfficialSource 1
If it happens on every server, check your own connection is working normally (no packet loss; try a wired connection).OfficialSource 3
Caveats
Epic's related 'TemporaryCooldown' reason (temporarily blocked from that server when anti-cheat messages are often lost) has the same advice. Ignore hosting-blog advice to add -eac_launcher or switch to Proton-GE; no source supports either for Rust.
Also seen asEasy Anti-Cheat: Game Security Violation DetectedGame Security Violation
Where you see it
In an Easy Anti-Cheat dialog at launch or during play; the game then closes.
Why it happens
A critical anti-cheat component was terminated, or the PC is set up in a way that bypasses Windows' default kernel security. A common cause is hardware-control software (for example RGB lighting tools) that ships drivers with known, cheat-abused vulnerabilities.
What to do, in order
Close RGB, fan-control and hardware-monitoring software before launching Rust.OfficialSource 1
Update that software to its latest version, or contact its vendor if no fixed version exists.OfficialSource 1
Restart the PC, then repair EAC (EasyAntiCheat_EOS_Setup.exe repair from the Rust EasyAntiCheat folder) and verify Rust's files.CommunitySource 3
If it persists, uninstall recently added software that also loads drivers (tuning, overlay or 'optimiser' tools) and test again.CommunitySource 4
Caveats
'Bypasses default Windows kernel security' covers test signing, disabled integrity checks and kernel debugging, so turning Windows security off to 'fix' EAC makes this worse.
Also seen asforbidden application (output_log.txt)EAC blocked softwareEOS_ACCVT_ForbiddenToolDetected
Where you see it
In output_log.txt or as a kick/launch reason when EAC finds blocked software running.
Why it happens
EAC blocks software that touches the game the way cheats do. Legitimate overlays, hardware monitors, macro/automation tools and modding tools can be caught as well.
What to do, in order
Open ...\steamapps\common\Rust\output_log.txt and find near the bottom the application EAC marked "forbidden".OfficialSource 1
Close that application in Task Manager before launching Rust.OfficialSource 1
Update it to the latest version (many tools have added EAC compatibility).OfficialSource 2
Use the tool's game mode or exclusion setting for the Rust process, or start the overlay after the game.OfficialSource 2
Caveats
EAC says the block applies only while the game runs and is not permanent. The exact on-screen text varies; 'Forbidden Tool' is how Epic's docs say a player may see it. Running macro or recoil tools is cheating and can end in a ban, not just a kick.
Memory integrity can't be turned on (incompatible driver)
Easy Anti-CheatOfficial sources
Also seen asCore IsolationMemory IntegrityHVCIMicrosoft Vulnerable Driver BlocklistA security setting is preventing a driver from loading
Where you see it
In Windows Security > Device security > Core isolation details, or a Program Compatibility Assistant banner, often noticed while troubleshooting EAC.
Why it happens
Core isolation's Memory integrity and the Vulnerable Driver Blocklist block drivers with known security holes, the same class of driver EAC treats as a cheat route. An old driver from RGB, tuning or monitoring software is the usual reason Memory integrity will not turn on.
What to do, in order
Open Windows Security > Device security > Core isolation details (or run windowsdefender://coreisolation/) and read which driver is listed as incompatible.OfficialSource 1
Update that driver through Windows Update, Device Manager or the device maker's website.OfficialSource 1
If no fixed driver exists, uninstall the software or device that installed it.OfficialSource 1
Turn Memory integrity on and restart.OfficialSource 1
Caveats
Myth: 'disable Core Isolation/Memory Integrity to fix EAC'. No EAC or Facepunch source read asks for it off, and Epic says machines that bypass Windows kernel security cause Game Security Violation. If a support agent has you turn it off for one test, turn it back on afterwards. The wording 'can't be turned on (incompatible driver)' paraphrases Microsoft's 'If memory integrity fails to turn on, it may tell you that you have an incompatible device driver already installed'.
Also seen asKernel-mode Hardware-enforced Stack ProtectionDriver load error in Windows 11This driver has been blocked from loading
Where you see it
At launch on Windows 11 PCs with Kernel-mode Hardware-enforced Stack Protection turned on.
Why it happens
Epic says this Windows 11 protection can stop some EAC games from launching or working; 1275 is Windows' 'driver blocked from loading' code.
What to do, in order
Repair the EAC service from an Administrator Command Prompt (EasyAntiCheat_EOS.exe repair in C:\Program Files (x86)\EasyAntiCheat_EOS\).OfficialSource 2
Open Core isolation details, update any driver it lists as incompatible, and install pending Windows updates.OfficialSource 3
Caveats
Do that only if Facepunch or Epic support directs it, as a test, and turn it back on in Core isolation afterwards. No Rust report of error 1275 was read.
Also seen asVirtual machine detectedVMHyper-VVMwareVirtualBoxProxmox
Where you see it
When launching Rust inside a VM, or joining a secured server from one.
Why it happens
EAC's client does not support virtual machines, so Rust run inside one cannot pass EAC.
What to do
Install and run Rust on Windows directly on the PC, not inside a VM.OfficialSource 1
Caveats
This covers running the game inside a guest OS. Windows features that use virtualisation on the host itself (Memory integrity/VBS) are a different thing; no source read says they must be off for EAC. Guides that hide a VM from EAC (CPU flags, BIOS strings) are anti-cheat circumvention: do not use them. The heading is descriptive; the exact in-game wording was not confirmed.
As NullClient, authentication-timeout or random EAC kicks when a VPN, proxy or DPI-bypass tool is running.
Why it happens
Players report that VPNs and DPI-bypass tools can stop EAC downloading its module or reaching its back-end; some servers also block VPN addresses.
What to do, in order
Turn off the VPN, proxy or DPI-bypass tool, fully close it, and relaunch Rust from Steam.CommunitySource 1
If you need the VPN, check it allows HTTPS to client.easyanticheat.net (ports 80/443).OfficialSource 2
Caveats
No Facepunch or EAC statement on VPNs was found. The supporting report is a single May 2026 reply in the NullClient Steam thread; hosting blogs repeat the advice without evidence. The heading is descriptive, not an on-screen message.
EAC: DisconnectedFacepunch Studios (Rust Support) · accessed 30 Oct 2026
EAC is not supported on Linux, Steam Deck or Proton
Easy Anti-CheatOfficial sources
Also seen asDisconnected: EAC: Anti-cheat client protection not active (NullClient)Steam DeckProtonLinuxSteamOSSteam MachineRust does not launch or cannot join servers on Linux / Steam DeckProton crash on Play gameDropped support on Linux / SteamOS
Where you see it
When joining official or most community servers from Linux, SteamOS, Steam Deck or Proton.
Why it happens
Rust has no EAC module for Proton/Linux. EAC can support Wine/Proton only when a developer turns on a Linux module, and Facepunch says it has no plans to.
What to do, in order
Play on a supported platform (64-bit Windows or macOS on Apple Silicon).OfficialSource 5
Play Rust on Windows; there is no supported way to join EAC-secured servers from Linux or Steam Deck.OfficialSource 2
Without EAC you can join only insecure community servers, which the server browser does not list (Facepunch's article shows joining one by IP from the F1 console).OfficialSource 3
Caveats
Facepunch's statement is quoted by PC Gamer (2025-11-20) from a Reddit comment; the Reddit comment itself was not read. Rust's native Linux client was dropped in 2019. Ignore guides that say Proton-GE plus disabling Secure Boot fixes EAC for Rust: no Linux module exists, and secure servers now require Secure Boot ON. Running with EAC off is not a way to play normal servers. The heading is descriptive; Epic's docs say Wine/Proton with no Linux module ends in NullClient, but the exact disconnect text on a Steam Deck was not confirmed from a Rust report. Platform support read from the store appdetails API 2026-10-30 (windows: true, mac: true, linux: false); the page still shows an old Linux spec block, which is stale.
In an Easy Anti-Cheat launch-error dialog; the game does not start.
Why it happens
Community sources describe a launch failure where the EAC service is broken or another program (often antivirus) stopped the game starting. A 2017 Rust case came from an EAC update clashing with Bitdefender and was fixed on EAC's side.
What to do, in order
Repair the EAC service (Administrator Command Prompt: cd "C:\Program Files (x86)\EasyAntiCheat_EOS", then EasyAntiCheat_EOS.exe repair).OfficialSource 2
Add the Rust folder to your antivirus exclusions and test again (suggested by EAC staff in the 2017 thread).CommunitySource 1
Caveats
No official definition of 10011 was found. In the 2017 thread an EAC staff member rolled back an update; it is old evidence. Third-party guides (for example theglobalgaming.com) were seen only in search results and not read. Error 20006 was only reported for another game (7 Days to Die) in the sources found, so it has no entry.
Also seen asEAC: Verify ID token CanceledEAC: Verify ID token ConnectInvalidToken
Where you see it
As the kick reason a few seconds after joining a particular community server, for every player.
Why it happens
A server-side failure of EAC's ID-token check, reported mostly by admins of servers on older or Windows Server hosts after a 2024–2025 token-system update.
What to do, in order
As a player: try another server, and tell that server's admin; it is not your PC.CommunitySource 1
As an admin: install missing root certificates on the server host (the threads name Amazon's SFSRootCAG2) and restart the server.CommunitySource 1
Caveats
No fix is confirmed in the threads. Admins report +server.anticheattoken 0 letting players in; it switches off part of EAC's checking and should not be left set.
Also seen asEAC: KickedDisconnected: EAC: <reason>Disconnected: EAC: ViolationDisconnected:EAC:Bad AuthenticationBackendViolationTemporaryCooldown
Where you see it
On the disconnect screen; the text after 'EAC:' is the reason.
Why it happens
EAC removed you from the session; Epic says most kick reasons affect only that session, and only TemporaryBanned/PermanentBanned put a sanction on the account. Match the reason to its own entry where one exists.
What to do, in order
Read the reason after 'EAC:' and use the matching entry (Authentication timed out, Client Integrity Violation, NullClient, Heartbeat timed out, Banned).OfficialSource 1
For a reason with no entry: restart Rust from Steam, verify files and repair EAC.OfficialSource 2
If it persists, contact Facepunch support with output_log.txt and the EAC logs from %AppData%\EasyAntiCheat\.OfficialSource 3
Caveats
'EAC: Violation' (2018) and 'EAC:Bad Authentication' (2017, Mac/Linux players) are old Steam reports kept as aliases. A Violation kick is not by itself a ban, despite replies saying so. Epic's TemporaryCooldown reason means a short block from one server when anti-cheat messages are often lost.
Also seen asUnknown file version keeps coming backfiles verify fine but EAC still fails
Where you see it
When EAC integrity errors keep coming back after Steam reports every file valid.
Why it happens
EAC says repeated file-mismatch errors with valid files can come from faulty hardware corrupting data in memory or on disk.
What to do, in order
Verify Rust's files once more and note whether any were re-downloaded.OfficialSource 2
Run a hardware stress test such as Prime95 and test RAM; fix or replace failing parts.OfficialSource 1
Caveats
'Integrity check failed' is a common way players describe this; the exact string was not found in a Facepunch or EAC source, so it is a descriptive heading. If the drive reports errors, a fresh install to another drive is reasonable but not documented.
Also seen asRust.exe missingRustClient.exe was deleted by antivirus
Where you see it
A Steam error when you press Play.
Why it happens
Antivirus or similar software removed the game's executable as a false positive.
What to do, in order
Check your antivirus quarantine or Windows Security Protection history for the Rust file and restore/allow it.OfficialSource 1
Add the problem file or Rust folder to your antivirus exceptions.OfficialSource 2
Verify Rust's files in Steam to re-download the missing file.OfficialSource 2
Caveats
From Facepunch's shared Steam article. Do not leave antivirus permanently disabled; Steam Support and Microsoft recommend exceptions/temporary testing, and Microsoft warns exclusions reduce protection, so exclude only the Rust/Steam library folder.
Also seen asStuck on Preparing to launchSteam shows Rust running, then it stops with nothing on screen
Where you see it
In Steam after pressing Play: Rust briefly shows as running and then closes, or never starts.
Why it happens
Per Steam Support, the game is usually crashing immediately on start; common causes are an outdated Windows/.NET install, old drivers, damaged files, interfering software, or a PC at or below the requirements.
An error occurred while updating Rust (disk write error)
Steam and updatesOfficial sources
Also seen asAn error occurred while installing Rust (disk write error)An error occurred while updating Rust (disk read error)
Where you see it
A Steam download/update error on Rust's library page or in Downloads.
Why it happens
Steam could not write the update to disk: the file is locked, antivirus is scanning or quarantining it, folder permissions are broken, or the drive has errors.
What to do, in order
Close Rust completely, then restart Steam (or the PC) and resume the update.OfficialSource 1
Clear Steam's download cache: Steam → Settings → Downloads → Clear Cache (you will need to log in again).OfficialSource 2
Add the Steam library folder as an exclusion in your antivirus' real-time scanning.OfficialSource 3
Check the drive: This PC → right-click drive → Properties → Tools → Error checking.OfficialSource 3
If one drive keeps failing, add a Steam library on another drive and move Rust there (Settings → Storage → +).OfficialSource 3
Caveats
Steam's article no longer has a page per error; the reason in brackets at the end of the message tells you which. Facepunch's article also suggests temporarily turning antivirus fully off to test; if you do, turn it back on right after and use an exclusion instead.
An error occurred while updating Rust (corrupt update files)
Steam and updatesOfficial sources
Also seen asRust keeps re-downloading and re-validatingCorrupt update files
Where you see it
A Steam update error, often after the update appears to finish, sometimes looping.
Why it happens
Downloaded update data failed Steam's checks, commonly because antivirus deleted or altered update files before Steam could apply them, or because of disk/RAM errors.
Exclude the library folder in your antivirus and retry.OfficialSource 1
If it persists, create a new Steam library folder on the drive (Settings → Storage → +) and install Rust there.OfficialSource 1
Caveats
Steam Support: library folders 'need to be writable by all users'. A 2020 Rust player reported Repair Folder alone did not fix it. Do not take ownership of or change permissions on Windows system folders.
An error occurred while updating Rust (content servers unreachable)
Steam and updatesOfficial sources
Also seen asContent servers unreachableContent server unreachable
Where you see it
A Steam update error.
Why it happens
Steam could not reach a content server in your download region, because the region's servers are busy or failing, or a VPN, proxy, firewall or antivirus is blocking the connection.
What to do, in order
In Steam, go to Settings > Downloads and change the Download Region to a different nearby region, then retry.OfficialSource 6
In Settings > Downloads, click Clear Download Cache, confirm, and log back in.OfficialSource 2
Turn off VPNs, proxies and download accelerators.OfficialSource 3
Restart your router and check your firewall allows Steam's required ports.OfficialSource 7
Allow Steam through your firewall/antivirus.OfficialSource 1
Test on a different network (for example a phone hotspot) to rule out your ISP.OfficialSource 1
Caveats
Steam's 'Update & Installation Issues' FAQ covers all bracketed reasons. Players' reports (2016–2018) mostly say changing region worked; one also needed a Steam reinstall. Reinstall Steam into the same folder; Steam warns that uninstalling Steam deletes installed game content. The message text is as Steam users report it (Steam forum); Steam Support has no article under this exact title, so the download-region step is taken from Steam's 'Servers Are Currently Unavailable or Too Busy' article. Clearing the download cache does not remove installed games. Avoid third-party 'Steam fixer' tools and hosts-file edits.
An error occurred while updating Rust (not enough disk space)
Steam and updatesOfficial sources
Also seen asNot enough disk spaceUpdate needs much more space than its download size
Where you see it
A Steam update or install error, even when there seems to be enough free space.
Why it happens
Rust needs about 45 GB, and Steam may need extra free space on the same drive while it stages an update (one 2025 player saw 108 GB requested for a 3 GB update).
What to do, in order
Free space on the drive Rust is installed on (Rust lists 45 GB available space).OfficialSource 1
Clear Steam's download cache and retry.OfficialSource 2
If the drive is too small, add a library on a larger drive (Settings → Storage → +) and move Rust there.OfficialSource 3
Caveats
Exact Steam wording not quoted by an official source; the bracketed form follows Steam's documented 'An error occurred while updating [game] (reason)' pattern. The 'staging space' explanation is community-reported; Steam Support does not document how much extra space an update needs.
Also seen asPreallocatingValidatingVerifying installation
Where you see it
Steam's Downloads page during a Rust update.
Why it happens
Before downloading, Steam reserves disk space and checks existing files; on a slow hard drive, a busy disk, or with antivirus scanning each file, these steps can take a long time.
What to do, in order
Let it run; do not run other heavy disk work (defragmenting, virus scans) at the same time.OfficialSource 1
Exclude the Steam library folder from antivirus real-time scanning.OfficialSource 2
If it never progresses, restart Steam and clear the download cache.OfficialSource 3
Move Rust to an SSD (Settings → Storage → move), which Rust's store page highly recommends.OfficialSource 4
Caveats
No Steam Support page explains 'Preallocating'; the explanation is a community understanding. Players report slow preallocation even on SSDs (2019) and blame download servers; changing download region is also suggested.
Also seen asAn error occurred while launching this game: No licensesno licensingThis item is currently unavailable in your region
Where you see it
When pressing Play (on Steam or a cloud service like GeForce NOW) or on the store page.
Why it happens
The signed-in Steam account does not currently own a usable Rust licence: wrong account, a borrowed/family-shared copy, a region mismatch, or a linked account that no longer has Rust.
What to do, in order
Make sure you are signed in to the Steam account that bought Rust and that Rust shows in your full library list.OfficialSource 1
If Rust was a gift, redeem it from your Steam Inventory.OfficialSource 1
If you played through Family Sharing, buy your own copy; Rust family sharing has been disabled since February 17, 2021.OfficialSource 2
On GeForce NOW, check the Steam account linked there still owns Rust.CommunitySource 3
Restart Steam and sign in again, then check Rust appears under your full library list.OfficialSource 1
Caveats
No Steam Support article for 'No licenses' was found. No evidence was found that Rust is regionally blocked anywhere in 2025–2026 (searched; only 2022 Russian price changes and a 2024 report of Steam itself being blocked in Vietnam). Third-party guides say a VPN can cause the region message; not verified. Account buying, region-changing tricks and key resellers risk losing the account; do not use them.
Also seen asFamily sharing not working for RustFamily sharing not workingSteam Families RustCan't play shared RustSteam family sharing disabledSteam: NoLicenseOrExpired
Where you see it
Trying to play a shared copy of Rust through Steam Family Sharing/Families.
Why it happens
Facepunch disabled Steam family sharing for Rust from February 17, 2021.
What to do
Buy your own copy of Rust on the Steam store; Facepunch says no exceptions are made.OfficialSource 1
Caveats
Article re-checked 2026-10-30 (updated 2026-10-04): still disabled 'for the foreseeable future'. 'Steam: NoLicenseOrExpired' is the Steam authentication response for an account without a licence and may be what a server reports, but no player report showing it for family sharing was found (Assumed).
Also seen asServer list not loadingServer list emptyOnly a few servers in the listPartial server listServer browser slow to fillServers show no pingServer shows 0 playersServer info missingServer browser emptyServer not in the list
Where you see it
Rust main menu server browser (Play Game).
Why it happens
Facepunch: the list is seeded by Steam, then filled only as each server answers the client's A2S queries, so it behaves differently per player. Low Steam ping rate, launching Staging Branch, a VPN, Steam betas, packet loss or a firewall can all shrink it.
What to do, in order
In Steam, open Settings > In-Game and set 'Server browser pings / minute' to at least 5000.OfficialSource 1
Launch regular Rust, not 'Rust Staging Branch' (Staging has fewer servers).OfficialSource 1
Turn off any VPN: the list is populated by your IP's geolocation.OfficialSource 1
Opt out of betas (Library > right-click Rust > Properties > Betas), then verify game files.OfficialSource 1
Verify Rust's files through Steam.OfficialSource 2
Update antivirus and test with your firewall temporarily disabled.OfficialSource 1
Connect directly: from the main menu press F1 and type connect IP:Port (find the address on BattleMetrics or Just-wiped).OfficialSource 1
Caveats
Re-verified against the article (updated 2026-09-20). Facepunch writes the console form as 'connect IP:Port'; 'client.connect' is the form Lone Wolf Rust publishes, and both are used. Turn the firewall back on after testing. Servers showing no ping or 0 players have simply not answered your A2S query yet: results differ per player, so check the live count on BattleMetrics before calling a server down. Facepunch's article writes the command as 'connect IP:Port'; 'client.connect IP:PORT' is the same command's full name, and the wiki also lists 'connecthidden IP:Port', which keeps the address out of the console (useful for streamers). General advice not taken from a cited source: also check the in-game browser's own tabs and filters, which can hide a server.
Useful Console CommandsFacepunch Rust Wiki (wiki.facepunch.com, community-editable) · accessed 30 Oct 2026
Server browser shows servers from the wrong region
Server browserOfficial sources
Also seen asRegion filter wrongOnly EU servers showingCan't see NA servers
Where you see it
Rust server browser, region filters/tags.
Why it happens
The list is populated by your IP address's geolocation, so a VPN shows servers for the VPN's location. Region filters use server-set tags (NA, SA, EU, WA, EA, OC, AF), and a server shows under a region only if its owner set that tag.
What to do, in order
Turn off your VPN and refresh the list.OfficialSource 1
Use the region filter, but search by server name too: a server only appears under a region if its owner tagged it.OfficialSource 2
Caveats
Region tag list from the Facepunch wiki's Server Browser Tags page. Lone Wolf Rust added the North America tag in September 2026 (v3.10.0 changelog).
Also seen asPremium tagCan't join Premium serverNot eligible for PremiumPremiumPremium server not visibleNot eligible for Premium servers
Where you see it
Rust server browser: Premium filter and 'Premium' tag.
Why it happens
Premium Servers are visible only to accounts whose Rust Steam inventory is valued at $15 or more (Permanent Store items and tradable Rust items; standalone DLC such as Instruments, Sunburn and Voice Props is not counted).
What to do, in order
Click any server's 'Premium' tag to open the eligibility panel.OfficialSource 1
After a new purchase or trade, wait up to 20 minutes for Premium status to update.OfficialSource 1
Use the refresh button next to your name to re-check (once every 60 seconds).OfficialSource 1
Use the server browser's Premium filter to find these servers.OfficialSource 1
Caveats
Lone Wolf Rust is not a Premium server and uses its Firewall instead (Firewall explainer post). The $15 threshold 'may change over time' per Facepunch. The exact message when a non-eligible player tries to join was not confirmed.
Sources
Premium ServersFacepunch Studios Support · accessed 30 Oct 2026
Server isn't in the Community tab (listed as Modded)
Server browserOfficial sources
Also seen asOfficial / Community / Modded tabsCan't find server in CommunityModded tab
Where you see it
Rust server browser tabs.
Why it happens
Facepunch requires servers running gameplay-changing or UI-changing plugins to list under Modded. Admin plugins, queue-skip plugins, coloured names, custom maps and vanilla convar changes may stay in Community.
What to do, in order
If you can't find a server in Community, check the Modded tab, or search by name across tabs.OfficialSource 1
Look for the Modded/Oxide/Carbon tags on a server row to see which kind it is.OfficialSource 2
Caveats
How the client decides which tab shows a server is not documented. The Facepunch rule is a listing guideline for server owners. Lone Wolf Rust's Solo server calls itself vanilla; its separate [WILDERNESS] project is modded (2026-05-03 blog post).
Also seen asFavorite servers disappearedServer not saved to historyCan't favourite server
Where you see it
Rust server browser Favourites/History tabs.
Why it happens
Community-reported: favourites and history can drop servers after an update or a Steam server-browser bug. No Facepunch article covers it.
What to do, in order
Connect once by IP from the F1 console, then star the server from the History tab.CommunitySource 1
Add it as a Steam favourite: Steam > View > Game Servers > Favorites > Add Server, enter IP:PORT, refresh.CommunitySource 2
If it still won't show, connect directly with the F1 console every time.OfficialSource 3
Caveats
Hosting-company guides; Host Havoc's claim that Facepunch 'confirmed' a Steam browser bug was not traced to a Facepunch source. Menu names in the Steam client vary by version.
Also seen asRust stutters / freezes for a secondHitching after playing for a while
Where you see it
During play, especially after a while on a busy server; often mistaken for a crash.
Why it happens
Windows' page file is set too small or turned off, so Windows runs short of memory under Rust's load; installing Windows and Rust on a hard drive instead of an SSD makes it worse.
What to do, in order
Set the page file to Automatically manage paging file size for all drives (Advanced System Settings → Performance → Settings → Advanced → Virtual memory → Change).OfficialSource 1
FPS drops when moving the mouse (high polling rate mice)
PerformanceOfficial sources
Also seen asRust stutters only when looking aroundFPS tank with 1000Hz+ mouse
Where you see it
During play, frame rate drops sharply when turning the camera.
Why it happens
Facepunch: the Unity 6 update changed how mouse input is processed, and 1000Hz+ polling rate mice cause significant CPU overhead and frame drops.
What to do
Lower your mouse polling rate below 1000 Hz in the mouse software (for example Logitech G HUB, SteelSeries GG).OfficialSource 1
Caveats
Facepunch PSA, June 4, 2026, said a proper fix was being investigated; no later fix was found in Rust news through 2026-10-22, so check current patch notes. Players independently found the same (Steam thread '[SOLVED] Stutters and FPS drops', and a reply to the 2026-07-19 gc.buffer report).
If it helps, tell Facepunch support; opt back out if you later have trouble launching.OfficialSource 1
Caveats
Article updated 2026-05-20; whether the branch is still listed was not checked in the Steam client. Remember to leave the branch before reporting other launch problems, since betas cause their own errors.
Also seen asMicrophone not detectedMic not working in RustVoice chat not workingOthers can't hear me
Where you see it
In game, proximity voice chat.
Why it happens
Rust uses Steam's voice input. A loose connection, the wrong Steam input device, several Windows recording devices enabled, out-of-date drivers, or Windows blocking desktop apps from the microphone can stop it.
What to do, in order
Check the headset/mic is plugged in properly; try another port (directly into the motherboard rather than the front of the case).OfficialSource 1
In Steam: Friends & Chat > settings cog > Voice. Check the input device and levels.OfficialSource 1
In Windows Control Panel > Hardware and Sound > Sound > Recording, enable only the one input device you want.OfficialSource 1
Update sound drivers in Device Manager (Sound, video and game controllers) and any headset software.OfficialSource 1
Windows 11: Settings > Privacy & security > Microphone, and turn on 'Let desktop apps access your microphone'.OfficialSource 2
Caveats
The Windows privacy step is Microsoft's, not Facepunch's. Steam Community users also suggest it (source 2), and setting the mic as the default communication device.
Mic not workingSteam Community (Rust General Discussions) · accessed 30 Oct 2026
Push-to-talk (V) does nothing
In gameOfficial and community sources
Also seen asPush to talk not workingVoice key not workingMic icon doesn't light up
Where you see it
In game when holding the voice key.
Why it happens
Community-reported: the voice key is unbound or rebound, another app (often Discord) uses the same key, or the mic itself is not set up (see 'Microphone not working').
What to do, in order
Work through the 'Microphone not working' steps first.OfficialSource 1
Check the voice bind in Rust's control options. Players report the default push-to-talk key is V.CommunitySource 2
Make sure Discord or other software is not using the same push-to-talk/mute key.CommunitySource 2
Rebind from the F1 console if needed (bind key action), then run writecfg so it is saved.OfficialSource 3
Caveats
The default key V is community-reported (Steam thread title 'Lag Spike When I press V (Push to Talk) button'); Facepunch's Keybinds wiki lists no defaults. The wiki does not give the voice action's console name, so do not publish a voice bind command.
KeybindsFacepunch Rust Wiki · accessed 30 Oct 2026
Freezing or hitching when using in-game voice
In gameOfficial and community sources
Also seen asLag spike when I press VGame stutters when talkingRust freezes when I press push-to-talk
Where you see it
In game, when pressing the voice key.
Why it happens
Facepunch: usually the wrong input device selected as the microphone; third-party sound software such as RTX Voice or Voicemeeter; or Steam Beta enabled.
What to do, in order
Confirm or change the microphone device (see 'Microphone not working').OfficialSource 1
Test without RTX Voice, Voicemeeter or similar sound software.OfficialSource 1
Opt out of Steam client betas in Steam settings.OfficialSource 1
Community fix: in Windows sound settings set 'your input device' to the real mic (one player had a leftover VR headset mic selected).CommunitySource 2
Caveats
Article last updated 2023-03-17; still listed in Facepunch's General section.
Also seen asPlayer's voice mutedChat messages missing from one playerUnmute playerChat words filteredCensored chat
Where you see it
In game text and voice chat.
Why it happens
You may have muted them. Muting a player in Rust mutes both their text AND voice. Steam's chat filtering settings also control what text reaches you.
What to do, in order
Type mutelist in the F1 console to see the players you muted, then unmute using the index it shows.OfficialSource 1
Muting can be set from a player's name in chat or their contact card; check there too.OfficialSource 2
Words filtered? Change Steam Settings > In-Game > Chat Filtering (or Steam store account preferences).OfficialSource 3
Caveats
Lone Wolf Rust also mutes players itself (callouts, slurs); a server mute is not undone with unmute. See the Lone Wolf mute entry. Lone Wolf Rust also censors slurs server-side, and its rules say trying to get round the censor can lead to a permanent mute or ban.
Facepunch lists in-game volume/Speaker Config, loose connections, the wrong Windows playback device, drivers, Windows spatial sound and the Windows Audio service.
What to do, in order
Check Rust's sound settings and try a different 'Speaker Config'.OfficialSource 1
Check connections and try another port.OfficialSource 1
Control Panel > Hardware and Sound > Sound > Playback: enable the right device, disable others.OfficialSource 1
Update sound drivers in Device Manager.OfficialSource 1
Turn off Windows spatial sound (taskbar speaker icon > Spatial sound > Off).OfficialSource 1
Restart the 'Windows Audio' service via services.msc.OfficialSource 1
Sources
No SoundFacepunch Studios Support · accessed 30 Oct 2026
Keybinds reset or not saving
In gameOfficial sources
Also seen asBinds lost after updateCustom binds gone
Where you see it
F1 console / controls.
Why it happens
Binds typed in the F1 console are saved to the config only when written out. Facepunch's wiki says keybinds are saved to keys.cfg in the Rust installation folder.
What to do, in order
After setting binds in the F1 console, run writecfg.OfficialSource 1
Bind syntax: bind key action (e.g. bind k kill). Unbind with bind x "" or bind x clear.OfficialSource 1
Keep a copy of keys.cfg from your Rust folder so you can restore it.OfficialSource 1
Caveats
A fresh install or a verify can replace config files. That is inferred, not stated by Facepunch, so back keys.cfg up first.
Sources
KeybindsFacepunch Rust Wiki · accessed 30 Oct 2026
fps shows frames per second; fps.limit sets the FPS cap.OfficialSource 1
ping shows your latency to the server.OfficialSource 1
combatlog shows recent damage you dealt and received.OfficialSource 1
find <text> lists matching commands and variables; console.copy copies the console to your clipboard (useful for tickets).OfficialSource 1
connect IP:Port connects directly to a server.OfficialSource 1
Caveats
graphics.* commands were not found in any Facepunch source and are deliberately left out. The wiki table marks 'kill' as admin-only, so it is left out too.
Also seen asBuilding blockedCan't build hereBUILDING PRIVILEGE
Where you see it
Bottom-right HUD when placing building parts.
Why it happens
You are inside another tool cupboard's building privilege area and are not authorised on it. The radius comes from the foundations of the building the cupboard is connected to. Unauthorised players can still place twig floors and wooden ladders (orange outline, red 'BUILDING BLOCKED'); other placements show a red outline and a private chat notification.
What to do, in order
Move outside the other base's privilege area: walk around and watch where the indicator appears and disappears.OfficialSource 1
In your own base, press E on your tool cupboard to authorise (placing a TC authorises you automatically).OfficialSource 1
Keep resources in your cupboard: without them your base decays.OfficialSource 1
Caveats
This is normal gameplay, not an error. On Lone Wolf Rust (solo only) authorising other players on your cupboard may break the Solo Only rules; see /rules#solo-only. Other building-blocked causes (e.g. near monuments) are not covered by this Facepunch page.
UI too large or too small / server panel can't be closed
In gameCommunity reports
Also seen asUI scaleHUD too bigPlugin UI off screen
Where you see it
Game options / any on-screen UI.
Why it happens
Community-reported: Rust has a client-side UI scale setting. Some modded-server plugin panels render off screen at the default scale.
What to do, in order
Lower the UI scale in Rust's options; players report a value below 0.8 makes oversized plugin panels closable.CommunitySource 2
Return it to the default afterwards if vanilla UI looks too small.CommunitySource 1
Caveats
No current Facepunch source found; the option's menu location and console name could not be confirmed, so no console command is given. Lone Wolf Rust's Solo server is vanilla, so this mostly applies elsewhere.
Also seen asGamepad supportSteam Deck RustLinux Rust
Where you see it
Steam store / Steam Deck.
Why it happens
Steam's store data for Rust (app 252490) lists no controller support and Windows and macOS only (no Linux). Steam Deck compatibility is 'Unsupported' with the reason 'Unsupported Anti-Cheat Configuration'.
What to do, in order
Play with keyboard and mouse on Windows or macOS.OfficialSource 1
Rust Console Edition is a separate game supported by Double Eleven, not Facepunch.OfficialSource 2
Caveats
Read 2026-10-30 from store.steampowered.com/api/appdetails?appids=252490 (controller_support absent; platforms windows:true, mac:true, linux:false) and the Deck compatibility report (#SteamDeckVerified_TestResult_UnsupportedAntiCheatConfiguration). Steam Input remapping to a gamepad is not official support, and on Lone Wolf Rust any macro or script use is bannable; do not recommend it.
Also seen asDrop not in Steam inventorySkin from stream missingInventory not showing drop
Where you see it
Steam inventory / in-game skins after a drops campaign.
Why it happens
Your Steam account was not linked to your Twitch/KICK account when you claimed it, the link is to the wrong account, or the item is still delivering. You also need Rust in your Steam library.
What to do, in order
Sign in at twitch.facepunch.com and press 'Check For Missing Drops'.OfficialSource 1
If the wrong account is linked, use 'unlink account' and relink with the right Twitch and Steam accounts.OfficialSource 1
Allow up to 1 hour after pressing Claim.OfficialSource 1
For KICK drops, link at kick.facepunch.com/connect and use 'Check For Missing Drops' after a few hours; if you signed up to KICK with Google, set a username first.OfficialSource 2
Caveats
Unclaimed drops expire after 180 days. If Twitch did not count the watch time for a drop that has ended, it cannot be recovered.
KICK DropsFacepunch Studios Support · accessed 30 Oct 2026
Missing in-game crossover items
In gameOfficial sources
Also seen asGmod Toolgun missingClatter Helmet missingChippy Arcade missingDLC skin not showing
Where you see it
Steam inventory / crafting skin picker.
Why it happens
Crossover items drop only after 40 minutes in the other game (Garry's Mod, Chippy or Clatter) and then 40 minutes in Rust. DLC skin-pack skins are applied when you craft the base item, not given as separate items.
What to do, in order
Own Rust and the other game, play it for at least 40 minutes, then relaunch Rust and play for at least 40 minutes.OfficialSource 1
For DLC packs: check your Steam inventory for the pack, then craft the base item and pick the skin in the crafting menu's skin picker (or apply at a repair bench).OfficialSource 2
Caveats
Refunding the other game confiscates the crossover item for good.
Also seen asSteam: PublisherIssuedBanGame BannedGame ban on record1 game ban on recordMultiple game bans on recordDeveloper banFacepunch game banBanned for playing with cheaters
Where you see it
On the disconnect screen when joining any secured server, often appearing suddenly mid-session.
Why it happens
Facepunch has placed a game ban on the Steam account. Facepunch says game bans for cheating or for playing with cheaters are permanent and final.
What to do, in order
Check your Steam profile for a 'game ban' notice to confirm it is a game ban, not a server ban.CommunitySource 1
Appeal to the game's developer, not Steam: the developer holds the data.OfficialSource 5
For Rust EAC bans, use EAC's appeal route (see 'EAC Banned').OfficialSource 6
Facepunch's manual bans for playing with cheaters or racism/homophobia are permanent and appeals are automatically rejected; community servers remain open to you where their rules allow.OfficialSource 2
Do not make a new account to get around it: Facepunch treats that as ban evasion. Read Facepunch's Ban Second Chances article for the only route back (bans older than 8 months, first offence, new copy).OfficialSource 3
Caveats
The exact text 'Publisher Banned' is as a player reported it (2021); the in-game wording may differ. EAC-issued bans show 'EAC Banned' and belong to the EAC section. Lone Wolf Rust's FIREWALL refuses any account with a game ban (0 game bans required), so a player with this ban cannot join Lone Wolf even if a community server lets them in. Staff cannot lift a Facepunch ban. Only permanent game bans appear on profiles; temporary ones don't. The profile line wording is observed on profiles (source 4), not quoted by Valve.
Also seen asKicked: BannedBanned: <reason>You are banned from this serverBanned from a community serverServer banBanned from this serverKicked: banned
Where you see it
On the disconnect screen when trying to join one particular server.
Why it happens
That server's staff (not Facepunch) have banned your Steam account. Servers can show a reason and the time left on the ban when you connect, but some setups show only a generic message.
What to do, in order
Confirm it is only that server: if other servers work, it is a server ban, not a game ban.OfficialSource 1
Read the reason and time remaining shown when you connect.OfficialSource 1
Rejoin once and read the F1 console for the reason or expiry the server sends.CommunitySource 2
Appeal through that server's own process (its Discord or website). Facepunch support cannot lift a community server ban.OfficialSource 3
For Lone Wolf Rust: one appeal per ban, by you, via the Ban Appeal button in #open-a-ticket on Discord.OfficialSource 4
Caveats
The exact wording varies by server and by ban plugin. Facepunch's centralized-banning documentation says a ban reason and remaining time are displayed to the player. Facepunch's 'Ban Second Chances' article confirms community server bans are handled by server owners. How to tell bans apart: 'EAC Banned' or a Steam profile game ban means Facepunch/EAC; a VAC line on your profile means Valve; anything that blocks only one server is that server's ban.
Valve applies VAC bans when an account (or one using a phone number tied to other accounts) connects to a VAC-secured server while running cheat software. Rust is listed on Steam as 'Valve Anti-Cheat enabled'.
What to do, in order
See which games it covers: Steam > Settings > Account > 'Click here for details' under VAC Status.OfficialSource 1
VAC bans cannot be appealed; one issued wrongly is removed automatically after investigation.OfficialSource 1
Caveats
The profile wording '1 VAC ban on record' / 'X day(s) since last ban' is observed on Steam profiles; Valve's FAQ does not quote it. Lone Wolf allows at most one VAC ban three or more years old; see the Firewall VAC entry. Myth: Steam Support or a server's staff can remove a VAC ban. Neither can.
Can I buy a new account after a Rust ban? (Ban Second Chances)
Bans and accountsOfficial sources
Also seen asSecond chanceRejoin after ban
Where you see it
Facepunch policy.
Why it happens
Facepunch lets players banned over 8 months ago, who have not reoffended or evaded, return by buying Rust on a new account. Not eligible: repeat cheaters, bans in the last 8 months, hardware bans and community server bans.
What to do
Check eligibility against Facepunch's Ban Second Chances article before buying; returning too soon is likely to be detected and banned again.OfficialSource 1
Caveats
Important for Lone Wolf Rust: Facepunch's second chance does not get you past Lone Wolf's Firewall or bans. A new account fails the 30-day and 24-hour checks at first, and Lone Wolf counts using another account to get around a game ban, VAC ban, staff ban or Firewall requirement as ban/Firewall evasion, a permanent unappealable ban of all associated accounts. Staff, not this guide, decide edge cases.
Also seen asLimited accountCan't add friendsYour account is limited
Where you see it
Steam community features.
Why it happens
Steam limits community features until an account has spent at least $5.00 USD in the Steam store (adding friends, Market, profile visible to non-friends, profile levels, and more).
What to do
Spend $5 USD or more in the Steam store (wallet funds, a game, a wallet card or a gift you buy; received gifts, retail keys and free games don't count).OfficialSource 1
Caveats
Valve lists 'Making your Steam profile visible to non-friends' as unavailable to limited accounts. Whether that affects Lone Wolf's 'Steam profile set up' check is Unknown; if you are turned away on that requirement with a limited account, open a ticket. 'Your account is restricted' wording was not found in Valve's FAQ for Rust and is not confirmed.
Also seen asRust is not available in your regionRegion locked keyThis item is currently unavailable in your region
Where you see it
Activating a Rust CD key or gift on Steam.
Why it happens
A regionally restricted key or gift registered outside its region. Products bought directly on the Steam store usually have no region restriction.
What to do, in order
Contact the seller for a refund; Steam Support cannot refund third-party keys or remove region restrictions.OfficialSource 1
If travelling, keep your store region set to the country you live in (Account Details).OfficialSource 1
Caveats
The exact 'Rust is not available in your region' wording was not found from Facepunch; Valve's documented key message is 'Game not available in your territory'. Myth: use a VPN to get round it. Valve says that breaks the Steam Terms of Service, and a VPN is also turned away by Lone Wolf's Firewall. Treat 'secret trick' unlock pages as spam.
Also seen asRust+ pairing failedPair with Server does nothingCan't pair Rust+
Where you see it
In game (Esc menu > Rust+ > Pair with Server) and the Rust+ phone app.
Why it happens
A Facepunch developer: notifications must be enabled and working to pair servers with your phone. Pairing is done while connected to the server in game.
What to do, in order
Enable push notifications for Rust+ on your phone and update the app.OfficialSource 1
Check the bell icon at the top right of the Rust+ app for the pairing request in your notification history.OfficialSource 2
While connected in game, open the Esc menu, choose Rust+, click 'Pair with Server', then tap Pair Server in the app.CommunitySource 3
Keep the app open while you pair.CommunitySource 2
Caveats
Sources 0 and 1 are replies by a Facepunch developer (tagged as a developer) on Steam Community, 2020–2021. Menu labels come from a 2023 community guide. Myth: you need admin rights to pair. Host guides say so, but they are written for server owners. Lone Wolf Rust's rules allow native Rust+; third-party bots built on Lone Wolf data are restricted by its Acceptable Use Policy (/rules).
Also seen asRust+ server not respondingRust+ is unavailableRust+ disabled on this server
Where you see it
Rust+ app; the in-game Rust+ menu.
Why it happens
The server's companion server is not reachable. Facepunch's wiki: without it, players see the server load for a while and then show offline even when paired; a failed startup test disables Rust+ on that server. This is server-side.
What to do, in order
Open the Rust+ menu in game while connected: it shows whether Rust+ is disabled on that server.OfficialSource 1
If it is disabled, tell the server's staff; players can't fix it. (Owners: the TCP companion port, default game or RCon port + 67, must be reachable and 10000 or higher.)OfficialSource 1
If one server works and another doesn't, the problem is that server, not your phone.OfficialSource 1
Caveats
The exact strings 'Server not responding' / 'Rust+ is unavailable' were not found in a Facepunch source; they are kept as aliases only. Server log text Facepunch quotes: 'Rust+ companion server connectivity test failed! Disabling Rust+ features.' Deleting a server's companion.id can force players to re-pair.
Also seen asSmart Alarm notification not receivedRaid alarm not workingNo push notifications
Where you see it
Phone.
Why it happens
Smart Alarms and team alerts use push notifications, so phone notification or background settings can block them, and a server whose companion server is down can't send them.
What to do, in order
Allow notifications for Rust+ (including background), and check the bell icon's history.OfficialSource 1
Check your phone's background/battery settings for Rust+: blocked background notifications can stop alerts.CommunitySource 2
Check the server still works in the app (see 'Paired server ... shows offline').OfficialSource 3
Caveats
Facepunch's Rust+ page: 'Smart Alarms send customizable push notification alerts when an electrical signal is detected.' Team 'teammate joins' alerts are of little use on Lone Wolf Rust, which is solo only.
The device can only pair after the server itself is paired, and the device needs power and an input to be useful.
What to do, in order
Pair the server first (see the pairing entry).CommunitySource 1
While connected, press E on the smart device and choose 'Pair', then accept it in the app.CommunitySource 1
Wire the device with power and a trigger so it has something to report.CommunitySource 2
Caveats
Community guides disagree on press vs hold E. No current Facepunch step-by-step was found. A '3 devices per server' limit appears in one forum post and is unconfirmed.
Our own server's rules and requirements. Here, Official means Lone Wolf Rust's own pages.
Turned away by the Lone Wolf Firewall: game ban on the Steam account
Lone Wolf RustOfficial sources
Also seen asKicked for game banFirewall: game ban
Where you see it
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Requirement: no game bans on your Steam account. 'A game ban means a game's developer caught the account cheating.'
What to do, in order
Check your account: your Steam profile shows any game or VAC bans and how long ago they were, and your BattleMetrics player page shows your Rust hours.OfficialSource 1
There is no fix: staff can't make exceptions for Steam game bans, and a ban from a Steam game ban is never reduced on appeal.OfficialSource 1
Caveats
Any game ban counts, not only Rust's (the site says 'No game bans'). Using another account is ban evasion.
Turned away by the Lone Wolf Firewall: VAC ban too recent or more than one
Lone Wolf RustOfficial sources
Also seen asKicked for VAC banFirewall: VAC ban
Where you see it
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Requirement: at most one VAC ban, three or more years old. 'One old ban is allowed; recent or repeated bans are not.'
What to do, in order
Check your account: your Steam profile shows any game or VAC bans and how long ago they were, and your BattleMetrics player page shows your Rust hours.OfficialSource 1
If you have one VAC ban, you can join once it is three or more years old; time resolves it. Two or more VAC bans never qualify.OfficialSource 2
Still think it's wrong? Register your account, then open a ticket in our Discord and include your Steam profile link.OfficialSource 1
Caveats
Steam profiles show days since the last ban. Staff can't make exceptions for VAC bans.
Turned away by the Lone Wolf Firewall: Steam profile not set up
Lone Wolf RustOfficial sources
Also seen asSteam profile not set upThis user has not yet set up their Steam Community profile.
Where you see it
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Requirement: Steam profile set up. 'A set-up profile is a basic sign of a real, lived-in account.'
What to do, in order
Set up your Steam profile, then connect again.OfficialSource 1
On Steam, an unset-up profile shows 'This user has not yet set up their Steam Community profile.'; open your profile and use Edit Profile to set it up.CommunitySource 3
Still think it's wrong? Register your account, then open a ticket in our Discord and include your Steam profile link.OfficialSource 1
Caveats
Which Steam field the Firewall reads is not documented (Unknown). Whether the profile must be public is not stated on the site, so don't tell players to make it public as the fix. The Steam string is observed on profiles, not from Valve's FAQ. Limited Steam accounts can't make their profile visible to non-friends.
Turned away: account not created by you (bought, botted or stolen)
Lone Wolf RustOfficial sources
Also seen asPurchased accountBot-farm account
Where you see it
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Requirement: an account you created yourself. 'Accounts bought from bot farms, resellers or stolen-account markets are not allowed.'
What to do
Play on an account you created yourself. If you think you were flagged wrongly, register your account and open a Discord ticket with your Steam profile link.OfficialSource 1
Caveats
The knowledge repository records that this criterion has no machine check at connection and is enforced through the evasion and account-integrity rules, so this may arrive as a ban rather than a Firewall kick.
Turned away by the Lone Wolf Firewall: under 24 hours of Rust
Lone Wolf RustOfficial sources
Also seen asNot enough Rust hoursFirewall: playtime
Where you see it
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Requirement: at least 24 hours of Rust in the last five years, counted on BattleMetrics-connected servers. 'It shows the account really plays Rust.'
What to do, in order
Check your Rust hours on your BattleMetrics player page.OfficialSource 1
Play Rust on other BattleMetrics-connected servers until you reach 24 hours, then connect again.OfficialSource 2
Still think it's wrong? Register your account, then open a ticket in our Discord and include your Steam profile link.OfficialSource 1
Caveats
Steam's own Rust playtime is not what counts; BattleMetrics hours are. These 24 hours are not Lone Wolf's playtime roles, which count Lone Wolf time only (knowledge repo). Myth: boosting or idling hours. The Firewall announcement named 'boosted Rust gameplay hours' as a rule under test (status Proposed per the knowledge repo).
Turned away by the Lone Wolf Firewall: VPN detected
Lone Wolf RustOfficial sources
Also seen asVPN not allowedFirewall: VPNCan I use GeForce NOW?
Where you see it
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Requirement: no VPN. 'GeForce NOW and ShadowPlay are allowed.'
What to do, in order
Turn off your VPN, then connect again.OfficialSource 1
If you genuinely need a VPN, open a VPN exception ticket in our Discord. Exceptions aren't given for ping, because a VPN doesn't improve it.OfficialSource 2
Caveats
VPN is the only requirement with a documented exception route (knowledge repo firewall.md; ticket questions in ticket-intake-questions.md).
Turned away by the Lone Wolf Firewall (kicked as you join)
Lone Wolf RustOfficial sources
Also seen asWhy can't I join?Kicked on joinFirewall kick
Where you see it
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
'Every account is checked automatically when it joins, and an account that doesn't meet all eight requirements below is turned away.' The check is automatic and nobody reviews it by hand.
What to do, in order
Check your account: your Steam profile shows any game or VAC bans and how long ago they were, and your BattleMetrics player page shows your Rust hours.OfficialSource 1
Fix what you can: turn off your VPN, launch Rust rather than Rust – Staging Branch, and set up your Steam profile. Then connect again.OfficialSource 1
Still think it's wrong? Register your account, then open a ticket in our Discord and include your Steam profile link.OfficialSource 1
Caveats
Using another account to get around the Firewall or any ban is ban evasion and is bannable in its own right. Requirements last changed Jan 12, 2026 per /firewall. The Firewall fails open during a BattleMetrics outage (knowledge repo): an account let in during an outage was not 'approved'.
Moonlighter (earned free at 300 h played in one wipe) also skips the queue for the rest of that wipe and the first two weeks of the next; check progress with /moonlighter in game.OfficialSource 3
Caveats
Rust's own queue wording isn't quoted here. The Moonlighter threshold changed from 250 h (January 2026) to 300 h (February 2026 changelog), and /new shows 300 h.
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Callouts in global chat warn the player they're being watched, so the evidence disappears; the first time earns a temporary mute.
What to do
Wait out the mute, and report with F7 plus a Discord ticket next time.OfficialSource 1
Caveats
A callout doesn't count as an earlier offence for ban-appeal purposes (FAQ). Slurs are censored and also muted (rules). The local 'unmute' console command does not lift a server mute.
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Bans need a written rule, real evidence and reasonable timing. You may appeal once per ban, yourself.
What to do, in order
Register your account (link Steam and Discord) at players.lonewolfrust.gg.OfficialSource 1
Join discord.gg/lonewolf and allow DMs from server members.OfficialSource 1
In #open-a-ticket click 'Ban Appeal' and answer every question from the 'Lone Wolf Support' bot; the outcome comes by DM.OfficialSource 1
Caveats
Decisions are final. Never reduced on appeal: cheating (except autoclicker bans), ban evasion, and bans that come from a Steam game ban or VAC ban. A Lone Wolf ban is a community server ban; Facepunch and EAC can't lift it, and Lone Wolf can't lift theirs.
Also seen asLone Wolf Rust not in listHow do I join?
Where you see it
When connecting to Lone Wolf Rust (solo.lonewolfrust.gg:28010).
Why it happens
Server browser problems (see 'No servers showing'), or searching for a name that doesn't match the listing.
What to do, in order
Connect directly: in Rust, press F1, paste client.connect solo.lonewolfrust.gg:28010 and press Enter. Or use Open in Steam on the home page.OfficialSource 1
Search the browser for 'Lone Wolf Rust'. The listed name is 'Lone Wolf Rust | Solo Only, Monthly, Vanilla, No BP Wipes', and it carries the North America tag.OfficialSource 2
Caveats
Wipe posts tell players to search 'Lone Wolf Rust - Solo' (hyphen), but the listed name uses ' | ' (site/data/site.ts SERVER.name). Whether Rust's browser search matches across that difference was not tested. Recommend 'Lone Wolf Rust'.
