Hi, One of our installers is removing the old bundle (via a pre-flight script), but failing to install the new bundle. We need help resolving the situation. We have a Packages-built installer (.pkg) which includes a pre-flight script to remove a particular audio plug-in bundle before continuing to install the new one. This was done because certain installations of the old bundle had version numbers that were incorrect - higher than the new bundle’s version number - and so are not replaced automatically. For our VST3 bundles, this is working correctly, but for our AAX bundles, something in the system seems to be holding onto the deleted bundle, preventing writing of the new one. After the installer runs, the old bundle is gone, but the new one has not been written. The user has to run the installer a *second* time in order to get it ti install the new bundle. Obviously, that is not a good result. Is there some reason for this behavior? Perhaps ownership of the containing folder hierarchy or something? More importantly, is there some way to ensure that this does not happen? The script line to remove the bundle is simple enough. Here it is. Is there something that I can do to modify the script to make the system let go of the old bundle and allow the new one to write? rm -fR /Library/Application\ Support/Avid/Audio/Plug-Ins/Antares\ Audio\ Technologies/Mic\ Mod\ EFX.aaxplugin rm -fR /Library/Application\ Support/Avid/Audio/Plug-Ins/Mic\ Mod\ EFX.aaxplugin (That second line is just in case the plug-in was moved to the root of Plug-Ins folder, which we have seen happen.) Any thoughts? Thanks, Howard _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com