Program, Setup Execution¶

This page allows you to open a document file or launch an application executable after a successful extraction or specify the loader (executable file) for your Setup routine. For a standard package, this refers to the document file you wish to open after the package closes (optional).

Program/Document Filename (for Standard Package type)¶

Use this field to specify the full path to the file to be executed after extraction. For document files (e.g., text or help files), the associated application will open the file. You can also specify an Internet address, such as https://www.mycompany.com, which will open the default browser to the specified page.

Example: %DESTPATH%\Readme.txt will open the Readme.txt file extracted to the default destination folder.

Setup Launcher Filename (for Package for a Setup routine type)¶

Specify the full path to the program file that will launch your setup routine. The package will wait for the setup to complete before removing all temporary files. The file must be an executable (e.g., .exe).

To run a Microsoft Windows Installer package (MSI) or patch (MSP), enable the "Install a Windows Installer package" option. See details on installing Windows Installer packages with Paquet Builder.

Other Options¶

These options vary depending on the package type, unless marked "common."

Display an "Additional Task" Checkbox on the Final Screen¶

(For Standard Package only)
Optionally, allow users to decide whether the document file specified above should open. This adds a checkbox to the final screen. If unchecked, the file will not open.

For more complex tasks, you can use custom actions to prompt users. Set the checkbox caption using the "Task Description" field.

Run Program as Un-Elevated Process¶

(For Standard Package only)
If the package runs with administrative rights (defined by the manifest), any launched executable will also run with administrative rights. Enable this option to launch the program with standard user rights instead.

Remove Setup Files Only at Windows Startup (for Reboots)¶

(For Package for a Setup routine)
Advanced users may enable this option if the setup routine requires a reboot (e.g., for replacing files in use).

When enabled:
- The package extracts files to a temporary folder and launches the setup.
- Temporary files remain until the next Windows restart.
- An uninstaller is created to silently remove temporary files and folders at startup. This does not affect installed application files.

Command Line Switches¶

Use this field to pass command-line switches or parameters to the executed file. Variables referencing system or shell folders are supported.

Use a Fixed Name for the Temporary Folder¶

(For Package for a Setup routine)
Certain setups (e.g., MSI packages) may require their files to remain in the same location. Enter a unique name, such as "MyCompanyProgramSetupFiles," to ensure the setup files are always extracted to the same temporary folder.