c:\program files\java\jre1.8.0_221\bin worked for me


i had this problem too on a win7 machine. i wanted to update the jre with a jdk. so i deleted the jre folder and downloaded and unzipped the new jdk. the issue was i manually deleted the jre folder, when instead i should've uninstalled it. this leaves a bunch of registry entries that still point to the old jre. somehow eclipse still wants to use the old jre. i couldn't uninstall the old java vm, i kept getting this error:

error 1723. there is a problem with this windows installer package. a dll required for this install to complete could not be run. contact your support personnel or package vendor

so i had to use this ms utility to fix the uninstall:

then i had to install again the vm. i installed to the same location the original one was at, to avoid losing another hour! after that eclipse started correctly.



i just had this problem and fixed it this way. i noticed the error message has jre in it not jre6 or jre7, so i copied jre6 from program files to eclipse folder then renamed it from jre6 to jre, then it worked :p


newb move on my part, but i had installed just the jre instead of jdk. installed jdk and my problem went immediately away.


i had this problem and it was due to my windows machine playing up. i went into control panel -> system -> advanced - environment variables.

i edited the path variable (which was already correctly set up), changed nothing, clicked ok to come back out of the screens.

then eclipse worked. no idea why, except because windows. hopefully this may help someone.


i had this issue; i fixed it by going to

computer-->properties-->advanced settings-->environmental variables

in the system variables find the variable named path.
-->select edit -->at the very end of the path variable, put a ";" then add your path of your jdk and put \bin\ at the end

should be fixed.


system variable-

c:\program files (x86)\common files.......hp\leanft\bin

jdk path-

c:\programs files\java\jre1.8.0_121

final path -

c:\program files (x86)\common files.......hp\leanft\bin;c:\programs files\java\jre1.8.0_121\bin\



its simple. jdk bin directory or jre bin directory should be in path variable example : java installed directory: assume your java installed in 'c:\program files\java\jdk1.8.0_144' directory now you can find bin directory in 'c:\program files\java\jdk1.8.0_144\bin'

navigate to user's environment variable

control panel --> user accounts --> user accounts --> change my environment variables

in popup click path under user variables for section click edit... button and another popup will appear

click new button and enter c:\program files\java\jdk1.8.0_144\bin

click ok button and again ok button in environment variables popup.

now you can open your eclipse without error


i found a solution wherein the eclipse.ini the location was the old version of java, and after updating the new version of java the location of -vm

c:\program files\java\jre1.8.0_201\bin

was same so i had to change the directory to my new version of java.

so solution is to just open the most updated java version and copying its directory path and replacing it in the eclipse.ini file.


moderately future proof example for linux-like systems. assuming javac installed and on your path.

./eclipse -vm dirname $(readlink -f $(which javac))

this will find the directory where javac is installed, and pass as vm argument to eclipse.


if on linux (ex: ubuntu 18), try installing (or reinstalling in your case?) default-jre, as follows:

sudo apt update
sudo apt install default-jre

i had the same error when just trying to run the eclipse installer (./eclipse-inst) on a fresh eclipse download just now, and the installer wouldn't even run! installing default-jre solved it!



in my case i had edited the eclipse.ini for a different purpose to include -vm parameter. that was causing the failure. i removed the -vm and following line where i had included \bin and that fixed the problem.


this sometimes happen if you remove java from your path variables. to set the path variable again, add the full path of the jdk\bin directory to the path variable. typically, the full path is:

c:\program files\java\jdk-11\bin

to set the path variable on microsoft windows:

  1. select control panel and then system.
  2. click advanced and then environment variables.
  3. add the location of the bin folder of the jdk installation to the path variable in system variables.


i also had same problem when developing android applications using eclipse ide. i solved it by removing all the java installations (i had java 6 and 7 both) and re-install only jdk 7.


adding -vm c:/program files/java/jdk1.6.0_29/bin/javaw.exe to the .ini file helped me.


i got this fixed by doing the below steps,


  1. the eclipse finds the java executables from 'c:\programdata\oracle\java\javapath'
  2. the folder structure will contain shortcuts to tenter image description herehe 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
  4. i corrected it to program files path(64 bit) and the issue got resolved

please find the screenshot for the same.


just to add on top of other answers:

windows users: you can give the path to jre in eclipse.ini separated by '/' or '\'. it doesn't matter. eclipse will pick it anyway. for example, in my windows system, either of the paths is fine (after -vm of course):

c:/program files/java/jre1.8.0_181/bin or c:\program files\java\jre1.8.0_181\bin


change the vm value in eclipse.ini file with the correct path to your jdk something like this,

-vm /library/java/javavirtualmachines/jdk-11.0.5.jdk/contents/home/bin

path to eclipse.ini looks to me something like this,



is so simple,only add your java path for example:

c:\program files\java\jdk1.8.0_121\bin

in path system variable


i have faced the similar issue earlier with eclipse and sts ide's

  • please check weather jdk/jre is available or not in your machine. if not please install jdk and setup the environment variables.
  • even after step 1, if you are still facing the issue then it's time to set the vm argument in eclipse.ini or sts.ini in the following way.
c:program files (x86)\java\jre8\bin


make sure the install path of jdk is in your path variable in windows.


did you install java via the web browser auto install? if so, then that's your problem! you need to to the "manual" install:

it's just a matter of having the correct match of 32-bit eclipse/32-bit java or 64-bit eclipse/64-bit java. many 64-bit windows have 32-bit browsers and the latter is the version of java that the auto-installer will provide - not what the 64-bit eclipse wants.


i had the same problem and the issue was that i had a 32 bit version of eclipse running on my 64 bit machine and it wanted the 32 bit version of jre.

i changed program files to program files (x86) in the eclipse.ini file like so:

c:program files (x86)\java\jre6\bin

and that solved the problem.

you may want to just install the 64 bit eclipse, but this will take care of the error.


here is how i fixed mine:

  1. find the location where your jre is installed. in my case, it was located at c:\program files\java\jdk1.7.0_10

  2. copy the jre folder and paste it where your eclipse files are located (where eclipse.exe is located).

when you download eclipse, you get a .zip package containing eclipse.exe and all the other files needed to run eclipse but it is missing the jre files. so all you need to do is to find where jre folder is located on your hard drive and add it to the rest of the eclipse package.


copy javaw.exe from c:\program files\java\jre1.8(or)1.6(or)1.7\bin

enter image description here

and paste it inside eclipse folder where eclipse.exe is there. that's all.

enter image description here


it usually is because:

  • you indicated the wrong jvm path in your -vm argument: see this so question for an concrete example.
  • the eclipse.ini got corrupted somehow (if it hasn't been modified, this isn't it, but if setting a jvm path doesn't work, ... i would replace the eclipse.ini by one coming from a fresh installation just to be sure)
  • the java which eclipse search by default is no longer accessible (because the $path is no longer up-to-date)

more details on the wiki page "finding a vm, using jni invocation or executing java"

no -vm specified

when no -vm is specified, the launcher looks for a virtual machine first in a jre directory in the root of eclipse and then on the search path.
if java is found in either location, then we look for a jvm shared library (jvm.dll on window, on *nix platforms) relative to that java executable.

  • if a jvm shared library is found we load it and use the jni invocation api to start the vm.
  • if no jvm shared library is found, we exec the java launcher to start the vm in a new process.

as mentioned in "faq how do i run eclipse?":

eclipse does not consult the java_home environment variable.

so i would check your $path, starting by n new shell sesion (whatever your os is), typing 'java -version' to see if it still returns anything.


i got this problem because i uninstalled the jdk version 13 and reinstall the jdk version 8

even though i have updated the path variables eclipse still pick the old configuration.

you need to edit the eclipse.ini file which is in your folder where eclipse.exe is placed.

enter image description here

just update this file with the latest path so eclipse can pick it up

enter image description here


you can explicitly tell eclipse where to find it. open eclipse.ini and add the following lines to the top of the file:


update: i just nailed down the root cause on my own windows machine. the glassfish installer complained with exactly the same error message and after digging in glassfish forums, the cause was clear: a corrupt jre install on a windows machine. my jre came along with the jdk and the java 6 jdk installer didn't install the jre properly somehow. a dll file was missing in jdk's jre installation. after i reinstalled the standalone jre from, overwriting the old one, the glassfish installer continued and also eclipse was able to start flawlessly without those two lines in eclipse.ini.

Related Query

More Query from same tag