Startup & Crashes
- Nothing happens after pressing Play
- Black screen during startup
- Crash while loading a save or joining a game
Use this path when the game will not start, shows a black screen, or crashes while loading.
Explore this problemFind the Error Before You Delete Anything
Start with the symptom, confirm your build, and work through safe fixes for crashes, error logs, broken mods, and multiplayer problems.
Start With What You See
You do not need to know the cause yet. Pick the symptom that looks closest to your problem.
Use this path when the game will not start, shows a black screen, or crashes while loading.
Explore this problemUse the visible message and console.txt to narrow down what failed before changing files.
Explore this problemCheck installation, version support, dependencies, and load order when a mod is missing or broken.
Explore this problemFollow server-specific checks for hosting failures, connection loops, and client-server file mismatches.
Explore this problemPopular Fixes
Open the guide that matches the message or symptom you are seeing.
Build 41 & Build 42
The game stops and tells you to check console.txt.
Open this fixBuild 41 & Build 42
Find console.txt or logs.zip and identify the useful error lines.
Open this fixBuild 42
Read Build 42 console errors without treating every warning as the cause.
Open this fixBuild 41 & Build 42
Understand the red Error 1–4 counter and find the underlying log entry.
Open this fixBuild 42
Troubleshoot a hosted server that stops or reports that the host terminated.
Open this fixMods & Multiplayer
Mod and server issues often look like game errors, but they need their own installation, dependency, version, and synchronization checks.
Check where mods are installed, whether they loaded, and whether they support your build.
Browse Mod TroubleshootingSeparate local game problems from hosting, server configuration, and client-server synchronization issues.
Browse Multiplayer TroubleshootingSafe Troubleshooting
Use the smallest reversible change that tests one likely cause at a time.
Check whether you are using Build 41 or Build 42 before following version-specific paths or mod instructions.
Start from what the game shows instead of guessing which component failed.
Keep the relevant log before restarting repeatedly or changing files.
Test settings, dependencies, load order, or one mod at a time before removing data.
Copy saves and important configuration before deleting, resetting, or replacing folders.
Current guides prioritize Build 42. Build 41-only steps are labeled, and paths, menus, mod structures, or server settings are separated when they differ.
Deleting the Zomboid folder, saves, databases, or Workshop data is never presented as a universal quick fix.
Learn How to Read the Error LogQuick Answers
It is an error counter, not a fixed error code. Open console.txt and look for the related error entry to identify the actual cause.
It is stored in your user Zomboid folder. The error-log guide shows how to find console.txt or logs.zip and which lines are useful.
Not automatically. Check the Workshop page for supported builds, required dependencies, and recent author updates before enabling a mod.
The server and every client may need matching mod versions, dependencies, and server mod or Workshop settings. Treat it as a synchronization problem first.
Not as a first step. Diagnose the symptom, save the logs, try reversible fixes, and back up saves and settings before any reset or deletion.
Choose the closest symptom, keep your current log, and begin with the safest checks.