Project Settings


Enable silent/unattended install

Enable the install to be run in "silent mode" using the /S command line option. This means that there will be no user interaction required during the installation process. If you are performing silent installations, it is highly recommended that you use a log file during the setup process so that you can debug the setup if problems occur.

Note: Screen actions will only be executed if screens are displayed, therefore when run in silent mode, no screen actions will be executed.

Start in silent mode

Start the setup in "silent mode" by default.  If unchecked, you can run your setup in silent mode using the command line option /S, for example C:\Output\setup.exe /S. Selecting this option sets the global variable _SilentInstall to true.

Default User Profile for Shortcuts


On Windows NT based operating systems, this option allows you to specify which users the program shortcuts will be created for by default:

Current user only

Create program shortcuts in the current user's profile only. This option sets the boolean global variable _UsePerUserFolders to true.

All users

Create program shortcuts in the "All Users" profile. This option sets the boolean global variable _UsePerUserFolders to false.

Application Settings

Use custom icon:

Display a custom icon in the top left corner of your installation window.  It will also be used to represent the installation on the Windows task bar. Click the Browse button to open the Insert File Reference where you can select an existing standard icon (.ico) file from your project's Primer Files list, or add one. After the file has been selected, this field will contain the location to reference the icon file during the installation.

Hide taskbar icon

Hide the taskbar icon during the install.

Always on top

Make the installation window always appear on top of all other windows on the desktop. The window will remain on top even if the user switches to another application.

Requested User Privilege Level

This section specifies which requested execution level to include in the install/uninstall's application manifest for distribution on Windows Vista or later. Installations should generally always be built using the default "Require administrator" setting. Before changing this default setting, see Installing on Windows Vista or Later for important information concerning required changes to your install, and feature limitations.

Note: For more information on the settings below and general Windows Vista/Windows 7/Windows 8/Windows 8.1/Windows 10 information, see Installing on Windows Vista or Later.

As invoker

The setup runs with the same access token as the parent process. For example, if the user is logged in as a standard user, those are the privileges they will inherit during the setup. This option should only be used in special circumstances where you are certain you do not need access to protected areas of the operating system.

Highest available

The setup runs with the highest privileges the current user can obtain. This setting is designed for applications that can be run by all users. It is most useful for applications that require privileges above that of a limited user, but less than a full administrator.

Require administrator (default)

The setup requires to be run with the full access token of an administrator. Generally installations make changes to protected system locations that are typically writable to only by administrator users. This is the default setting for installs created with Setup Factory.