What is the hidden first-session step after Windows SteamCMD install?

A healthy server process is not enough on its own. On the current live baseline, you still need to connect from the game client, open Manage Server, and Start New Session or Load Session before treating the world as ready.

When should I leave this Windows first-start checklist?

Switch guides early if your real goal is Proton, Wine, Docker, or a Linux host panel workflow. The Windows SteamCMD quick start is still useful context, but Linux hosting has different failure modes and deserves its own setup path.

StarRupture Windows SteamCMD First Start

This Windows first-start checklist begins after SteamCMD and StarRupture App ID 3809400. Place DSSettings.txt, keep UDP 7777 open, then use Manage Server before you treat a running process as a loaded world. For Linux, Docker, ports, and the rest of the install, use the dedicated server setup guide.

Step 1: Install SteamCMD and pull the server files

The fastest current live-baseline path is still Windows plus SteamCMD. Use a permanent directory such as C:\SteamCMD\, then run the standard dedicated-server install path with app ID 3809400.

force_install_dir C:\StarRuptureServer\

app_update 3809400 validate

quit

Keep the validate flag on first install and after suspicious update failures.

Step 2: Set the first DSSettings.txt baseline

Treat DSSettings.txt as the first config surface, then cross-check the exact path for your current host workflow before editing a live save.

# Server name shown in the browser

ServerName=My StarRupture Base

# Max concurrent players

MaxPlayers=4

# Autosave interval in minutes

AutoSaveInterval=15

Keep this quick-start file simple. If your real blocker is password handling, save loading, or host-panel config drift, move to the full dedicated server guide or the admin guide.

Step 3: Verify UDP 7777 before you chase edge cases

StarRupture dedicated servers still point to UDP 7777 as the first network baseline. Keep the launch command, DSSettings path, firewall rules, router forwarding, and join target aligned before you assume the problem is something stranger.

netsh advfirewall firewall add rule name="StarRupture" protocol=UDP dir=in localport=7777 action=allow

If the browser still looks wrong after this, do not guess. Run the server-not-showing checklist next.

Step 4: Start the world from the game client

This is the hidden step that many setup guides bury: a running process is not the same thing as a playable world.

Launch the server process and confirm it stays alive.
Open StarRupture on a client PC.
Join through the dedicated server flow.
Open Manage Server.
Choose Start New Session or Load Session.

If you skip this, the setup can look healthy while players still see odd browser behavior, missing world state, or failed persistence.

Step 5: Use the right troubleshooting fork

Problem: Players can connect but immediately disconnect

Fix: Check version mismatch first, then verify that the right world was actually started through Manage Server. A healthy process with no active session can look like a network issue.

Problem: Server starts but does not appear in the browser

Fix: Treat the browser as one signal, not the only signal. Re-check UDP 7777, DSSettings path, firewall rules, and direct join behavior, then use the browser troubleshooting guide if the listing still looks wrong.

Problem: Players can join but rubberband or desync

Fix: Move to the lag checklist next. Start with host region, wired networking, player count, and autosave cadence before you assume the answer is a hidden launch flag.

Problem: Linux or host-panel instructions do not match this page

Fix: Switch to the Linux server guide or your host-panel documentation early. The quick-start Windows baseline is useful context, but Linux and hosted panels have different paths for service files, save locations, and restarts.

What to open next

Dedicated Server Guide for the broader DSSettings, save-loading, and setup reference.
Linux Server Guide if your real target is Proton, Wine, Docker, or Linux host-panel deployment.
Server Not Showing Fix Guide when the browser or direct-join path still looks wrong.
Server Lag Fix Guide when players can join but performance collapses under load.
Controller and Steam Deck Guide if couch or handheld input issues are getting mixed into co-op testing.

StarRupture Windows SteamCMD First Start — App ID 3809400

Quick Start Answers