Error In Loading Jvm.dll
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Failed to load the JNI shared Library (JDK) up vote 746 down vote favorite 159 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 StackOverflow, 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? eclipse jni java share|improve this question edited Feb 18 '13 at 19:19 community wiki Mike S. What exactly was the problem in your case? –sjas Jul 3 '12 at 22:30 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). –Mike S. Jul 4 '12 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. –Mike S. Jul 4 '12 at 10:42 @MikeGates I had that problem too, used LockHunter. Obnoxious. Getting this tool to run on Windows is way too much work. –jcollum Jan 17 '13 at 23:33 Eclipse/Java sucks when it comes to 64bits, it is a
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers http://superuser.com/questions/849353/java-runtime-environment-path-issues or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Java runtime environment path issues up vote 0 down vote favorite I've had a problem with my Java installations error in for quite some time and I've never had time to sit and try to fix this problem. So I went ahead and uninstalled all the various versions of Java I'd installed to get Weka to work. I then went ahead and installed JDK v7u71 x64 (my machine is a 64bit one). I added the bin directory of this newly installed java to my PATH. I go to the command prompt and type in 'java -version'. Here, I'm greeted by the same error in loading old error messages: "Error: loading: C:\Windows\jre\bin\msvcr100.dll Error: loading: C:\Windows\jre\bin\client\jvm.dll" Then I ran this command: '"C:\Program Files\Java\jre7\bin\java" -version' and the correct version comes up. I went and looked at the jre directory within the Windows directory and it had an msvcr100.dll there and a jvm.dll. Why is that particular 'java' not working? and what do I have to do to get java to work correctly on my system? One solution was that I renamed (removed) the Windows jre folder and tried the 'java -version' command. It worked. But I'm not sure that's the best solution to my problem. windows-7 java path environment-variables share|improve this question asked Dec 6 '14 at 16:18 Siddharth Kumar 11 after you change the PATH, type PATH