I have been using InstallShield for a very long time and using the AdvancedUI since 2012. However, just today I discovered something I missed - it appears that the installer does not validate if the target system has enough disk space for the feature cost. I am using Suite/AdvancedUI 2021.  Do I need to create a custom action to evaluate the disk cost requirements and ensure the target system has enough disk space? I had always thought that InstallShield would include this basic expected feature from the start. I know it is complex because you have to evaluate if you are extracting files to the cache directory or if the file is running from DVD/CD media as well as determine where each package will be installed.  In our case, I have an installer where we are attempting to upgrade customers from SQL Server 2012 Express to a newer version. The install for SQL Server 2016 does not appear to do its own check for available disk space. If I add a custom setup dialog to the setup wizard stack, the file cost is displayed correctly there, but it does not stop the user if the available disk space is lower than the required disk space. ... View more

Objective I need to be able to restart a system after a suite installer InstallScript custom action finishes. Background I have a requirement to do the following: Uninstall an instance of SQL Server 2012 Express (done) Create that instance using SQL Server 2016 Express (done - except when there is a  PendingFileRenameOperations ) Sometimes the uninstall of SQL Server 2012 Express will create a new  PendingFileRenameOperations. If this exists, then the next step to install SQL Server 2016 will fail.  If the user just restarts after getting the error, then the suite installer does not call the OnResuming event - which contains a step to collect setup information that the installer writes to a config file in the OnRebooting event. This leaves the suite installer starting over and trying to access database settings and values that do not exist since the install for SQL Server 2016 did not finish. What I have so far I can correctly detect if the system requires a reboot by querying the appropriate registry keys If I just force an exit of the setup, that does not cause the installer to restart after the user has restarted the system and logged back in.  I have thought about manually writing to the RunOnce registry key, but I am not certain of the syntax for this.  I already check for  PendingFileRenameOperations and RunOnce registry keys when starting the install and correctly ask the user to restart the computer before starting the install. However, this does not fix this current issue, where the Uninstall of SQL Server 2012 Express instance will generate a PendingFileRenameOperations .  Thank you in advance.    ... View more