JDK Setup and installation Android Studio prompt does not a valid JVM issue
Setup method:
- The following environment variables are added to the system variables, such as environment variables, properties---
- The Java_home value is: Install JDK directory, my C:\Program files\java\jdk1.8.0_05 (installation time has a path selection, copy down)
- The Classpath value is:.; %java_home%\lib\tools.jar;%java_home%\lib\dt.jar;%java_home%\bin; (Note the preceding ".;" To add, if not new)
- Path: Append at start.; %java_home%\bin;%java_home%\jre\bin; (Note the preceding ".;" To add, if not new)
The above method is search on the Internet, there is no error, but I set the value of the Java_home as C:\Program files\java\jdk1.8.0_05, is the next semicolon, run the Java command no problem, so that the environment variable settings are not a problem. The installation of ANDROID Studio, unable to run, prompted "dose not a valid JVM", based on similar problems found on the Internet, added JDK_HOME,ANDROID_STUDIO_JDK variables, the same value as Java_home , but they couldn't solve the problem.
Run Studio.bat to view the issue, prompting "Error:cannot start Android Studio. No JDK found. Please validate either ANDROID_STUDIO_JDK, or Jdk_home or java_home points to valid JDK installation. ECHO is off. Press any key to continue ... ".
So again a search, finally on this page "http://stackoverflow.com/questions/16574189/ Android-studio-installation-on-windows-7-fails-no-jdk-found "Got a hint, a buddy said:
This MOSTLY worked for me. I am running the windows and JDK 1.7.0. I tried adding both Jdk_home and java_home with "C:\Program files\java\jdk1.7.0\". It still would not load. However, I capitalized the "C" and removed the trailing slash and it works now: "C:\Program files\java\jdk1.7.0" –aseale May + ' at 12:08
As I am a 64-bit system, so check my input java_home value, try to remove the back of the semicolon, sure enough to start, a small problem unexpectedly toss me fast 2 days ah ...
JDK Setup and installation Android Studio prompt does not a valid JVM issue