JDK-7027774 : New feature request: remove dependency on RemoveFile table in MSI
  • Type: Enhancement
  • Component: install
  • Sub-Component: install
  • Affected Version: 6,6u15,7
  • Priority: P2
  • Status: Resolved
  • Resolution: Not an Issue
  • OS: generic,windows
  • CPU: generic,x86
  • Submitted: 2011-03-15
  • Updated: 2014-05-20
  • Resolved: 2014-05-20
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 8
8-poolResolved
Related Reports
Duplicate :  
JDK-6913472 - Can't uninstall JRE normally if I had clicked the "cancel" button of FIU.
Duplicate :  
JDK-6461252 - java uninstaller performance needs improvement
Duplicate :  
JDK-2143114 - java uninstaller performance needs improvement
Relates :  
JDK-7027582 - Java SE install process to fully support direct interaction with msiexec technology on Windows
Description
Using the RemoveFile table in MSI causes issues with JRE uninstallation:

1. It dramatically decreases performance (uninstallations a SLOW).
2. It prevents disabling the "FilesInUse" dialog, which along with inherent limitations, can cause JRE uninstallations to fail, or otherwise leave the user in an unacceptable state.
Comments
The new stand-alone MSI in 8u20/9 no longer needs the remove file table for most jre files. Now that we use the File Table properly, the MSI does not need as many RemoveFile table entries. It only uses the remove file table for the files it does not no about (.jar, classes.jsa files). There is no way around this as these files are generated during install runtime, and the msi does not know they are getting created. Closing as not-an-issue, as this has been resolved in 8u20/9 with msi redesign project.
20-05-2014
It's still applicable with new and old msi's. The only way we'd stop doing this is if we have one file component, which we may do at some point (if an enterprise really wants it for repair mode). To improve uninstall performance, we may want to write the code ourselves in installer.exe (because the remove file table is super slow).
28-08-2013
Is this still applicable to Wix in 8? For the new MSI project?
07-06-2013