About Some Setup Software
When creating a Setup Routine package, the package extracts files to a temporary folder, launches the setup, and removes the temporary files when the setup finishes. Some third-party setup programs cause issues because they exit before the installation is actually complete.
The Problem
Section titled “The Problem”Certain setup programs use a small bootstrap loader that initializes temporary files, launches the real installation, then exits immediately, even though the installation is still running. Paquet Builder sees the loader exit and removes the temporary files prematurely.
Solutions
Section titled “Solutions”InstallShield setups use a loader that closes before the installation finishes.
Fix: Add the /SMS parameter to the Command Line Options field. This instructs the loader to wait until the installation routine completes before exiting.
For other setup programs (e.g. Visual Studio Installer, MSI bootstrappers) or setups that require a system reboot:
Enable “Remove Setup files only at Windows startup (in case of a reboot)” in the Setup Execution panel.
- The package extracts files to a temporary folder.
- The setup procedure is launched.
- Instead of immediate cleanup, an internal uninstaller is created and scheduled to run at the next Windows startup.
- At startup, the uninstaller silently removes the temporary files and folder.