WindowsGSM documentation

Set up your first instance, update an existing one and find the right settings for your game. These instructions describe the MeFriendos fork.

Install your first server

Download the Windows x64 ZIP from GitHub Releases. Extract the whole archive to its own writable folder. The .NET runtime is bundled with the app. Individual games may need Steam access, Java or additional runtimes.
Start WindowsGSM.exe. Choose Install for a new server or Import for a supported existing installation.
Check the server name, local IP, game and query ports, and startup parameters. For an import, check that the world and configuration files are present before starting.
Start the instance and review its console. Test a connection locally before opening the required game ports for other players.

Ports and Auto Firewall

Assign distinct ports to instances on the same host. Use the game port for player connections and the query port where the game supports separate status queries. Use the protocol documented for that game.

Auto Firewall controls WGSM’s automatic Windows Firewall rules per server. Turn it off for instances whose rules you manage yourself. For internet access behind NAT, configure the router separately. Keep RCON and other administration ports on localhost or a trusted VPN.

DayZ and Minecraft

DayZ

Select DayZ Dedicated Server and use a Steam account with access to the dedicated server app. Choose a mission that exists in mpmissions. WGSM writes the configured name, slots and query port into the selected config. With Embed Console enabled, the RPT log comes from the -profiles folder. DayZ setup and logs ↗

Minecraft Java, NeoForge and ATM10

Pick the entry for your server type. Vanilla follows stable Mojang releases unless you pin one in serverfiles/minecraft-version.txt. NeoForge uses serverfiles/neoforge-version.txt for the version family or exact loader build. Use the required 64-bit Java release and review the Minecraft EULA during setup. Change RAM in user_jvm_args.txt. For ATM10, use its own entry and keep a world backup before pack updates.

Vanilla setup ↗ · NeoForge setup ↗ · All bundled servers ↗

Update and back up

Before updating the manager, stop your instances for maintenance, close WindowsGSM and back up its folder. Replace WindowsGSM.exe from the new release and keep servers, configs, plugins and bin. If you use the Steam password helper, keep its accompanying tools files together.

A game update is separate. Back up worlds, configs and mods before updating the instance. Check the console and connect to the server before reopening it to players. GitHub Releases also provides a separate SHA-256 sums file so you can verify the archive.

Workshop mods

For DayZ and Arma 3, stop the instance and back up its mods. Create servers/<id>/configs/WorkshopMods.cfg. Enter one item per line and list dependencies first. Replace the example IDs with those from your Workshop URLs.

123456789|@Dependency|mod
234567891|@AdminTools|servermod

WGSM downloads the listed mods before starting and manages their target folders as complete Workshop copies. Keep persistent settings outside those folders where the mod supports it. Missing access or a download failure can stop startup. The recovery guide explains the backup and pending marker paths. Workshop setup and recovery ↗

Steam credentials

Use Set Account when a game needs an authenticated SteamCMD download. To protect the saved password on disk, close WGSM and run Encrypt-SteamPassword.cmd from the release ZIP under the Windows account that runs WGSM. Enter your password in the helper’s local prompt.

The encrypted value is tied to that Windows account and machine. Run the helper again after moving to another account or host. Steam Guard may still need confirmation. Password setup and compatibility ↗

Scheduled restarts

Start the instance once, then open Browse → Server Configs. Place a CSV file in Crontab and enable Restart Crontab. Restart the instance after editing its schedule. This example restarts every day at 02:00 in the Windows host’s local time.

0 2 * * *;restart

For games that support it, schedule a warning and a save before the restart. Test the sequence with an empty server first. Crontab commands and RCON examples ↗

Source console

For Garry’s Mod and other Source servers, the native Windows console handles commands. With Embed Console enabled, WGSM follows the game log and adds -condebug. Keep the default log filename so WGSM can find it. Source console setup ↗

Troubleshooting

The server starts but no one can connect

Test the game locally first. Compare the listening address and port with WGSM’s settings, then check the Windows Firewall and any router forwarding. A working query reply only confirms the status endpoint.

Garry’s Mod closes after loading

Check the fork version. v1.25.4.7 fixes the Source console input error. The native console handles input and the embedded view follows the game log. Keep the default log filename when using Embed Console.

SteamCMD or a Workshop download fails

Check Steam access, Steam Guard and free disk space. Check the first failing item in the log before retrying. Use the Workshop recovery guide if an interrupted update left a pending marker.