Running Java gives “Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'”












35















After years of working OK, I'm suddenly getting this message when trying to start the JVM:



Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


I tried uninstalling, and got a message saying a DLL was missing (unspecified)
Tried re-installing, all to no avail.



At the same time, when trying to start Scala I get:



Javajdk1.6.0_25binjava.exe was unexpected at this time.


Checked %JAVA_HOME% and %path% - both OK



Can anyone help?










share|improve this question

























  • Looks like your JVM got corrupt, or your PATH is polluted. The JVM you think you are running might not be the JVM you should be running. try running java -version to find out if it is 1.6.0_xx.

    – Raze
    May 17 '11 at 20:34






  • 2





    How is this related to Scala?

    – Rodney Gitzel
    May 17 '11 at 20:42






  • 2





    I can't even do java -version without getting the message!

    – Highland Mark
    May 17 '11 at 20:55











  • It's related to scala in that scala fails too. Both occurred at the same time.

    – Highland Mark
    May 17 '11 at 20:56











  • here is what i've found in google. Maybe it will help: link

    – tonek
    May 17 '11 at 21:06
















35















After years of working OK, I'm suddenly getting this message when trying to start the JVM:



Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


I tried uninstalling, and got a message saying a DLL was missing (unspecified)
Tried re-installing, all to no avail.



At the same time, when trying to start Scala I get:



Javajdk1.6.0_25binjava.exe was unexpected at this time.


Checked %JAVA_HOME% and %path% - both OK



Can anyone help?










share|improve this question

























  • Looks like your JVM got corrupt, or your PATH is polluted. The JVM you think you are running might not be the JVM you should be running. try running java -version to find out if it is 1.6.0_xx.

    – Raze
    May 17 '11 at 20:34






  • 2





    How is this related to Scala?

    – Rodney Gitzel
    May 17 '11 at 20:42






  • 2





    I can't even do java -version without getting the message!

    – Highland Mark
    May 17 '11 at 20:55











  • It's related to scala in that scala fails too. Both occurred at the same time.

    – Highland Mark
    May 17 '11 at 20:56











  • here is what i've found in google. Maybe it will help: link

    – tonek
    May 17 '11 at 21:06














35












35








35


8






After years of working OK, I'm suddenly getting this message when trying to start the JVM:



Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


I tried uninstalling, and got a message saying a DLL was missing (unspecified)
Tried re-installing, all to no avail.



At the same time, when trying to start Scala I get:



Javajdk1.6.0_25binjava.exe was unexpected at this time.


Checked %JAVA_HOME% and %path% - both OK



Can anyone help?










share|improve this question
















After years of working OK, I'm suddenly getting this message when trying to start the JVM:



Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


I tried uninstalling, and got a message saying a DLL was missing (unspecified)
Tried re-installing, all to no avail.



At the same time, when trying to start Scala I get:



Javajdk1.6.0_25binjava.exe was unexpected at this time.


Checked %JAVA_HOME% and %path% - both OK



Can anyone help?







java scala






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 23 '14 at 14:02









xyz

17.3k2995143




17.3k2995143










asked May 17 '11 at 20:07









Highland MarkHighland Mark

6371512




6371512













  • Looks like your JVM got corrupt, or your PATH is polluted. The JVM you think you are running might not be the JVM you should be running. try running java -version to find out if it is 1.6.0_xx.

    – Raze
    May 17 '11 at 20:34






  • 2





    How is this related to Scala?

    – Rodney Gitzel
    May 17 '11 at 20:42






  • 2





    I can't even do java -version without getting the message!

    – Highland Mark
    May 17 '11 at 20:55











  • It's related to scala in that scala fails too. Both occurred at the same time.

    – Highland Mark
    May 17 '11 at 20:56











  • here is what i've found in google. Maybe it will help: link

    – tonek
    May 17 '11 at 21:06



















  • Looks like your JVM got corrupt, or your PATH is polluted. The JVM you think you are running might not be the JVM you should be running. try running java -version to find out if it is 1.6.0_xx.

    – Raze
    May 17 '11 at 20:34






  • 2





    How is this related to Scala?

    – Rodney Gitzel
    May 17 '11 at 20:42






  • 2





    I can't even do java -version without getting the message!

    – Highland Mark
    May 17 '11 at 20:55











  • It's related to scala in that scala fails too. Both occurred at the same time.

    – Highland Mark
    May 17 '11 at 20:56











  • here is what i've found in google. Maybe it will help: link

    – tonek
    May 17 '11 at 21:06

















Looks like your JVM got corrupt, or your PATH is polluted. The JVM you think you are running might not be the JVM you should be running. try running java -version to find out if it is 1.6.0_xx.

– Raze
May 17 '11 at 20:34





Looks like your JVM got corrupt, or your PATH is polluted. The JVM you think you are running might not be the JVM you should be running. try running java -version to find out if it is 1.6.0_xx.

– Raze
May 17 '11 at 20:34




2




2





How is this related to Scala?

– Rodney Gitzel
May 17 '11 at 20:42





How is this related to Scala?

– Rodney Gitzel
May 17 '11 at 20:42




2




2





I can't even do java -version without getting the message!

– Highland Mark
May 17 '11 at 20:55





I can't even do java -version without getting the message!

– Highland Mark
May 17 '11 at 20:55













It's related to scala in that scala fails too. Both occurred at the same time.

– Highland Mark
May 17 '11 at 20:56





It's related to scala in that scala fails too. Both occurred at the same time.

– Highland Mark
May 17 '11 at 20:56













here is what i've found in google. Maybe it will help: link

– tonek
May 17 '11 at 21:06





here is what i've found in google. Maybe it will help: link

– tonek
May 17 '11 at 21:06












18 Answers
18






active

oldest

votes


















16














Might be a slightly different cause, but that second issue occurs for me in scala 2.9.0.1 on Win7 (x64), though scala-2.9.1.final has already resolved this issue mentioned here:



Javajdk1.6.0_25binjava.exe was unexpected at this time.


My %JAVA_HOME% set to a path like this: c:program files(x86)Javajdk...



Note the space and the parentheses.



If you change line 24 in %SCALA_HOME%binscala.bat from:



if exist "%JAVA_HOME%binjava.exe" set _JAVACMD=%JAVA_HOME%binjava.exe


to



if exist "%JAVA_HOME%binjava.exe" set "_JAVACMD=%JAVA_HOME%binjava.exe"


It works fine. Note the quotes around the set command parameters, this will properly enclose any spaces and 'special' characters (eg: spaces and parentheses) in the variable's value.



Hope this helps someone else searching for an answer.






share|improve this answer


























  • Well done! That seems like the problem.

    – Highland Mark
    Jun 4 '11 at 19:21











  • thank you dude, saved me :-)

    – Jahan Zinedine
    Aug 29 '11 at 5:22








  • 1





    +1, but same treatment should be applied also to the file: %SCALA_HOME%binscalac.bat

    – Israel Unterman
    Dec 14 '12 at 6:27











  • thanks! in my case, I renamed the Windows partition where Java was installed. Reverting that change fixed it.

    – asgs
    May 29 '15 at 17:01



















80














I checked my environment variables - JAVA_HOME & PATH and they all refer to C:java. So this was bit frustrating. After sometime I found that the default installation also copied java.exe, javaw.exe and javaws.exe to C:WindowsSystem32 (i.e. uninstall of JRE didn't go well). I just removed them and voila, I'm back on track. That annoying error is no longer popping.



This works for me



So, If exists, remove java.exe, javaw.exe and javaws.exe from System32






share|improve this answer





















  • 7





    The most bizarre answer that has ever worked, THANK YOU!

    – jn1kk
    Jul 25 '13 at 20:22






  • 1





    The right answer is here :)

    – Farah
    Dec 15 '13 at 20:09






  • 1





    Worked like a charm..... Thanks man!!!!

    – Saumil
    Dec 18 '13 at 7:40






  • 1





    Why Oracle/Sun ever decided to do this and not fix the uninstaller is beyond me. Thank you.

    – makhdumi
    May 11 '14 at 23:17






  • 1





    Still didn't get it but it worked

    – Weishi Zeng
    Aug 5 '14 at 17:53



















28














put %JAVA_HOME%bin at the begin of PATH.






share|improve this answer



















  • 3





    Got the same problem on Windows although my PATH and JAVA_HOME was OK. Moving the %JAVA_HOME% to the beginning of the PATH solved it. Thanks!

    – Samuel
    Nov 21 '12 at 10:33











  • It works too! Thanks!

    – bsiamionau
    Apr 5 '13 at 11:10











  • nice .......................

    – N..
    Dec 3 '13 at 10:54











  • You just saved me a lot of pain. Thank you !

    – Antoine Cloutier
    Sep 13 '14 at 14:26











  • Despite doing this, I was getting the error. What I didn't notice was when I opened a CMD prompt, it would default to C:WindowsSystem32, which contained the troublesome java install. Changing out to any other directory would make Java work just fine with the JDK I wanted on the path.

    – CrazyPenguin
    Feb 11 '16 at 20:41



















8














I had the same problem: I have a 64 bit Windows and when I typed "java -version" in CMD-Console i received the same Error message.
Try to start a 64bit-cmd(C:WindowsSysWOW64cmd.exe) and you will see, it works there ;)






share|improve this answer


























  • Great, it works! A lot of thanks!

    – bsiamionau
    Apr 5 '13 at 11:03













  • Thanks so much!! it helped me too

    – sunskin
    Jul 5 '13 at 18:52



















2














If this was working before, it means the PATH isn't correct anymore.



That can happen when the PATH becomes too long and gets truncated.

All posts (like this one) suggest updating the PATH, which you can test first in a separate DOS session, by setting a minimal path and see if java works again there.





Finally the OP Highland Mark concludes:




Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing.




scary ;)






share|improve this answer


























  • Thanks. Still I can't sort it. With minimal path (path = %JAVA_HOME%bin) it works - as you say, however, I can't see the problem in the actual path which is "...;%JAVA_HOME%bin;..." which contains the same thing.

    – Highland Mark
    May 19 '11 at 8:37













  • Finally managed to remove old versions of JRE using JavaRA & MSICUU2.exe, reloaded latest version, but still the same message.

    – Highland Mark
    May 19 '11 at 9:18






  • 1





    @Highland: if this works with a minimal path but not with a full path, that means %JAVA_HOME%bin isn't the issue. Some other element in the PATH causes the runtime to fail. Could you try with a PATH you would build, one element at a time, to see when java stop launching?

    – VonC
    May 19 '11 at 10:32











  • Thanks VonC - that gives me something to work on. I'll report back.

    – Highland Mark
    May 19 '11 at 10:50











  • It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all.

    – Highland Mark
    May 19 '11 at 15:01



















2














I thought I will share how I resolved the same issue "Error Could not open libamd64jvm.cfg". I found the Java run time Jre7 is missing amd64 folder under lib. However, I have 1.7.0_25 JDK which is having jre folder and also having amd64.



I moved the original contents of jre7 folder to a backup file and copied everything from 1.7.0_25jre.



Now I am not getting this error anymore and able to proceed with scene builder.






share|improve this answer































    2














    The Java 7 install on my work PC broke after a patch was forced out to us, giving this error any time you tried to run a Java program. Somehow the entire 'lib' subdirectory of the Java 7 install vanished! Might have been related to having both Java 6 and Java 7 installed -- the 'jre6' directory still had everything there.



    In any case, I fixed it by uninstalling both Java 6 and Java 7 and reinstalling just Java 7. But if the file it's complaining about is actually there, then you're likely having a path issue as described in some of the other answers here.






    share|improve this answer
























    • except in my case reinstalling the JRE did not replace the missing lib folder :(

      – David
      Apr 17 '14 at 15:26











    • Ah ... I reinstalled the 64-bit JRE, but it turns out there was also a 32-bit JRE installed. I uninstalled both -- they were a couple of patchlevels behind anyway -- then reinstalled the 64-bit JRE (only) and now everything is copacetic.

      – David
      Apr 17 '14 at 17:58



















    2














    Had suddenly the same Problem, from one day to another eclipse said



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


    after trying to run java on the console



    Error: could not open `C:WINDOWSjrelibamd64jvm.cfg' 


    now i just deleted the whole directory



    C:WINDOWSjre


    and everything worked again... i don't know there this jre came from, i hope it was not a virus






    share|improve this answer































      1














      I had the same problem in Eclipse and I fixed it by changing the JRE from 64 bit to 32 bit:



      Window > Preferences > Java > Installed JREs > Add... > Next > Directory > select "C:Program Files (x86)Javajre1.8.0_65" instead of "C:Program FilesJavajre1.8.0_60"






      share|improve this answer
























      • This issue occurred to me while installing eclipse. I was installing eclipse after JAVA update where my earlier version was 1.8.0_60 and the newer version was 1.8.0_191 which i guess is changed while installing update so i changed folder name to earlier i.e. 1.8.0_60 . So the issue is with post install script of JAVA update i guess @ time of Update installation both names should be changed by install which is not the case. i.e. minor change is remaining after post install of java update.

        – Rahul
        Nov 15 '18 at 17:31





















      1














      C:ProgramDataOracleJavajavapath worked for me .. , I have took back up of the files and removed the files in it.Opened new cmd prompt and then .. tested and works like charm






      share|improve this answer
























      • Had to go too deep for this. Thank you, worked like a charm.

        – Fernando Martín Besteiro
        Aug 31 '17 at 18:28



















      1















      • I had a similar problem (trying to start a Jenkins slave agent on Windows) on Windows 2008R2, Java 1.7.0_15



      • I had two situations that contributed to the problem and that changing both of them fixed it:



        1) Installing Java in a unix-compatible path (changing from c:Program Files... to c:Software...); I don't think this directly affected the problem described in this thread, but noting the change;



        2) Running Java not through a shortcut. It originally failed with a shortcut, but re-running from the direct executable (C:SoftwareJava...binjava) worked.








      share|improve this answer

































        0














        Reinstalling java didn't help me. But the trick to put the JAVA_HOME variable at the beginning of the env-vars. The problem occoured after an upgrade from jdk1.7.0_11 to jdk1.7.0_13






        share|improve this answer

































          0














          Another workaround is using shortpath in windows:




          1. open windows command console using cmd.exe

          2. goto c:

          3. type command> dir program* /x

          4. it should display as short path like: PROGRA~2

          5. so C:PROGRA~2 is same as C:Program Files (x86)

          6. in your JAVA_HOME replace path to :
            C:PROGRA~2Javajre7


          This should work in windows 64 environment as it worked for me in win7 64bit version.






          share|improve this answer

































            0














            I have changed the java installation path from c:Program Files (x86)java to another folder like c:javajdk1.7 and updated the %Java_HOME% and path values accordingly,it worked.



            example



            %JAVA_HOME% = C:javaJDK1.7

            path-C:javaJDK1.7bin;





            share|improve this answer

































              0














              I had this problem after updating your java. The best way to solve this problem is just go to your c:/ProgramFiles/Java folder. There you will find two jre folders one is as jre.your version and other with exactly like jdk folder. Try to remove jre.1.your version folder. There you go your problem is solved. Hope this might help. It's worked for me.






              share|improve this answer































                0














                Typically it because of upgrading JRE.



                It changes symlinks into C:ProgramDataOracleJavajavapath



                Intall JDK - it will fix this.






                share|improve this answer































                  0














                  Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


                  Looking @ it the issue of post install script is there and getting propagated since I am using update jdk8 1.8.0_191 since issue occurred with me after installing update of java and which was happened automatically.



                  Error: could not open `C:Program FilesJavajre1.8.0_191libamd64jvm.cfg'


                  This will be never ending in this case and need to do workaround like changing path's manually.






                  share|improve this answer































                    -1














                    It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all @Highland Mark- Can you tell me the process to removing references from registry. I tried all possible way people mentioned here, nothing worked.






                    share|improve this answer






















                      protected by Community Apr 9 '17 at 14:54



                      Thank you for your interest in this question.
                      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                      Would you like to answer one of these unanswered questions instead?














                      18 Answers
                      18






                      active

                      oldest

                      votes








                      18 Answers
                      18






                      active

                      oldest

                      votes









                      active

                      oldest

                      votes






                      active

                      oldest

                      votes









                      16














                      Might be a slightly different cause, but that second issue occurs for me in scala 2.9.0.1 on Win7 (x64), though scala-2.9.1.final has already resolved this issue mentioned here:



                      Javajdk1.6.0_25binjava.exe was unexpected at this time.


                      My %JAVA_HOME% set to a path like this: c:program files(x86)Javajdk...



                      Note the space and the parentheses.



                      If you change line 24 in %SCALA_HOME%binscala.bat from:



                      if exist "%JAVA_HOME%binjava.exe" set _JAVACMD=%JAVA_HOME%binjava.exe


                      to



                      if exist "%JAVA_HOME%binjava.exe" set "_JAVACMD=%JAVA_HOME%binjava.exe"


                      It works fine. Note the quotes around the set command parameters, this will properly enclose any spaces and 'special' characters (eg: spaces and parentheses) in the variable's value.



                      Hope this helps someone else searching for an answer.






                      share|improve this answer


























                      • Well done! That seems like the problem.

                        – Highland Mark
                        Jun 4 '11 at 19:21











                      • thank you dude, saved me :-)

                        – Jahan Zinedine
                        Aug 29 '11 at 5:22








                      • 1





                        +1, but same treatment should be applied also to the file: %SCALA_HOME%binscalac.bat

                        – Israel Unterman
                        Dec 14 '12 at 6:27











                      • thanks! in my case, I renamed the Windows partition where Java was installed. Reverting that change fixed it.

                        – asgs
                        May 29 '15 at 17:01
















                      16














                      Might be a slightly different cause, but that second issue occurs for me in scala 2.9.0.1 on Win7 (x64), though scala-2.9.1.final has already resolved this issue mentioned here:



                      Javajdk1.6.0_25binjava.exe was unexpected at this time.


                      My %JAVA_HOME% set to a path like this: c:program files(x86)Javajdk...



                      Note the space and the parentheses.



                      If you change line 24 in %SCALA_HOME%binscala.bat from:



                      if exist "%JAVA_HOME%binjava.exe" set _JAVACMD=%JAVA_HOME%binjava.exe


                      to



                      if exist "%JAVA_HOME%binjava.exe" set "_JAVACMD=%JAVA_HOME%binjava.exe"


                      It works fine. Note the quotes around the set command parameters, this will properly enclose any spaces and 'special' characters (eg: spaces and parentheses) in the variable's value.



                      Hope this helps someone else searching for an answer.






                      share|improve this answer


























                      • Well done! That seems like the problem.

                        – Highland Mark
                        Jun 4 '11 at 19:21











                      • thank you dude, saved me :-)

                        – Jahan Zinedine
                        Aug 29 '11 at 5:22








                      • 1





                        +1, but same treatment should be applied also to the file: %SCALA_HOME%binscalac.bat

                        – Israel Unterman
                        Dec 14 '12 at 6:27











                      • thanks! in my case, I renamed the Windows partition where Java was installed. Reverting that change fixed it.

                        – asgs
                        May 29 '15 at 17:01














                      16












                      16








                      16







                      Might be a slightly different cause, but that second issue occurs for me in scala 2.9.0.1 on Win7 (x64), though scala-2.9.1.final has already resolved this issue mentioned here:



                      Javajdk1.6.0_25binjava.exe was unexpected at this time.


                      My %JAVA_HOME% set to a path like this: c:program files(x86)Javajdk...



                      Note the space and the parentheses.



                      If you change line 24 in %SCALA_HOME%binscala.bat from:



                      if exist "%JAVA_HOME%binjava.exe" set _JAVACMD=%JAVA_HOME%binjava.exe


                      to



                      if exist "%JAVA_HOME%binjava.exe" set "_JAVACMD=%JAVA_HOME%binjava.exe"


                      It works fine. Note the quotes around the set command parameters, this will properly enclose any spaces and 'special' characters (eg: spaces and parentheses) in the variable's value.



                      Hope this helps someone else searching for an answer.






                      share|improve this answer















                      Might be a slightly different cause, but that second issue occurs for me in scala 2.9.0.1 on Win7 (x64), though scala-2.9.1.final has already resolved this issue mentioned here:



                      Javajdk1.6.0_25binjava.exe was unexpected at this time.


                      My %JAVA_HOME% set to a path like this: c:program files(x86)Javajdk...



                      Note the space and the parentheses.



                      If you change line 24 in %SCALA_HOME%binscala.bat from:



                      if exist "%JAVA_HOME%binjava.exe" set _JAVACMD=%JAVA_HOME%binjava.exe


                      to



                      if exist "%JAVA_HOME%binjava.exe" set "_JAVACMD=%JAVA_HOME%binjava.exe"


                      It works fine. Note the quotes around the set command parameters, this will properly enclose any spaces and 'special' characters (eg: spaces and parentheses) in the variable's value.



                      Hope this helps someone else searching for an answer.







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Jun 6 '14 at 13:46









                      user1585643

                      96118




                      96118










                      answered Jun 2 '11 at 14:15









                      ClintonClinton

                      2,2291410




                      2,2291410













                      • Well done! That seems like the problem.

                        – Highland Mark
                        Jun 4 '11 at 19:21











                      • thank you dude, saved me :-)

                        – Jahan Zinedine
                        Aug 29 '11 at 5:22








                      • 1





                        +1, but same treatment should be applied also to the file: %SCALA_HOME%binscalac.bat

                        – Israel Unterman
                        Dec 14 '12 at 6:27











                      • thanks! in my case, I renamed the Windows partition where Java was installed. Reverting that change fixed it.

                        – asgs
                        May 29 '15 at 17:01



















                      • Well done! That seems like the problem.

                        – Highland Mark
                        Jun 4 '11 at 19:21











                      • thank you dude, saved me :-)

                        – Jahan Zinedine
                        Aug 29 '11 at 5:22








                      • 1





                        +1, but same treatment should be applied also to the file: %SCALA_HOME%binscalac.bat

                        – Israel Unterman
                        Dec 14 '12 at 6:27











                      • thanks! in my case, I renamed the Windows partition where Java was installed. Reverting that change fixed it.

                        – asgs
                        May 29 '15 at 17:01

















                      Well done! That seems like the problem.

                      – Highland Mark
                      Jun 4 '11 at 19:21





                      Well done! That seems like the problem.

                      – Highland Mark
                      Jun 4 '11 at 19:21













                      thank you dude, saved me :-)

                      – Jahan Zinedine
                      Aug 29 '11 at 5:22







                      thank you dude, saved me :-)

                      – Jahan Zinedine
                      Aug 29 '11 at 5:22






                      1




                      1





                      +1, but same treatment should be applied also to the file: %SCALA_HOME%binscalac.bat

                      – Israel Unterman
                      Dec 14 '12 at 6:27





                      +1, but same treatment should be applied also to the file: %SCALA_HOME%binscalac.bat

                      – Israel Unterman
                      Dec 14 '12 at 6:27













                      thanks! in my case, I renamed the Windows partition where Java was installed. Reverting that change fixed it.

                      – asgs
                      May 29 '15 at 17:01





                      thanks! in my case, I renamed the Windows partition where Java was installed. Reverting that change fixed it.

                      – asgs
                      May 29 '15 at 17:01













                      80














                      I checked my environment variables - JAVA_HOME & PATH and they all refer to C:java. So this was bit frustrating. After sometime I found that the default installation also copied java.exe, javaw.exe and javaws.exe to C:WindowsSystem32 (i.e. uninstall of JRE didn't go well). I just removed them and voila, I'm back on track. That annoying error is no longer popping.



                      This works for me



                      So, If exists, remove java.exe, javaw.exe and javaws.exe from System32






                      share|improve this answer





















                      • 7





                        The most bizarre answer that has ever worked, THANK YOU!

                        – jn1kk
                        Jul 25 '13 at 20:22






                      • 1





                        The right answer is here :)

                        – Farah
                        Dec 15 '13 at 20:09






                      • 1





                        Worked like a charm..... Thanks man!!!!

                        – Saumil
                        Dec 18 '13 at 7:40






                      • 1





                        Why Oracle/Sun ever decided to do this and not fix the uninstaller is beyond me. Thank you.

                        – makhdumi
                        May 11 '14 at 23:17






                      • 1





                        Still didn't get it but it worked

                        – Weishi Zeng
                        Aug 5 '14 at 17:53
















                      80














                      I checked my environment variables - JAVA_HOME & PATH and they all refer to C:java. So this was bit frustrating. After sometime I found that the default installation also copied java.exe, javaw.exe and javaws.exe to C:WindowsSystem32 (i.e. uninstall of JRE didn't go well). I just removed them and voila, I'm back on track. That annoying error is no longer popping.



                      This works for me



                      So, If exists, remove java.exe, javaw.exe and javaws.exe from System32






                      share|improve this answer





















                      • 7





                        The most bizarre answer that has ever worked, THANK YOU!

                        – jn1kk
                        Jul 25 '13 at 20:22






                      • 1





                        The right answer is here :)

                        – Farah
                        Dec 15 '13 at 20:09






                      • 1





                        Worked like a charm..... Thanks man!!!!

                        – Saumil
                        Dec 18 '13 at 7:40






                      • 1





                        Why Oracle/Sun ever decided to do this and not fix the uninstaller is beyond me. Thank you.

                        – makhdumi
                        May 11 '14 at 23:17






                      • 1





                        Still didn't get it but it worked

                        – Weishi Zeng
                        Aug 5 '14 at 17:53














                      80












                      80








                      80







                      I checked my environment variables - JAVA_HOME & PATH and they all refer to C:java. So this was bit frustrating. After sometime I found that the default installation also copied java.exe, javaw.exe and javaws.exe to C:WindowsSystem32 (i.e. uninstall of JRE didn't go well). I just removed them and voila, I'm back on track. That annoying error is no longer popping.



                      This works for me



                      So, If exists, remove java.exe, javaw.exe and javaws.exe from System32






                      share|improve this answer















                      I checked my environment variables - JAVA_HOME & PATH and they all refer to C:java. So this was bit frustrating. After sometime I found that the default installation also copied java.exe, javaw.exe and javaws.exe to C:WindowsSystem32 (i.e. uninstall of JRE didn't go well). I just removed them and voila, I'm back on track. That annoying error is no longer popping.



                      This works for me



                      So, If exists, remove java.exe, javaw.exe and javaws.exe from System32







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Mar 2 '18 at 11:04









                      Helder Pereira

                      3,37521339




                      3,37521339










                      answered Apr 18 '13 at 15:03









                      Full-Stack Software EngineerFull-Stack Software Engineer

                      1,0532910




                      1,0532910








                      • 7





                        The most bizarre answer that has ever worked, THANK YOU!

                        – jn1kk
                        Jul 25 '13 at 20:22






                      • 1





                        The right answer is here :)

                        – Farah
                        Dec 15 '13 at 20:09






                      • 1





                        Worked like a charm..... Thanks man!!!!

                        – Saumil
                        Dec 18 '13 at 7:40






                      • 1





                        Why Oracle/Sun ever decided to do this and not fix the uninstaller is beyond me. Thank you.

                        – makhdumi
                        May 11 '14 at 23:17






                      • 1





                        Still didn't get it but it worked

                        – Weishi Zeng
                        Aug 5 '14 at 17:53














                      • 7





                        The most bizarre answer that has ever worked, THANK YOU!

                        – jn1kk
                        Jul 25 '13 at 20:22






                      • 1





                        The right answer is here :)

                        – Farah
                        Dec 15 '13 at 20:09






                      • 1





                        Worked like a charm..... Thanks man!!!!

                        – Saumil
                        Dec 18 '13 at 7:40






                      • 1





                        Why Oracle/Sun ever decided to do this and not fix the uninstaller is beyond me. Thank you.

                        – makhdumi
                        May 11 '14 at 23:17






                      • 1





                        Still didn't get it but it worked

                        – Weishi Zeng
                        Aug 5 '14 at 17:53








                      7




                      7





                      The most bizarre answer that has ever worked, THANK YOU!

                      – jn1kk
                      Jul 25 '13 at 20:22





                      The most bizarre answer that has ever worked, THANK YOU!

                      – jn1kk
                      Jul 25 '13 at 20:22




                      1




                      1





                      The right answer is here :)

                      – Farah
                      Dec 15 '13 at 20:09





                      The right answer is here :)

                      – Farah
                      Dec 15 '13 at 20:09




                      1




                      1





                      Worked like a charm..... Thanks man!!!!

                      – Saumil
                      Dec 18 '13 at 7:40





                      Worked like a charm..... Thanks man!!!!

                      – Saumil
                      Dec 18 '13 at 7:40




                      1




                      1





                      Why Oracle/Sun ever decided to do this and not fix the uninstaller is beyond me. Thank you.

                      – makhdumi
                      May 11 '14 at 23:17





                      Why Oracle/Sun ever decided to do this and not fix the uninstaller is beyond me. Thank you.

                      – makhdumi
                      May 11 '14 at 23:17




                      1




                      1





                      Still didn't get it but it worked

                      – Weishi Zeng
                      Aug 5 '14 at 17:53





                      Still didn't get it but it worked

                      – Weishi Zeng
                      Aug 5 '14 at 17:53











                      28














                      put %JAVA_HOME%bin at the begin of PATH.






                      share|improve this answer



















                      • 3





                        Got the same problem on Windows although my PATH and JAVA_HOME was OK. Moving the %JAVA_HOME% to the beginning of the PATH solved it. Thanks!

                        – Samuel
                        Nov 21 '12 at 10:33











                      • It works too! Thanks!

                        – bsiamionau
                        Apr 5 '13 at 11:10











                      • nice .......................

                        – N..
                        Dec 3 '13 at 10:54











                      • You just saved me a lot of pain. Thank you !

                        – Antoine Cloutier
                        Sep 13 '14 at 14:26











                      • Despite doing this, I was getting the error. What I didn't notice was when I opened a CMD prompt, it would default to C:WindowsSystem32, which contained the troublesome java install. Changing out to any other directory would make Java work just fine with the JDK I wanted on the path.

                        – CrazyPenguin
                        Feb 11 '16 at 20:41
















                      28














                      put %JAVA_HOME%bin at the begin of PATH.






                      share|improve this answer



















                      • 3





                        Got the same problem on Windows although my PATH and JAVA_HOME was OK. Moving the %JAVA_HOME% to the beginning of the PATH solved it. Thanks!

                        – Samuel
                        Nov 21 '12 at 10:33











                      • It works too! Thanks!

                        – bsiamionau
                        Apr 5 '13 at 11:10











                      • nice .......................

                        – N..
                        Dec 3 '13 at 10:54











                      • You just saved me a lot of pain. Thank you !

                        – Antoine Cloutier
                        Sep 13 '14 at 14:26











                      • Despite doing this, I was getting the error. What I didn't notice was when I opened a CMD prompt, it would default to C:WindowsSystem32, which contained the troublesome java install. Changing out to any other directory would make Java work just fine with the JDK I wanted on the path.

                        – CrazyPenguin
                        Feb 11 '16 at 20:41














                      28












                      28








                      28







                      put %JAVA_HOME%bin at the begin of PATH.






                      share|improve this answer













                      put %JAVA_HOME%bin at the begin of PATH.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Nov 8 '11 at 11:36









                      deskmoredeskmore

                      34033




                      34033








                      • 3





                        Got the same problem on Windows although my PATH and JAVA_HOME was OK. Moving the %JAVA_HOME% to the beginning of the PATH solved it. Thanks!

                        – Samuel
                        Nov 21 '12 at 10:33











                      • It works too! Thanks!

                        – bsiamionau
                        Apr 5 '13 at 11:10











                      • nice .......................

                        – N..
                        Dec 3 '13 at 10:54











                      • You just saved me a lot of pain. Thank you !

                        – Antoine Cloutier
                        Sep 13 '14 at 14:26











                      • Despite doing this, I was getting the error. What I didn't notice was when I opened a CMD prompt, it would default to C:WindowsSystem32, which contained the troublesome java install. Changing out to any other directory would make Java work just fine with the JDK I wanted on the path.

                        – CrazyPenguin
                        Feb 11 '16 at 20:41














                      • 3





                        Got the same problem on Windows although my PATH and JAVA_HOME was OK. Moving the %JAVA_HOME% to the beginning of the PATH solved it. Thanks!

                        – Samuel
                        Nov 21 '12 at 10:33











                      • It works too! Thanks!

                        – bsiamionau
                        Apr 5 '13 at 11:10











                      • nice .......................

                        – N..
                        Dec 3 '13 at 10:54











                      • You just saved me a lot of pain. Thank you !

                        – Antoine Cloutier
                        Sep 13 '14 at 14:26











                      • Despite doing this, I was getting the error. What I didn't notice was when I opened a CMD prompt, it would default to C:WindowsSystem32, which contained the troublesome java install. Changing out to any other directory would make Java work just fine with the JDK I wanted on the path.

                        – CrazyPenguin
                        Feb 11 '16 at 20:41








                      3




                      3





                      Got the same problem on Windows although my PATH and JAVA_HOME was OK. Moving the %JAVA_HOME% to the beginning of the PATH solved it. Thanks!

                      – Samuel
                      Nov 21 '12 at 10:33





                      Got the same problem on Windows although my PATH and JAVA_HOME was OK. Moving the %JAVA_HOME% to the beginning of the PATH solved it. Thanks!

                      – Samuel
                      Nov 21 '12 at 10:33













                      It works too! Thanks!

                      – bsiamionau
                      Apr 5 '13 at 11:10





                      It works too! Thanks!

                      – bsiamionau
                      Apr 5 '13 at 11:10













                      nice .......................

                      – N..
                      Dec 3 '13 at 10:54





                      nice .......................

                      – N..
                      Dec 3 '13 at 10:54













                      You just saved me a lot of pain. Thank you !

                      – Antoine Cloutier
                      Sep 13 '14 at 14:26





                      You just saved me a lot of pain. Thank you !

                      – Antoine Cloutier
                      Sep 13 '14 at 14:26













                      Despite doing this, I was getting the error. What I didn't notice was when I opened a CMD prompt, it would default to C:WindowsSystem32, which contained the troublesome java install. Changing out to any other directory would make Java work just fine with the JDK I wanted on the path.

                      – CrazyPenguin
                      Feb 11 '16 at 20:41





                      Despite doing this, I was getting the error. What I didn't notice was when I opened a CMD prompt, it would default to C:WindowsSystem32, which contained the troublesome java install. Changing out to any other directory would make Java work just fine with the JDK I wanted on the path.

                      – CrazyPenguin
                      Feb 11 '16 at 20:41











                      8














                      I had the same problem: I have a 64 bit Windows and when I typed "java -version" in CMD-Console i received the same Error message.
                      Try to start a 64bit-cmd(C:WindowsSysWOW64cmd.exe) and you will see, it works there ;)






                      share|improve this answer


























                      • Great, it works! A lot of thanks!

                        – bsiamionau
                        Apr 5 '13 at 11:03













                      • Thanks so much!! it helped me too

                        – sunskin
                        Jul 5 '13 at 18:52
















                      8














                      I had the same problem: I have a 64 bit Windows and when I typed "java -version" in CMD-Console i received the same Error message.
                      Try to start a 64bit-cmd(C:WindowsSysWOW64cmd.exe) and you will see, it works there ;)






                      share|improve this answer


























                      • Great, it works! A lot of thanks!

                        – bsiamionau
                        Apr 5 '13 at 11:03













                      • Thanks so much!! it helped me too

                        – sunskin
                        Jul 5 '13 at 18:52














                      8












                      8








                      8







                      I had the same problem: I have a 64 bit Windows and when I typed "java -version" in CMD-Console i received the same Error message.
                      Try to start a 64bit-cmd(C:WindowsSysWOW64cmd.exe) and you will see, it works there ;)






                      share|improve this answer















                      I had the same problem: I have a 64 bit Windows and when I typed "java -version" in CMD-Console i received the same Error message.
                      Try to start a 64bit-cmd(C:WindowsSysWOW64cmd.exe) and you will see, it works there ;)







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Apr 27 '12 at 13:12









                      Sergey Glotov

                      16.9k117289




                      16.9k117289










                      answered Apr 27 '12 at 8:49









                      serganmserganm

                      8111




                      8111













                      • Great, it works! A lot of thanks!

                        – bsiamionau
                        Apr 5 '13 at 11:03













                      • Thanks so much!! it helped me too

                        – sunskin
                        Jul 5 '13 at 18:52



















                      • Great, it works! A lot of thanks!

                        – bsiamionau
                        Apr 5 '13 at 11:03













                      • Thanks so much!! it helped me too

                        – sunskin
                        Jul 5 '13 at 18:52

















                      Great, it works! A lot of thanks!

                      – bsiamionau
                      Apr 5 '13 at 11:03







                      Great, it works! A lot of thanks!

                      – bsiamionau
                      Apr 5 '13 at 11:03















                      Thanks so much!! it helped me too

                      – sunskin
                      Jul 5 '13 at 18:52





                      Thanks so much!! it helped me too

                      – sunskin
                      Jul 5 '13 at 18:52











                      2














                      If this was working before, it means the PATH isn't correct anymore.



                      That can happen when the PATH becomes too long and gets truncated.

                      All posts (like this one) suggest updating the PATH, which you can test first in a separate DOS session, by setting a minimal path and see if java works again there.





                      Finally the OP Highland Mark concludes:




                      Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing.




                      scary ;)






                      share|improve this answer


























                      • Thanks. Still I can't sort it. With minimal path (path = %JAVA_HOME%bin) it works - as you say, however, I can't see the problem in the actual path which is "...;%JAVA_HOME%bin;..." which contains the same thing.

                        – Highland Mark
                        May 19 '11 at 8:37













                      • Finally managed to remove old versions of JRE using JavaRA & MSICUU2.exe, reloaded latest version, but still the same message.

                        – Highland Mark
                        May 19 '11 at 9:18






                      • 1





                        @Highland: if this works with a minimal path but not with a full path, that means %JAVA_HOME%bin isn't the issue. Some other element in the PATH causes the runtime to fail. Could you try with a PATH you would build, one element at a time, to see when java stop launching?

                        – VonC
                        May 19 '11 at 10:32











                      • Thanks VonC - that gives me something to work on. I'll report back.

                        – Highland Mark
                        May 19 '11 at 10:50











                      • It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all.

                        – Highland Mark
                        May 19 '11 at 15:01
















                      2














                      If this was working before, it means the PATH isn't correct anymore.



                      That can happen when the PATH becomes too long and gets truncated.

                      All posts (like this one) suggest updating the PATH, which you can test first in a separate DOS session, by setting a minimal path and see if java works again there.





                      Finally the OP Highland Mark concludes:




                      Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing.




                      scary ;)






                      share|improve this answer


























                      • Thanks. Still I can't sort it. With minimal path (path = %JAVA_HOME%bin) it works - as you say, however, I can't see the problem in the actual path which is "...;%JAVA_HOME%bin;..." which contains the same thing.

                        – Highland Mark
                        May 19 '11 at 8:37













                      • Finally managed to remove old versions of JRE using JavaRA & MSICUU2.exe, reloaded latest version, but still the same message.

                        – Highland Mark
                        May 19 '11 at 9:18






                      • 1





                        @Highland: if this works with a minimal path but not with a full path, that means %JAVA_HOME%bin isn't the issue. Some other element in the PATH causes the runtime to fail. Could you try with a PATH you would build, one element at a time, to see when java stop launching?

                        – VonC
                        May 19 '11 at 10:32











                      • Thanks VonC - that gives me something to work on. I'll report back.

                        – Highland Mark
                        May 19 '11 at 10:50











                      • It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all.

                        – Highland Mark
                        May 19 '11 at 15:01














                      2












                      2








                      2







                      If this was working before, it means the PATH isn't correct anymore.



                      That can happen when the PATH becomes too long and gets truncated.

                      All posts (like this one) suggest updating the PATH, which you can test first in a separate DOS session, by setting a minimal path and see if java works again there.





                      Finally the OP Highland Mark concludes:




                      Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing.




                      scary ;)






                      share|improve this answer















                      If this was working before, it means the PATH isn't correct anymore.



                      That can happen when the PATH becomes too long and gets truncated.

                      All posts (like this one) suggest updating the PATH, which you can test first in a separate DOS session, by setting a minimal path and see if java works again there.





                      Finally the OP Highland Mark concludes:




                      Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing.




                      scary ;)







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited May 23 '17 at 10:31









                      Community

                      11




                      11










                      answered May 18 '11 at 4:17









                      VonCVonC

                      847k29626953252




                      847k29626953252













                      • Thanks. Still I can't sort it. With minimal path (path = %JAVA_HOME%bin) it works - as you say, however, I can't see the problem in the actual path which is "...;%JAVA_HOME%bin;..." which contains the same thing.

                        – Highland Mark
                        May 19 '11 at 8:37













                      • Finally managed to remove old versions of JRE using JavaRA & MSICUU2.exe, reloaded latest version, but still the same message.

                        – Highland Mark
                        May 19 '11 at 9:18






                      • 1





                        @Highland: if this works with a minimal path but not with a full path, that means %JAVA_HOME%bin isn't the issue. Some other element in the PATH causes the runtime to fail. Could you try with a PATH you would build, one element at a time, to see when java stop launching?

                        – VonC
                        May 19 '11 at 10:32











                      • Thanks VonC - that gives me something to work on. I'll report back.

                        – Highland Mark
                        May 19 '11 at 10:50











                      • It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all.

                        – Highland Mark
                        May 19 '11 at 15:01



















                      • Thanks. Still I can't sort it. With minimal path (path = %JAVA_HOME%bin) it works - as you say, however, I can't see the problem in the actual path which is "...;%JAVA_HOME%bin;..." which contains the same thing.

                        – Highland Mark
                        May 19 '11 at 8:37













                      • Finally managed to remove old versions of JRE using JavaRA & MSICUU2.exe, reloaded latest version, but still the same message.

                        – Highland Mark
                        May 19 '11 at 9:18






                      • 1





                        @Highland: if this works with a minimal path but not with a full path, that means %JAVA_HOME%bin isn't the issue. Some other element in the PATH causes the runtime to fail. Could you try with a PATH you would build, one element at a time, to see when java stop launching?

                        – VonC
                        May 19 '11 at 10:32











                      • Thanks VonC - that gives me something to work on. I'll report back.

                        – Highland Mark
                        May 19 '11 at 10:50











                      • It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all.

                        – Highland Mark
                        May 19 '11 at 15:01

















                      Thanks. Still I can't sort it. With minimal path (path = %JAVA_HOME%bin) it works - as you say, however, I can't see the problem in the actual path which is "...;%JAVA_HOME%bin;..." which contains the same thing.

                      – Highland Mark
                      May 19 '11 at 8:37







                      Thanks. Still I can't sort it. With minimal path (path = %JAVA_HOME%bin) it works - as you say, however, I can't see the problem in the actual path which is "...;%JAVA_HOME%bin;..." which contains the same thing.

                      – Highland Mark
                      May 19 '11 at 8:37















                      Finally managed to remove old versions of JRE using JavaRA & MSICUU2.exe, reloaded latest version, but still the same message.

                      – Highland Mark
                      May 19 '11 at 9:18





                      Finally managed to remove old versions of JRE using JavaRA & MSICUU2.exe, reloaded latest version, but still the same message.

                      – Highland Mark
                      May 19 '11 at 9:18




                      1




                      1





                      @Highland: if this works with a minimal path but not with a full path, that means %JAVA_HOME%bin isn't the issue. Some other element in the PATH causes the runtime to fail. Could you try with a PATH you would build, one element at a time, to see when java stop launching?

                      – VonC
                      May 19 '11 at 10:32





                      @Highland: if this works with a minimal path but not with a full path, that means %JAVA_HOME%bin isn't the issue. Some other element in the PATH causes the runtime to fail. Could you try with a PATH you would build, one element at a time, to see when java stop launching?

                      – VonC
                      May 19 '11 at 10:32













                      Thanks VonC - that gives me something to work on. I'll report back.

                      – Highland Mark
                      May 19 '11 at 10:50





                      Thanks VonC - that gives me something to work on. I'll report back.

                      – Highland Mark
                      May 19 '11 at 10:50













                      It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all.

                      – Highland Mark
                      May 19 '11 at 15:01





                      It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all.

                      – Highland Mark
                      May 19 '11 at 15:01











                      2














                      I thought I will share how I resolved the same issue "Error Could not open libamd64jvm.cfg". I found the Java run time Jre7 is missing amd64 folder under lib. However, I have 1.7.0_25 JDK which is having jre folder and also having amd64.



                      I moved the original contents of jre7 folder to a backup file and copied everything from 1.7.0_25jre.



                      Now I am not getting this error anymore and able to proceed with scene builder.






                      share|improve this answer




























                        2














                        I thought I will share how I resolved the same issue "Error Could not open libamd64jvm.cfg". I found the Java run time Jre7 is missing amd64 folder under lib. However, I have 1.7.0_25 JDK which is having jre folder and also having amd64.



                        I moved the original contents of jre7 folder to a backup file and copied everything from 1.7.0_25jre.



                        Now I am not getting this error anymore and able to proceed with scene builder.






                        share|improve this answer


























                          2












                          2








                          2







                          I thought I will share how I resolved the same issue "Error Could not open libamd64jvm.cfg". I found the Java run time Jre7 is missing amd64 folder under lib. However, I have 1.7.0_25 JDK which is having jre folder and also having amd64.



                          I moved the original contents of jre7 folder to a backup file and copied everything from 1.7.0_25jre.



                          Now I am not getting this error anymore and able to proceed with scene builder.






                          share|improve this answer













                          I thought I will share how I resolved the same issue "Error Could not open libamd64jvm.cfg". I found the Java run time Jre7 is missing amd64 folder under lib. However, I have 1.7.0_25 JDK which is having jre folder and also having amd64.



                          I moved the original contents of jre7 folder to a backup file and copied everything from 1.7.0_25jre.



                          Now I am not getting this error anymore and able to proceed with scene builder.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Aug 9 '13 at 17:36









                          user2668741user2668741

                          211




                          211























                              2














                              The Java 7 install on my work PC broke after a patch was forced out to us, giving this error any time you tried to run a Java program. Somehow the entire 'lib' subdirectory of the Java 7 install vanished! Might have been related to having both Java 6 and Java 7 installed -- the 'jre6' directory still had everything there.



                              In any case, I fixed it by uninstalling both Java 6 and Java 7 and reinstalling just Java 7. But if the file it's complaining about is actually there, then you're likely having a path issue as described in some of the other answers here.






                              share|improve this answer
























                              • except in my case reinstalling the JRE did not replace the missing lib folder :(

                                – David
                                Apr 17 '14 at 15:26











                              • Ah ... I reinstalled the 64-bit JRE, but it turns out there was also a 32-bit JRE installed. I uninstalled both -- they were a couple of patchlevels behind anyway -- then reinstalled the 64-bit JRE (only) and now everything is copacetic.

                                – David
                                Apr 17 '14 at 17:58
















                              2














                              The Java 7 install on my work PC broke after a patch was forced out to us, giving this error any time you tried to run a Java program. Somehow the entire 'lib' subdirectory of the Java 7 install vanished! Might have been related to having both Java 6 and Java 7 installed -- the 'jre6' directory still had everything there.



                              In any case, I fixed it by uninstalling both Java 6 and Java 7 and reinstalling just Java 7. But if the file it's complaining about is actually there, then you're likely having a path issue as described in some of the other answers here.






                              share|improve this answer
























                              • except in my case reinstalling the JRE did not replace the missing lib folder :(

                                – David
                                Apr 17 '14 at 15:26











                              • Ah ... I reinstalled the 64-bit JRE, but it turns out there was also a 32-bit JRE installed. I uninstalled both -- they were a couple of patchlevels behind anyway -- then reinstalled the 64-bit JRE (only) and now everything is copacetic.

                                – David
                                Apr 17 '14 at 17:58














                              2












                              2








                              2







                              The Java 7 install on my work PC broke after a patch was forced out to us, giving this error any time you tried to run a Java program. Somehow the entire 'lib' subdirectory of the Java 7 install vanished! Might have been related to having both Java 6 and Java 7 installed -- the 'jre6' directory still had everything there.



                              In any case, I fixed it by uninstalling both Java 6 and Java 7 and reinstalling just Java 7. But if the file it's complaining about is actually there, then you're likely having a path issue as described in some of the other answers here.






                              share|improve this answer













                              The Java 7 install on my work PC broke after a patch was forced out to us, giving this error any time you tried to run a Java program. Somehow the entire 'lib' subdirectory of the Java 7 install vanished! Might have been related to having both Java 6 and Java 7 installed -- the 'jre6' directory still had everything there.



                              In any case, I fixed it by uninstalling both Java 6 and Java 7 and reinstalling just Java 7. But if the file it's complaining about is actually there, then you're likely having a path issue as described in some of the other answers here.







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Sep 24 '13 at 17:54









                              MattMatt

                              491




                              491













                              • except in my case reinstalling the JRE did not replace the missing lib folder :(

                                – David
                                Apr 17 '14 at 15:26











                              • Ah ... I reinstalled the 64-bit JRE, but it turns out there was also a 32-bit JRE installed. I uninstalled both -- they were a couple of patchlevels behind anyway -- then reinstalled the 64-bit JRE (only) and now everything is copacetic.

                                – David
                                Apr 17 '14 at 17:58



















                              • except in my case reinstalling the JRE did not replace the missing lib folder :(

                                – David
                                Apr 17 '14 at 15:26











                              • Ah ... I reinstalled the 64-bit JRE, but it turns out there was also a 32-bit JRE installed. I uninstalled both -- they were a couple of patchlevels behind anyway -- then reinstalled the 64-bit JRE (only) and now everything is copacetic.

                                – David
                                Apr 17 '14 at 17:58

















                              except in my case reinstalling the JRE did not replace the missing lib folder :(

                              – David
                              Apr 17 '14 at 15:26





                              except in my case reinstalling the JRE did not replace the missing lib folder :(

                              – David
                              Apr 17 '14 at 15:26













                              Ah ... I reinstalled the 64-bit JRE, but it turns out there was also a 32-bit JRE installed. I uninstalled both -- they were a couple of patchlevels behind anyway -- then reinstalled the 64-bit JRE (only) and now everything is copacetic.

                              – David
                              Apr 17 '14 at 17:58





                              Ah ... I reinstalled the 64-bit JRE, but it turns out there was also a 32-bit JRE installed. I uninstalled both -- they were a couple of patchlevels behind anyway -- then reinstalled the 64-bit JRE (only) and now everything is copacetic.

                              – David
                              Apr 17 '14 at 17:58











                              2














                              Had suddenly the same Problem, from one day to another eclipse said



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


                              after trying to run java on the console



                              Error: could not open `C:WINDOWSjrelibamd64jvm.cfg' 


                              now i just deleted the whole directory



                              C:WINDOWSjre


                              and everything worked again... i don't know there this jre came from, i hope it was not a virus






                              share|improve this answer




























                                2














                                Had suddenly the same Problem, from one day to another eclipse said



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


                                after trying to run java on the console



                                Error: could not open `C:WINDOWSjrelibamd64jvm.cfg' 


                                now i just deleted the whole directory



                                C:WINDOWSjre


                                and everything worked again... i don't know there this jre came from, i hope it was not a virus






                                share|improve this answer


























                                  2












                                  2








                                  2







                                  Had suddenly the same Problem, from one day to another eclipse said



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


                                  after trying to run java on the console



                                  Error: could not open `C:WINDOWSjrelibamd64jvm.cfg' 


                                  now i just deleted the whole directory



                                  C:WINDOWSjre


                                  and everything worked again... i don't know there this jre came from, i hope it was not a virus






                                  share|improve this answer













                                  Had suddenly the same Problem, from one day to another eclipse said



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


                                  after trying to run java on the console



                                  Error: could not open `C:WINDOWSjrelibamd64jvm.cfg' 


                                  now i just deleted the whole directory



                                  C:WINDOWSjre


                                  and everything worked again... i don't know there this jre came from, i hope it was not a virus







                                  share|improve this answer












                                  share|improve this answer



                                  share|improve this answer










                                  answered Apr 20 '14 at 7:31









                                  wutzebaerwutzebaer

                                  7,3021357122




                                  7,3021357122























                                      1














                                      I had the same problem in Eclipse and I fixed it by changing the JRE from 64 bit to 32 bit:



                                      Window > Preferences > Java > Installed JREs > Add... > Next > Directory > select "C:Program Files (x86)Javajre1.8.0_65" instead of "C:Program FilesJavajre1.8.0_60"






                                      share|improve this answer
























                                      • This issue occurred to me while installing eclipse. I was installing eclipse after JAVA update where my earlier version was 1.8.0_60 and the newer version was 1.8.0_191 which i guess is changed while installing update so i changed folder name to earlier i.e. 1.8.0_60 . So the issue is with post install script of JAVA update i guess @ time of Update installation both names should be changed by install which is not the case. i.e. minor change is remaining after post install of java update.

                                        – Rahul
                                        Nov 15 '18 at 17:31


















                                      1














                                      I had the same problem in Eclipse and I fixed it by changing the JRE from 64 bit to 32 bit:



                                      Window > Preferences > Java > Installed JREs > Add... > Next > Directory > select "C:Program Files (x86)Javajre1.8.0_65" instead of "C:Program FilesJavajre1.8.0_60"






                                      share|improve this answer
























                                      • This issue occurred to me while installing eclipse. I was installing eclipse after JAVA update where my earlier version was 1.8.0_60 and the newer version was 1.8.0_191 which i guess is changed while installing update so i changed folder name to earlier i.e. 1.8.0_60 . So the issue is with post install script of JAVA update i guess @ time of Update installation both names should be changed by install which is not the case. i.e. minor change is remaining after post install of java update.

                                        – Rahul
                                        Nov 15 '18 at 17:31
















                                      1












                                      1








                                      1







                                      I had the same problem in Eclipse and I fixed it by changing the JRE from 64 bit to 32 bit:



                                      Window > Preferences > Java > Installed JREs > Add... > Next > Directory > select "C:Program Files (x86)Javajre1.8.0_65" instead of "C:Program FilesJavajre1.8.0_60"






                                      share|improve this answer













                                      I had the same problem in Eclipse and I fixed it by changing the JRE from 64 bit to 32 bit:



                                      Window > Preferences > Java > Installed JREs > Add... > Next > Directory > select "C:Program Files (x86)Javajre1.8.0_65" instead of "C:Program FilesJavajre1.8.0_60"







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Oct 26 '15 at 7:50









                                      ROMANIA_engineerROMANIA_engineer

                                      34.4k19156146




                                      34.4k19156146













                                      • This issue occurred to me while installing eclipse. I was installing eclipse after JAVA update where my earlier version was 1.8.0_60 and the newer version was 1.8.0_191 which i guess is changed while installing update so i changed folder name to earlier i.e. 1.8.0_60 . So the issue is with post install script of JAVA update i guess @ time of Update installation both names should be changed by install which is not the case. i.e. minor change is remaining after post install of java update.

                                        – Rahul
                                        Nov 15 '18 at 17:31





















                                      • This issue occurred to me while installing eclipse. I was installing eclipse after JAVA update where my earlier version was 1.8.0_60 and the newer version was 1.8.0_191 which i guess is changed while installing update so i changed folder name to earlier i.e. 1.8.0_60 . So the issue is with post install script of JAVA update i guess @ time of Update installation both names should be changed by install which is not the case. i.e. minor change is remaining after post install of java update.

                                        – Rahul
                                        Nov 15 '18 at 17:31



















                                      This issue occurred to me while installing eclipse. I was installing eclipse after JAVA update where my earlier version was 1.8.0_60 and the newer version was 1.8.0_191 which i guess is changed while installing update so i changed folder name to earlier i.e. 1.8.0_60 . So the issue is with post install script of JAVA update i guess @ time of Update installation both names should be changed by install which is not the case. i.e. minor change is remaining after post install of java update.

                                      – Rahul
                                      Nov 15 '18 at 17:31







                                      This issue occurred to me while installing eclipse. I was installing eclipse after JAVA update where my earlier version was 1.8.0_60 and the newer version was 1.8.0_191 which i guess is changed while installing update so i changed folder name to earlier i.e. 1.8.0_60 . So the issue is with post install script of JAVA update i guess @ time of Update installation both names should be changed by install which is not the case. i.e. minor change is remaining after post install of java update.

                                      – Rahul
                                      Nov 15 '18 at 17:31













                                      1














                                      C:ProgramDataOracleJavajavapath worked for me .. , I have took back up of the files and removed the files in it.Opened new cmd prompt and then .. tested and works like charm






                                      share|improve this answer
























                                      • Had to go too deep for this. Thank you, worked like a charm.

                                        – Fernando Martín Besteiro
                                        Aug 31 '17 at 18:28
















                                      1














                                      C:ProgramDataOracleJavajavapath worked for me .. , I have took back up of the files and removed the files in it.Opened new cmd prompt and then .. tested and works like charm






                                      share|improve this answer
























                                      • Had to go too deep for this. Thank you, worked like a charm.

                                        – Fernando Martín Besteiro
                                        Aug 31 '17 at 18:28














                                      1












                                      1








                                      1







                                      C:ProgramDataOracleJavajavapath worked for me .. , I have took back up of the files and removed the files in it.Opened new cmd prompt and then .. tested and works like charm






                                      share|improve this answer













                                      C:ProgramDataOracleJavajavapath worked for me .. , I have took back up of the files and removed the files in it.Opened new cmd prompt and then .. tested and works like charm







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered May 25 '17 at 4:33









                                      ananthkvaananthkva

                                      92310




                                      92310













                                      • Had to go too deep for this. Thank you, worked like a charm.

                                        – Fernando Martín Besteiro
                                        Aug 31 '17 at 18:28



















                                      • Had to go too deep for this. Thank you, worked like a charm.

                                        – Fernando Martín Besteiro
                                        Aug 31 '17 at 18:28

















                                      Had to go too deep for this. Thank you, worked like a charm.

                                      – Fernando Martín Besteiro
                                      Aug 31 '17 at 18:28





                                      Had to go too deep for this. Thank you, worked like a charm.

                                      – Fernando Martín Besteiro
                                      Aug 31 '17 at 18:28











                                      1















                                      • I had a similar problem (trying to start a Jenkins slave agent on Windows) on Windows 2008R2, Java 1.7.0_15



                                      • I had two situations that contributed to the problem and that changing both of them fixed it:



                                        1) Installing Java in a unix-compatible path (changing from c:Program Files... to c:Software...); I don't think this directly affected the problem described in this thread, but noting the change;



                                        2) Running Java not through a shortcut. It originally failed with a shortcut, but re-running from the direct executable (C:SoftwareJava...binjava) worked.








                                      share|improve this answer






























                                        1















                                        • I had a similar problem (trying to start a Jenkins slave agent on Windows) on Windows 2008R2, Java 1.7.0_15



                                        • I had two situations that contributed to the problem and that changing both of them fixed it:



                                          1) Installing Java in a unix-compatible path (changing from c:Program Files... to c:Software...); I don't think this directly affected the problem described in this thread, but noting the change;



                                          2) Running Java not through a shortcut. It originally failed with a shortcut, but re-running from the direct executable (C:SoftwareJava...binjava) worked.








                                        share|improve this answer




























                                          1












                                          1








                                          1








                                          • I had a similar problem (trying to start a Jenkins slave agent on Windows) on Windows 2008R2, Java 1.7.0_15



                                          • I had two situations that contributed to the problem and that changing both of them fixed it:



                                            1) Installing Java in a unix-compatible path (changing from c:Program Files... to c:Software...); I don't think this directly affected the problem described in this thread, but noting the change;



                                            2) Running Java not through a shortcut. It originally failed with a shortcut, but re-running from the direct executable (C:SoftwareJava...binjava) worked.








                                          share|improve this answer
















                                          • I had a similar problem (trying to start a Jenkins slave agent on Windows) on Windows 2008R2, Java 1.7.0_15



                                          • I had two situations that contributed to the problem and that changing both of them fixed it:



                                            1) Installing Java in a unix-compatible path (changing from c:Program Files... to c:Software...); I don't think this directly affected the problem described in this thread, but noting the change;



                                            2) Running Java not through a shortcut. It originally failed with a shortcut, but re-running from the direct executable (C:SoftwareJava...binjava) worked.









                                          share|improve this answer














                                          share|improve this answer



                                          share|improve this answer








                                          edited Dec 15 '18 at 11:52









                                          Agilanbu

                                          1,2021420




                                          1,2021420










                                          answered Mar 13 '13 at 12:55









                                          user1676075user1676075

                                          2,60311222




                                          2,60311222























                                              0














                                              Reinstalling java didn't help me. But the trick to put the JAVA_HOME variable at the beginning of the env-vars. The problem occoured after an upgrade from jdk1.7.0_11 to jdk1.7.0_13






                                              share|improve this answer






























                                                0














                                                Reinstalling java didn't help me. But the trick to put the JAVA_HOME variable at the beginning of the env-vars. The problem occoured after an upgrade from jdk1.7.0_11 to jdk1.7.0_13






                                                share|improve this answer




























                                                  0












                                                  0








                                                  0







                                                  Reinstalling java didn't help me. But the trick to put the JAVA_HOME variable at the beginning of the env-vars. The problem occoured after an upgrade from jdk1.7.0_11 to jdk1.7.0_13






                                                  share|improve this answer















                                                  Reinstalling java didn't help me. But the trick to put the JAVA_HOME variable at the beginning of the env-vars. The problem occoured after an upgrade from jdk1.7.0_11 to jdk1.7.0_13







                                                  share|improve this answer














                                                  share|improve this answer



                                                  share|improve this answer








                                                  edited Feb 12 '13 at 11:20









                                                  Jan Hančič

                                                  41.5k138390




                                                  41.5k138390










                                                  answered Feb 12 '13 at 11:00









                                                  m_cm_c

                                                  1716




                                                  1716























                                                      0














                                                      Another workaround is using shortpath in windows:




                                                      1. open windows command console using cmd.exe

                                                      2. goto c:

                                                      3. type command> dir program* /x

                                                      4. it should display as short path like: PROGRA~2

                                                      5. so C:PROGRA~2 is same as C:Program Files (x86)

                                                      6. in your JAVA_HOME replace path to :
                                                        C:PROGRA~2Javajre7


                                                      This should work in windows 64 environment as it worked for me in win7 64bit version.






                                                      share|improve this answer






























                                                        0














                                                        Another workaround is using shortpath in windows:




                                                        1. open windows command console using cmd.exe

                                                        2. goto c:

                                                        3. type command> dir program* /x

                                                        4. it should display as short path like: PROGRA~2

                                                        5. so C:PROGRA~2 is same as C:Program Files (x86)

                                                        6. in your JAVA_HOME replace path to :
                                                          C:PROGRA~2Javajre7


                                                        This should work in windows 64 environment as it worked for me in win7 64bit version.






                                                        share|improve this answer




























                                                          0












                                                          0








                                                          0







                                                          Another workaround is using shortpath in windows:




                                                          1. open windows command console using cmd.exe

                                                          2. goto c:

                                                          3. type command> dir program* /x

                                                          4. it should display as short path like: PROGRA~2

                                                          5. so C:PROGRA~2 is same as C:Program Files (x86)

                                                          6. in your JAVA_HOME replace path to :
                                                            C:PROGRA~2Javajre7


                                                          This should work in windows 64 environment as it worked for me in win7 64bit version.






                                                          share|improve this answer















                                                          Another workaround is using shortpath in windows:




                                                          1. open windows command console using cmd.exe

                                                          2. goto c:

                                                          3. type command> dir program* /x

                                                          4. it should display as short path like: PROGRA~2

                                                          5. so C:PROGRA~2 is same as C:Program Files (x86)

                                                          6. in your JAVA_HOME replace path to :
                                                            C:PROGRA~2Javajre7


                                                          This should work in windows 64 environment as it worked for me in win7 64bit version.







                                                          share|improve this answer














                                                          share|improve this answer



                                                          share|improve this answer








                                                          edited Jun 12 '13 at 11:07









                                                          stefan

                                                          7,75833977




                                                          7,75833977










                                                          answered Jun 12 '13 at 10:45









                                                          RudraRudra

                                                          1




                                                          1























                                                              0














                                                              I have changed the java installation path from c:Program Files (x86)java to another folder like c:javajdk1.7 and updated the %Java_HOME% and path values accordingly,it worked.



                                                              example



                                                              %JAVA_HOME% = C:javaJDK1.7

                                                              path-C:javaJDK1.7bin;





                                                              share|improve this answer






























                                                                0














                                                                I have changed the java installation path from c:Program Files (x86)java to another folder like c:javajdk1.7 and updated the %Java_HOME% and path values accordingly,it worked.



                                                                example



                                                                %JAVA_HOME% = C:javaJDK1.7

                                                                path-C:javaJDK1.7bin;





                                                                share|improve this answer




























                                                                  0












                                                                  0








                                                                  0







                                                                  I have changed the java installation path from c:Program Files (x86)java to another folder like c:javajdk1.7 and updated the %Java_HOME% and path values accordingly,it worked.



                                                                  example



                                                                  %JAVA_HOME% = C:javaJDK1.7

                                                                  path-C:javaJDK1.7bin;





                                                                  share|improve this answer















                                                                  I have changed the java installation path from c:Program Files (x86)java to another folder like c:javajdk1.7 and updated the %Java_HOME% and path values accordingly,it worked.



                                                                  example



                                                                  %JAVA_HOME% = C:javaJDK1.7

                                                                  path-C:javaJDK1.7bin;






                                                                  share|improve this answer














                                                                  share|improve this answer



                                                                  share|improve this answer








                                                                  edited Oct 24 '14 at 4:58









                                                                  Saghir A. Khatri

                                                                  2,49163569




                                                                  2,49163569










                                                                  answered Oct 24 '14 at 4:40









                                                                  sivasubramaniansivasubramanian

                                                                  1




                                                                  1























                                                                      0














                                                                      I had this problem after updating your java. The best way to solve this problem is just go to your c:/ProgramFiles/Java folder. There you will find two jre folders one is as jre.your version and other with exactly like jdk folder. Try to remove jre.1.your version folder. There you go your problem is solved. Hope this might help. It's worked for me.






                                                                      share|improve this answer




























                                                                        0














                                                                        I had this problem after updating your java. The best way to solve this problem is just go to your c:/ProgramFiles/Java folder. There you will find two jre folders one is as jre.your version and other with exactly like jdk folder. Try to remove jre.1.your version folder. There you go your problem is solved. Hope this might help. It's worked for me.






                                                                        share|improve this answer


























                                                                          0












                                                                          0








                                                                          0







                                                                          I had this problem after updating your java. The best way to solve this problem is just go to your c:/ProgramFiles/Java folder. There you will find two jre folders one is as jre.your version and other with exactly like jdk folder. Try to remove jre.1.your version folder. There you go your problem is solved. Hope this might help. It's worked for me.






                                                                          share|improve this answer













                                                                          I had this problem after updating your java. The best way to solve this problem is just go to your c:/ProgramFiles/Java folder. There you will find two jre folders one is as jre.your version and other with exactly like jdk folder. Try to remove jre.1.your version folder. There you go your problem is solved. Hope this might help. It's worked for me.







                                                                          share|improve this answer












                                                                          share|improve this answer



                                                                          share|improve this answer










                                                                          answered Oct 30 '15 at 6:22









                                                                          Naseer AhammedNaseer Ahammed

                                                                          411111




                                                                          411111























                                                                              0














                                                                              Typically it because of upgrading JRE.



                                                                              It changes symlinks into C:ProgramDataOracleJavajavapath



                                                                              Intall JDK - it will fix this.






                                                                              share|improve this answer




























                                                                                0














                                                                                Typically it because of upgrading JRE.



                                                                                It changes symlinks into C:ProgramDataOracleJavajavapath



                                                                                Intall JDK - it will fix this.






                                                                                share|improve this answer


























                                                                                  0












                                                                                  0








                                                                                  0







                                                                                  Typically it because of upgrading JRE.



                                                                                  It changes symlinks into C:ProgramDataOracleJavajavapath



                                                                                  Intall JDK - it will fix this.






                                                                                  share|improve this answer













                                                                                  Typically it because of upgrading JRE.



                                                                                  It changes symlinks into C:ProgramDataOracleJavajavapath



                                                                                  Intall JDK - it will fix this.







                                                                                  share|improve this answer












                                                                                  share|improve this answer



                                                                                  share|improve this answer










                                                                                  answered Oct 24 '16 at 21:55









                                                                                  beloblotskiybeloblotskiy

                                                                                  48946




                                                                                  48946























                                                                                      0














                                                                                      Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


                                                                                      Looking @ it the issue of post install script is there and getting propagated since I am using update jdk8 1.8.0_191 since issue occurred with me after installing update of java and which was happened automatically.



                                                                                      Error: could not open `C:Program FilesJavajre1.8.0_191libamd64jvm.cfg'


                                                                                      This will be never ending in this case and need to do workaround like changing path's manually.






                                                                                      share|improve this answer




























                                                                                        0














                                                                                        Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


                                                                                        Looking @ it the issue of post install script is there and getting propagated since I am using update jdk8 1.8.0_191 since issue occurred with me after installing update of java and which was happened automatically.



                                                                                        Error: could not open `C:Program FilesJavajre1.8.0_191libamd64jvm.cfg'


                                                                                        This will be never ending in this case and need to do workaround like changing path's manually.






                                                                                        share|improve this answer


























                                                                                          0












                                                                                          0








                                                                                          0







                                                                                          Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


                                                                                          Looking @ it the issue of post install script is there and getting propagated since I am using update jdk8 1.8.0_191 since issue occurred with me after installing update of java and which was happened automatically.



                                                                                          Error: could not open `C:Program FilesJavajre1.8.0_191libamd64jvm.cfg'


                                                                                          This will be never ending in this case and need to do workaround like changing path's manually.






                                                                                          share|improve this answer













                                                                                          Error: could not open `C:Program FilesJavajre6libamd64jvm.cfg'


                                                                                          Looking @ it the issue of post install script is there and getting propagated since I am using update jdk8 1.8.0_191 since issue occurred with me after installing update of java and which was happened automatically.



                                                                                          Error: could not open `C:Program FilesJavajre1.8.0_191libamd64jvm.cfg'


                                                                                          This will be never ending in this case and need to do workaround like changing path's manually.







                                                                                          share|improve this answer












                                                                                          share|improve this answer



                                                                                          share|improve this answer










                                                                                          answered Nov 15 '18 at 17:49









                                                                                          RahulRahul

                                                                                          19419




                                                                                          19419























                                                                                              -1














                                                                                              It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all @Highland Mark- Can you tell me the process to removing references from registry. I tried all possible way people mentioned here, nothing worked.






                                                                                              share|improve this answer




























                                                                                                -1














                                                                                                It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all @Highland Mark- Can you tell me the process to removing references from registry. I tried all possible way people mentioned here, nothing worked.






                                                                                                share|improve this answer


























                                                                                                  -1












                                                                                                  -1








                                                                                                  -1







                                                                                                  It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all @Highland Mark- Can you tell me the process to removing references from registry. I tried all possible way people mentioned here, nothing worked.






                                                                                                  share|improve this answer













                                                                                                  It wasn't in the path. Finally fixed by uninstalling java, removing all references to it from the registry, and then re-installing. None the wiser, but back working again. Thanks all @Highland Mark- Can you tell me the process to removing references from registry. I tried all possible way people mentioned here, nothing worked.







                                                                                                  share|improve this answer












                                                                                                  share|improve this answer



                                                                                                  share|improve this answer










                                                                                                  answered Apr 22 '16 at 5:55









                                                                                                  Rookie_GuyRookie_Guy

                                                                                                  2628




                                                                                                  2628

















                                                                                                      protected by Community Apr 9 '17 at 14:54



                                                                                                      Thank you for your interest in this question.
                                                                                                      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                                                                                      Would you like to answer one of these unanswered questions instead?



                                                                                                      Popular posts from this blog

                                                                                                      Bressuire

                                                                                                      Vorschmack

                                                                                                      Quarantine