If a restart is necessary and the '/NORESTART' command isn't used (see below) and Setup is silent, it will display a Reboot now? message box. If it's very silent it will reboot without asking.
The default response in situations where there's a choice is:
5 message boxes are not suppressible:
The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)
The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parseable; the format of the file is subject to change without notice.
Don't forget to use quotes if the filename contains spaces.
Don't forget to use quotes if the filename contains spaces.
When a valid /LANG parameter is used, the Select Language dialog will be suppressed.
Only the specified tasks (and their children) will be selected; the rest will be deselected. Use the /MERGETASKS parameter instead if you want to keep the default set of tasks and only select/deselect some of them.
If UsePreviousTasks is set to yes, the specified tasks will be selected/deselected after any previous tasks are restored.
When an invalid password is specified, this command line parameter is also ignored.
0 | Setup was successfully run to completion. |
1 | Setup failed to initialize. |
2 | The user clicked Cancel in the wizard before the actual installation started, or chose "No" on the opening "This will install..." message box. |
3 | A fatal error occurred while preparing to move to the next installation phase (for example, from displaying the pre-installation wizard pages to the actual installation process). This should never happen except under the most unusual of circumstances, such as running out of memory or Windows resources. |
4 | A fatal error occurred during the actual
installation process.
Note: Errors that cause an Abort-Retry-Ignore box to be displayed are not fatal errors. If the user chooses Abort at such a message box, exit code 5 will be returned. |
5 | The user clicked Cancel during the actual installation process, or chose Abort at an Abort-Retry-Ignore box. |
6 | The Setup process was forcefully terminated by the debugger (Run | Terminate was used in the IDE). |
Before returning an exit code of 1, 3, or 4, an error message explaining the problem will normally be displayed.
Future versions of Inno Setup may return additional exit codes, so applications checking the exit code should be programmed to handle unexpected exit codes gracefully. Any non-zero exit code indicates that Setup was not run to completion.
If a restart is necessary and the '/NORESTART' command isn't used (see below) and '/VERYSILENT' is specified, the uninstaller will reboot without asking.
The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)
The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parseable; the format of the file is subject to change without notice.
Note that at the moment you get an exit code back from the uninstaller, some code related to uninstallation might still be running. Because Windows doesn't allow programs to delete their own EXEs, the uninstaller creates and spawns a copy of itself in the TEMP directory. This "clone" performs the actual uninstallation, and at the end, terminates the original uninstaller EXE (at which point you get an exit code back), deletes it, then displays the "uninstall complete" message box (if it hasn't been suppressed with /SILENT or /VERYSILENT).