This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
User Account Control on Windows Vista RC1 prevents installer from running external processes => installer fails. We must decide if/how will we handle this.
Created attachment 34500 [details] Exception call stack
The reason is that InstallShield uses its own launcher LauncherMain.exe ran from temp dir to start some external java process. As this exe is unknown to OS it is not allowed to run when UAC is active. If I run JDK java.exe using Runtime.exec it works fine. So it is IS who is breaking security constraints imposed by UAC. There is no way in Java API how to increase security level for such call so far. See issue http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6410605.
Note: Workaround described in issue #6410605 (use "cmd","/c","prog" instead of "prog" in Runtime.exec) is not appropriate for such usecase because it invokes confirmation dialog and it is unacceptable for background tasks. (It would mean user would have to approve such processes during installation manualy.)
Will send a waiver request. This should be IMO mentioned in Release Notes together with issue 85361.
Info for release notes (the same as in issue #85361): Installer must be run on JDK 6.0 build 96 and newer. Also Compatibility mode must be disabled. (Vista sets compatibility mode for installer exe automaticaly. It must be switched off manually in File Properties -> Compatibility tab.) Then installer exe runs fine even if UAC is enabled.
Additional note: If both JDK 5 and JDK 6 are installed JDK 6 must be selected explicitly using command line option -is:javahome <Path to JDK 6>. Otherwise JDK 5 will be selected by launcher - it is given by JVM resolution order defined in installer launcher for Windows. As we currently use common installer for all supported Windows versions we do not want to change order for JVM resolution. Solution depends on when fix for JFileChooser will be backported to JDK 5. If fix will not be backported to JDK in next update we can distribute separate installer for Vista with modified JVM resolution - JDK 6.0 and newer will be required to run installer.
Closing this issue as WORKSFORME because when issue #85658 is workarounded by disabling compatility mode ie. installer exe can be run directly it does not happen. In other words this problem happens only when running installer using "java -jar setup.jar" which is not usual way. If for any reason there is need to run setup.jar instead of exe UAC should be disabled but it does not limit usual users.
Note, that issue 85658 is about something completely different. Issue 85361 is the one that stays open for Vista.
Yes right.