JDK-6487334 : vista: changes made by java control panel has no effect
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 5.0u11
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows,windows_vista
  • CPU: x86
  • Submitted: 2006-10-27
  • Updated: 2014-02-27
  • Resolved: 2006-12-07
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.
Other
5.0u11 b02Fixed
Related Reports
Duplicate :  
JDK-6491327 - Vista: "Program Incomaptible" dialog is shown on jusched startup
Description
vista only, tiger only.

run 5u11 or 5u10 on latest vista build.

invoke java control panel, set some settings, e.g enable java console.

run a java web start or java plugin applet/application, java console won't be enabled.  settings made by java control panel will  have no effect.
Comments
SUGGESTED FIX A possible fix for the Vista 5u11 java control panel issue from our side is to simply modify the javacpl.exe and jpicpl32.cpl file version, so the Vista compatiblity shim won't be applied: http://web-east.east/deployment/www/webrevs/ngthomas/6487334/webrev/ I tried the fix on Vista 5840 and java control panel works as before. Vista will no longer require you to become admin in order to start the Java Control Panel. Once Microsoft removed the shim, we can revert back the file version information.
31-10-2006
EVALUATION in vista build 5840, the OSVERIONINFO is now correct, but another problem is the shim will cause the java control panel to run as admin, and when you run as admin, your user home directory changes to the admin user home directory as well. So any settings make by the user will have no effect, because the properties are stored in a wrong location.
31-10-2006
WORK AROUND rename javacpl.exe to something else (e.g javacpl2.exe), then run it. this will bypass the shim.
27-10-2006
EVALUATION since 5u10, in order for plugin/webstart/control panel to work properly on windows vista, we moved the deployment infrastructure directory to c:\users\<username>\appdata\locallow\sun\java\deployment so that plugin/webstart/control panel, even running at different integrity level, can both read/write to the deployment directories. but recently, vista has applied a compatiblity shim to javacpl.exe, which causes it to run in compatiblity mode, with OSVERSIONINFO.majorVersion=5. This breaks the functionality of Control Panel to modify settings in our deployment.properties file. (control panel will write out properties to deployment directory under "roaming" instead, due to the majorVersion is 5 instead of 6 for Vista). So properties set by control panel will not be pick up by plugin/webstart, since plugin/webstart is looking at the locallow location. the shim is only applied to 5.x release, so 6.0 does not have this problem.
27-10-2006