Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsTo restart a Minecraft server without losing progress, announce maintenance, stop new activity, save the world, issue the server’s graceful stop command, wait until the process has fully exited, and then launch the same installation again. Java Edition normally uses the server’s existing Java startup command; Bedrock Dedicated Server uses its console save/stop commands and the existing Bedrock executable. Never start a second process against the same world directory.
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
What a safe Minecraft server restart actually does
A restart is a controlled shutdown followed by a fresh launch of the same server installation. It is different from closing a terminal window, killing a process, or launching another copy while the first one is still running. A graceful shutdown gives the server a chance to finish writing world data and close its files.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →The reliable sequence is:
- Tell players when maintenance will start and prevent new activity.
- Save the world with the command supported by your server software.
- Run
stopin the server console. - Wait for the process to exit and for the console or hosting panel to show that it is stopped.
- Launch the same server files with the existing startup script or command.
- Confirm that the expected world, software version, mods or plugins, and settings loaded before reopening the server.
Restart duration is not a universal number. World size, hardware, storage speed, mods, plugins, player activity, and the host environment all affect how long saving and startup take. Do not promise players a fixed downtime unless you have measured it for your installation.
Before you restart: a short safety checklist
Announce the maintenance window
Give players a clear start time and explain that they should log out before maintenance. If the server is public, temporarily stop new joins through the control panel, network access rule, allow-list, or maintenance message available in your setup. The objective is to avoid players changing the world while you are trying to save it.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Check that you are operating the correct installation
- Identify the world directory used by the running server.
- Confirm which Java server JAR or Bedrock executable the service starts.
- Note the active Minecraft version and the installed mod or plugin set.
- Make sure you have enough free disk space for world saves, logs, and any backup you intend to create.
- Keep the existing startup script or service definition; do not replace it with a guessed command.
If several Minecraft installations are present, write down the exact working directory before stopping anything. Starting the right executable from the wrong directory can make the server appear to load a new or empty world.
Create a backup when the data matters
A restart is not a backup. For a valuable world, copy or snapshot the world while the server is stopped, or use the backup facility supplied by your host. Keep the backup separate from the live world directory so an accidental overwrite does not remove both copies. If the server is already showing write errors or crashing, make a backup before attempting repair rather than repeatedly restarting it.
Recommended Free Tools
How to restart a Minecraft Java server safely
1. Use the server console, not ordinary client chat
Open the terminal, service console, or hosting-panel console attached to the Java server process. The console is the dependable place to issue administrative commands. A command typed into in-game chat may require permissions, a command prefix, or a plugin-specific interpretation, so use the server console whenever it is available.
2. Save the world
Run save-all if that command is exposed by your Java server implementation. Wait for the save confirmation or for the console to finish reporting the operation. Do not close the terminal immediately after typing the command; the save must complete before shutdown.
Some server wrappers and management tools provide their own save action. Use the action documented for the software actually running your world, and do not assume that a wrapper command has the same behavior as the vanilla server command.
3. Stop the process gracefully
After saving, enter stop in the console and press Enter. Let the server perform its shutdown sequence. A normal shutdown ends with the Java process returning to the shell, the service entering a stopped state, or the panel showing that the process is no longer running.
Do not press a terminal close button, send a forced kill, or reboot the host while the server is still writing data. A forced process termination can interrupt writes and leave the world less consistent than it was before the attempt.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
4. Wait for complete exit
Wait until the process has actually exited. A console that has stopped printing messages is not proof that the process is gone; check the service or panel status as well. Never launch another Java server against the same world directory while the first process might still have open files.
5. Relaunch the existing Java command
Run the installation’s established startup script or its existing Java command. The official Minecraft server download documentation describes command-line launching, but the JAR filename, working directory, Java version, memory settings, and optional flags vary by installation. Use your real command rather than copying a universal example:
java -jar <your-server-jar>
The angle-bracket text is a placeholder for the JAR name in your own server directory. Preserve any memory flags, nogui option, module flags, environment variables, or wrapper settings already used by your installation. Changing those at the same time as a restart can turn a routine maintenance operation into a version or performance problem.
Free tools Windows power users keep installed
One-click scans. No signup required.
6. Verify the Java server before reopening it
- Check that the expected world name and spawn area load.
- Confirm that the intended Minecraft version is running.
- Look for errors involving mods, plugins, permissions, or missing files.
- Connect with a test account and move, place, or break a harmless block.
- Check that essential commands and plugins respond normally.
Only announce completion after the test connection succeeds and the console is not reporting an ongoing startup failure.
How to restart Bedrock Dedicated Server
1. Save Bedrock game data
Bedrock Dedicated Server documents the save command for saving the current game. Its console also supports save-all; save-all flush writes chunks immediately. Microsoft notes that the flush operation freezes the server while it works, so players may stop moving or interacting until the operation completes. Use the flush form when an immediate chunk write is important, and warn connected players about the temporary freeze.
save-all
save-all flush
These are alternatives for the save step, not commands to run repeatedly without a reason. Wait for the save operation to finish before continuing.
2. Stop Bedrock Dedicated Server cleanly
Enter stop in the Bedrock server console. Microsoft’s command documentation defines /stop as stopping the server. In a dedicated-server console, use the command form accepted by that console; do not assume that an in-game chat command is equivalent.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Rank #3
- Fight your way through an all-new action-adventure game, inspired by classic dungeon crawlers and set in the Minecraft universe!
- Play with up to four friends or brave the dungeons alone. Battle new-and-nasty mobs across action-packed, wildly varied levels, in a quest to defeat the evil Arch-Illager!
3. Wait until the Bedrock process exits
Do not start the executable again while the original process is still shutting down. Confirm that the terminal has returned to the operating-system prompt or that the service manager or panel reports a stopped state. This prevents two processes from competing for the same world files.
4. Launch the same Bedrock installation
On a Windows installation following Microsoft’s setup example, the executable is named bedrock_server.exe. Start the executable from the same server directory and with the same service, script, permissions, and environment used previously. Do not substitute a different copy of the executable unless you are intentionally upgrading and have checked compatibility.
Microsoft’s current Bedrock Dedicated Server download information lists Windows and Ubuntu 22.04 or later support. Supported platforms and requirements can change, so check the current official download documentation when installing or migrating rather than treating those requirements as permanent.
5. Test the Bedrock world
- Verify that the intended world and player data are present.
- Check that the expected server version and resource or behavior packs load.
- Connect from a Bedrock client and perform a small world-changing test.
- Review the console for missing permissions, add-ons, or configuration errors.
Java and Bedrock restart workflows compared
| Item | Java Edition server | Bedrock Dedicated Server |
|---|---|---|
| Save step | save-all when exposed by the implementation |
save; save-all and save-all flush are documented console options |
| Shutdown step | stop in the server console |
stop in the dedicated-server console |
| Restart step | Run the installation’s existing Java command or startup script | Run the existing Bedrock executable, such as bedrock_server.exe on Windows |
| Important caution | JAR names, Java versions, memory flags, and wrappers differ by installation | save-all flush freezes the server while chunks are written |
| Official platform note | Use the current official Java server documentation for launch requirements | Current download information lists Windows and Ubuntu 22.04 or later; verify the live requirements |
The shared principle is more important than the command spelling: save, stop, wait, relaunch, and verify.
Changing server settings during a restart
Bedrock’s server.properties
Bedrock Dedicated Server stores most server options in server.properties, an INI-style text file made of key=value lines. Stop the server before editing it whenever practical. Make one deliberate change at a time, save the file, and then restart so the process reads the updated values.
Preserve the key names, equals signs, and value spelling. Keep a copy of the previous file so you can restore it if the next launch fails. A malformed line, unsupported value, or setting intended for another server version can prevent startup or produce behavior different from what you expected.
Not every administrative change requires a full restart
Some allow-list or administrative files have their own reload command or can be changed through a management interface. Follow the command documentation for that specific feature. Do not imply that every edit to an administrative file requires stopping the entire world, and do not assume that a reload applies to ordinary server.properties settings.
Rank #4
- 8,800 MINECOINS — Get 8,800 Minecoins to spend on creator-made content in the Minecraft Marketplace.
- MINECRAFT MARKETPLACE — Browse a constantly updating library of content from Minecraft creators, with new content available every week.
- CREATOR-MADE CONTENT — Use Minecoins to get Marketplace content such as skin packs, mash-up packs, mini-games, and adventure maps.
- ACCESS ACROSS DEVICES — Once redeemed and linked to your Microsoft account, your Minecoins and purchases are available on supported devices that run Minecraft, including Android, iOS, Windows, and Xbox.
- A GIFT FOR PLAYERS — Give Minecraft players Minecoins to spend on content in the in-game Marketplace.
Java configuration and mods
Java servers may read settings from configuration files, wrappers, mods, or plugins. Stop the process before changing files that the running software may be writing. If you change a mod, plugin, server JAR, or Java runtime at the same time as the restart, treat the operation as a change deployment: keep a backup, record what changed, and be prepared to restore the previous set if the server does not load.
Using a hosting panel or a managed service
Many managed hosts expose a Restart button that automates a stop-and-start cycle. Panel labels and behavior differ: some buttons send a graceful stop first, while others may immediately restart a service wrapper. Read the provider’s documentation and confirm that the old process reaches a stopped state before a new one starts.
Even with a button, use the same operational checks:
- Warn players and pause new activity.
- Use the panel’s save, console, or backup function if available.
- Choose the documented restart action.
- Watch the status and console until shutdown and startup both complete.
- Test the world with a player connection.
A panel is an interface, not a guarantee of safe data handling. Verify its backup retention, supported Minecraft edition, restart behavior, and permissions before relying on it for a valuable world.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Minecraft Realms and other hosted worlds
Realms and other fully managed worlds do not expose the same local Java or Bedrock process controls. Use the restart, reset, download, or restore options that the service actually provides. Do not apply local-console commands to a hosted world that does not give you a server console. If the service offers no restart control, contact its support channel or use its documented maintenance workflow instead of attempting to run a second copy elsewhere.
What to do when the server will not stop
First response: capture evidence
Copy the console error and note the command you issued, the time, and whether the server was saving. Check available disk space and file permissions. If a panel reports a timeout, save its event or log entry before trying another action.
Try a graceful recovery before forcing termination
- Wait a reasonable interval if the world is large or a Bedrock flush is in progress.
- Check whether the process is still using CPU or disk; activity may indicate that saving is continuing.
- Issue the documented
stopcommand once more only if the console is responsive and the first command was not accepted. - Ask the host or service manager for its documented graceful-stop procedure.
Use a forced process kill only as a last resort when the process is unresponsive and you have accepted the risk. It can interrupt writes and leave the world in a less consistent state. Afterward, make a backup of the resulting files before attempting repairs or another launch.
If the server starts and immediately stops
Read the complete startup log instead of clicking Restart repeatedly. Common operational causes include a crash, an incompatible mod or plugin, an invalid configuration value, insufficient resources, missing files, incorrect permissions, or a server-version mismatch. Revert the most recent change, test with the previous known-good configuration, and change one variable at a time.
If players see a new or empty world
Stop the server and inspect the working directory and world setting. Starting from a different directory, changing the world name, or launching a different installation can make the server create or open another world. Do not let players build in the unexpected world while you investigate. Restore the intended startup path and confirm the original world directory before proceeding.
If the world appears damaged
Stop all server processes, preserve the current files, and work from a copy. Check the logs for the first read or write error. Restore a known-good backup only after verifying that it belongs to the same edition and world. If no backup exists, obtain specialist assistance rather than repeatedly launching and stopping the damaged copy.
Automation and scheduled restarts
Automatic restarts can reduce maintenance work, but a loop of stop-and-start actions is not a fix for a failing server. Schedule maintenance only after confirming that the script or panel performs a graceful save and stop, waits for process exit, and launches the intended installation from the correct directory.
For an automated job, include these safeguards:
- Announce the maintenance window before the stop command.
- Prevent overlapping runs so two server processes cannot start together.
- Record exit codes and console logs.
- Wait for a stopped state before launching.
- Alert an administrator after a failed startup instead of retrying forever.
- Keep backups independent of the restart script.
Repeated automatic restarts usually point to an underlying crash, incompatible mod or plugin, bad configuration, or resource problem. Diagnose the log and correct the cause rather than hiding it with shorter restart intervals.
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 minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Post-restart verification checklist
Use this checklist before telling players that maintenance is complete:
- The console or panel shows one running server process, not two.
- The expected world directory and world name are loaded.
- The intended Java or Bedrock version is running.
- Mods, plugins, packs, permissions, and allow-list behavior are present.
- A test player can connect and move through the world.
- A harmless block change or inventory action persists after a test save.
- The log contains no unresolved startup or storage errors.
- Players receive a clear all-clear message.
If any check fails, keep the server closed to normal players, preserve the logs and current files, and investigate before making further changes.
Restart commands at a glance
| Purpose | Java server | Bedrock Dedicated Server |
|---|---|---|
| Save | save-all, when supported by the implementation |
save or save-all |
| Force immediate Bedrock chunk write | Not established as a universal Java command in this guide | save-all flush; the server freezes while it runs |
| Graceful shutdown | stop |
stop |
| Start again | Existing Java startup script or command | Existing Bedrock executable, for example bedrock_server.exe on Windows |
Commands must be entered in the server console that accepts them. The exact launcher, file paths, service account, and options belong to your installation and should not be replaced with a one-size-fits-all command.
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.




