We Keep Coding

java was started by returned exit code=13 eclipse [duplicate]

I just append
-vm
C:\Program Files\Java\jre6\bin\javaw.exe
in eclipse.ini then I try to start eclipse again and got this error. Give me how to solve or link that actually solve it.
this is my eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.1.R36x_v20100810
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize 256m
--launcher.defaultAction
openFile
-vm
C:\Program Files\Java\jre6\bin\javaw.exe
-vmargs
-Xms40m
-Xmx384m
Thank you

I had the same error when configuring eclipse.ini to use JRE6. Turns out I caused this error by incorrectly configuring eclipse to use the 64 bit JVM while running a 32 bit version of eclipse 3.7.
The correct configuration required the eclipse.ini -vm argumument to use "C:/Program Files (x86)/" instead of "C:/Program Files/".
Make sure that the JVM version (32/64 bit) you use matches the eclipse version (32/64 bit).

It may just be the way the error shows (and not how it is written in the eclipse.ini file), but there is text in Eclipse.ini (Specifying the JVM) that says the following:
The -vm option and its value (the path) must be on separate lines.
The value must be the full absolute path to the Java executable, not just to the Java home directory.
The -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the JVM

Look at the second line of the message box. There you can see which java runtime in fact is started. Mine was suddenly C:\ProgramData\Oracle\Java\javapath\javaw.exe. This happened after I have installed a "chrome java updater" (Chrome browser moaned: 'your java is outdated, you have to update...').
Before this "chrome java update" my eclipse (luna jee x64) started without error. Looking closer to the background I detected following: the chrome java updater (notabene started from an Oracle site) added C:\ProgramData\Oracle\Java\javapath in front of the env var PATH. It contains three symbolic links to the newest java 8 JRE installation in (x86) program folder -> hence to a 32 bit java JRE. Oracle replaces with Java8 the old technique having the symlinks in system32 (64bit) resp. SysWOW64 (32bit).
Meanwhile I learned. Whatever java installer you have executed last (the *.exe) leads windows to remember that java flavour (32b or 64b), with the result that after an update the links in C:\ProgramData\Oracle\Java\javapath point to a java installation of the remembered flavour. If you have a 64b eclipse installation and encounter the described error: just re-install the newest 64b JDK. After that the java updates do no more link to a 32b version. And eclipse 64b will start correctly without the entry in eclipse.ini .

You need to check if your PC has a 64-bit or 32-bit operating system, then same goes for your JDK (64-bit/32-bit) and also for Eclipse (64-bit/32-bit).
Make sure they are all the same; if not, you need to download the one that matches your bitness.

For Eclipse:
Added this two lines in eclipse.ini
Second line represents the JDK location of the javaw.exe file.
-vm
C:\Program Files\Java\jdk1.7.0_60\bin\javaw.exe
Note: place -vm lines before -vmargs, otherwise default location is taken.
For STS
Change the same as above in STS.ini

I just hit this too. Turns out that at least for me, this was due to trying to use a win64 version of the JRE with a win32 Eclipse. I seems that win32 Eclipse requires a win32 Java (what is called -586 in the list of Java installers from Oracle/Sun).
The reason I was using both is that I was trying to pinpoint a bug that only manifested itself in 64-bit Eclipse, so I needed a 32-bit to compare to.
Once I installed BOTH the "x64" (win64) and "i586" (win32) versions of the JRE on my machine, things work fine and no error 13. You can apparently have both installed at the same time.

The error means it's the wrong JVM version for that version of Eclipse. The link has more details:
http://www.ehow.com/how_4784069_terminated-exit-code-error-eclipse.html

Make sure the Eclipse and the Java that you are using are both either 32-bit or 64-bit.
You cannot run 64-bit eclipse with 32-bit JRE.
java -version
Java HotSpot(TM) 64-Bit Server VM
The 32 bit version JRE will not have 64-Bit in it.

I just had the same issue, and spend about an hour trying to solve the problem.
In the end it was a '#' character in the path.
So I renamed "C:\# IDE\eclipse 3.7\" to "C:\+ IDE\eclipse 3.7\" and that solved the problem.

Recently I faced same issue.My version of eclipse didnt support java version 8.
I had accidently installed jre 8 on my machine which automatically updated my PATH variable by appending "C:\ProgramData\Oracle\Java\javapath" in the beginging which led eclipse to pick up this version(and ignore the manually added 1.6 version which came later in order)and crash with exit code 13.
I just removed this string from the path so which led system to pick up my older version and eclipse started just fine.

I had the same issue with eclipse in my both machine. I had jre 32 bit installed. So I removed 32 bit and installed 64 bit instead and it worked perfectly.

simply install 64 bit version of JAVA from http://java.com/en/download/manual.jsp
and uninstall older version if prompted by the 64 bit installer

Go to the folder where you saved Eclipse. Look in the configuration folder at the startup log. It will give you a much better diagnostic than "exit code 13".

After java update, eclipse will not start because default jdk location has changed. Adding the following lines to eclipse.ini file solved my problem immediately:
-vm
C:\Program Files (x86)\Java\jdk1.7.0_75\bin\javaw.exe
I added these lines just before vmargs. It looks like as the following :
...
--launcher.defaultAction
openFile
-vm
C:\Program Files (x86)\Java\jdk1.7.0_75\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx512m
For more information on eclipse.ini, visit this the site http://wiki.eclipse.org/Eclipse.ini#-vm_value:_Windows_Example
In my case, i use 32 bit eclipse and java. If you installed both 32 bit and 64 bit versions of java, be careful to choose the right version. For 64 bit versions, refer to the javaw.exe file under the directory
C:\Program Files\Java\jdk1.8.0_60\bin

Whenever you see this error, go to Configuration directory and check for a log file generated just now. It should have proper Exception stacktrace. Mine was a case where I got an updated 32-bit JRE (or JVM) installed which was the default Java that got added to the Path. And my Eclipse installation was 64-bit which meant it needed a 64-bit VM to run its native SWT libraries. So I simply uninstalled the 32-bit JVM and replaced it with a 64-bit JVM.
I wonder if they will improve this reporting mechanism, instead of silently generating a log file in some directory.

This error occurred to me on ubuntu, having installed 32bit and 64bit java. Use
sudo update-alternatives --config java
to set the right version to use as default.

Just uninstalled jre-32 bit version and It worked fine for me.

I was using Eclipse Juno and I didn't remember if it was 32 or 64 bits. I installed Java 32 bits and that's why it failed. I then installed Java 64 bits and Eclipse Juno is working again.
I also removed any java or jre reference in my environment variables (PATH).

In my opinion the most answers here regarding different architectures of Eclipse and Java are simply wrong and this can be easily checked using e.g. Process Monitor under Windows. The -vm option is there to run a specific version of java and the point of it is, that the configured process is started and runs all the Java code on its own, that's why you configure up to java.exe. In that case you DON'T need to have the same architecture for Eclipse and Java, but can happily mix both 32 Bit and 64 Bit. You only CAN'T mix both, if you DON'T use -vm, but let Eclipse load Java natively into its own process using jvm.dll and such. That latter behavior is Eclipse's default, but not the case anymore if you properly configure -vm in eclipse.ini.
If you don't believe me, do some tests on your own using different architectures of Eclipse and Java and do configure -vm or not properly. In the end, that's exactly what the questioner described in his comment to the accepted answer:
Cannot run Eclipse; JVM terminated. Exit code=13
He is telling that a 64 Bit JDK is working now, but in his screenshot one can see that his Eclipse is 32 Bit, because the path for launcher.library is 32 Bit.
And now for the reason I came here: Ony of my customers had some problems loading one of our Eclipse/OSGI based applications as well and Java exited with exit code 13. In the end it showed that the problem was not about -vm or the architectures of Java and eclipse.exe, but instead he was simply missing config.ini and I guess eclipse.exe wasn't aware what to load or such. After we recognized that and put a config.iniback in place, the app loaded fine with using -vm and a 64 Bit JRE7 in combination with a 32 Bit eclipse.exe.

I had the same issue on Ubuntu, and solved it by unpack all *.pack files in jdk directory.
for example:
cd /usr/java/jdk1.7.0_03/jre/lib
sudo ../bin/unpack200 rt.pack rt.jar

use the configuration below;
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20130807-1835
-product
org.springsource.ggts.ide
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-vm
C:\Program Files\Java\jdk1.7.0_51\jre\bin\javaw.exe
-vmargs
-Dorg.eclipse.swt.browser.IEVersion=10001
-Dgrails.console.enable.interactive=false
-Dgrails.console.enable.terminal=false
-Djline.terminal=jline.UnsupportedTerminal
-Dgrails.console.class=grails.build.logging.GrailsEclipseConsole
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m
-XX:MaxPermSize=256m
-Dorg.eclipse.swt.browser.IEVersion=10001

I fixed it reinstalling the jdk. In my case it was necessary to do:
java -version
sudo apt-get purge openjdk*
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
java -version
javac -version
taken from Install Java JDK+JRE (oracle) in Kubuntu 13.04 from apt

In my case JAVA path was not set in Env variables. Started to work after correct path was set in Env PATH.
Type javac in command prompt and make sure JAVA PATH is correct.

I did couple of things inorder to get rid of this annoying error as modifying .ini never worked for me.
Installed latest JDK
Delete old eclipse IDE folder completely.
This time i Unziped to different location
Double Click "eclipse.exe" Works now like charm
Use default workspace to load your old projects.
Am suspecting it to be JDK's Java VM issue more than eclipse.

I used the new Eclipse Installer. I didn't like the installation path and I changed it manually. After that, I got the exit code=13 message too.
There is a new property in the eclipse.ini file named -install. I just had to modify it with the new location, and that solved this issue.
In the new installer I selected D:/eclipse, but the IDE was installed at D:/eclipse/eclipse. So, I moved the folder manually. The next time I tried to open eclipse I got the exit error. Thus, I had to modify eclipse.ini and set the current location:
-install
D:/eclipse

Before going to the solution, let us know why it is showing that error. If you know the problem behind this issue we can easily fix that error.
Reason 1: The most common reason behind this problem is, we are trying to install different bit version-that is, 64 bit or 32 bit version of the software. It maybe either Eclipse or Java.
Solution:
Check which version of operating system you are running.make sure you downloaded the same version of Eclipse as well as same version of Java software.
Reason 2: Configuration mistake in Eclipse.ini file
Solution:
Add this line "-vm then path of your java sdk" at the end of Eclipse.ini file. for example:
-vm
C:\Program Files\Java\jdk1.7.0_71\bin\javaw.exe
Reason 3: Special characters ( #, !, #) in Eclipse installation directory.
Solution:
Make sure you don’t have any special characters.
Reason 4: You have added JAVA path two times in PATH system variable and both the path are different.
Solution:
Remove one incorrect/different JAVA path from PATH system variable.
Reason 5: You maybe using latest version of Eclipse, but you might be using wrong version or unsupported version of Java Virtual Machine (JVM).
Solution:
To check which version of java you are using open command prompt by pressing win+R key and type cmd and press enter. Now in that console type Java -version command to know java version.
Now research whether eclipse support that version or not.
Or
You can open “readme” folder in Eclipse folder and open readme_eclipse.html to see which version it supports.

for ones with Eclipse Neon
I wanted to run Eclipse Neon and had JRE 1.8 but JDK 1.7
It returned error=13
then I installed java JDK 1.8 and everything worked like a charm

I had this issue also. I had an old JDK1.8.0_05. I installed the newest JDK1.8.0_111 and everything works great now. Just be sure to update your environment variable.
I am on Windows 7 64 bit.
Using Eclipse Neon 1a.
Hope that helps someone.

I face same issue with sts 3.8.4, so I tried different settings but not luck,
I reinstall jdk again n tried but same problem.
Finally I downloaded sts 3.8.2 n it runs with out any issue.
Using windows 8, 64 bit os.
thanks

This can happen when the PATH environment variable is point to a wrong java instalation.

Menu bar is a mess in eclipse neon.3 on Ubuntu 16.10

I just installed eclipse neon.3 on Ubuntu 16.10 but the menu bar is a mess in the Java Perspective:
As you can see from above the menu buttons seems to have been thrown randomly in there and I cannot reorder/drag/move them.
Also save buttons looks like at file is dirty - read to be saved but nothing is changed.
Is Eclipse neon.3 broken on Linux/Ubuntu 16.10?
Resetting the perspective has no effect.
Restarting eclipse and now I have even less buttons in the menu bar:
Works fine on windows 7.
As suggested below I have tried to add the following to the eclipse.ini:
But then I can no longer start eclipse and instead get this error:
Get the impression that eclipse has not been that throughly tested for Linux/Ubuntu.

I was having same problem. I found a solution as follows:
export SWT_GTK3=0
eclipse/eclipse
I have verified that the above solution works with Ubuntu 16.10, Eclipse neon.2 and JDK 8.
These two bug reports provided the solution:
https://bugs.launchpad.net/ubuntu/+bug/1634872
https://bugs.eclipse.org/bugs/show_bug.cgi?id=497705

Another option to disable GTK 3 is to add the following option to eclipse.ini file:
--launcher.GTK_version
2

I've been through the same problem using the neon.3 and the Ubuntu 17.04.To solve it, I changed my eclipse.desktop launcher file (in ~/local/share/applications/) to set the environment variable SWT_GTK3 to 0 as explained in this answer and as showed above:
Exec=sh -c "export SWT_GTK3=0 && {path_to_eclipse_folder}/eclipse"
but I got some errors while opening and/or editing some files. So reading about a problem while trying to read a markup file I ran into this forum post. In this post is said that there is a lib needed to be installed to avoid those errors. So after install the lib (as above) everything is working properly.
sudo apt-get install libwebkitgtk-1.0-0

If you want to use the .ini modification workaround; it needs to be before the vmargs. Like this -
-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.550.v20170928-1359
-product
org.eclipse.epp.package.dsl.product
-showsplash
org.eclipse.epp.package.common
--launcher.defaultAction
openFile
--launcher.defaultAction
openFile
--launcher.GTK_version
2
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Dosgi.instance.area.default=#user.home/eclipse-workspace
-XX:+UseG1GC
-XX:+UseStringDeduplication
--add-modules=ALL-SYSTEM
-Dosgi.requiredJavaVersion=1.8
-Xms256m
-Xmx2024m
--add-modules=ALL-SYSTEM

Eclipse will not run, seems like Java issue [duplicate]

I just append
-vm
C:\Program Files\Java\jre6\bin\javaw.exe
in eclipse.ini then I try to start eclipse again and got this error. Give me how to solve or link that actually solve it.
this is my eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.1.R36x_v20100810
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize 256m
--launcher.defaultAction
openFile
-vm
C:\Program Files\Java\jre6\bin\javaw.exe
-vmargs
-Xms40m
-Xmx384m
Thank you

I had the same error when configuring eclipse.ini to use JRE6. Turns out I caused this error by incorrectly configuring eclipse to use the 64 bit JVM while running a 32 bit version of eclipse 3.7.
The correct configuration required the eclipse.ini -vm argumument to use "C:/Program Files (x86)/" instead of "C:/Program Files/".
Make sure that the JVM version (32/64 bit) you use matches the eclipse version (32/64 bit).

It may just be the way the error shows (and not how it is written in the eclipse.ini file), but there is text in Eclipse.ini (Specifying the JVM) that says the following:
The -vm option and its value (the path) must be on separate lines.
The value must be the full absolute path to the Java executable, not just to the Java home directory.
The -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the JVM

Look at the second line of the message box. There you can see which java runtime in fact is started. Mine was suddenly C:\ProgramData\Oracle\Java\javapath\javaw.exe. This happened after I have installed a "chrome java updater" (Chrome browser moaned: 'your java is outdated, you have to update...').
Before this "chrome java update" my eclipse (luna jee x64) started without error. Looking closer to the background I detected following: the chrome java updater (notabene started from an Oracle site) added C:\ProgramData\Oracle\Java\javapath in front of the env var PATH. It contains three symbolic links to the newest java 8 JRE installation in (x86) program folder -> hence to a 32 bit java JRE. Oracle replaces with Java8 the old technique having the symlinks in system32 (64bit) resp. SysWOW64 (32bit).
Meanwhile I learned. Whatever java installer you have executed last (the *.exe) leads windows to remember that java flavour (32b or 64b), with the result that after an update the links in C:\ProgramData\Oracle\Java\javapath point to a java installation of the remembered flavour. If you have a 64b eclipse installation and encounter the described error: just re-install the newest 64b JDK. After that the java updates do no more link to a 32b version. And eclipse 64b will start correctly without the entry in eclipse.ini .

You need to check if your PC has a 64-bit or 32-bit operating system, then same goes for your JDK (64-bit/32-bit) and also for Eclipse (64-bit/32-bit).
Make sure they are all the same; if not, you need to download the one that matches your bitness.

For Eclipse:
Added this two lines in eclipse.ini
Second line represents the JDK location of the javaw.exe file.
-vm
C:\Program Files\Java\jdk1.7.0_60\bin\javaw.exe
Note: place -vm lines before -vmargs, otherwise default location is taken.
For STS
Change the same as above in STS.ini

I just hit this too. Turns out that at least for me, this was due to trying to use a win64 version of the JRE with a win32 Eclipse. I seems that win32 Eclipse requires a win32 Java (what is called -586 in the list of Java installers from Oracle/Sun).
The reason I was using both is that I was trying to pinpoint a bug that only manifested itself in 64-bit Eclipse, so I needed a 32-bit to compare to.
Once I installed BOTH the "x64" (win64) and "i586" (win32) versions of the JRE on my machine, things work fine and no error 13. You can apparently have both installed at the same time.

The error means it's the wrong JVM version for that version of Eclipse. The link has more details:
http://www.ehow.com/how_4784069_terminated-exit-code-error-eclipse.html

Make sure the Eclipse and the Java that you are using are both either 32-bit or 64-bit.
You cannot run 64-bit eclipse with 32-bit JRE.
java -version
Java HotSpot(TM) 64-Bit Server VM
The 32 bit version JRE will not have 64-Bit in it.

I just had the same issue, and spend about an hour trying to solve the problem.
In the end it was a '#' character in the path.
So I renamed "C:\# IDE\eclipse 3.7\" to "C:\+ IDE\eclipse 3.7\" and that solved the problem.

Recently I faced same issue.My version of eclipse didnt support java version 8.
I had accidently installed jre 8 on my machine which automatically updated my PATH variable by appending "C:\ProgramData\Oracle\Java\javapath" in the beginging which led eclipse to pick up this version(and ignore the manually added 1.6 version which came later in order)and crash with exit code 13.
I just removed this string from the path so which led system to pick up my older version and eclipse started just fine.

I had the same issue with eclipse in my both machine. I had jre 32 bit installed. So I removed 32 bit and installed 64 bit instead and it worked perfectly.

simply install 64 bit version of JAVA from http://java.com/en/download/manual.jsp
and uninstall older version if prompted by the 64 bit installer

Go to the folder where you saved Eclipse. Look in the configuration folder at the startup log. It will give you a much better diagnostic than "exit code 13".

After java update, eclipse will not start because default jdk location has changed. Adding the following lines to eclipse.ini file solved my problem immediately:
-vm
C:\Program Files (x86)\Java\jdk1.7.0_75\bin\javaw.exe
I added these lines just before vmargs. It looks like as the following :
...
--launcher.defaultAction
openFile
-vm
C:\Program Files (x86)\Java\jdk1.7.0_75\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx512m
For more information on eclipse.ini, visit this the site http://wiki.eclipse.org/Eclipse.ini#-vm_value:_Windows_Example
In my case, i use 32 bit eclipse and java. If you installed both 32 bit and 64 bit versions of java, be careful to choose the right version. For 64 bit versions, refer to the javaw.exe file under the directory
C:\Program Files\Java\jdk1.8.0_60\bin

Whenever you see this error, go to Configuration directory and check for a log file generated just now. It should have proper Exception stacktrace. Mine was a case where I got an updated 32-bit JRE (or JVM) installed which was the default Java that got added to the Path. And my Eclipse installation was 64-bit which meant it needed a 64-bit VM to run its native SWT libraries. So I simply uninstalled the 32-bit JVM and replaced it with a 64-bit JVM.
I wonder if they will improve this reporting mechanism, instead of silently generating a log file in some directory.

This error occurred to me on ubuntu, having installed 32bit and 64bit java. Use
sudo update-alternatives --config java
to set the right version to use as default.

Just uninstalled jre-32 bit version and It worked fine for me.

I was using Eclipse Juno and I didn't remember if it was 32 or 64 bits. I installed Java 32 bits and that's why it failed. I then installed Java 64 bits and Eclipse Juno is working again.
I also removed any java or jre reference in my environment variables (PATH).

In my opinion the most answers here regarding different architectures of Eclipse and Java are simply wrong and this can be easily checked using e.g. Process Monitor under Windows. The -vm option is there to run a specific version of java and the point of it is, that the configured process is started and runs all the Java code on its own, that's why you configure up to java.exe. In that case you DON'T need to have the same architecture for Eclipse and Java, but can happily mix both 32 Bit and 64 Bit. You only CAN'T mix both, if you DON'T use -vm, but let Eclipse load Java natively into its own process using jvm.dll and such. That latter behavior is Eclipse's default, but not the case anymore if you properly configure -vm in eclipse.ini.
If you don't believe me, do some tests on your own using different architectures of Eclipse and Java and do configure -vm or not properly. In the end, that's exactly what the questioner described in his comment to the accepted answer:
Cannot run Eclipse; JVM terminated. Exit code=13
He is telling that a 64 Bit JDK is working now, but in his screenshot one can see that his Eclipse is 32 Bit, because the path for launcher.library is 32 Bit.
And now for the reason I came here: Ony of my customers had some problems loading one of our Eclipse/OSGI based applications as well and Java exited with exit code 13. In the end it showed that the problem was not about -vm or the architectures of Java and eclipse.exe, but instead he was simply missing config.ini and I guess eclipse.exe wasn't aware what to load or such. After we recognized that and put a config.iniback in place, the app loaded fine with using -vm and a 64 Bit JRE7 in combination with a 32 Bit eclipse.exe.

I had the same issue on Ubuntu, and solved it by unpack all *.pack files in jdk directory.
for example:
cd /usr/java/jdk1.7.0_03/jre/lib
sudo ../bin/unpack200 rt.pack rt.jar

use the configuration below;
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20130807-1835
-product
org.springsource.ggts.ide
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-vm
C:\Program Files\Java\jdk1.7.0_51\jre\bin\javaw.exe
-vmargs
-Dorg.eclipse.swt.browser.IEVersion=10001
-Dgrails.console.enable.interactive=false
-Dgrails.console.enable.terminal=false
-Djline.terminal=jline.UnsupportedTerminal
-Dgrails.console.class=grails.build.logging.GrailsEclipseConsole
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m
-XX:MaxPermSize=256m
-Dorg.eclipse.swt.browser.IEVersion=10001

I fixed it reinstalling the jdk. In my case it was necessary to do:
java -version
sudo apt-get purge openjdk*
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
java -version
javac -version
taken from Install Java JDK+JRE (oracle) in Kubuntu 13.04 from apt

In my case JAVA path was not set in Env variables. Started to work after correct path was set in Env PATH.
Type javac in command prompt and make sure JAVA PATH is correct.

I did couple of things inorder to get rid of this annoying error as modifying .ini never worked for me.
Installed latest JDK
Delete old eclipse IDE folder completely.
This time i Unziped to different location
Double Click "eclipse.exe" Works now like charm
Use default workspace to load your old projects.
Am suspecting it to be JDK's Java VM issue more than eclipse.

I used the new Eclipse Installer. I didn't like the installation path and I changed it manually. After that, I got the exit code=13 message too.
There is a new property in the eclipse.ini file named -install. I just had to modify it with the new location, and that solved this issue.
In the new installer I selected D:/eclipse, but the IDE was installed at D:/eclipse/eclipse. So, I moved the folder manually. The next time I tried to open eclipse I got the exit error. Thus, I had to modify eclipse.ini and set the current location:
-install
D:/eclipse

Before going to the solution, let us know why it is showing that error. If you know the problem behind this issue we can easily fix that error.
Reason 1: The most common reason behind this problem is, we are trying to install different bit version-that is, 64 bit or 32 bit version of the software. It maybe either Eclipse or Java.
Solution:
Check which version of operating system you are running.make sure you downloaded the same version of Eclipse as well as same version of Java software.
Reason 2: Configuration mistake in Eclipse.ini file
Solution:
Add this line "-vm then path of your java sdk" at the end of Eclipse.ini file. for example:
-vm
C:\Program Files\Java\jdk1.7.0_71\bin\javaw.exe
Reason 3: Special characters ( #, !, #) in Eclipse installation directory.
Solution:
Make sure you don’t have any special characters.
Reason 4: You have added JAVA path two times in PATH system variable and both the path are different.
Solution:
Remove one incorrect/different JAVA path from PATH system variable.
Reason 5: You maybe using latest version of Eclipse, but you might be using wrong version or unsupported version of Java Virtual Machine (JVM).
Solution:
To check which version of java you are using open command prompt by pressing win+R key and type cmd and press enter. Now in that console type Java -version command to know java version.
Now research whether eclipse support that version or not.
Or
You can open “readme” folder in Eclipse folder and open readme_eclipse.html to see which version it supports.

for ones with Eclipse Neon
I wanted to run Eclipse Neon and had JRE 1.8 but JDK 1.7
It returned error=13
then I installed java JDK 1.8 and everything worked like a charm

I had this issue also. I had an old JDK1.8.0_05. I installed the newest JDK1.8.0_111 and everything works great now. Just be sure to update your environment variable.
I am on Windows 7 64 bit.
Using Eclipse Neon 1a.
Hope that helps someone.

I face same issue with sts 3.8.4, so I tried different settings but not luck,
I reinstall jdk again n tried but same problem.
Finally I downloaded sts 3.8.2 n it runs with out any issue.
Using windows 8, 64 bit os.
thanks

This can happen when the PATH environment variable is point to a wrong java instalation.

Eclipse gives “Java was started but returned exit code 13” [duplicate]

This question already has answers here:
Can't start Eclipse - Java was started but returned exit code=13
(44 answers)
Closed 7 years ago.
All hell broke loose after i uninstalled my java 6 and installed java 7 (both jdk and jre). On opening eclipse it gave the error that "No JVM found at.....". So, i explicitly gave the location of javaw.exe as
-vm
C:\Progra~2\Java\jdk1.7.0_45\bin\javaw.exe
in the eclipse.ini file. Now it says "Java was started but returned exit code 13".
Also, in the elispse.ini file i changed
-Dosgi.requiredJavaVersion=1.5
to
-Dosgi.requiredJavaVersion=1.7
There are many solutions online like :
MyEclipse 10 does not start "Java was started but returned exit code 13"
but none of them works. Any insight?

if you have updated your jdk to 7 you are most likely to face this problem.
This happens mainly due to:
incompatible sdk and jdk versions
using a 32 bit java version for your 64 bit eclipse JVM (programfilex86-java)
WHAT YOU HAVE TO DO :
firstly check the eclipse.ini file to see if you have a path that is pointing to your jdk
it should look something like this
-vm
C:\Program Files\Java\blah\blah\blah\javaw.exe
if not then locate the jdk 7 javaw.exe file
sample :
C:\Program Files\Java\jdk1.7.0_45\jre\bin\javaw.exe
paste -vm and the path below it into your eclipse.ini file
-vm
C:\Program Files\Java\jdk1.7.0_45\jre\bin\javaw.exe
make sure that you type the above just before the -vmargs and after the OpenFile

This problem happened because either u install new version of jdk so you have both 32bit version and 64bit
how to solve the problem is just go open computer & go to c then you will see
after that you probably use 32 bit so just chose C:\Program Files
and there you will find folder called java
in it
so you have many different version of jdk so easily chose jre7
and to to bin and you will find javaw.exe in it like
now only just take that path copy and go to start type eclipse.ini you will see text file just open it and before -vmargs
write -vm enter path like photo
now just open eclipse again and have fun :D

The solution can be found here
The eclipse.ini file should be somewhat like this...
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120913-144807
-product
adtproduct
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vm
C:\Program Files\Java\jdk1.8.0_25\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m

In your eclipse.ini file simply put
–vm
/home/aniket/jdk1.7.0_11/bin(Your path to JDK 7)
before -vmargs line.

I had the same problem. i was using windows8 with 64 bit OS. I just changed the path to Program Files(*86) and then it started work.
I put this line in eclipse.ini file like,
-vm
C:\Program Files (x86)\Java\jre7\bin\javaw.exe

It would be the 32 bit version of eclipse , for instance if you are running the 32 bit version of eclipse in 64 bit JVM, this error will be the result.
To confirm this check for log in your configuration folder of the eclipse. Log will be as following
java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM ...
try installing the either 64 bit eclipse or run in 32 bit jvm

I installed 32 bits ADT and It works fine without changing my configuration (Windows 7 64 bits, Java 6 32 bits).

I got this fixed by doing the below steps,
The eclipse finds the JAVA executables from
'C:\ProgramData\Oracle\Java\javapath'
2.The folder structure will contain shortcuts to the below executables,
i. java.exe
ii. javaw.exe
iii. javaws.exe
3.For me the executable paths were pointing to my (ProgramFiles(x84)) folder location
I corrected it to Program Files path(64 bit) and the issue got resolved
Please find the screenshot for the same.

I could resolve this issue by changing JDK1.8 64bit version to JDK 1.8 32bit(x86) version

Check you PATH environment variable once. Make sure the correct location of your JDK is specified there.

Instead of opening eclipse.exe , first open folder named configuration then you will get log file like 1401241141809.log ; open that log (open latest one) detail error will be listed there.
Ex:
java.lang.UnsatisfiedLinkError: Cannot load 64-bit SWT libraries on 32-bit JVM
means you need to have JVM and SDK of same version.

When I uninstalled Java 8 it worked fine.

Eclipse returns error message "Java was started but returned exit code = 1"

This is a picture of the error code
Here is the content of the error message:
Java was started but returned exit code=1
C:\WINDOWS\system32\javaw.exe
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m
-Declipse.buildId=v22.0.5-757759
-XX:MaxPermSize=256m
-jar
D:\Programming\adt-bundle-windows-x86_64-20130729\eclipse\\plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
-os win32
-ws win32
-arch x86_64
-showsplash
-launcher
D:\Programming\adt-bundle-windows-x86_64-20130729\eclipse\eclipse.exe
-name Eclipse
--launcher.library
D:\Programming\adt-bundle-windows-x86_64-20130729\eclipse\\plugins/org.ecl
ipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120913-144807\eclipse_1503
.dll
-startup
D:\Programming\adt-bundle-windows-x86_64-20130729\eclipse\\plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.overrideVmargs
-exitdata 1c50_48
-product com.android.ide.eclipse.adt.package.product
-vm C:\WINDOWS\system32\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m
-Declipse.buildId=v22.0,5-757759
-XX:MaxPermSize=256m
-jar
D:\Pragramming\adt-bundle-windows-x86_64-20130729\eclipse\\plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
I just downloaded and dearchived android SDK for Windows. I`m currently using W8 64x.

The error message points to a problem with your Java version. Do you have a JDK installed?
Try adding the following (noting the new line):
/!\ make sure, that the -vm option occurs before the -vmargs command.
Everything after -vmargs is passed directly to the JVM.
-vm
c:/wherever/java/jdk1.6.0_21/jre/bin/server/jvm.dll
-vmargs...
...to your eclipse.ini file, pointing to the JDK you want to use, and check that the required Java version is at least as new as your JDK. This is the path for a Windows system. More on paths can be found here (scroll down).
If you don't know where the eclipse.ini file is: regularly it is in the folder of your eclipse.exe.
Edit2: #KadoLakatt: the reason why installing the latest Java Version worked for you is because Eclipse checks the standard path for a JVM if it doesn't find a -vm entry (see here). However I'd not recommend that, since you might be wrong guessing the JVM used. If you update Java (automatically?) you might run into problems in your Eclipse wondering what you might have changed. Better set it to a specific folder in your eclipse.ini to be certain.

I received this error out of the blue. Eclipse stopped working even though I made no config changes and did not install any new jdk's.
Here was my eclipse.ini file :
--clean
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20130807-1835
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vm
C:/Program Files (x86)/Java/jre7/bin/javaw.exe
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx1024m
To get Eclipse to start successfully I removed
-vmargs
-Dosgi.requiredJavaVersion=1.6
-vm
C:/Program Files (x86)/Java/jre7/bin/javaw.exe
So here is my updated file :
--clean
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20130807-1835
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-Xms40m
-Xmx1024m
I have no idea why removing osgi.requiredJavaVersion=1.6 fixed this as my jvm version is 1.6. From the doc http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html
osgi.requiredJavaVersion
The minimum java version that is required to launch Eclipse. The default value is "1.4.1".
I think my java version was set correctly. Anyway Eclipse starts and runs for me now......

it can be like this as well:
-vm
C:\Program Files\Java\jre6\bin\server\jvm.dll

Working combinations of OS, JDK and eclipse bitness.
32-bit OS , 32-bit JDK , 32-bit Eclipse (32-bit only)
64-bit OS , 32-bit JDK , 32-bit Eclipse
64-bit OS , 64-bit JDK , 64bit Eclipse (64-bit only)
Kindly use 1 of the above combinations.

Adding -vm parameters works for me.
-vm
C:\Program Files\Java\jdk1.7.0_45\jre\bin\server\jvm.dll

For those of you who tried all the above answers without any success, try lowering your -Xms value. I am required to support an older Eclipse (Weblogic Eclipse 10.3.6) - I had the following .ini on my Windows 7 machine and my Windows Server 2008 R2 Enterprise VM (the Java version below points to a 32-bit Java) that had worked and were working perfectly, respectively.
-vm
C:/Java/Java7/jdk1.7.0_79/bin/javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20120522-1813
-showsplash
org.eclipse.platform
--launcher.defaultAction
openFile
-vmargs
-Xms1024m
-Xmx1024m
-XX:MaxPermSize=256m
-Dsun.lang.ClassLoader.allowArraySyntax=true
-Dweblogic.home=C:/Oracle/Middleware/wlserver_10.3
So a 32-bit Java for a 32-bit Eclipse, but still exit code 1. Based on all answers I had seen here, and the only change being a new laptop with Windows 10, the only possible explanation was that the new OS and the Eclipse were disagreeing on something. So I started playing around with each of the values, and it worked when I lowered both Xms and Xmx to 512m. I have a hunch that possibly the new Windows OS is preventing a higher initial heap size based on some run condition (the higher -Xms does work on Windows 10 on all other similar devices I came across) - so any other explanation is welcome. Meanwhile following is the only value I tweaked to successfully launch Eclipse.
-Xms512m

I've encountered similar problems. The reason is that the path to my eclipse includes Chinese characters. Once those characters are deleted, the problem is solved. Please check if there are characters other than English in your path.

I had same issue in my windows 7, 64-bit machine. Then I downloaded and installed 64 bit jdk for Java(which includes jre). This solved the issue.

I too faced the similar issue , not solved after adding the command in eclipse.ini file. My root cause is different. I was experimenting on sequence diagrams using objectaid. This is throwing an exception and disturbed my workspace. You may have different issue when working on new plugins. Better you check the log file located in your project work-space C:\path\to\workspace\.metadata\.log

This can be resolved by adding the following line to the eclipse.ini file
-XX:-UseCompressedOops

I had the same issue which was caused due to crash shutdown of my windows 10. Earlier in the path I had Oracle path ie the path inserted by Oracle at the time of installation of JDK. I removed it and changed the path to the JDK location. This solved the problem.

Mine is a 64 bit system with 64bit java installation.
what worked for me was the following:
Goto the eclipse installation directory
right click the eclipse icon and click "send to desktop as shortcut"
Then right click on the shortcut icon in the desktop and then > properties > shortcut tab
In the target field point it to the correct java 64 bit installations home path using the vm argument with the java_home path enclosed in quotes like so :
D:\Scala_eclipse\eclipse.exe -vm "C:\Program Files\Java\jdk1.8.0_11"
This almost always solves all my Eclipse (scala eclipse as well) related problems.
As mentioned in the answer , please make sure you are using the right combination of eclipse and java

If you have java 8 installed it might be related to the following issue:
https://support.oracle.com/knowledge/Middleware/2412304_1.html
Simply removing/renaming the "C:\Program Files (x86)\Common Files\Oracle\Java\javapath" worked for me.

Directly changing eclipse file is not a good idea, no matter facet or ini, unless it could be changed in eclipse. Had the same problem, with jdk1.8 installed. Change it to jdk 1.7.
Besides, according to https://wiki.eclipse.org/Eclipse/Installation, both LUNA and MARS need 1.7. So just ensure you have it installed.

1 ) Open the SpringToolSuite4.ini File.
2 ) Search For the openFile.
3 ) Provide the jvm.dll file location in SpringToolSuite4.ini
4 ) Note : Provide the New Line between -vm and your jvm.dll file location path.as shown below.
openFile
-vm
C:\Program Files\Java\jre8\bin\server\jvm.dll
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms256m

i had Java Run time environment and Java SDK both on my machine. I removed Java Run time environment and it resolved my error.
Earlier this error, i was using elipse with Java SDK only and later had installed JRE specifically for one need.

just to add here...For the guys those who still couldn't start eclipse due same error, please check eclipse.ini file again and see have you forgot to put M after memory size.
For example:
-Xmx1024
or
-Xmx1024MB
or
-Xmx1024 M
or
-Xmx1024 mb
or
-Xmx1024mb
are incorrect, it should be -Xmx1024M. I have been trying different ideas from SOF and from other forums, and in this cut/paste I forgot that I missed M (such a little thing to miss), so I thought I should share. If it works for some of you please up-vote.

I had this issue recently, but I hadn't changed any java or updated the java version, May be this issue happened because of crash shutdown of the system.
And after reading a couple of answers here I decided to change the java version from 1.6 to 1.7 in the eclipse.ini file.
-vmargs
-Dosgi.requiredJavaVersion=1.6
After this change the Eclipse started well and it worked. Since I didnt had changed anything i decided to change it back to 1.6 to what it was originally.
Then I started eclipse and guess what it worked. So Looks like in my case just touching/modifiying the eclipse.ini file worked.
I hope this answer is helpful to somebody.

If none of the solutions works, please check if you have more than one version of java installed on your machine. Please keep only one version which you prefer and everything should work fine.

None of the above answers helped for me. I discovered that, in general, an error like that could mean that your eclipse.ini has an invalid entry. So, all the above answers could be correct, depending on your particular case. In my case, it turned out I added a locale argument with a typo in it.

I tried to change the path in the parameter -vm, but it did not help. Then I deleted the parameter -vm and -vmargs from the eclipse.ini.
It worked for me

My path of -javaagent argument was having Spacial characters like '&'. I placed the Lambok jar in different place and gave the path to that place. It worked for me.
previously it was
-javaagent:C:\Software & Tool\lambok.jar
i changed it to
-javaagent:C:\Labmok\lambok.jar

Please check your computer and if Java JRE not install download and install it.
https://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
If install please check is it 32 bit or 64 bit as per your operating system
To check for 32 or 64-bit JVM, run:
$ java -d64 -version
$ java -d32 -version
Error: This Java instance does not support a X-bit JVM.
Please install the desired version.

Open the Eclipse Installation Folder on Windows Machine
Find the eclipse.ini
Open the eclipse.ini File and add the below two lines before -vmargs
-vm
C:\Users\IshaqKhan\jdk1.8.0_173\bin\javaw.exe

This work for me in eclipse js and eclipse php:
-vm
C:/java/jdk-11.0.1/bin/javaw.exe
--launcher.appendVmargs
-vmargs

I had a similar issue. I opened my eclipse.ini file and noticed that I configured at the end some lines for the lombok library in the past. The path to my lombok jar file was no more valid. After correcting it, my eclipse was working like a charm again. In conclusion, my piece of advice would be to verify that all the paths configured in this file are valid.
eclipse.ini :
-...
-javaagent:C:\some\path\to\lombok.jar
-Xbootclasspath/a:C:\some\path\to\lombok.jar

JAVA Path could be incorrect
Trying above solution didn't help me.
So i checked java --version on command prompt, which gave virtualization conflict. It seemed installation of virtualization software on system had messed up environment variables.
Hence I checked JAVA_HOME which was on correct path, then checked system variable PATH which had correct JAVA bin path as well, so removed 'C:\Program Files (x86)\Common Files\Oracle\Java\javapath' and checked java --version on command prompt again, which gave correct value and also fixed above issue of eclipse start.

On Windows 10, removing
-XstartOnFirstThread
from the eclipse.ini fixed the issue for me

Go to eclipse folder and then go Configuration Setting file
change the below path under -vm tag in config file
Note- you need to mention new java path with bin and then javaw.exe like below
-vm
java path/bin/javaw.exe
It should work. Thanks.

if it says
c:/program files/java/jre/bin/server/jvm.dll not found
then copy the jre from jdk folder and paste it outside the jdk folder . and then try again...