JDK-6610497 : Wrong registry script referenced in Windows JDK installer
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u5
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2007-09-27
  • Updated: 2010-09-17
  • Resolved: 2007-11-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
6u10 b07Fixed 7Fixed
In deploy/src/plugin/win32/regutils/RegInstall.cpp, RegCurrentVersionKeys:

If installType != 0, IDR_RegCurrentVersion is being used. It is clear that this should be IDR_RegSDKCurrentVersion. IDR_RegSDKCurrentVersion is unreferenced in the current code.

The expected side effect is if the JDK is installed without the associated public JRE, we will pollute the registry with a bunch of incorrect and/or corrupt keys.

Testing indicates that for an unknown reason this does not happen. It is possible that the unresolved macros cause the application of the registry script to fail. Currently it is unknown why the HKLM/SOFTWARE/JavaSoft/Java Development Kit/Current registry key is being correctly created.

SUGGESTED FIX The issue was due to the wrong script name in the code. The same registry key was also set by CanonicalizeJava2Registry. The fix will be to remove the extra section with the wrong script name.

EVALUATION Assigning to Jennifer to investigate, after her 6u5-b06 deliverables are finished.

SUGGESTED FIX Even if we can not immediately diagnose why things appear to be working correctly, make the obviously correct code change and do testing to ensure no regressions.