Skip to main content

SteamCMD succeeded. Why is Rust still on the old build?

Compare the folder SteamCMD updated with the executable path your server launches. A successful download to a spare copy leaves the running installation untouched.

Write down the update target

Read force_install_dir in the update script. If it is a relative path, locate it from the working directory SteamCMD uses.

Write down the executable path

Find the path in the active startup script, service or host panel. Resolve relative paths from that launcher’s working directory. In a setup with a staging folder and a live folder, a success message for staging tells you nothing about the live executable.

Correct the target without switching worlds

When the right game instance is stopped, update its actual install folder. Keep the original server identity and startup settings. Launch again, confirm which executable started and check the build or startup output. A successful join should take you back to the existing world.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details