BATCH_INSTALL

InstallShield 2026 » InstallScript Language Reference

Project: This information applies to the following project types:

•

InstallScript

•

InstallScript MSI—if the InstallScript user interface (UI) style is the traditional style (which uses the InstallScript engine as an external UI handler)

This information does not apply to InstallScript MSI projects in which the InstallScript UI style is the new style (which uses the InstallScript engine as an embedded UI handler). To learn more, see Using the InstallScript Engine as an External vs. Embedded UI Handler for InstallScript MSI Installations.

The BATCH_INSTALL system variable is set to a non-zero value to indicate that one or more operations need to be performed after the target system restarts. BATCH_INSTALL can be set to a non-zero value for any of the following reasons:

•

The installation determines that a file cannot be installed because the file already exists on the target system and it is locked.

•

BATCH_INSTALL is set to non-zero manually through script. Note that this can occur in some objects if the object determines that an embedded installation needs a reboot to complete.

•

LAAW_OPTION_SET_BATCH_INSTALL is used when calling LaunchApplication, and the function determines that the launched installation needs a reboot to complete.

•

The installation attempted to update a Windows service (through ServiceAddService and the related functions), but it could not stop the existing service.

•

The DIFx integration indicated that a reboot is needed, due to the installation of a DIFx driver.

If BATCH_INSTALL is set to FALSE, no locked files were found and the installation process can end normally.

For more information, see Understanding When an Installation or Uninstallation Restarts the Target System.