JDK-6674868 : Issues with "Files in Use" dialog during Uninstallation
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-03-13
  • Updated: 2010-09-17
  • Resolved: 2008-06-16
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 6 JDK 7
6u10 b26Fixed 7Fixed
Related Reports
Duplicate :  
JDK-6714838 - Reinstalltion will fail when tried with applet opened in IE
Duplicate :  
JDK-6697567 - Remove the ignore button from "File in Use" dialog during uninstallation
Relates :  
JDK-6718336 - kernel jre uninstallation interrupted with java setup - close applications dialog
Description
How to reproduce   

1.  Install 6u10.

2. Lock some of the 6u10 JRE files by running applications such as Bugster (open 3-4 bugster windows)

3. Uninstall 6u10 offline. You will see "Files in Use" dialog. It only shows one entry in the list for all the windows which have same name.

4. Click the "Ignore" button. Though uninstallation goes fine but it may cause failure in subsequent install/unistall.

Issue 1:
"Files in Use" dialog only shows one entry in the list for all the windows which have same name. Where as it should show one entry for each window.

Issue 2:
Ignore button should be removed from the "Files in Use" dialog during unistallation as well. It will make sure that we have clean uninstallation and installation for the subsequent attempt.
Fixed by invoking our custom version of FilesInUse before MSI's default version (the one that includes problematic 'ignore' buttom).
Comments
EVALUATION The issue here was that MSI's version of the FilesInUse dialog did not behave in an acceptable manner for our requirements. We essentially implemented a work-around...we now invoke our custom version of a FilesInUse dialog BEFORE MSI has a chance to invoke the problematic built-in version. We accomplished this by creating a custom action that ivokes the dialog, and executing that custom action before InstallValidate in the ExecuteSequence.
13-08-2008
SUGGESTED FIX I suggest fixing this by either calling our own version of FilesInUse(), just like we do for installation, in order to avoid this MSI-specific version altogether. If this is not possible, the ignore button can be hidden from the user quite easily. Should not pose a risk to b25 code freeze.
12-05-2008
EVALUATION We need to see if this is really reproducible. The "ignore" button shouldn't be there anymore.
30-04-2008
EVALUATION I thought we got rid of the "ignore" button? These issues may not exist with the latest builds. Assigning to Paul for evaluation.
13-03-2008