How to Install Build 41.66 on a Project Zomboid Dedicated Server

To run Project Zomboid Build 41.66, install the dedicated-server files, deliberately select the Build 41 multiplayer branch, and verify that the server and every client report the same 41.66 build. The current Steam default has moved to Build 42, so a normal default-branch installation is not sufficient. On Windows, install the server from Steam Tools and launch StartServer64.bat. On Linux or another headless machine, use SteamCMD with dedicated-server app ID 380870, then launch start-server.sh. For internet play, configure the UDP ports printed by the running server—normally 16261 for Steam queries and 16262 for direct connections—and test from outside the host network.

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 Build 41.66 requires

Build 41.66 is an older multiplayer target. Build 42 files, worlds and clients are not interchangeable with a Build 41 server. The most important installation step is therefore branch selection, not merely downloading the dedicated-server tool. Select the Build 41 multiplayer or legacy branch, confirm the exact build string in the server console, and have each player select the matching client branch before anyone creates or opens a long-term world.

#	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 on Linux and other headless machines through SteamCMD. Either method creates the same type of server profile and uses the same networking and backup practices.

Choose a hosting method

A managed service can reduce router and uptime work, but you must confirm support for the exact legacy branch before moving a Build 41 world. No generic promise that a host supports Build 41.66 is safe: ask which branch and build the control panel installs, how backups are exported, and whether Workshop and mod IDs can be edited separately.

#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 Build 41.66 on Windows with Steam

1. Install the dedicated-server tool

1. Open Steam and go to Library.
2. Enable the Tools filter. The regular game entry is not the dedicated-server executable.
3. Install Project Zomboid Dedicated Server and wait for Steam to finish writing the files.

2. Select the Build 41 multiplayer branch

1. Right-click the dedicated-server tool in the Steam Library and open Properties.
2. Open the Betas tab.
3. Select the Build 41 multiplayer branch. The cited guide identifies it as b41multiplayer; branch labels can change, so use the label currently displayed by Steam and do not assume that a similarly named option is identical.
4. Wait for Steam to complete any branch download or update. A default-branch installation that reports Build 42 is the wrong installation for a 41.66 world.

Record the branch name and the build string shown by Steam or the server console. Give players the same branch-selection instructions before they attempt to join.

3. Start the server and create the first administrator

1. Open the dedicated-server installation directory.
2. Run StartServer64.bat. Use the 64-bit script supplied with the installation.
3. On the first launch, allow the server to create its user database and answer the prompt for an administrator password.
4. Wait for the console to print *** SERVER STARTED ***. If the process exits before that message, fix the error before changing gameplay settings.

The password entered during first boot is for the server administrator account. It is not automatically the same as a join password that you may configure for players.

Install on Linux or a headless machine with SteamCMD

1. Use a controlled installation directory

Create a directory owned by the account that will run the server and keep the game files separate from the generated Zomboid user data. A controlled path makes backups, permissions and branch rollback easier. The cited Steam workflow uses the following commands:

login anonymous
force_install_dir C:PZServer
app_update 380870 validate
quit

380870 is the dedicated-server application ID. The example path is Windows-style because it is the path shown in that workflow; on Linux, substitute the controlled Linux directory used by your SteamCMD installation. Anonymous login is sufficient for downloading the dedicated-server application itself, so a second Steam account is not required for that download.

2. Select and verify Build 41

When SteamCMD exposes the Build 41 multiplayer or legacy branch, select or pin that branch in the SteamCMD workflow before updating. Do not infer the branch from the fact that files downloaded successfully. Record the branch and exact build reported by SteamCMD, then check the server console after launch. If the output identifies Build 42, stop and correct the branch before creating a world.

3. Launch the Linux server

1. Change to the directory containing the installed server scripts.
2. Run start-server.sh using the account that owns the files.
3. Complete the first-run administrator-password prompt.
4. Wait for the same successful-start indication, *** SERVER STARTED ***, before testing a client.

Keep the terminal output or service log from this first launch. It records the build and the ports the server is actually using, which are more useful than assumptions copied from an older setup guide.

Complete the first boot safely

Stop cleanly before editing

After confirming that the process started, stop it through the server’s normal shutdown mechanism before editing configuration files. Do not change profile files while the server is actively writing them. An unclean stop can leave a save or configuration in a partially written state.

Back up the complete Zomboid data directory

Back up the user’s entire Zomboid folder, not only one save file. Include saves, server profiles and logs. Generated server configuration normally appears under the user’s Zomboid/Server directory. Give each backup a date and keep a named copy of the active profile before changing it.

• Keep one untouched vanilla backup for diagnosing branch and network problems.
• Keep a second backup immediately before every mod or major sandbox change.
• Store at least one copy outside the machine that hosts the server so a disk failure does not remove both the live world and its backup.

Prove a vanilla connection first

Start with the default, unmodded profile. Have one local or remote client join with the exact same Build 41.66 string before changing sandbox values or adding Workshop content. This isolates branch and networking faults from configuration and mod faults. Once that test succeeds, stop the server, make a fresh backup, and make one category of change at a time.

Configure ports and internet connectivity

Project Zomboid’s Build 41 networking uses more than one port. The official networking announcement identifies the game port, 16261 by default, as the port used to handle Steam queries. It identifies the additional direct-connection port, 16262 by default, for the direct connection itself. Both can be changed through server options.

Port requirements and networking paths changed during Build 41. Before opening the router, inspect the live server output and use the exact port values it reports. The older guide references ports 8766 and 16261 for its Steam-server setup, while the official announcement describes 16261 and 16262. That difference is why copying a port list without checking the running build can leave a server visible but unreachable.

Forward ports on the router and host firewall

1. Give the hosting machine a stable private LAN address, or reserve its address in the router’s DHCP settings.
2. Create UDP forwarding rules for every port the server reports, mapping each external port to the same port on the server’s LAN address.
3. Create matching inbound UDP rules in the operating system firewall.
4. Apply the router and firewall changes, then restart only the server if necessary; do not edit live profile files during this test.
5. Test from a machine outside the host’s LAN, such as a friend on another connection. A successful connection from the same LAN does not prove that internet forwarding works.

If your internet connection uses carrier-grade NAT or another upstream router, local forwarding may still fail even when the rules look correct. Check whether the host has a publicly reachable address and whether another device or modem also needs forwarding.

Join from the Project Zomboid client

1. Open Multiplayer in the client.
2. Add the server and enter its address and configured port.
3. Enter the join password if you set one.
4. Use the public address for players outside your network and the LAN address for players on the same network when the client asks for an address.
5. Confirm that the client is on the same Build 41 branch and exact 41.66 build as the server.

Keep the public address, LAN address, join password and administrator credentials in separate notes. Confusing a join password with the first-run administrator password is a common reason an administrator appears unable to log in.

Set server visibility and passwords

Use the server profile’s public or open settings consistently with the way you intend to host. A private group can use a join password and share the address directly; a public listing requires the relevant open or public setting and still needs a reachable UDP path. If clients can see a listing but fail while loading, visibility has worked but the direct connection, build, profile or mod state may not match.

After changing visibility, passwords or ports, stop the server cleanly, edit the saved profile, start it again and read the resulting console output. Keep a copy of the previous profile so a typo can be reverted without losing the world.

Add mods without breaking the first working profile

Dedicated-server mod configuration has two related but separate fields: WorkshopItems contains Workshop item IDs, while Mods contains the corresponding mod IDs. Both fields must match what the server and clients require. A client’s local mod manager does not automatically synchronize a dedicated server’s INI file.

Safe mod rollout

1. Stop the server and back up the complete Zomboid folder.
2. Write down the Workshop item ID and mod ID for every addition.
3. Add a small batch to the server profile, keeping WorkshopItems and Mods as matched lists.
4. Start the server and let Workshop content download before asking clients to connect.
5. Have clients use the same branch and the same mod set, then test the world.
6. If the test succeeds, make that profile your new named backup. If it fails, restore the previous profile or remove only the latest batch.

Adding one large collection at once makes a loading-map error difficult to diagnose. Small batches provide a clear rollback point and reveal which item introduced a dependency, an incompatible version or a missing map.

Update without converting a Build 41 world

Before any server update, stop the process cleanly and copy the complete Zomboid folder. Keep Build 41 saves on the Build 41 branch. Never point a Build 42 dedicated-server installation at a Build 41 world, and never assume that a current default download preserves the older branch.

After an update, verify the branch and exact build in the server output before allowing players to load the world. Have one client perform a controlled join first. If the branch or world files no longer match, stop the server and restore the last known-good backup rather than continuing to edit a live or partially upgraded profile.

Troubleshoot the problems players report most

The server starts, but nobody can join

• Compare the complete build strings on server and client; selecting the wrong Steam branch is enough to block a connection.
• Check the configured open or public setting and confirm that a join password has been entered correctly.
• Read the server output for the actual game and direct-connection ports.
• Confirm matching UDP rules in both the router and host firewall.
• Test from outside the host LAN rather than relying on a local loopback test.

Local players connect, but remote players cannot

The world and server process are probably functioning, while the internet path is not. Recheck the host’s private address, UDP forwarding and firewall rules. Verify that the public address belongs to the host’s internet connection and test from an external network. If the router is behind another router or carrier-grade NAT, identify that upstream layer before changing Project Zomboid settings.

The client stops at Loading Map or reports mod errors

Return to the clean vanilla profile and test the same Build 41.66 client. If vanilla works, compare both WorkshopItems and Mods, remove the latest batch, and re-add items in small groups. The local client mod manager cannot repair a missing or incorrect server INI entry.

Administrator access fails

Use the administrator account and password created during the first server launch, not the player join password. If the credentials were lost or the user database is damaged, stop the server and restore the appropriate pre-change backup rather than repeatedly editing a running process.

A patch leaves the world unusable

Stop the server, compare the branch and build reported by Steam and the console, and restore the last complete Zomboid backup if they no longer match. Do not launch a Build 42 installation against the Build 41 world while troubleshooting.

Self-hosting versus managed hosting

The installation steps above assume that you operate the machine. A managed service changes who performs the operating work, not the compatibility requirement. Evaluate the two approaches on the following points before moving an existing world:

For either approach, preserve an independent copy of the Zomboid folder and keep a written record of the branch, build, port values and mod IDs. Those records let you move or restore the server without guessing.

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

Build 41.66 installation checklist

• Dedicated-server files are installed through Steam Tools or SteamCMD app ID 380870.
• The Build 41 multiplayer or legacy branch is selected deliberately; the default Build 42 branch is not used.
• The server launches with StartServer64.bat on Windows or start-server.sh on Linux.
• The first-run administrator account is created, and the console prints *** SERVER STARTED ***.
• The exact 41.66 build string matches on server and clients.
• A complete backup of the Zomboid folder exists before configuration or mod changes.
• The running server’s UDP ports are recorded, forwarded and allowed through the host firewall.
• A vanilla client completes a local or remote join before mods are added.
• WorkshopItems and Mods contain matching server-side entries for every mod.
• Build 41 saves remain on Build 41 files during updates and recovery.

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.