EE6 JDK Installer Problems on Windows

Asked By 0 points N/A Posted on -


I have a fresh, clean Windows 7 Pro x64 system with only updates and I think Office 2010 installed.

  1. Java JRE (1.6.0_26) 32 bit installed.
  2. Trying to install JDK (6u24) 32 bit. Offline installer fails with error 1722, which seems to be a generic Install Shield error.
  3. Tried downloading again. Same result. Tried with JDK 6u25. Tried removing all Java traces. Nothing works.
  4. suggests removing Java and installing offline. That's what I'm doing.
  5. Workaround implemented: install full SDK with JDK, so the JDK resides inside C:Glassfish3jdk dir.
  6. Now, Eclipse Helios 32 bit cannot start. It says that the JNI shared library "jvm.dll" could not be loaded. But "jvm.dll" sits just fine in System32.
  7. Path and system variables look fine to me. JAVA_HOME points to the JDK. JRE and JDK bin folders are appended to the system path.


  1. How can this fail?
  2. Is it some residual Java configuration left in the system?
  3. Is it some kind of tricky system variable setting that we got wrong? I think I must have installed rather many previous versions of this software before.
  4. Is it something with 32/64 bit inconsistency in the system config? I am using 32 bit JDK for Android development.
  5. Is Windows simply missing some files necessary to load jvm.dll properly?
  6. Is it that I am losing my mind?

I suspect this problem may be Windows related, and it's kind of technical, so maybe this should've been posted to a different forum, but since the error occurs with installing and using Java, someone here might have seen it. Anyone out there a tech genius, or a poor developer who has suffered and overcome this stumble block?

Best Answer by Balram
Best Answer
Best Answer
Answered By 0 points N/A #87183

EE6 JDK Installer Problems on Windows

Just copy the jdk directory from its location in Program Files to c:jdk. Windows enabled applications will continue to use the version under Program Files and the tools which do not like spaces in the paths, use the c:jdk version. And this usually works well enough. (as long as the version do not grow to far apart).
Another alternative is becoming an expert in escaping and quoting filenames, with spaces in a dozen configuration file types and scripting languages.

Login/Register to Answer

Related Questions