970

When I try opening Eclipse, a pop-up dialog states:

Failed to load the JNI shared library "C:/JDK/bin/client/jvm.dll"`.

Following this, Eclipse force closes.

Here's a few points I'd like to make:

  • I checked to see if anything exists at that path. It does exist.
  • My Eclipse and Java SE Development Kit are both 64-bit. I checked my system, and it can handle 64-bit.
  • I've searched for this problem on Google and on Stack Overflow, and the only answer I found was to download the 32-bit versions of JDK and Eclipse.

Downloading the 32-bit versions is something I only want to do as a very last resort.
What would be suggested to solve this issue?

10
  • 4
    I had, to my surprise, 5 or so Java installed onto my computer. Not only that, but it turned out that I downloaded the 32-bit Eclipse by accident. So, I uninstalled every Java I had, deleted Eclipse (Eclipse doesn't have an "uninstall"), and downloaded Eclipse Classic 64-bit for my machine, along with a 64-bit Java (see SPP's answer for that link).
    – Mxyk
    Jul 4, 2012 at 10:39
  • 2
    Also: if anyone has trouble "deleting" their Eclipse (e.g. the folder won't go away no matter how many times you remove it manually or via command prompt), try deleting it using safe mode with command prompt.. I have no idea why I had to do this, but that ended up working.
    – Mxyk
    Jul 4, 2012 at 10:42
  • 1
    @MikeGates I had that problem too, used LockHunter. Obnoxious. Getting this tool to run on Windows is way too much work.
    – jcollum
    Jan 17, 2013 at 23:33
  • 1
  • 1
    hey. if you DO have 64-bit version of all of the below stated software, just try deleting the 'eclipse.ini' file. worked for me:)
    – eiran
    May 15, 2014 at 13:26

39 Answers 39

871

You need a 64-bit trio:

  • 64-bit OS
  • 64-bit Java
  • 64-bit Eclipse
13
  • Explaination: Imagine native code (DLL) being loaded into an application. Now imagine a 32bit function wants to call a 64bit one, or alike. Same with alignment and datasizes and everything. I guess I dont have to tell anything more =P
    – imacake
    Mar 17, 2012 at 17:15
  • Correctly! My laptop is running on x64 OS but I installed x86 JDK. Just installed x64 jdk and the issue go away. Thanks. Dec 2, 2013 at 7:20
  • This answer is actually not totally accurate. You do not need to run 64-bit JDK and 64-bit Eclipse if you're on a 64-bit OS. 64-bit OS can just as well run a combo of 32-bit Java + 32-bit Eclipse. What must match is the bittedness of JRE/JDK and Eclipse.
    – E-Riz
    Jul 3, 2014 at 15:23
  • @E-Riz You are right, a correct answer can also be "take a 32-bit eclipse!". But is it a good answer?
    – Grim
    Jul 3, 2014 at 15:29
  • 1
    @Tarik yes, its 2015 and unfortunatelly the Visual Page Editor(VPE) of JBoss Tools still awaiting since years for a 64-bit upgrade. Look at the "Working-Pairs" answer below, at the second pair. The JBoss Tools-Plug-in is bound to the same architecture you downloaded Eclipse. So Eclipse(with the JBossTools) must be 32bit, the JDK must be 32bit and the OS can be 64 bit. A 64bit eclipse does currently not work with JBoss Tools.... I remember a project called JBossIDE that works using Eclipse, you shall use this instead of install JBossTools into eclipse. Shame on you JBoss, shame on mozilla too.
    – Grim
    Feb 12, 2015 at 16:50
321

Working pairings of OS, JDK and Eclipse:


  • 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)

I had several JDKs and JREs installed.

Each of them had their own entry in the PATH variable, all was working more or less.

Judging from the PATH variables, some installations were completely useless, since they were never used. Of course, the "inactive" Javas could be referenced manually from within Eclipse if I needed, but I never did that, so I really did not need them. (At least I thought so at that time...)

I cleaned up the mess, deinstalled all current Java's, installed only JDK + JRE 1.7 64-bit.

One of the Eclipse 'installations' failed afterwards with the Failed to Load the JNI shared Library and a given path relative to the fresh installed JDK where it thought the jvm.dll to be.

The failing Eclipse was the only one of all my IDEs that was still a 32-bit version on my otherwise all-64-bit setup.

Adding VM arguments, like so often mentioned, in the eclipse.ini was no use in my case (because I had only the wrong JDK/JRE to relate to.)

I was also unable to find out how to check if this Eclipse was a 32-bit or 64-bit version (I could not look it up in the Task Manager, since this Eclipse 'installation' would not start up. And since it had been a while since I had set it up, I could not remember its version either.)

In case you use a newer JDK and a older JRE you might be in for trouble, too, but then it is more likely a java.lang.UnsupportedClassVersionError appears, IIRC.

6
  • 3
    It should only use the first \bin it comes to in the Path variable
    – ekinnear
    Jul 20, 2012 at 18:21
  • Mmmm, that is always the question... The Oracle docs say it only uses the first one, but maybe something else was being changed/was already in place and working. Seems like its always something strange like that.
    – ekinnear
    Jul 23, 2012 at 0:13
  • 9
    to check which version 32-bit or 64-bit, open eclipse.ini and look for the equinox launcher used (e.g. org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502)
    – Steve Oh
    Jun 6, 2013 at 9:16
  • I had this combo with the error. 64-bit OS - 32-bit JDK - 32-bit Eclipse and it doesn't work. I resolved it with this combo: 64-bit OS - 64-bit JDK - 64bit Eclipse (64-bit only). The %PATH% variable has been updated to point to the 64 bit java version. Actually the %JAVA_HOME% has been updated as this variable is used into %PATH% variable values.
    – thanos.a
    Mar 29, 2014 at 23:58
  • 1
    It was the comment by @ekinnear that solved my issue. I am not sure why it was looking for the JVM.dll in my windows/bin folder but putting the proper path in place seems to have resolved it.
    – James
    Mar 31, 2014 at 18:58
277

Make sure your eclipse.ini file includes the following lines.

-vm
C:\path\to\64bit\java\bin\javaw.exe

My eclipse.ini for example:

-startup
plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.2.R36x_v20101222
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
-vm
C:\Program Files\Java\jdk1.6.0_32\bin\javaw.exe
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m

Use OS and Eclipse both 64 bit or both 32 bit keep same and config eclipse.ini.

Your eclipse.ini file can be found in your eclipse folder.

9
  • 9
    This solves the problem. I added the -vm C:\Program Files\Java\jdk1.6.0_32\bin\javaw.exe line to my eclipse.ini file and it started up just fine. Thanks for the help +1.
    – prolink007
    Sep 10, 2012 at 13:36
  • 1
    this work fine please check your version of Java, run java -version in a console and Check that this is the version being used by Eclipse or not Oct 10, 2012 at 9:48
  • 2
    I did this with my Java 6 SDK, and it didn't work. I tried it again, pointing to my Java 7 SDK, and it worked. I'm on Windows 8 64-bit, Java 6 and 7 (both 64-bit) and Eclipse Helios (32-bit). I was ready to uninstall and re-install Eclipse 64-bit, but it seems the java 7 SDK includes some new intelligence to run 32 bit apps better. Jan 9, 2013 at 15:40
  • 9
    this works. but need to put -vm in the top of the ini file; at least before -vmargs or --launcher.xxx
    – pinkdawn
    Mar 27, 2013 at 1:33
  • 3
    Very Very Important point that I missed. If you use like: "-vm C:\ProgramFiles\Java\jdk1.6.0_32\bin\javaw.exe" it will never work Correct way "-vm C:\Program Files\Java\jdk1.6.0_32\bin\javaw.exe" New line after the -vm is very important.
    – School Boy
    Dec 27, 2013 at 2:11
57

I had same problem

I resolved it by installing 64 bit JVM from

http://www.java.com/en/download/manual.jsp

0
46

This error means that the architecture of Eclipse does not match the architecture of the Java runtime, i.e. if one is 32-bit the other must be the same, and not 64-bit.

The most reliable fix is to specify the JVM location in eclipse.ini:

-vm
C:\Program Files (x86)\Java\jdk1.7.0_55\bin\javaw.exe

Important: These two lines must come before -vmargs. Do not use quotes; spaces are allowed.

1
  • Hi, i'm working since some time ago with this .ini setup, Should i update the architecture to 64-bit or i can ignore the fact of having diferent architectures?? Thx
    – Billyjoker
    Mar 28, 2015 at 13:02
32

Another option is:

Create a shortcut to the Eclipse.exe. Open the shortcut and change the target to:

"C:\Program Files\eclipse\eclipse.exe" -vm "c:\Program Files\Java\jdk1.7.0_04\bin\javaw.exe"

For your installation, make sure the locations point to the correct Eclipse installation directory and the correct javaw.exe installation directory.

(The 64/32 bit versions of Eclipse and Java need to be the same, of course.)

2
  • Good options but adding it to the ini file as above should work Jan 19, 2013 at 4:16
  • 2
    No need to change the .ini file. Just use the 64 bit combo for java and eclipse
    – thanos.a
    Mar 29, 2014 at 23:59
29

I have multiple versions of Java installed, both Sun JDK & JRockit, both 32 bit and 64-bit, etc. and ran into this problem with a fresh install of 64-bit Eclipse for Java EE (JUNO).

What did NOT work:

64-bit trio as suggested by Peter Rader:

I'm using 64-bit Eclipse on 64-bit OS (Windows 7).

I ensured Sun JDK 7 64-bit was the default java version. When I typed "java -version" from command line (cmd.exe), Sun JDK 7 64-bit was returned...

java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)

This did not resolve the problem for me.

What DID work:

Adding -vm option to eclipse.ini as suggested by Jayesh Kavathiya:

I added the following to eclipse.ini:

-vm
C:/apps/java/jdk7-64bit/bin/javaw.exe

Note:

I did not have to uninstall any of the various versions of JDK or JRE I have on my machine.

3
  • I did not have to uninstall the JDK's either, but I chose to clean my system to wipe out future error causes. I had also mentioned the VM arguments, and explained why they could obviously not work for me. It is your choice how you want to set up your system, depending on what you really need.
    – sjas
    Oct 8, 2012 at 15:09
  • I had to do both things, but adding the javaw.exe line then led me to install everything on 64 bit, anyways. It depends on how much karma punishment you are due to pay to android.
    – Josh
    Aug 12, 2014 at 8:16
  • I have been developing for years, and with no change to my system (that I am aware of), Eclipse throws this error. Adding the -vm option sorted it out for me, without needing to change any other settings or un/re/install anything.
    – Knossos
    Apr 22, 2015 at 5:40
18

For a missing jvm.dll file, we can provide the path of the dll file in eclipse.ini file as

-vm
C:\Progra~1\Java\jdk1.6.0_38\jre\bin\server\jvm.dll

Here it is important to remove any space in the path and the double quotes. It worked for me when i removed the quotes and space.

I hope it helps someone.

1
  • 1
    This helped me instead of -vm javaw.exe
    – amj
    Feb 23, 2015 at 6:32
10

I had a similar problem. It was solved doing the following.

  • Move Eclipse to Program Files (not to Program Files (x86)).
  • Remove the path to the 32-bit version of Java from the 'path' environment variable.

I have both versions of Java installed, but Eclipse kept trying to use the 32-bit one.

0
10

Sure, you need to have a compatible version of JDK and Eclipse, but you also need to add in the eclipse.ini file the below lines:

-vm
yourdrive\java\bin

Make them the first two lines of your eclipse.ini file.

0
7

As many folks already alluded to, this is a 32 vs. 64 bit problem for both Eclipse and Java. You cannot mix up 32 and 64 bit. Since Eclipse doesn't use JAVA_HOME, you'll likely have to alter your PATH prior to launching Eclipse to ensure you are using not only the appropriate version of Java, but also if 32 or 64 bit (or modify the INI file as Jayath noted).

If you are installing Eclipse from a company-share, you should ensure you can tell which Eclipse version you are unzipping, and unzip to the appropriate Program Files directory to help keep track of which is which, then change the PATH (either permanently via (Windows) Control Panel -> System or set PATH=/path/to/32 or 64bit/java/bin;%PATH% (maybe create a batch file if you don't want to set it in your system and/or user environment variables). Remember, 32-bit is in Program files (x86).

If unsure, just launch Eclipse, if you get the error, change your PATH to the other 'bit' version of Java, and then try again. Then move the Eclipse directory to the appropriate Program Files directory.

1
  • It's clearly a problem as this page as 700k views currently... and a year later there's apparently no fix for it that doesn't involve poking around in environment variables just to get the IDE to run! Dec 2, 2014 at 15:23
7

The answers above me got me tempted so much, that I decided to dry run all the possible combinations with OS, Eclipse and JVM trio. Anyway, whoever is digging down and reading my post, check the following as a hot spot (I am Windows 7 user).

  1. You understand Program Files and Program File (x86) are two different folders... x86 stands for the 32-bit version of programs and the former is the 64-bit version.

  2. If you have multiple versions of Java installed with different bitness and release versions, which is bound to happen with so many open source IDEs, managers, administrative consoles, the best option is to set the VM argument directly in the eclipse.ini file. If you don't, Eclipse will go crazy and try searching itself which is not good.

0
6

Alternatively, get the same "bit" version of JRE and Eclipse and then create a new shortcut with the below target (replace the installed JRE and Eclipse location/path):

"C:\studio\eclipse.exe" -vm "C:\Program Files\Java\jre7\bin\server\jvm.dll" eclipse.vm="C:\Program Files\Java\jre7\bin\server\jvm.dll" java.home="C:\Program Files\Java\jre7" java.runtime.version=1.7.0

That should do the trick.

0
6

You can solve that problem as many other replicated. You need that Eclipse and the JDK be 32-bits or both on 64-bits. The architecture of the OS doesn't matter while the others remains on the same type of arquitecture.

5

One of the easy ways to resolve it is to copy the jre folder from installed the JDK into the Eclipse installation folder. Make sure that JDK you copy from is the same architecture as your Eclipse installation.

I had to configure my machine that way, because I run both Eclipse and Appcelerator Titanium Studio on my machine. The Studio needs 32-bit Java, while Eclipse needs 64-bit.

3
  • I did the same thing a long time ago, but for eclipse-jee-juno-SR1-win32 and Java6, I could not get it to work, this time around. Did you also edit the eclipse.ini with an absolute path to the jre ?
    – user77115
    Oct 10, 2012 at 3:25
  • I also have Eclipse 64 width jdk 7 64bit, but titanium tall me it's unable to load jni shared dll.
    – realtebo
    Apr 19, 2013 at 14:25
  • Because of Window's crazy autoupdates, whenever there is an update for JAVA, it blocks my Eclipe from launching. Above solution is the easiest way to work independently without caring about autoupdates. Thanks! Feb 28, 2019 at 12:27
4

Yes, just make sure your versions of Eclipse and JDK are both 64-bit. Just to make sure everything is correct uninstalled JDK and install it in Program Files and not in Program Files (x86). At least that resolved my problem.

4

Just check the PATH environment variable. In My Computer - > Properties -> Advanced System settings -> Environment Variables -> (left upper window "User Variables for "some name of PC"" ) just check the PATH variable. If it doesn't exist create it with the following -- > C:\Program Files (x86)\Java\jre7\bin <--

I was faced with the same problem after had updated my Eclipse. I've found that the path asked 64-bit version, but I had the 32-bit in dif path. It was helpful for me. P.S.: I have a 64-bit OS, 32-bit JRE and 32-bit Eclipse. All works fine :)

4

You should uninstall all old [JREs][1] and then install the newest one... I had the same problem and now I solve it. I've:

Better install Jre 6 32 bit. It really works.

3

Downloaded 64 bit JVM from site and installed it manually and updated the system path variable. That solved the issue.

  1. Default JVM is installed in my system was in "C:\Program Files
    (x86)\Java\jre7"
  2. Manually installed JVM got installed in "C:\Program Files\Java\jre7" and after updating this pate to system path variable it worked.
3

Thank you misterfrb, I realised that Eclipse was giving this error, because I had just installed Oracle 10g Developer suite, and it was looking for the jvm.dll file in the C:\DevSuiteHome_1 folder (I must have opted to install JDK again along with developer suite).

After removing the DevSuiteHome lines from the paths variable and adding the correction location for 64-bit jvm.dll (not sure if this was necessary, didn't try without), Eclipse worked again, and Developer suite still does too.

3

Simple, I have a 64-bit OS, 32-bit Eclipse and both JDK 32 & 64 installed... I just uninstalled the 64-bit JDK and Eclipse is working fine..

3

I had the same issue after upgrading from Java 6 to Java 7. After I removed Java 6 (64 bit) and reinstalled Java 7 (64 bit), Eclipse worked. :)

0
3

It is crucial to add the -vm parameter and its value on 2 lines AT THE BEGINNING of the eclipse.ini

-vm C:\Program Files\Java\jdk1.7.0_45\bin\javaw.exe

3

You have change proper version of the JAVA_HOME and PATH in environmental variables.

1
  • 1
    Worked well for me. I've installed multiple Java versions to test and the Path and JAVA_HOME wasn't pointing to the same installation. My Solution: Changed the Path to "%JAVA_HOME%\bin" Dec 4, 2020 at 18:21
3

I want to previde another solution for this error, especially for who want to use 32-bit and 64-bit Eclipse in one system.

Eclipse will startup using the JRE/JDK in jre sub-directory if it exists. (STS or other eclipse based IDE also support this feature...)

The solution is create directory junction using mklink.exe command which exist in windows vista or newer version (junction.exe offer similar function for Windows 2000/XP)
Open the command line windows and exeute following command:

mklink /j "$ECLIPSE-HOME/jre" "$JDK_or_JRE_home"

Of course, if the Eclipse is for 64-bit Windows, the architecture of JDK/JRE must be the same.

Assume:

  • Eclipse for windows x86_64 is installed in d:\devTool\eclipse
  • JDK for windows x64 is installed in C:\Program Files\Java\jdk1.8.0

The command for creating the jre folder will be:

mklink /j "d:\devTool\eclipse\jre" "C:\Program Files\Java\jdk1.8.0"

BTW, delete directory junction will NOT delete any file. If you create a wrong link, you can delete it using file explorer or rmdir command.

rmdir "d:\devTool\eclipse\jre"

2

Make sure you are starting Eclipse with Administrator rights.

0
2

If you use whole 64-bit trio and it still doesn't work (I've come to this problem while launching Android Monitor in Intellij Idea), probably wrong jvm.dll is being used opposed to what your java expects. Just follow these steps:

  1. Find the jvm.dll in your JRE directory: C:\Program Files\Java\jre7\server\bin\jvm.dll

  2. Find the jvm.dll in your JDK directory: c:\Program Files\Java\jdk1.7.0_xx\jre\bin\server\

  3. Copy the jvm.dll from JRE drectory into your JDK directory and overwrite the jvm.dll in JDK.

Don't forget to make a backup, just in case. No need to install or uninstall anything related to Java.

0
2

The same occurred to me. I had 64-bit Eclipse, but my JDK was 32-bit. So I installed the 64-bit version and it's OK right now.

2

I'm not sure why but I had the jre installed into my c:\windows directory and java.exe and javaw.exe inside my windows\system32 directory.

Obviously these directories were getting priority even AFTER adding the -vm flag to my eclipse.ini file.

Delete them from here fixed the issue for me.

0
1

On the download page of Eclipse, it should be written "JRE 32 bits" or "JRE 64 bits" and not "Windows 32 bits" or "Windows 64 bits".

Be sure to use the correct version compatible with your JDE, as answered previously.

Not the answer you're looking for? Browse other questions tagged or ask your own question.