I have a Java MSI package installing as a Windows service (XP & 2003). When the package is uninstalled, either by right-clicking the MSI, or by installing a newer version, the jar files from the package are entered into the Windows Registry PendingFileRenameOperations key to be deleted upon reboot. According the Microsoft, that key gets created by applications when files are detected to be in use, so the files can be removed upon reboot. However, the Java service is not running and no other apps use these files. The only user of these files at the time of uninstall is the AI MSI package.
The registry key is:
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\Session Manager]
PendingFileRenameOperations
How can I keep those entries from being created in the PendingFileRenameOperations registry key when I'm upgrading a package? Please note, it's only the jar files that this is affecting--the config files are all deleted, etc. My suspicion is that the MSI is seeing the jars in the classpath or something and thinks the jars are in use. Any ideas?
What should happen is, from package version to package version, the files from the new package overlay the files from the old package, which happens fine, except that when the old package is uninstalled, the PendingFileRenameOperations entries are being made.
Thanks,
Matt
FOLLOW US
Get the latest news in Application Packaging