How to Set Up an ARK Survival Ascended Dedicated Server on Windows

1. Prepare the host before downloading anything

Choose a machine with enough free memory and disk space for the map, saves, mods and future updates. The server does not need to render the game, but it still simulates creatures, structures and players. A lightly used gaming PC can host a private group, while a busy modded cluster benefits from a machine reserved for hosting. Use a wired network connection where possible and prevent Windows from sleeping while the server should remain available.

Create a simple folder such as C:\arkserver instead of installing under a user desktop or a path full of spaces. Run the server under a normal Windows account that can read and write the entire folder. The first successful start should create ShooterGame\Saved. If that folder never appears, permissions or security software may be blocking writes, and the world will not persist correctly after a restart.

• Reserve a stable local IP for the host in the router.
• Keep at least one backup outside the live server folder.
• Do not use the same password for player access and administrator access.

2. Install ASA server files with SteamCMD

Download SteamCMD from Valve and extract it into its own folder. Open SteamCMD, set the installation directory, sign in anonymously and install the ARK: Survival Ascended dedicated server application. ASA uses application ID 2430930. The validate option checks installed files, but it can make routine updates slower, so use it for the first install or when files appear damaged rather than treating it as mandatory on every start.

When the download finishes, confirm that ArkAscendedServer.exe exists below ShooterGame\Binaries\Win64 in the chosen installation directory. A batch file must either run from that folder or use the executable's complete path. Many reports that Windows cannot find the server are simply batch files saved in the wrong directory or text files accidentally named start.bat.txt because file extensions are hidden.

steamcmd +force_install_dir C:\arkserver +login anonymous +app_update 2430930 validate +quit

3. Create a minimal launch command

Begin with one map, a unique session name, a game port, a query port, a player limit and an administrator password. For ASA the game port is supplied with -port rather than the older question-mark form found in many ASE examples. Keep ServerAdminPassword as the last question-mark option so later text is not consumed as part of the password. Avoid adding dozens of settings to the first command because every extra argument creates another possible failure point.

Save the batch file beside the server executable and run it. The first launch can take several minutes while directories and the world are created. A console window that remains open is not proof that the server is ready. Watch for completed startup messages, confirm the process is listening on the chosen ports, and check that save and configuration directories were created before troubleshooting visibility.

ArkAscendedServer.exe TheIsland_WP?SessionName=MyARKServer?MaxPlayers=10?ServerAdminPassword=CHANGE_ME -port=7777 -QueryPort=27015 -log

4. Allow traffic through Windows and the router

Create inbound Windows Firewall rules for the exact ports and protocols used by the launch command. Then forward those ports in the router to the host's reserved local IP address. Port forwarding to a changing DHCP address works until the router assigns a different address, which is why a reservation is part of setup rather than optional polish. Do not disable the entire firewall to make a test pass; that hides the missing rule and leaves the machine unnecessarily exposed.

Test locally first by searching the exact session name. Then ask a player outside your home connection to test. Many routers do not support NAT loopback, so trying your public address from inside the same network can fail even when external joining works. If the internet provider uses carrier-grade NAT, ordinary port forwarding may not provide a public inbound path and you may need a public IP option or hosted server.

5. Configure rates only after the world starts

Stop the server cleanly before editing GameUserSettings.ini or Game.ini. General rates and server behavior belong under ServerSettings in GameUserSettings.ini. Breeding and other game-mode rules belong under the shootergamemode section in Game.ini. Keep the first profile conservative, restart, and test one repeatable action for each changed group. A giant copied configuration can contain obsolete ASE options, duplicates and values that conflict with a host panel.

After every meaningful change, record the old value and keep a working copy. If a panel rewrites the file, make changes through the panel or stop its configuration synchronization instead of editing two competing sources. The server settings generator on ArkToolbox can create the basic sections, but the generated values still need an in-game test on a backup before an established community depends on them.

6. Verify joining, saving and restarting

Join once as a normal player, create a survivor, place an inexpensive structure and perform a manual save before a controlled shutdown. Restart the batch file and confirm that the character, tribe and structure return. This proves more than seeing the name in a browser because it checks that the server can write its save directory and reopen the same world. Also confirm that the administrator password is not required as the player password.

Finally, document how the server is updated, backed up and stopped. A working one-time launch is only the beginning of hosting. Updates should occur while the server is stopped, backups should include the world and configuration files, and players should receive notice before downtime. Once this routine is reliable, you can add mods, scheduled restarts or another map without turning basic recovery into guesswork.