JDK-7181744 : Access Bridge registry key is not properly handled in case of both 32 and 64 bit runtimes
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 7u6
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: windows
  • CPU: x86
  • Submitted: 2012-07-04
  • Updated: 2017-08-10
  • Resolved: 2017-08-10
Related Reports
Relates :  
Access Bridge registry key Oracle_JavaAccessBridge created by 64 bit JRE installation is overwritten by next 32 bit JRE installation. After 32 JRE uninstall, key is deleted.

No plans to fix. If there's an issue, please file a customer support case (SR).

It appears a backport could easily be derived from the 8 fix on this one as well...

Java Access Bridge is now in JDK8. So, this fix should go in 8 and back ported to 7uX.

Fix is in progress. With access bridge coming to JDK8 we might be able to simplify this fix. Depends on if access bridge is coming to JDK8 before 7u12.

SQE is ok to defer to 7u12

WORK AROUND Uninstall/reinstall the JRE you want registered as JAB.

EVALUATION This is an issue with 64-bit Windows only, and only when the user is installing both a 32-bit JRE and a 64-bit JRE and then uninstalling of them. This is the same issue we had with the .jar/.jnlp file association on 64-bit systems. It had been an issue since 64-bit Windows OS's existed. We addressed this in 7u6 for the .jar and .jnlp file associations. Most of the 64-bit Windows registry is split up into 2 nodes: 32-bit vs 64-bit. But for some types of system registration, there is only 1 node. The JAB registry key falls into that category (as does the .jar and .jnlp registration). Right now, if you install a 7u6 32-bit and 64-bit JRE, the last one you install will take over for JAB. And then when you uninstall, that JRE, it will not restore the other JRE for JAB.