Currently many of our users are deploying Java via windows Active Directory. This essentially run the installer in silent mode. If the user is running an upgrade, or uninstall, the potential for locked files is great.
The current implementation of our own FilesInUse dialog does not handle silent install. We should leverage the current code to add support for silent install, and write an error to the MSI and Java installer logs, to clearly convey that the upgrade/uninstall cannot proceed until all Java processes are stopped.
The current implementation of our own FilesInUse dialog does not handle silent install. We should leverage the current code to add support for silent install, and write an error to the MSI and Java installer logs, to clearly convey that the upgrade/uninstall cannot proceed until all Java processes are stopped.
- duplicates
-
JDK-6830672 Missing java files from system32
-
- Closed
-
-
JDK-6911757 Silent in place update of JRE fails during user session if browser is open.
-
- Closed
-
-
JDK-8037946 Java Installer (silent upgrade) can leave corrupted environment
-
- Closed
-