Coffee Stain ships Satisfactory updates regularly, and every time the game patches your dedicated server falls out of sync until you update it too. An outdated server throws a version mismatch and players simply cannot join. The good news: updating a Satisfactory dedicated server is a two-minute job once you know the SteamCMD command, and panel-based hosts make it a single click. This guide walks through updating on Linux and Windows, switching between the Early Access (stable) and Experimental branches, and restarting cleanly afterward.
How updating actually works
The Satisfactory Dedicated Server is its own Steam application with app ID 1690800 — separate from the playable game you own. You download and update it through SteamCMD using an anonymous login, so no Steam account or credentials are required. The same command you used to install the server is the command you use to update it: SteamCMD compares your local files against the chosen branch and re-downloads anything that has changed. Whenever the game releases a patch, you re-run that command and the server pulls the new build.
One rule matters above all else: the server and every connecting client must be on the same branch and version. If your client updates to a new patch but the server hasn’t, you get the dreaded version mismatch and connections fail. If you’re chasing down a join failure, our server not showing up / can’t join guide covers the common causes beyond version drift.
Update with SteamCMD on Linux
Stop the server process first, then run the update. Point +force_install_dir at your existing server folder so SteamCMD updates in place rather than reinstalling elsewhere:
- Shut down the running server instance.
- Run:
steamcmd +force_install_dir ~/SatisfactoryDedicatedServer +login anonymous +app_update 1690800 validate +quit - Wait for SteamCMD to finish validating, then start the server back up.
The validate keyword tells SteamCMD to check every local file against the selected branch and replace anything missing, outdated, or mismatched. It’s safe to leave in your update command permanently.
Update with SteamCMD on Windows
The flow is identical on Windows — only the path syntax changes. From your SteamCMD directory, stop the server and run:
steamcmd.exe +force_install_dir "C:\GameServers\SatisfactoryServer" +login anonymous +app_update 1690800 validate +quit
If you installed the server through the Steam GUI instead of SteamCMD, Steam handles updates for you — the server should update shortly after a patch releases, though you may need to shut the instance down and let Steam verify the files. SteamCMD installs do not auto-update; you must re-run the command after each patch.
Experimental vs Early Access branch
Satisfactory offers two server branches. The default public branch tracks the main Early Access release that most players run. The Experimental branch carries earlier builds and hotfixes that haven’t reached the main release yet. To download or update the Experimental server, add -beta experimental before validate:
- Experimental:
steamcmd +force_install_dir ~/SatisfactoryDedicatedServer +login anonymous +app_update 1690800 -beta experimental validate +quit - Back to stable: replace the flag with
-beta publicto force the switch back.
Steam remembers your last branch choice, so adding -beta public explicitly is the reliable way to leave Experimental. Remember that your game client must also be set to the matching Experimental or stable branch in Steam, or you’ll hit a version mismatch.
| Method | Branch flag | Auto-updates? |
|---|---|---|
| SteamCMD (stable) | -beta public (or none) | No — re-run command per patch |
| SteamCMD (experimental) | -beta experimental | No — re-run command per patch |
| Steam GUI install | set in Steam Betas tab | Yes — shortly after release |
| Game panel (managed host) | config/branch setting | Often one-click or automatic |
Restarting after an update
SteamCMD only patches the binaries — it doesn’t restart the game for you. After the update finishes, start your server process again (or your systemd/Windows service if you run one). On a managed control panel the restart is usually triggered automatically once the update completes. Either way, give the server a moment to fully load your save before clients reconnect. Your existing save files are untouched by updates, but it’s smart to keep backups regardless — see our save file location and backup guide.
Updating with a control panel
If typing SteamCMD commands isn’t your idea of fun, a managed panel removes the work entirely. On our Satisfactory hosting plans the server updates with a single button — and many setups update automatically when a patch drops, so your players are never stuck on a stale build. For the full walkthrough of installing, configuring, and updating through the panel, see the Satisfactory server documentation.
Frequently asked questions
Will updating my server delete my save?
No. Running the SteamCMD update only refreshes the server binaries, not your save files. Saves live in a separate save directory and are preserved across updates. Keeping a backup before any major patch is still good practice.
Why do players get a version mismatch after a patch?
The client updated but the server didn’t (or they’re on different branches). The server and every client must run the same build and the same branch — stable or Experimental. Re-run the SteamCMD update command, restart the server, and confirm everyone is on the matching branch.
Do I need a Steam account to update the dedicated server?
No. The dedicated server (app ID 1690800) downloads with +login anonymous, so no Steam credentials are needed for either the install or the update.
Ready to play?
Run your own Satisfactory server with XGamingServer
Spin up an always-on Satisfactory server your friends can join in minutes — no port-forwarding, no tech headaches.
