Romestead Server .NET 8 Runtime Fix: Server Exits Immediately

Home / SteamCMD App ID / Port 8050 fix

Short answer: install the standard .NET 8 Runtime, restart the server from a terminal so the error stays visible, then run dotnet --list-runtimes to confirm Microsoft.NETCore.App 8.x is available.

Quick Windows check

Open PowerShell in the server folder instead of double-clicking the executable.
Run dotnet --list-runtimes.
Look for a line starting with Microsoft.NETCore.App 8..
If it is missing, install the .NET 8 Runtime from Microsoft.
Launch the server again from PowerShell so any error message remains on screen.

What the symptoms usually mean

Symptom	Likely cause	Next action
Window opens, then disappears	Runtime missing or command error hidden	Start from PowerShell and read the message.
Error mentions framework or runtime	.NET 8 Runtime not installed	Install .NET 8 Runtime, not just SDK unless you need it.
Server starts after install	Runtime was the blocker	Move on to UDP 8050 and config testing.
Runtime exists but server still exits	Bad config, missing files, or save issue	Restore a clean config and launch again.

Runtime vs SDK

Most players only need the .NET 8 Runtime to run a dedicated server. The SDK is mainly for developers. Keep setup simple and install the runtime first.

After the runtime is fixed

Once the server stays open, confirm it creates a world, back up the generated config, open UDP 8050, and then invite friends to test direct connection.

Related Romestead server guides

Download files with SteamCMD App ID 4763510, continue with the config.json guide, then solve friend connection problems with port 8050 not working.