How to Install Build 41.66 on a Project Zomboid Dedicated Server

To run Build 41.66, install the dedicated server files and deliberately select the Build 41 multiplayer/legacy branch. The current default branch is Build 42, so a normal, unpinned download can install incompatible files. On Windows, use Steam’s Tools library and launch StartServer64.bat. On Linux or another headless machine, use SteamCMD with dedicated-server app ID 380870 and launch start-server.sh. Before anyone joins, confirm the exact build string on the server and every client, then configure the ports printed by the running server.

Godlike.Host offers hosted Project Zomboid servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.

What you need to know before installing

Build 41.66 is an older Build 41 target, not the current default release. Build 41 worlds, server profiles and clients must remain on the Build 41 branch; do not run a Build 41 world with Build 42 server files. Branch labels can change in Steam, so select the label that explicitly identifies the Build 41 multiplayer or legacy branch and verify the build reported by the server after installation.

#	Preview	Product	Price
1		Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board...		Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

You can host on a Windows PC with Steam, or install the files through SteamCMD on Linux and other headless systems. Self-hosting gives you direct control of branch selection, configuration files, saves and mods, but you are responsible for firewall rules, router forwarding, backups, updates and keeping the process running. A managed host can remove much of that operational work, but you must confirm in advance that it supports the exact Build 41.66 branch, lets you retain your files and mods, and provides the controls you need.

• A Steam account is not required a second time for the dedicated-server download when using SteamCMD anonymous login.
• Keep the server and all clients on the same Build 41.66 branch and exact build string.
• Have access to the host’s operating-system firewall and, for an internet server, the router controlling the host’s network.
• Plan a backup location for the complete Zomboid user folder before changing configuration or installing mods.

Install the server on Windows through Steam Tools

1. Install the dedicated-server tool

1. Open Steam and go to Library.
2. Enable the Tools filter so utility applications appear.
3. Install Project Zomboid Dedicated Server. Let Steam finish the download before changing branches.

2. Select the Build 41 multiplayer branch

1. Right-click the dedicated-server tool in your Steam library and choose Properties.
2. Open the Betas tab.
3. Choose the Build 41 multiplayer branch. The cited guide identifies it as b41multiplayer; Steam may display a different wording, so read the current label rather than assuming the name is unchanged.
4. Wait for Steam to download the branch-specific files. A default-branch installation is not sufficient simply because the game is installed.

3. Start the first server process

1. Open the dedicated-server installation directory from Steam’s local-files option.
2. Run StartServer64.bat. Use the 64-bit launcher supplied with the installation.
3. Allow the first launch to create its user database and generated server files.
4. When prompted, set the administrator password. Store it separately from any player join password you later configure.
5. Watch the console for *** SERVER STARTED ***. That line indicates that the process reached a listening state; it does not by itself prove that an outside player can reach the machine.

For the first test, leave the profile close to vanilla. Do not add a large mod list or heavily alter sandbox settings until one client has joined successfully with the exact Build 41.66 version.

#1 Best Overall

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

• UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
• COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
• ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
• INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
• SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?

Buy on Amazon

Install on Linux or a headless machine with SteamCMD

1. Choose and protect an install directory

Create a dedicated directory owned by the account that will run the server. Keep the SteamCMD installation separate from the Zomboid user-data directory so that updating binaries does not accidentally overwrite saves and profiles. Ensure that the account can execute shell scripts and write to both locations.

2. Download the dedicated-server app

The documented SteamCMD workflow uses app ID 380870:

login anonymous
force_install_dir C:PZServer
app_update 380870 validate
quit

The example path is from the cited workflow. On Linux, substitute the absolute path you selected for the server. Run the commands from SteamCMD, and retain the output showing which branch and build were installed. If the SteamCMD interface offers a branch-selection or beta parameter, select and pin the Build 41 multiplayer/legacy branch before or during the update. Do not rely on an unqualified default branch while targeting 41.66.

3. Launch the server

1. Change to the downloaded server directory.
2. Make the supplied launcher executable if your distribution requires it.
3. Run start-server.sh.
4. Allow the first run to create the user database and generated profile files.
5. Set the requested administrator password, then wait for the console’s started indication and record the build string and port values it prints.

Run the process inside a service manager or terminal multiplexer only after the manual first boot succeeds. Keeping the first launch visible makes branch, Java, permission and port errors easier to identify.

Confirm that every component is really on Build 41.66

Version alignment is the most important check because Build 42 is now the default in many Steam installations. Check the server console or SteamCMD output for the exact Build 41.66 string, then check the client’s displayed version and branch. A client on the current default branch can fail to join even when the server process is running normally.

1. Stop the server cleanly after the first boot has completed.
2. Record the build string shown by the server and the branch selected in Steam or SteamCMD.
3. Set each test client to the same Build 41 multiplayer/legacy branch and wait for its files to finish updating.
4. Start the server again and compare the strings character for character before troubleshooting networking.
5. Use a vanilla profile for the first connection test. This isolates branch and network errors from mod or sandbox errors.

The current administration guidance is oriented toward Build 42, but its branch-separation warning still applies: keep Build 41 saves on Build 41 files and never point a Build 42 installation at a Build 41 world.

Back up the generated profile before editing it

After the first successful start, stop the process cleanly before changing files. The generated configuration normally lives in the user’s Zomboid/Server directory, while the broader Zomboid folder contains saves, server profiles and logs.

1. Stop the server from its console rather than closing the window abruptly.
2. Copy the complete Zomboid folder to a dated backup location.
3. Keep a named copy of the active server profile, including its settings and world-related files, before each substantial edit.
4. Record which Build 41 branch and exact build produced the backup.

Backups are especially important before a branch change, game update, world conversion or mod change. If a patch leaves the branch and world files mismatched, restoring the known-good folder is safer than repeatedly editing a live process.

Configure ports and make the server reachable

Project Zomboid’s official Build 41 networking announcement identifies game port 16261 for Steam queries and additional port 16262 for the direct connection. An older Steam setup guide also refers to port 8766. Because networking paths changed during Build 41, use the values printed by your running 41.66 server as the authoritative list, then apply those values consistently in the server options, router and firewall.

Apply the network rules

1. Start the server and note every port it prints. Also note whether it is configured as open or public and whether a join password is enabled.
2. In the host operating system’s firewall, create inbound UDP rules for the reported ports. If the firewall distinguishes application rules, allow the dedicated-server executable as well.
3. On the router, forward those same UDP ports to the host’s private LAN address. Give the host a stable DHCP reservation or static address so the rule does not follow a different device after a reboot.
4. Save the server configuration and restart it if a port setting requires a restart.
5. Test from a machine outside the host’s LAN, such as a friend’s connection or a mobile hotspot. A test from the same LAN can succeed even when internet forwarding is wrong.

Keep the public address, the host’s private LAN address and the configured game port separate when entering connection details. Sharing the wrong address is a common reason a local test works while remote players time out.

Join the server from the Project Zomboid client

1. Open Multiplayer in the client.
2. Add a server entry and enter the host address and the configured port shown by the server.
3. Enter the join password if one is set. This password is not the administrator password created during first boot.
4. Use the Build 41.66 client branch, then connect.

The first administrator connection may create or use the admin account established during first boot. Keep administrative credentials private and provide ordinary players only the address, port and join password they need.

Add mods only after the vanilla connection works

A dedicated server does not automatically inherit the mod list from a client’s local mod manager. The server configuration has separate WorkshopItems and Mods fields, and both must match what the clients need. Workshop item IDs identify downloads; mod IDs identify the actual mods loaded by the game. Treat them as a matched set rather than filling one field and assuming the other will be inferred.

A safe mod rollout

1. Stop the server cleanly and back up the complete Zomboid folder.
2. Add a small, known-compatible group of Workshop item IDs and the corresponding mod IDs to the server profile.
3. Start the server and read the console for download, dependency or load errors.
4. Have a client use the same Build 41.66 branch and matching mod set.
5. Join and test the world before adding another group.
6. If the map hangs at Loading Map or a mod error appears, return to the clean backup, verify both fields, and re-add items in smaller groups.

Keep a written copy of the working IDs and their order. This makes it possible to reproduce a known-good profile after an update instead of guessing which item caused a failure.

Update without breaking a Build 41 world

Before any server update, stop the process cleanly and copy the Zomboid folder. Keep the world, server profile and client on the Build 41 branch. Do not update the installation to Build 42 and then attempt to reuse the Build 41 world. If a patch changes the selected branch or leaves the files inconsistent, restore the backup and reselect the intended Build 41 branch before starting again.

After an update, verify the exact server build string, launch with the same profile, and connect with one unmodified test client before allowing the full player group back in. This staged check catches a branch mismatch before it changes a shared world.

Troubleshoot by symptom

The server starts, but nobody can join

• Compare the complete server and client build strings; do not stop at the major version number.
• Confirm that every client selected the Build 41 multiplayer/legacy branch rather than the current default.
• Check the server’s open/public setting and whether a join password is required.
• Verify host-firewall rules and router forwarding for the exact UDP ports printed by the running process.
• Test from outside the host LAN to distinguish a forwarding problem from a local configuration problem.

A local player can connect, but a remote player cannot

This pattern usually points to the network path rather than the game files. Recheck the router’s destination LAN address, the UDP rules, the public address supplied to the remote player and the ports shown in the console. A successful local connection does not validate internet forwarding.

The client remains on “Loading Map” or reports mod errors

Stop changing multiple variables at once. Restore the clean profile, confirm that a vanilla client can join, then verify the server’s WorkshopItems and Mods fields as a pair. Add one small batch at a time and keep a backup before each change.

Administrator login fails

Separate the first-run administrator credentials from the player join password. Use the administrator password requested during the initial server boot for administrative access; use the join password only when the client asks to enter the server.

A patch causes new errors

Stop the live process, identify whether Steam moved the installation to another branch, and compare the current build with the backup’s recorded build. Restore the backup if necessary, reselect Build 41, and retest with one vanilla client. Do not continue editing files while the server process is running.

Self-hosting versus managed hosting

Both approaches can work, but they shift responsibility differently. The deciding question is not only monthly cost; it is whether the service can hold the exact Build 41.66 branch and give you the file and mod control your world requires.

Whichever model you choose, ask one operational question before migrating a world: can you export and restore the complete Zomboid folder while staying on Build 41.66? If the answer is unclear, keep the authoritative backup under your own control.

What a successful 41.66 installation looks like

The server launches with the correct Build 41 branch, reports the expected 41.66 build string and reaches its started state. Its configured ports are visible in the console and allowed through the host firewall and, when needed, the router. One clean client on the same branch can join using the configured address, port and join password. Only after that baseline works should you add sandbox changes or mods. Maintaining that order makes every later failure attributable to a specific change instead of leaving branch, network and configuration problems mixed together.

Quick Recap

Bestseller No. 1

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.