We have an application set to run as a custom action on install "After the system has been successfully modified", and "Wait for custom action to finish before proceeding" is set.
On XP, we have had no problems with it.
On Windows 7, however, the application window launches behind the installer - and this is problematic, because the window is smaller than the installer window, so it just looks like the installer has frozen on the step "Removing backup files".
We have two products that use advanced installer, independently created by separate groups in our organisation, and both use this same mechanism of launching an application at this stage of the installation process. Both products have exhibited this behaviour on Windows 7 and not on XP.
We are using Advanced Installer 9.9, with an Enterprise license.
Is this a bug in Advanced Installer, a configuration error on our part, or something else?
FOLLOW US
Get the latest news in Application Packaging