You cannot carry a Build 41 world directly into stable Build 42.20. The Indie Stone’s 29 July 2026 stable announcement says Build 41 savegames are not compatible with Build 42. Keep the existing world by pinning the server and every player to Steam’s legacy41 branch, or start a new Build 42.20 world. If the world was created on Unstable 42.19, keep it on the 42.19 branch instead; 42.20 added map content that makes those saves incompatible.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Project Zomboid servers with free DDoS protection and up to three free backups a day.
This guide gives you a backup-first migration runbook, branch-selection instructions, mod and network checks, validation tests, and rollback procedures for a dedicated server.
As an Amazon Associate I earn from qualifying purchases.
Choose the correct destination before touching the server
“Upgrade” means different things depending on the world you need to preserve. Decide the destination first, then make the server, clients, mods, and save data agree with it.
| Current world | Destination | What happens to the world | Steam branch |
|---|---|---|---|
| Build 41 | Continue the same world | Remain on Build 41; do not update that installation to Build 42. | legacy41 |
| Build 41 | Play Build 42.20 | Start a new Build 42 world. There is no supported in-place conversion. | Stable/public Build 42.20 |
| Unstable 42.19 | Finish the existing world | Remain on 42.19. The 42.19 save cannot be opened by 42.20 because new map content was added. | 42.19 |
| Unstable 42.19 | Move to 42.20 | Keep the 42.19 backup, then create a fresh 42.20 world. | Stable/public Build 42.20 |
The same branch decision applies to everyone who connects. A server on legacy41 needs clients on Build 41; a 42.19 server needs clients on 42.19; and a 42.20 server needs clients on stable 42.20. A player on a different branch is not a harmless version mismatch: the connection can fail before the login screen or the client can reject the server.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
What Build 42.20 changes for a migration
Build 42.20 was announced as stable on 29 July 2026. “Stable” does not mean it can read older-world data. The official announcement specifically states: “Build 41 savegames clearly will not be compatible with Build 42.” Treat the change as a new-world migration rather than an upgrade that transforms the old map.
The earlier Unstable guidance also warned that Build 42 was work in progress, that Build 41 saves and mods were not compatible, and that saves could break after Unstable updates. Those warnings explain why a 42.19 world must stay on its matching branch and why an immutable backup matters even when moving between two Build 42 versions.
What you can preserve
- Your old server configuration, administrator list, launch arguments, Workshop collection, mod notes, and logs can be copied for reference.
- A Build 41 world can remain playable by keeping a separate Build 41 installation on
legacy41. - A 42.19 world can remain playable by pinning the server and clients to
42.19.
What you should not promise players
- Do not promise that characters, bases, explored cells, vehicles, or map edits will appear in a new 42.20 world.
- Do not copy a live save into the new installation and assume the game will convert it. A running server may also leave the copied files incomplete.
- Do not assume a mod that worked on Build 41 or 42.19 will load safely on 42.20.
Prepare a safe maintenance window
Plan the change like a database migration. Pick a start and end time, tell players when the server will be unavailable, and freeze gameplay before you begin.
Record the current state
Before stopping anything, capture the information needed to reproduce the old server:
- Current game build and Steam branch.
- Server name and the exact server-settings file in use.
- The
Mods=line, Workshop item IDs, Workshop settings, and intended load order. - Game and query ports, including any custom values.
- Administrator usernames and permission settings.
- Launch scripts, JVM or memory arguments if used by your host, operating-system details, and scheduled tasks.
- The most recent server and console logs, including the last clean shutdown.
Save this inventory outside the live server directory so an update cannot overwrite it. A plain text change record is enough; its purpose is to make rollback and troubleshooting deterministic.
Stop the server cleanly
- Announce that the world is entering maintenance and prevent new logins.
- Use the server console or hosting panel’s normal stop action. Wait for the process to exit rather than killing it.
- Confirm that no dedicated-server process is still writing to the save directory before copying files.
Never copy a save while the server is running. A partially written chunk, database, or map file can make a supposedly good backup unusable.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Back up the complete data set
Make a dated, restorable copy of the entire Zomboid server-data tree, not just the visible world folder. Include saves, server configuration, Workshop and mod lists, logs, administrator data, launch scripts, and any host-specific files. Keep the original backup immutable: do not use it as the working directory for the upgrade.
Use at least two destinations when the world has significant play time—for example, a local copy and a separate storage location. Label each copy with the build and branch, such as 2026-10-15-b41-legacy41 or 2026-10-15-b42-19. The label prevents a later 42.20 backup from being mistaken for the pre-migration restore point.
Prove that the backup is usable
A backup is only useful if it can be read. Check that the archive opens, that its size is plausible compared with the live data, and that representative save, configuration, and Workshop files are present. If your host provides a restore or staging feature, restore the copy to a disposable location and verify that the files are readable before changing branches.
Update the dedicated-server files
There are two normal ways to select Build 42: a hosting control panel or SteamCMD. In either case, update the game files only after the backup is complete.
Using a hosting control panel
- Open the server’s version, branch, or Steam beta selector.
- Choose stable/public Build 42.20 for a new Build 42 world,
legacy41to preserve a Build 41 world, or42.19to continue an Unstable 42.19 world. - Apply the change and allow the panel to finish downloading and validating files.
- Do not restore an incompatible old save into the new branch. For a new 42.20 world, leave the save location empty so the server can generate it.
Control-panel labels differ between hosts. Confirm the resulting build in the startup log instead of trusting a button label alone.
Using SteamCMD
The dedicated-server application is identified as App ID 380870. A typical SteamCMD session uses the following syntax; authentication and install-directory options depend on your operating system and host:
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
steamcmd +login anonymous +app_update 380870 validate +quitFor a branch, the same command commonly includes -beta:
steamcmd +login anonymous +app_update 380870 -beta legacy41 validate +quit
steamcmd +login anonymous +app_update 380870 -beta 42.19 validate +quitRun the command appropriate to the branch you selected, not both. SteamCMD branch names and host wrappers can change, so verify the current syntax in your provider’s documentation and inspect the downloaded files and startup log afterward. The command updates binaries; it does not convert a Build 41 save into a Build 42 save.
Build a clean Build 42 test instance
For a Build 41-to-42 move, create a separate test instance rather than experimenting on the only copy of production data.
- Install or update the dedicated server to stable Build 42.20.
- Give the test instance a different server name and, if it will run at the same time, different configured ports.
- Start it with no old save and minimal or no mods so it generates a clean world.
- Join with one administrator account, create a character, move between cells, quit normally, and reconnect.
- Stop it cleanly and confirm that the new save loads again.
This test separates an installation or network problem from a migration problem. Once the clean world works, copy only the configuration you intentionally want to keep and add compatible mods in controlled batches.
Handle saves correctly
Moving from Build 41 to a new 42.20 world
Do not place the Build 41 save in the 42.20 save directory. Keep it in the dated backup or in a separate legacy41 installation. Start 42.20 with a new world, then communicate clearly that characters, bases, map exploration, and loot state begin again.
Continuing a 42.19 world
Install the 42.19 branch and restore the 42.19 data only after confirming that the branch is selected. Do not let an automatic update move the server to 42.20 while players are still using that save. Keep the 42.19 branch and backup available until you have deliberately ended that run.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Keeping both eras available
Running two instances is the least ambiguous option for a community that wants to finish Build 41 while testing Build 42. Give each instance its own data directory, server name, configuration, logs, and port set. Never point both processes at the same save directory.
Audit mods before inviting players
Build 41 mods are not automatically safe on Build 42. Build 42’s mod architecture supports version-specific directories, allowing a Workshop item to ship separate B41 and B42 content, but that feature does not certify every item.
Make a compatibility inventory
- List every Workshop item and mod ID from the old server.
- Check the author’s current description or release notes for explicit Build 42.20 support.
- Identify whether the item has separate B41 and B42 directories or files.
- Record dependencies and load order; a compatible core mod can still fail if a required dependency is missing.
- Remove abandoned or B41-only items from the initial 42.20 test.
Add mods in small batches
- Start the clean 42.20 world without mods and confirm that it saves and reloads.
- Add one related group of verified B42 mods.
- Restart, inspect the console and log for errors, and join with a test character.
- Save, stop, and reload. If the test fails, remove the last batch and isolate the offending item.
Do not copy the old Mods= line wholesale. Rebuild it from the verified list, preserving order only where the mod author requires it. During the Unstable multiplayer testing period, The Indie Stone advised disabling mods and avoiding more than 20 players while warning that future updates could disrupt games. Those statements describe that testing period, not a permanent player cap for stable 42.20; they are nevertheless a reason to test conservatively.
Recommended Free Tools
Configure ports and firewalls
Build 42 does not automatically require a second internet connection or a new port range. The official networking notice identifies these default UDP ports:
| Purpose | Default | What to check |
|---|---|---|
| Steam queries and game port | UDP 16261 | Allow it through the host firewall and forward it on the router if the server is behind NAT. |
| Direct client connections | UDP 16262 | Allow and forward it as well when direct connections are used. |
Both values can be changed in server options. Use the actual configured values, not the defaults, when creating firewall rules or publishing connection instructions. A changed port requires matching client information. If multiple instances run on one public address, assign non-overlapping ports and forward each pair to the correct machine.
Network checklist
- Confirm the server is listening on the intended UDP ports after startup.
- Allow the same ports in the operating-system firewall and any cloud security group.
- Forward them to the correct private address when using a home router.
- Check that the private address has not changed through DHCP.
- Test from outside the local network; a connection from the host itself does not prove that internet forwarding works.
Validate the upgraded server before opening it
- Start the server and wait for the ready message in the console.
- Read the startup log for the expected Build 42.20, 42.19, or
legacy41branch and for the intended server name. - Confirm that the configured ports match the firewall and router rules.
- Connect with an administrator account using a client on exactly the same branch and build.
- Create or load a test character, move through more than one area, interact with containers, and save.
- Stop the server cleanly, start it again, and verify that the test state persists.
- Test a normal player account so permissions and whitelist behavior are not masking a problem.
- Only after these checks invite the full player group.
Keep the old branch and the immutable backup available through at least one real play session. Set a rollback decision time in advance; otherwise a rushed fix can overwrite the only known-good copy.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Troubleshoot the common failed connections
“The server is not visible”
- Check that the server process reached its ready state rather than stopping during mod or map loading.
- Verify UDP 16261 and 16262, or the custom ports, in the host firewall, router, and cloud security group.
- Confirm that the router forwards to the current internal IP address.
- Test using the direct connection details supplied by the server instead of relying only on the public listing.
“The client says the build is different”
- Compare the branch selector on the server with the branch selected in the player’s Steam client.
- Make sure a client has finished downloading the update; a paused or partial download can leave old binaries.
- Check that the server did not silently return to stable after a panel restart.
- For a B41 world, select
legacy41; for a 42.19 world, select42.19. Do not attempt to solve a compatibility error by copying saves between branches.
“The server starts, then stops or throws mod errors”
- Temporarily disable all mods and restart.
- Re-enable only items with explicit B42 support, in small batches.
- Read the first mod-related error in the log; later errors can be cascading symptoms.
- Check dependencies and load order, and remove duplicate versions of an item.
“The old world will not load”
First confirm the world’s original branch. A Build 41 save belongs on legacy41; an Unstable 42.19 save belongs on 42.19. If the goal is 42.20, restore the backup to the old branch only to preserve or finish the old run, and create a separate 42.20 world. Do not repeatedly launch an incompatible save in the new branch, because each attempt can complicate diagnosis.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesSelf-hosting or managed hosting?
Self-hosting gives you direct control but makes you responsible for every operational detail. Managed hosting can reduce routine work, but you still need to verify that the service supports the required Build 42 branch and provides usable backups.
| Decision axis | Self-hosted server | Managed server |
|---|---|---|
| Branch and version pinning | You select SteamCMD or maintain the installation and can pin legacy41, 42.19, or stable 42.20 yourself. |
Convenient selector if offered; verify that the exact branches remain available and are not auto-updated. |
| Backup and restore | You design the schedule, destinations, retention, and restore test. | Ask whether backups include the complete Zomboid data tree, how often they run, how long they are retained, and whether you can download and restore them. |
| Files and logs | Full filesystem and console access, subject to your operating system. | Panel, FTP/SFTP, or log viewer access varies; confirm that saves, configs, and logs are downloadable. |
| Port forwarding | You configure the host firewall, router, and any cloud security group. | The provider usually exposes a port or handles the network layer, but you must still use the assigned values in client instructions. |
| Mod management | You control Workshop downloads, load order, and version pinning. | A panel may simplify IDs and restarts; verify that it supports Build 42 version-specific content. |
| Rollback speed | Fast only if you already have tested archives and scripts. | Potentially faster with snapshots, but snapshot scope and restore time must be confirmed. |
| Player capacity | Limited by your CPU, memory, bandwidth, and chosen settings. | Limited by the plan’s allocated resources and provider policy; no universal capacity follows from the hosting model. |
| Operating-system support | You choose a supported operating system and maintain updates. | Restricted to the provider’s images and control panel. |
| Recurring cost | Uses your existing hardware, electricity, and storage; the actual total depends on those resources. | A recurring fee applies; compare the included storage, backup retention, support, and resource limits rather than headline price alone. |
Whichever model you choose, ask one practical question before migrating: “Can I pin the branch and restore the complete data set without provider intervention?” If the answer is unclear, keep an independent backup and test the process before moving an established community.
Rollback and recovery plan
Rollback means returning the server and players to the exact branch and data set that worked before the change.
- Stop the new server cleanly and preserve its logs. Do not overwrite the pre-migration backup with the failed state.
- Reinstall or select the previous branch:
legacy41for Build 41 or42.19for an Unstable 42.19 world. - Restore the matching dated backup into a clean data directory.
- Restore the matching mod list and configuration, not the experimental 42.20 files.
- Start the server privately, connect with a test account, and verify that the expected world and player data are present.
- Tell players which branch to select before reopening access.
Keep the failed 42.20 logs separately. They can identify a mod, port, or configuration issue without risking the known-good world.
Free tools Windows power users keep installed
One-click scans. No signup required.
Player communication checklist
A short, precise announcement prevents most avoidable support requests. Include:
- The maintenance start and expected reopening time.
- Whether the community is continuing Build 41, finishing 42.19, or starting a new 42.20 world.
- The exact Steam branch players must select.
- Whether they must disable or update any mods.
- The server name and any changed direct-connection port.
- A clear statement that a new 42.20 world does not contain the Build 41 world.
- Instructions to let Steam finish downloading before launching the game.
After reopening, ask players to report the branch shown in their client, the first error message, and whether they can reach the server listing. That information is more useful than a general “it does not work” report.
Final decision
For an established Build 41 community, the safe choices are separate servers: keep the old world on legacy41, or launch stable 42.20 as a new world. For an Unstable 42.19 community, pin 42.19 until that run is complete. In every case, stop cleanly, back up the complete Zomboid data tree, validate the branch and mods on a disposable or copied instance, check UDP 16261 and 16262 (or the configured alternatives), and require every player to use the same build before reopening the server.
Quick Recap
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.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →
