JDK-8048860 : Windows register deploy introduces issues with static downgraded scenario
  • Type: Bug
  • Component: deploy
  • Affected Version: 8u20
  • Priority: P1
  • Status: Resolved
  • Resolution: Duplicate
  • OS: windows
  • CPU: generic
  • Submitted: 2014-07-01
  • Updated: 2014-07-10
  • Resolved: 2014-07-03
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 8
8u20Resolved
Related Reports
Duplicate :  
Description
It is a important regression register deploy on Windows .   It happens likely related to the new change in 8u20-b19 which  no longer copies java binaries to system dir
With this change, end users will likely run into important deploy registration issue on Windows with the static downgrade scenario after installing 8u20

*** Case in point: Users have 8u20 and try to install 7ux
As such, they can not use 8u20 java plug-in in their browser. If they decide to uninstall 7ux after all, their browsers no longer registered with the remaining 8u20 and no java control panel found in Windows control panel



*** Tested Configuration: 
- OS: x86 Windows 7
- Browser:  FF, IE, GC
- JRE build:  8u20-b18, 8u20-b20, 7u60 live fcs

* Steps to reproduce:
0) Use a clean machine or
 Uninstall all java*.exe from system dir C:\Windows\System32 and   user deployment related files
1) Install latest  8u20-b20 promotion
2) Install 7u60 fcs version from java.com

Expected:  All deployment registration is from 8u20
Actual:      All deployment registration is from 7u60

Details:
- 7u60  Java control panel found under windows control panel  (not 8u20 and hence, all security level slider is different from expected 8u20 security level radio buttons)
- 7u60 java plug-in registered with all browsers( not 8u20)
- Use any browser to load any applet and 7u60 (not 8u20) is used

and more serious problem below:
3) Uninstall 7u60  from the system

Expected:  8u20 java control panel will appear in window control panel
Actual:  No Java control panel existed in window control panel  (even 8u20 still left on the system)

Comments
this should be fixed by the changes for JDK-8049056.
03-07-2014

For now I have not even tried to reproduce\debug the issue, but it's clear that for 8u20 the plugin cannot be registered properly in registry, because plugin.jar is missing in java_home\lib when RegisterDeployEx() is called by the installer. so deployment considers 8u20 java_home\lib as fake, and removes the plugin registry keys in the end of registration process. after that, when installing 7u60, we won't be able to find 8u20 keys in registry, this way 7u60 plugin can be registered as latest.
02-07-2014

It seems to me that this would be a bug in the 7u60 deploy registration code (in deploy.dll). Why is 7u60 deploy.dll registering itself as the latest plugin for the browser when 8u20 is already there? Does it detect whether to do this via binaries in the system directory? If so, that is the bug. It should check the registry and only register if it's the latest. Assigning to deploy team to answer these questions.
02-07-2014

Likely it's a regression of 7166597. Re-assinging to install component for initial evaluation.
02-07-2014