What is causing the ‘Java was started but returned exit code =12’ error?
We investigated this particular issue by looking at various user reports. Based on what we gathered, there are several fairly common scenarios that are known to trigger this particular error message: If you’re struggling to resolve this particular error message, this article will provide you with a list of quality troubleshooting steps. Below you have a collection of methods that other users in a similar situation have used to get the issue resolved. For the best results, follow the methods below in order that they are presented until you encounter a fix that is effective in getting fixing the problem in your particular scenario
Method 1: Using the correct combination of Eclipse – JDK
Eclipse and JDK (Java Development Kit) are very picky when it comes to working with one another. Keep in mind that there are only several working combinations of OS, JDK and Eclipse bitness. If you happen to use an unsupported combination, of Operating System, JDK and Eclipse, you will get the Java Was Started but Returned Exit Code=13 Eclipse error message. Below we’ve compiled a list of working combinations. Use them for reference to verify whether is issue occurs due to an unsupported combination:
32-bit OS, 32-bit JDK, 32-bit Eclipse (32-bit only)64-bit OS, 64-bit JDK, 64-bit Eclipse (64-bit only)64-bit OS, 32-bit JDK, 32-bit Eclipse
If you have a different setup, uninstall the unsupported component and then install an appropriate one until you are able to open Eclipse without encountering the error message. Note: In the event that you don’t know the bit architecture of your operating system, press Windows key + R to open up a Run dialog box. Then, type “msinfo32” and press Enter to open the System Information screen. In the System Information screen, go to System Summary and check up the System Type from the right pane. That’s where you’ll find your OS architecture. If this method wasn’t applicable, move down to the next method below.
Method 2: Removing special characters from the Eclipse directory path
You might also be encountering the issue because the installation directory contains special characters. Several users who were in a similar situation have managed to get the issue resolved after eliminating the special characters (@#$%^&()+) from the directory name. By default, you should be able to find Eclipse in C:\IDE\eclipse or in C:\Users*YourUsername\eclipse. However, if you installed in a custom location, you might have mistakenly added a special character that is creating the issue. You can remedy the issue by navigating to the location of the Eclipse installation manually and removing any special character that might end up creating the error message. Note: Certain users have reported that they started getting a different error after removing the special characters from the Eclipse installation directory. This is most likely occurring because there are other dependencies that were relying on that particular location and they no longer function properly due to the change. In this case, you can resolve the problem entirely by reinstalling Eclipse. If this method didn’t allow you to resolve the Java Was Started by Returned Exit Code=13 Eclipse error, move down to the next method below.
Method 3: Removing the broken System PATH variable
As it turns out Java 8 and a few other Java updates have the potential to mess up the environment variables, triggering the Java Was Started but Returned Exit Code=13 Eclipse error message. If you only started to get this error message after installing Java (or a Java update), follow the steps below to remove the broken System variable PATH: If you’re still encountering the same error message, move down to the next method below.
Method 4: Reinstalling the JAVA JDK
If you’ve come this far without a result, you can probably resolve the issue by clean installing the latest JAVA JDK version. Several users finding themselves in a similar situation have reported that the Java Was Started but Returned Exit Code=13 Eclipse error was finally resolved after they uninstalled their current JDK and they installed the latest version available. Here’s a quick guide on how to do this:
Fix: “Exit Code: 1” Crash Error on Minecraft Java EditionHow to Fix ‘Sub-process /usr/bin/dpkg returned an error code (1)’ Error while…Star Wars: Eclipse To Feature an All-New Race And The Game Will Revolve Around a…Quantic Dream Reportedly Leaked for Gamescom 2022, Possibility for Star Wars…
