Project Zomboid “Normal Termination” Error: Read the Real Cause

Build 42.19 co-op and dedicated-server troubleshooting: use the earlier log error—not the final “Normal Termination” label—to choose a fix.

This guide covers Host Game / co-op launch failures and sudden hosted-server exits. Always open your own log first. If the UI only shows a generic stop message, check coop-console.txt, console.txt, and, for dedicated servers, server-console.txt.

1. Back up before you change anything

Build 42 also has built-in server backups. Defaults in the current server options are:

• BackupsCount=5 — keep five rotating archives per backup type.
• BackupsOnStart=true — create a startup backup when the server starts.
• BackupsOnVersionChange=true — back up when the detected game version changes.
• BackupsPeriod=0 — periodic real-time backups are off; set a positive minute value only if you want them.

Automatic archives usually land under the Zomboid/backups tree as rotating backup_*.zip files. They are a safety net, not a substitute for a full manual copy before you rename or delete world files.

2. Collect the correct logs

Current log names use hyphens, not underscores. The co-op console file is coop-console.txt, not coop_console.txt. When you package logs for support, include console.txt, coop-console.txt, and server-console.txt.

Search the current co-op log first when Host Game fails:

# Windows PowerShell
Select-String -Path "$env:USERPROFILE\Zomboid\coop-console.txt","$env:USERPROFILE\Zomboid\console.txt" `
  -Pattern "exception|error|caused by|bind|address already in use|OutOfMemory|workshop|mod|map_t|WorldVersion|terminated|fail"

# macOS / Linux
grep -niE "exception|error|caused by|bind|address already in use|OutOfMemory|workshop|mod|map_t|WorldVersion|terminated|fail" \
  ~/Zomboid/coop-console.txt ~/Zomboid/console.txt

Do not stop at the last generic line. Read upward to the first exception, bind failure, mod/Workshop failure, or named file in the same launch attempt, and keep that full block.

3. Branch by log signature, not by the UI text

4. Stale processes and ports — only when the log supports them

Leftover Java or Project Zomboid processes can leave ports occupied and make the next Host Game launch fail. Checking Task Manager, Activity Monitor, or lsof is reasonable after a bind error or after a previous crash that never closed cleanly. It is not a substitute for reading the log.

# Example: inspect default player-data port 16261 (replace with your INI value)
# Windows PowerShell
Get-NetUDPEndpoint -LocalPort 16261 -ErrorAction SilentlyContinue

# macOS / Linux
lsof -nP -iUDP:16261

Restarting the computer can clear a stuck process. It does not fix a wrong INI port pair, a broken mod list, or a damaged world file.

5. “Server has stopped launching” and map_t.bin

1. Confirm the log actually names map_t.bin or a version mismatch. If it does not, stay on the branch that matches the real signature.
2. Stop the server and client. Keep the full folder backup you already made.
3. Prefer restoring the complete multiplayer save (or a native backup_*.zip) over deleting individual world files.
4. Only as an advanced, last-resort test — and only with a restore path ready — rename map_t.bin out of the save so the game can recreate a missing first-run version file. Understand that this can desync world time or version expectations; restore immediately if the world still fails or behaves wrong.
5. Never delete players.db, chunk maps, or the whole <server> directory while “trying something.” Those steps can erase characters and built structures permanently.

6. Manual multiplayer backup layout

For a hosted world named servertest, the common pair is:

• Saves/Multiplayer/servertest/ — server world data (map chunks, meta, vehicles, world databases).
• Saves/Multiplayer/servertest_player/ — host/player-side multiplayer data for that world name.

Copy both folders, the matching Server/<name>.ini settings, and recent logs together. Put restored folders back under the same names before relaunching.

7. Controlled retest

1. Close the client and stop every server instance.
2. Archive the complete Zomboid user-data folder.
3. Preserve coop-console.txt, console.txt, and any server-console.txt / logs.zip.
4. Apply one change that matches the exact log signature (free a port, fix mods, restore a backup, or adjust memory only after an OOM line).
5. Start Host Game or the dedicated server once and wait for a clear ready or failure message.
6. Compare the new log with the old one. If the message changed, follow the new signature instead of stacking unrelated fixes.

What to include when asking for help

• Exact Project Zomboid build and Steam branch for host and clients.
• Whether this is Host Game co-op or a dedicated / rented server.
• The first real exception, bind line, Workshop/mod failure, or named file from coop-console.txt — not only “Normal Termination.”
• Operating system and whether the machine recently lost power or force-killed Java.
• Enabled Workshop IDs and mod IDs, plus whether a clean no-mod test server still fails.
• Sanitized logs.zip after removing passwords, tokens, and addresses you do not want public.

Related guides: multiplayer log triage when a vague error code appears, server administrator backup and options, server memory sizing when logs show heap pressure, finding a mod that breaks launch, and manual save backup steps.