Updating a Minecraft server safely is a controlled replacement of the server software, not a simple file overwrite. First identify whether the installation is Java Edition or Bedrock Dedicated Server, record the current version and extensions, stop the server cleanly, and create a separate backup. Then install the new release beside the old one, verify runtime or operating-system requirements, start it against the existing world, inspect the logs, and test with a client running the matching version.
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
The procedure differs substantially by edition. Java Edition uses an official server JAR and a compatible Java runtime. Bedrock Dedicated Server uses an operating-system-specific package that you extract and launch with its included executable. In both cases, keep the old executable and an untouched backup until players can connect and the important game features work.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What “latest version” means for a Minecraft server
Minecraft Java and Bedrock releases do not share one universal server file. The correct download depends on the edition, and the current release number changes over time. Use Minecraft’s official server-download page and release-changelog index to identify the release available when you perform the maintenance; do not build an evergreen procedure around a fixed filename or version number.
A server update can also involve more than the vanilla executable. A Java installation may run a fork such as Paper, Fabric, Forge, or another server implementation, with plugins, mods, datapacks, a proxy, and custom startup settings. Those components have their own compatibility requirements. Replacing only the underlying JAR does not make third-party extensions compatible automatically.
#1 Best Overall
| Installation | Update package | Requirements to check | Connection consideration |
|---|---|---|---|
| Java Edition | Official Java server JAR, or the new build of the fork you actually run | Compatible Java runtime, memory settings, plugins, mods, datapacks and proxy | Players need a Java client matching the server release |
| Bedrock Dedicated Server | Official package for Windows or Linux, extracted into an empty folder and launched with its executable | Supported operating system, storage, memory and configuration files | Protocol compatibility typically changes when the minor Minecraft version changes |
Before you update: record the installation
Write down the details below before touching the live directory. This inventory makes it possible to reproduce the current setup or roll back without guessing.
- Edition: Java or Bedrock Dedicated Server.
- Current Minecraft/server version and the date of the last successful start.
- Server implementation: vanilla, Paper, Fabric, Forge, another fork, or the Bedrock executable.
- Operating system and architecture.
- Java version and the exact startup command, if this is a Java server.
- World folder names and the location of
server.propertiesor Bedrock configuration files. - Installed plugins, mods, datapacks, resource packs, proxy software and permission settings.
- Port, firewall, service-manager and scheduled-task settings.
- Custom launch flags, memory limits and environment variables.
Also check whether the world has recently been opened by a snapshot, development build or modded loader. A newer server can convert world data in a way that an older build cannot safely reverse, so the version you are upgrading from must be known.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsStop the server and make a restorable backup
Announce a maintenance window before stopping the process. Players should know when connections will fail and when they can try again. Use the server’s normal shutdown command or the service manager that owns the process, then wait until the save completes and the process exits. Never replace an executable or copy a world while the server is actively writing region, player or configuration files.
Create the backup outside the live server directory. The safest option is a complete copy of the server folder, including worlds, configuration, logs, libraries and extension directories. If storage is limited, at minimum preserve every world folder plus the configuration and plugin/mod directories required by that installation; a complete copy is preferable because it captures the exact executable and settings needed for rollback.
- Stop the server normally and confirm that no server process remains.
- Copy the required data to a separate disk or directory that the update cannot overwrite.
- Label the copy with the old version and date, such as
survival-backup-1.21.x-2026-10-14. - Check that the world directories contain their region files and that the copy can be opened or listed independently of the live directory.
- Do not treat a backup made inside the same directory as a rollback plan; a failed update could modify or delete it.
Minecraft publishes separate Java and Bedrock guidance for backing up worlds. Follow the instructions for the edition you operate, and retain the untouched copy until the new release has passed a real player test.
Check the target release and host requirements
Obtain the new server software from Minecraft’s official download source and use the official changelog index to confirm which Java and Bedrock releases are current. Download the file into a new staging directory rather than replacing the production executable immediately.
Java runtime requirements
A Java server needs a compatible Java Runtime Environment. Runtime requirements can change between Minecraft releases. For example, the Minecraft Java Edition 26.1 release notes state that the game now requires Java 25. That requirement applies to that release; a later release may require a different runtime. Check the release notes at update time, then verify the installed runtime with java -version before launching the new JAR.
If the command reports an older major version, install the required runtime and update the service or scheduled task to use the intended Java executable. Do not assume that changing the interactive shell’s PATH also changes a system service’s environment. Test the exact command used by the service account.
Bedrock operating-system requirements
The current Bedrock Dedicated Server download requirements list Ubuntu 22.04 LTS or later for Linux. For Windows, the listed minimum is Windows 10 version 10.0.15063 or Windows Server 2016 or later. The same requirements section lists 4 GB of RAM and between 180 MB and 1 GB of available storage. These are published software requirements, not a promise that every world or player count will perform well at those limits; leave additional headroom for the operating system, backups and the world itself.
How to update a Java Edition server
1. Stage the new JAR
Download the current Java server JAR, whose filename follows Minecraft’s versioned naming pattern, into a new folder. If you run a fork, download the compatible build of that fork instead of silently switching to vanilla. Keep the old JAR in the original installation and give the staged file a clear name.
Do not copy a new JAR over a running process. A live process may continue using some files while the replacement changes others, producing an incomplete or misleading startup.
2. Check extensions before the first start
Read the target release notes and the compatibility notes for every plugin, mod, proxy and datapack. Remove or update components that explicitly do not support the target version, but keep a copy of the old extension set in the backup. A server can appear to start while a critical plugin has failed to load, so compatibility review is required even when the vanilla JAR itself is valid.
Rank #3
- The classic UNO card game builds fun on game night with a Minecraft theme.
- UNO Minecraft features a deck and storage tin decorated with graphics from the popular video game.
- Players match colors and numbers to the card on top of the discard pile as in the classic game.
- The Creeper card unique to this deck forces other players to draw 3 cards.
- Makes a great gift for kid, teen, adult and family game nights with 2 to 10 players ages 7 years and older, especially Minecraft and video game fans.
3. Point the startup command at the staged file
Use the same memory and service settings that worked before unless the release notes or your capacity planning require a change. A typical direct launch has the form:
java -Xms2G -Xmx4G -jar minecraft_server.NEW_VERSION.jar noguiReplace the filename and memory values with those appropriate to your installation. If a system service, container or script starts the server, edit that definition rather than launching a second copy manually. Ensure the working directory is the folder containing the world and configuration files; otherwise the server may create a new empty world in an unexpected location.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →4. Start once and read the complete log
Start the new build while the maintenance window is still closed to players. Read from the beginning of the startup log through the final ready message. Look for Java-version errors, missing libraries, failed plugin or mod loads, data conversion messages, invalid properties and port-binding failures.
Confirm that the expected world name and seed-related files are loaded. If the server creates a new world, stop immediately: the working directory, world setting or permissions are probably wrong. Do not continue playing in the accidental world and assume the original will reappear later.
5. Test the world and extensions
After the server reaches its ready state, connect with a Java client running the same release. Test login, movement, inventory access, permissions, commands and the features that matter to your community. For a modded or plugin-heavy installation, exercise at least one feature supplied by each critical extension and inspect the log for repeated warnings.
How to update a Bedrock Dedicated Server
1. Download the correct package
Select the package for the host operating system from the official Bedrock Dedicated Server page. Windows and Linux packages are different; do not extract a Windows package on Ubuntu or a Linux package on Windows. Verify that the host meets the listed operating-system, memory and storage requirements before scheduling downtime.
Rank #4
- Now Minecraft lovers can play a special version of UNO!
- Same as Basic UNO but features Minecraft characters and includes special Creeper rule card. Draw this card and the other players have to draw three more cards from the pile!
- The goal is to get rid of all the cards in your hand.
- First player or team to 500 wins.
- When you're down to one card, don't forget to yell "UNO"!
2. Stop, back up and create an empty staging folder
Stop the Bedrock process with its normal shutdown method and wait for the save to finish. Make a separate backup of the world folders and configuration, or copy the complete server directory. The official Bedrock instructions describe extracting the ZIP into an empty folder. Use a new folder for the update so the previous executable and files remain available.
3. Extract and preserve configuration
Extract the new package into the empty staging folder. Compare the supplied configuration files with the copies from the old installation and carry over only the settings you intentionally use. Keep the original files in the backup; do not blindly overwrite a new configuration with an obsolete one if the release adds or changes options.
Move or copy the world data into the location expected by the new package, or point the configuration at the existing world according to the Bedrock setup instructions. Confirm file ownership and execute permissions on Linux, and confirm that the Windows account running the service can read and write the folder.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
4. Launch the included executable
Start the platform’s included Bedrock executable from the staging directory, using the same service manager and network settings as before. Watch the console and log for missing libraries, permission failures, invalid configuration, port conflicts and world-loading messages. A successful process launch is not enough: verify that the intended world, ports and settings are actually active.
5. Test with a matching Bedrock client
Microsoft’s Bedrock documentation says protocol compatibility typically changes when the Minecraft minor version changes; it gives 1.21.0 and 1.20.0 as incompatible examples. Update the client before testing if it is on an older minor release. Join the server, check inventories and permissions, and exercise the gameplay systems your players use most.
Client and server version errors
A message such as “outdated client,” “outdated server,” or a protocol mismatch usually means the two sides are not on compatible releases. First record the server’s reported version from its startup log, then check the client’s version on its title or profile screen. Update the older side, restart the client if necessary, and try again.
- For Java, use a client release matching the server release and make sure the selected mod loader and mod set are compatible.
- For Bedrock, pay particular attention to minor-version changes because protocol compatibility commonly changes at that boundary.
- Do not “fix” a mismatch by deleting the world or changing random configuration values; version alignment is the first diagnostic step.
- If only one player fails while others connect, compare that player’s edition, version, installed mods and network path with a working client.
Verification checklist before reopening the server
Use a deliberate acceptance test instead of relying on the absence of a crash.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- The process remains running for several minutes with no repeating fatal or compatibility errors.
- The expected world and dimension folders load, and the world’s recent builds and player inventories are present.
- A client on the matching release can connect, move, disconnect and reconnect.
- Login permissions, operator status, command restrictions and whitelist behavior are correct.
- Containers, inventories, redstone or other mechanics central to the server work as expected.
- Plugins, mods, datapacks and proxies report successful loading and provide their critical features.
- Network ports, firewall rules, scheduled tasks and service restart behavior remain correct.
- The new logs are being written to the intended directory and disk space remains sufficient.
Only after these checks should you announce that the maintenance is complete. Keep the old executable, old extension set and untouched backup until the server has operated normally for a period that is meaningful for your community.
Rollback when the update fails
Rollback is safest when the new process has not been allowed to write further changes to the only copy of the world.
- Stop the updated server and confirm that it is no longer writing files.
- Preserve the failed update directory and its logs for diagnosis.
- Move the updated world directory or entire staging folder out of the live path.
- Restore the untouched backup made before the update; never restore files produced by the failed release over that backup.
- Relauch the previous executable with the previous Java runtime, service definition and extension set.
- Connect with a client matching the old release and verify that the world and key functions are back.
If the old server refuses to open a world after an attempted conversion, stop experimenting on that copy. Restore the pre-update backup again and investigate the failed release using a disposable copy. Keeping the old executable and backup separate is what makes this recovery possible.
Troubleshooting common update failures
| Symptom | Likely cause | Action |
|---|---|---|
| Java reports an unsupported class version or refuses to start | The installed Java runtime is older than the target release requires | Check the release notes, install the required runtime, verify java -version under the service account, and relaunch. |
| The server starts but generates a new world | Wrong working directory or world setting | Stop it, confirm the service’s working directory and world configuration, then restore the original world path before starting again. |
| “Outdated client” or protocol error | Client and server releases are incompatible | Update the client to the server’s release, with special attention to Bedrock minor-version changes. |
| Port already in use | The old process is still running or another service owns the port | Stop the old process, identify the listener with the operating system’s network tools, and start only one server on the configured port. |
| Plugins or mods are disabled or throw errors | The extension does not support the target Minecraft or loader version | Use the extension’s compatible build, remove it temporarily for isolation, and restore the prior set if you roll back. |
| Bedrock executable will not launch on Linux | Unsupported distribution, missing execute permission or incorrect package | Confirm Ubuntu 22.04 LTS or later is used, extract the Linux package, set the expected permissions, and review the console output. |
| Players can connect but settings or permissions changed | Configuration was overwritten, omitted or read from another directory | Compare the active path and configuration with the inventory made before maintenance, then restore intended values from the backup. |
| World loads slowly or the host runs out of memory | Insufficient headroom for the world, extensions or operating system | Check memory allocation, available disk space and extension behavior; do not treat the published minimum requirements as a performance guarantee. |
Choosing self-managed updates or managed administration
Self-hosting gives you direct control over files, configuration, backups, Java versions and extension testing, but you are responsible for downtime, security updates, storage and recovery. A managed Minecraft host can reduce routine administration and may provide automatic backups, but you must still verify its supported edition, release timing, backup retention, access to files and rollback process. The right choice depends on whether you want to operate the server infrastructure or delegate those tasks; neither option removes the need to match client and server versions.
Crashes, 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 minuteWindows 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 reinstallKeeping future updates safe
- Maintain a dated backup outside the live directory before every release change.
- Keep a short inventory of the active version, runtime, executable, world path and extensions.
- Use a staging folder and test server starts before reopening public access.
- Read release notes for runtime, protocol and world-conversion changes instead of assuming a minor update is risk-free.
- Retain the previous executable and backup until real player connections and critical gameplay checks pass.
- Document the exact service command so another administrator can stop, restore and relaunch the installation without guesswork.
The reliable pattern is simple: identify the edition, back up first, install beside the old build, satisfy the current requirements, test with a matching client, and keep rollback available. Following that sequence updates the software while preserving the world and giving you a controlled recovery path if the release or an extension is not ready.
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.
