JDK-8079141 : Investigate deploy registration problems after enabling\disabling Java Content in the browser
  • Type: Task
  • Component: deploy
  • Affected Version: 8u60
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows
  • Submitted: 2015-04-30
  • Updated: 2017-07-18
  • Resolved: 2017-07-18
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.
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
We cannot reproduce this issue internally, but we should check how this functionality affects installation process.
User provided the following steps:

>>Here is how I got it to work:
>>Install Java 32Bit and let it fail.
>>Uncheck the "Enable Java Content..."
>>Install Java 32Bit.
>>Check the "Enable Jave Content..."
>>Install Java 64Bit and let it fail.
>>Uncheck the "Enable Java Content..."
>>Install Java 64Bit.
>>Finally Check the "Enable Java Content..."
Investigated, added additional logs.

I filed the issue for adding more logs to SSV update process - JDK-8139773

The log file from archive (9065138.zip) doesn't contain any deployment errors.

If we cannot reproduce it internally, probably we could add more logs for SSV update process. So it will be easier to determine which exactly operations returned FALSE on user's machine.

I found only one deployment problem in ..._1.log. Seems like it cannot update registry for the path HKCU -> Software -> CLSID -> Java Plug-in %VERSION% Can you reproduce it on our oracle machines or it's user's log file?

Added new logs from the users who had failures with error 1603. JavaDeployReg_1.log have entry: RegisterDeployEx return: TRUE .. UnRegisterDeployEx return: TRUE

Actually, during installation process we skip many actions if WebJava is disabled: -- creating HKLM Javasoft version keys -- setting version key entry for current installing JavaWS -- associating Web Start at given path with IE & FF -- creating JNLP file associations -- updating plugin registry keys for IE & FF -- registering ssvagent.exe and jp2launcher.exe to IE explorer So, disabling web java is like a workaround to avoid various deployment registration problems (mostly, related to update of registry keys). If two different users can "resolve" their jre installation issues by disabling web java, it doesn't mean their deploy registration problems are the same. Every such issue should be considered separately, based on the content of JavaDeployReg.log.