Update the vanilla Rust server first, then reinstall or refresh the framework that matches that exact Rust build. Stop the server cleanly, back up its identity, saves, configuration and plugin data, run SteamCMD against the existing installation, and only then apply Oxide or Carbon. Treating the SteamCMD update and framework update as separate stages prevents a common failure: SteamCMD replacing modded files and leaving the server running vanilla.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Rust servers with free DDoS protection and up to three free backups a day.
What a Rust update changes
A Rust dedicated-server update replaces files in the installation directory. The Rust server itself is distributed through SteamCMD under app ID 258550. Oxide and Carbon add a second compatibility layer, so a successful SteamCMD update does not prove that the framework or its plugins still works.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key... | $25.00 | Buy on Amazon |
| 2 |
|
Rust Video Game Notebook | $15.00 | Buy on Amazon |
| 3 |
|
Rust Game Props Large Furnace (S) | $14.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Facepunch’s Rust Wiki says an Oxide update follows every Rust server update. Oxide’s owner documentation gives the same warning in stronger terms: “For every server update by Facepunch, there is an Oxide update. Don’t mismatch version of Oxide and version of servers.” Carbon uses a different installation model, but it still must be compatible with the new Rust build.
A wipe is separate from a binary update. Updating the server files should not intentionally delete your world save, identity, configuration or plugin data. A scheduled wipe can reset map or player data according to your server’s settings, but that is an administrative choice rather than a required part of SteamCMD maintenance.
#1 Best Overall
- Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
- High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
- Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
- Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
- NOT a sticker*
Back up the server before touching files
Stop the running RustDedicated process normally before copying or replacing anything. A clean shutdown reduces the chance of a partially written save or configuration file. Store the backup outside the live server directory and label it with the date and the Rust build you are leaving.
- Server identity: preserve the identity files that determine the server’s persistent identity and ownership of its save.
- Configuration: copy startup parameters, server configuration files, RCON settings and any environment or batch/shell scripts used to launch the process.
- World save: back up the current save directory, including any procedural-map or custom-map files your installation uses.
- Oxide or Carbon configuration: save framework configuration, permissions, groups and hooks settings.
- Plugin configuration and data: copy both plugin configuration directories and plugin data directories. Configuration alone may not preserve player balances, kits, permissions or other state.
- Operational records: keep recent console and server logs so you can compare startup failures after the update.
Do not overwrite the backup while testing. If a plugin migration damages its data, you need a known-good copy to restore rather than a second copy of the already-modified files.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The safe update sequence
- Announce maintenance and stop RustDedicated. Use the server’s normal shutdown command or service control, wait for the process to exit, and confirm that no RustDedicated process still has files open.
- Make the backup described above. Verify that the archive can be opened and that it contains the identity, save, configuration and plugin data you expect.
- Update the vanilla files with SteamCMD. Run SteamCMD against the existing installation directory, not a new empty directory. The documented pattern is:
steamcmd +force_install_dir <server-path> +login anonymous +app_update 258550 -beta public validate +quit
The<server-path>value is your real Rust Dedicated Server path. Thevalidateoption checks and restores files that do not match the current public build. - Read SteamCMD’s result. Do not continue merely because the command returned to a prompt. Confirm that the app update completed without an error and that the install path is the one used by your launcher.
- Start once in vanilla or maintenance mode when useful. A temporary vanilla start lets the update finish any first-run work and gives you a clean RustDedicated log. Do not assume the framework survived file replacement; stop again before installing or refreshing it.
- Apply the matching framework release. Follow the Oxide or Carbon procedure below for the Rust build you just installed.
- Start the server and verify before reopening it to players. Check framework messages, load one representative plugin, test RCON and confirm the intended identity, save, ports and configuration.
Keep SteamCMD separate from the launcher whenever possible. Facepunch warns that putting SteamCMD in a startup script can revert a modded installation to vanilla on every launch. If automatic updating is unavoidable, the script must deliberately reapply the compatible framework after SteamCMD finishes and before the server accepts players.
Updating an Oxide server
Install the release that matches Rust
After SteamCMD has completed, obtain the current Oxide release intended for that Rust server build. Oxide’s owner guide requires the server to be shut down before installation. Extract the release into the server’s RustDedicated_Data directory and allow the extraction to overwrite existing files. Overwriting is part of the documented upgrade process; it is not a reason to delete your plugin configuration or data directories.
Never combine an older Oxide build with a newer Rust server simply because the server starts. Hooks can change between Rust releases, and a mismatched framework may produce silent plugin failures, startup exceptions or incorrect game behavior. If no compatible Oxide release is available yet, leave the server in vanilla or maintenance mode rather than inviting players into an unsupported combination.
Restart and confirm Oxide loaded
Start RustDedicated using the same identity, save, ports and configuration as before. Read the console and log for framework load messages. At the server console, run:
Free tools Windows power users keep installed
One-click scans. No signup required.
oxide.version
A version response confirms that the command interface is present. It does not guarantee that every plugin is compatible, so continue with a representative plugin test and inspect errors before public access.
Preserve plugin state
Keep the existing plugin files unless a plugin author specifically requires a migration. Restore the backed-up configuration and data only if the update process changed or removed them. Test plugins individually when practical; one outdated plugin can make the framework look broken even when Oxide itself loaded correctly.
Updating a Carbon server
Restore vanilla Facepunch DLLs first
Carbon patches Facepunch DLLs dynamically. Its official documentation therefore requires vanilla Facepunch DLLs as the starting point. If Carbon fails after a Rust update, run the SteamCMD update command with validate against the live server directory to restore the original files, then stop the server before installing Carbon again.
Rank #2
Do not copy DLLs from an unrelated backup or another Rust build. The validation step is the documented way to bring the installation back to the current public vanilla state.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsInstall Carbon at the server root
Download the Carbon archive compatible with the Rust build you installed, then unzip it into the root of the Rust Dedicated Server installation. The root is the directory that contains the Rust server executable and its main data directory, not the RustDedicated_Data subdirectory used by the Oxide extraction process.
Carbon documents a self-updating feature and remote hook updates. Those facilities can reduce manual framework work, but they do not remove the need to check compatibility after a Facepunch release. A self-update that has not yet caught up to the new Rust build is not a substitute for a supported Carbon release.
Check the Carbon startup log
Start the server and inspect Carbon’s log and the RustDedicated console for patching or hook errors. If Carbon cannot initialize, stop the process, restore vanilla DLLs with SteamCMD validation, install the compatible Carbon build again and review the Carbon log before trying another launch. Keep the save and plugin data backup untouched while diagnosing the framework.
Windows and Linux command details
Windows
Windows installations commonly call steamcmd.exe from a batch file. The arguments are unchanged: select the existing install directory with +force_install_dir, log in anonymously, update app 258550 on the public branch, optionally validate, and quit. Quote the path when it contains spaces, and make sure the batch file points to the same directory that your RustDedicated launcher uses.
Recommended Free Tools
Linux
Linux installations commonly call steamcmd.sh. Use the same app ID and public branch arguments. Run the command as the account that owns the server files, or ensure the account running SteamCMD and the account running RustDedicated have compatible permissions. A successful download into a different user’s home directory will not update the server that your service actually launches.
Startup-script design
A launcher should primarily start RustDedicated. If it also performs updates, make the order explicit: stop any existing process, run SteamCMD, apply or verify the framework, and only then launch RustDedicated. Running SteamCMD on every restart without a framework step can repeatedly replace modded files with vanilla files, creating an apparently random loss of Oxide or Carbon.
Verification before players return
- SteamCMD: confirm the app update and any validation completed without errors.
- RustDedicated: read the fresh log from the current startup, not an older rotated log.
- Framework: confirm Oxide’s version with
oxide.version, or confirm Carbon’s patch and hook messages in its log. - Plugin sample: load one ordinary gameplay plugin and one plugin that stores persistent data, then inspect warnings and exceptions.
- Connectivity: verify the game port, query port and RCON endpoint are the intended values.
- Persistence: confirm the expected server identity, world save, player data and configuration are present.
- Access control: test an administrator login and a normal player path without exposing maintenance credentials.
- Performance symptoms: watch the console for repeated hook errors, exceptions or restart loops for several minutes before declaring the update complete.
If these checks pass, reopen the server. If one fails, keep it closed and use the troubleshooting branch that matches the symptom instead of repeatedly restarting an unknown file state.
Troubleshooting common update failures
The server starts vanilla and plugins are missing
This usually means SteamCMD replaced framework files and the framework was not reapplied. Stop RustDedicated, confirm that SteamCMD targeted the correct directory, install the matching Oxide release into RustDedicated_Data or the matching Carbon archive at the server root, and start again. Do not restore an old framework build merely because it worked before the Rust update.
Rank #3
- Acrylic Painting Pla Plastic
Oxide loads but reports plugin errors
First confirm the Oxide version and the Rust build. Then identify whether one plugin or the framework itself is failing. Disable the offending plugin temporarily, read its error and dependency messages, and check for an updated plugin release. Restore plugin configuration or data from the pre-update backup only when you know which file changed; replacing all data can hide the original cause.
Carbon fails to patch or crashes during startup
Carbon expects vanilla Facepunch DLLs. Stop the server and run the documented SteamCMD command with validate to restore them, then reinstall the Carbon build that supports the current Rust version. Inspect the Carbon log after each attempt. Do not layer Carbon over DLLs left by another framework or by an incomplete previous update.
The world or identity appears to have reset
Stop immediately and compare the active paths and startup parameters with the backup. An update into the wrong directory, a changed server identity, or a new save path can make an intact world appear lost. Restore the intended identity and save only after confirming that the process is stopped; never copy a live save over files that RustDedicated is writing.
SteamCMD succeeds but the launcher still runs the old build
Check the executable path in the launcher, service definition or batch file. SteamCMD may have updated one directory while the launcher starts another. The install path in +force_install_dir and the path used by RustDedicated must be identical.
Automatic updates keep removing the framework
Remove the SteamCMD call from the normal restart path, or add a deliberate post-update framework installation step. Facepunch and Oxide both warn about this vanilla-file replacement pattern. Schedule updates during maintenance windows so you can verify compatibility before the server becomes reachable.
Oxide or Carbon: which maintenance path fits?
| Decision point | Oxide | Carbon |
|---|---|---|
| How it is installed | Extract the compatible release into RustDedicated_Data while the server is stopped, overwriting existing framework files. |
Unzip the compatible archive into the root of the Rust Dedicated Server. |
| Relationship to Rust files | Uses an explicit file-replacement workflow; SteamCMD can remove it if run afterward. | Patches Facepunch DLLs dynamically and therefore requires vanilla Facepunch DLLs first. |
| Update timing | Requires a matching Oxide release after each Facepunch server update. | Provides self-updating and remote hook-update features, but compatibility still must be checked after each Rust release. |
| Primary verification | Framework startup messages and the oxide.version command, followed by plugin testing. |
Carbon patch and hook messages in the console and Carbon log, followed by plugin testing. |
| Recovery when files are wrong | Update or validate vanilla files, then reinstall the matching Oxide release. | Use SteamCMD validation to restore vanilla DLLs, then reinstall the compatible Carbon build. |
| Best fit for an administrator | A predictable, manual sequence with clearly documented extraction and version checks. | A workflow that values dynamic patching and built-in update mechanisms while retaining a vanilla-DLL recovery step. |
Neither framework eliminates the need for backups, a controlled maintenance window or plugin testing. Choose based on the framework your plugins support and the update workflow your administrators can reliably execute, not on the assumption that one will remain compatible longer than the other.
Handling a wipe or a normal update
For a normal Rust update, keep the identity, save, configuration and plugin data in place and follow the sequence above. For a planned wipe, decide separately which world or player data should be reset, document that decision, and retain an archive of the pre-wipe save in case you need to investigate a problem. Do not use a wipe as a workaround for a framework mismatch; replacing the map will not repair incompatible Oxide or Carbon files.
After either event, verify that the server starts with the intended seed or map settings, ports, RCON configuration and framework. A wipe changes gameplay data; it should not silently change who owns the server identity or where your backups are stored.
When a managed host is the practical alternative
Administrators who do not want to maintain SteamCMD, framework archives, backups and restart scripts can use a managed Rust host. Hosting-service installation of Oxide may be automated, according to Oxide’s setup guidance, but automation does not remove the need to confirm the host’s supported framework version, backup policy, restore process and maintenance notifications. Ask specifically whether the provider preserves plugin configuration and data and whether you can obtain the raw save and identity files before a Rust update.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
