JDK-7102214 : Obsolete "VERSION" registry entries appear for Plugin and JWS
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 7u2
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • CPU: generic
  • Submitted: 2011-10-18
  • Updated: 2012-03-20
  • Resolved: 2012-03-20
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.
JDK 6
6u32Resolved
Related Reports
Duplicate :  
JDK-7104732 - 7u2+FX: Unregistered plugin after JRE reinstall scenario
Relates :  
JDK-7131436 - Bogus 1.7.x deployment keys are not removed with 7u4-b05/b06.
Relates :  
JDK-7119192 - detect and remove bogus 1.7.x deployment keys
Description
The following registry entries:
HKLM\Software\JavaSoft\Java Plug-in\1.7.0_02
HKLM\Software\JavaSoft\Java Plug-in\10.2.0
HKLM\Software\JavaSoft\Java Web Start\1.7.0_02
HKLM\Software\JavaSoft\Java Web Start\10.2.0
appears after previous family JRE removal
These "VERSION" registry entries are obsolete for 7 and should not be there, they lead to crazy behavior like unexpected old plugin usage
The entires are left after 7u2 removal
I can reproduce the issue using 7u4 b08 and preb09:
Install 6u31(b04)
Install 7u4 b08(preb09)
Uninstall 6u31
See 1.7.0_04 keys:
HKLM\Software\JavaSoft\Java Plug-in\1.7.0_04
HKLM\Software\JavaSoft\Java Plug-in\10.2.0
HKLM\Software\JavaSoft\Java Web Start\1.7.0_04
HKLM\Software\JavaSoft\Java Web Start\10.2.0

so fixes for CR 7088173(integrated in b08) and CR 7119192(which duplicates this bug, intagrated in b07) do not fix this issue completely.
But now these keys are removed after 7u4 uninstall.
Comments
EVALUATION This has to do with the Java 6 uninstaller code not playing well with the new deployment registration model. It shouldn't be reproducible with 7u4 or 8, as they have the latest deployment registration code implemented. There will be some work that needs to be done to the 6u32 uninstaller though.
30-01-2012
EVALUATION This will go away when we fix 7088173 in 7u4.
19-10-2011
EVALUATION This seems to be an issue that should be addressed in the new deploy.dll RegisterDeploy/UnregisterDeploy code.
19-10-2011