Minecraft could not create the Java Virtual Machine: how to fix

The error 'Could not create the Java Virtual Machine. A fatal exception has occurred.' appears when Minecraft fails to initialize Java due to bad, syntax-errored, or oversized JVM arguments.

Common causes

• Bad or misspelled custom JVM startup arguments.
• Oversized maximum memory allocation flag (-Xmx) exceeding physical RAM.
• Using 32-bit Java with memory flags higher than 1.5 GB.
• Leftover or obsolete JVM arguments remaining after launcher updates.

How to fix

1. Reset custom JVM arguments — Open launcher options and clear or reset custom JVM arguments to default.
2. Set -Xmx between 2G and 4G — Set maximum heap memory allocation flag to a reasonable range like -Xmx2G or -Xmx4G.
3. Use 64-bit Java — Install and select 64-bit Java to allow proper heap allocation.
4. Remove leftover args — Clean up leftover or deprecated flags remaining after launcher updates.
5. Check system variables — Delete _JAVA_OPTIONS from system environment variables if set.
6. Relaunch Minecraft — Save settings and start the game to confirm JVM creation.

If nothing helped

If nothing helped, please reach out to our support team at support@superlauncher.org or visit our Help Center.

Frequently Asked Questions

What causes 'Could not create the Java Virtual Machine' in Minecraft?

It is caused by invalid JVM arguments, setting -Xmx higher than physical RAM, using 32-bit Java, or leftover launch flags.

What is the correct -Xmx setting for Minecraft?

For standard Minecraft, setting -Xmx between 2G and 4G (2048M to 4096M) provides optimal balance without crashing JVM initialization.

Why does 32-bit Java break JVM creation?

32-bit Java cannot address more than ~1.5 GB of heap space. Setting higher values causes immediate JVM creation failure.

How do I reset JVM args in SuperLauncher?

Go to launcher settings, locate Java / JVM arguments, clear custom strings, or press 'Reset to Default'.