JDK-7092378 : UAC dialog for ssvagent pops up unexpectedly
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7,7u1
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp,windows_vista,windows_7
  • CPU: x86
  • Submitted: 2011-09-19
  • Updated: 2011-11-09
  • Resolved: 2011-10-17
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 7 JDK 8
7u2 b08Fixed 8Fixed
Related Reports
Duplicate :  
JDK-7101694 - JRE 1.6 u27 and JRE 1.7 on the same machine needs administrator rights.
Duplicate :  
JDK-7109429 - REGRESSION:Java 7.01 -- Vista's User Account Control window appears when initiating IE 8
Description
Steps to reproduce:

Install JRE 7u1 followed by FX 2.0.

UAC dialog for ssvagent always pops up under the following scenarios:

1) invoke Java Control Panel

2) start IE browser
Comments
EVALUATION On win7 / vista, if one installs jre 7u1 followed by fx 2.0. A UAC dialog for ssvagent.exe always pops up on startup of Java Control Panel or startup of the IE browser. For fixing the problem related to Java Control Panel, in ControlPanel, checks if the fx config setting is different from the actually setting. Only calling setJavaFXEnabled() if they're different since setJavaFXEnabled() will invoke ssvagent as a high-integrity process and will trigger the UAC dialog. Similar fix also apply before calling setJavaPluginSettings(). 2 problems related to the IE browser: 1) The static version clsid reg keys for the latest JRE version on the machine wasn't set to point to the fx directory. A fix is in SSVSetup, we should also call the RedirectSelectedStaticVersionKeys() function so that all installed JREs static version keys will be set correctly. 2) The "TreatAs" key for the applet tag support wasn't set to point to the latest JRE version on the machine. A fix is in the SetIEPluginREGKeys(), we need to find the latest installed JRE version and set the "TreatAs" key accordingly.
20-09-2011