Several users struggling to resolve the same issue have managed to get the issue resolved after forcing the main Java executable (java.exe) to open with administrative privileges. Method 2: Opening java.exe with admin rights If you’re still seeing the same error message at the start of the application, try adding the Java Bin path which might be similar to “%\USER PATH\Java\jdk1.6.0_39\bin” to the environment variable as indicated in the above method and see if that works.
At the next startup, open the application that was previously showing you the Could Not Create the Java Virtual Machine error and see if is now functioning properly.Ĭreating a System Variable called _JAVA_OPTIONS and assigning it the value Xmx512M.
Close the previously opened windows and restart your machine to enforce the changes.Inside the New System Variable window, set the Variable name to _JAVA_OPTIONS and the Variable value to – Xmx512M and click Ok to save the changes.In the Environment Variables window, click on New (under System Variables).Inside the System Properties screen, go to the Advanced tab and click on Environment Variables.Then, type “ sysdm.cpl” and press Enter to open up the System Properties screen. Press Windows key + R to open up a Run dialog box.Here’s what you need to do to add a _JAVA_OPTIONS entry in System Variables to enlarge the global maximum heap memory size: Several users encountering the same issue have reported that the issue was resolved entirely after they performed the steps below. This will resolve any error message that occurs because the started Java application’s maximum heap memory size is larger than the one set as the System Variable. What this essentially does is it sets the global maximum heap memory size for Java. Most affected users have managed to get the issue resolved by creating a System Variable for Java called _JAVA_OPTIONS and setting it’s value to Xmx512M. Method 1: Adding the _JAVA_OPTIONS to System Variables To ensure the best results, follow the methods below in the order that they are presented until you discover a method that is effective in resolving the error for your particular scenario. Below you have a collection of methods that other users in a similar situation have used to get the issue resolved. If you’re currently looking for a way to resolve the, Could Not Create The Java Virtual Machine error, this article will provide you with several verified troubleshooting strategies. Java executable and/or application require administrative privileges – This might happen with applications that need admin access in order to function properly.Java global maximum heap memory is not high enough – One of the most common causes of why you can encounter this particular error is if you try to start a Java application with a maximum heap memory size larger than the one set as the System Variable.Java is invoked by the wrong arguments or options – This can occur if you’re running a home-brewed application or you’re trying to open an open-source application that is known to cause system instability.I tried to find on Google but found nothing useful or MC related. WARNING: Unknown module: specified to -add-opensĮxception in thread "main" : Module not found, required by Īt java.base/.findFail(Resolver.java:893)Īt java.base/.resolve(Resolver.java:192)Īt java.base/.resolve(Resolver.java:141)Īt java.base/.resolveAndBind(Configuration.java:492)Īt java.base/.resolveAndBind(Configuration.java:298)Īt .main(BootstrapLauncher.java:83) WARNING: Unknown module: specified to -add-exports I have no crash log and the Game Output tab in my laucher gives me only this:
I deleted everything again and tried with a few earlier versions of Forge, with no success. I deleted the MC folder and reinstalled it.
I was playing vanilla MC 1.17.1 no problem until I decided to test some new mods, so I did as always did back in 1.7.10 and tried to install the lastest compatible Forge version (37.0.111) and, to my surprise, it crashes.