JDK-6913472 : Can't uninstall JRE normally if I had clicked the "cancel" button of FIU.
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u15
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • CPU: x86
  • Submitted: 2009-12-29
  • Updated: 2011-03-15
  • Resolved: 2011-03-15
Related Reports
Duplicate :  
JDK-7027774 - New feature request: remove dependency on RemoveFile table in MSI
Description
There is an uninstall issue of JRE from 6u15,only reproducible with 32bit JRE uninstall.
To reproduce this issue by the following procedure on Windows/x86
   1. Install JRE on Windows XP/vista/7;
   2. Open "Java Control Panel" in Windows "Control Panel";
   3. Uninstall JRE with the "Java Control Panel" running (Java in using);
   4. "File In Use" dialog pop up and click the button "Ignore";
   5. Another dialog "Close Programs" prompt that some programs are using Java.
      Click the button "Cancel";
   6. Then click "OK" to close all the dialogs.

 Now the JRE could not be uninstalled normally anymore (no java working) without
 any warning message.It doesn't work even I re-login or restart the machine.To uninstall
 the JRE successfully,I have to repeat step1 to step5 and click button "Close Programs 
 and Continue" at step5. It is very difficult to uninstall Java for the users who 
 had failed to uninstall Java when Java was in using before.
Comments
EVALUATION Removing the dependency on the RemoveFile table in the JRE MSI will resolve this issue. See also 7027774.
15-03-2011
EVALUATION Unfortunately this cannot be fixed. The first instance of FilesInUse UE being shown is our own code. The 2nd is from MSI. We implemented our own FilesInUse dialog and supporting logic because of the limitations of the MSI version. As seen in this CR, the MSI version of the dialog is unable to handle the JCP. There is no way to disable the MSI version of FilesInUse. The best we can do is implement our own logic immediately before MSI's would be called, thereby circumventing the problematic MSI implementation. If the user 'ignores' our implementation, there is nothing that can be done to prevent the MSI version from causing these types of issues. This will only happen on uninstall, also.
15-03-2011