Direct answer

If Java prints “Could not create the Java Virtual Machine,” inspect the startup arguments first: a malformed flag, unsupported option or incompatible Java runtime can stop Java before the Minecraft server loads.

What it means

This error occurs during JVM startup. It is not proof that the Minecraft world, plugins or server JAR is corrupt; the decisive details are usually in lines immediately above the generic message.

If you are a player

  • If using a host panel, copy the exact Java executable/argument fields and the first error line.
  • Do not delete a world or plugins in response to a JVM startup flag error.

If you run the server

  1. Run java -version with the same Java executable the startup script uses.
  2. Inspect -Xms, -Xmx, flags copied from other Java releases and unnecessary quotation marks.
  3. Test a simple launch such as java -Xms1G -Xmx2G -jar server.jar nogui only when the real JAR filename and available RAM permit it.
  4. Reintroduce custom JVM flags one at a time after the basic command starts.

Confirm the fix: The JVM should reach Minecraft startup logging without printing an unrecognized or improperly specified option. Do not assume the newest Java supports every old flag.

Current Paper Java requirements

Paper currently documents Java 21 for Paper 1.20 through 1.21.11 and Java 25 for Paper 26.1+. Other server software or older Minecraft versions can require a different Java release, so check that project’s exact version table.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000