Inno Setup 6
Revision History

Copyright © 1997-2024 Jordan Russell. All rights reserved.
Portions Copyright © 2000-2024 Martijn Laan. All rights reserved.
For conditions of distribution and use, see LICENSE.TXT.

Want to be notified by e-mail of new Inno Setup releases? Subscribe to the Inno Setup Mailing List!

6.3.1 (2024-06-10)

- Fix Compiler IDE startup error on systems with very high DPI.

6.3.0 (2024-06-09)

Support for UTF-8 encoded files improved

- Added support for UTF-8 encoded files without a BOM for .iss script files, .isl messages files, `LicenseFile`, `InfoBeforeFile`, `InfoAfterFile`, and ISPP's `#file`.
- Compiler IDE changes:
  - New script files are now saved as UTF-8 without a BOM by default, bringing the IDE into line with most other text editors. Existing files are still saved as they were until the save encoding is changed manually using the Save Encoding submenu of the File menu.
  - Added new UTF-8 with BOM menu item to the Save Encoding submenu of the File menu to save new files with a BOM anyway.
- Pascal Scripting changes:
  - Support function `LoadStringsFromFile` now also supports UTF-8 encoded files without a BOM.
  - Added new `SaveStringsToUTF8FileWithoutBOM` support function.
- ISPP change: preprocessor output saved by `SaveToFile` is now always saved as UTF-8 without a BOM.

Support for Arm64 systems improved, and related enhancements

- Setup now officially supports the installation of x64 apps on Arm64 Windows 11 systems, which are able to run x64 binaries via emulation. To enable your x64 app installers to run properly on Arm64 Windows 11, some minor changes may be needed in your scripts. Most importantly:
  1. In `ArchitecturesAllowed` and `ArchitecturesInstallIn64BitMode`, change any use of `x64` to `x64compatible`.
  2. In `Check` parameters and `[Code]`, change any use of `IsX64` to `IsX64Compatible`.
  3. In `[Code]`, if there are any `ProcessorArchitecture = paX64` comparisons, replace them with calls to `IsX64Compatible`.
  The key difference between `x64`/`IsX64` and the new `x64compatible`/`IsX64Compatible` is that the latter matches both x64 Windows and Arm64 Windows 11.
  In most cases, you should make the above changes, because otherwise, users on Arm64 systems may not be able to run your installers. For example, an `ArchitecturesAllowed=x64` setting will only allow the installer to run on x64 Windows — not on Arm64 Windows 11. Or, if you ship x86 and x64 versions of your app in the same installer, the 32-bit x86 version may be chosen instead of the expected x64 version when running on Arm64 Windows 11.
- The `[Setup]` section directives `ArchitecturesAllowed` and `ArchitecturesInstallIn64BitMode` have been enhanced:
  - Six new architecture identifiers have been introduced. Briefly:
    - `arm32compatible` matches systems capable of running 32-bit Arm binaries.
    - `x64compatible` matches systems capable of running x64 binaries.
    - `x64os` matches systems running x64 Windows only. (Equivalent to the existing `x64` identifier, which is now deprecated.)
    - `x86compatible` matches systems capable of running 32-bit x86 binaries.
    - `x86os` matches systems running 32-bit x86 Windows only. (Equivalent to the existing `x86` identifier.)
    - `win64` matches systems running 64-bit Windows, regardless of architecture.
    See the new Architecture Identifiers help topic for further details on each.
  - Boolean expressions are now supported. Through use of the `and` operator, for example, it is possible to require two architecture identifiers to match at the same time. See the `ArchitecturesAllowed` help topic for usage examples.
- The `x64` architecture identifier is now deprecated. If it is used, the compiler will issue a warning and substitute `x64os`, which has the same effect. But as mentioned above, in most cases, scripts should be changed to use `x64compatible` because it matches both x64 Windows and Arm64 Windows 11.
- The 64-bit example scripts (`64Bit*.iss`) have all been updated to use `x64compatible` as preferred.
- Certain 64-bit functionality that previously only worked on x64 Windows now works on Arm64 Windows 11 as well. This includes:
  - The `Permissions` parameter of the `[Dirs]` section when running in 64-bit install mode.
  - The `Permissions` parameter of the `[Files]` section when running in 64-bit install mode or when the `64bit` flag is used.
  - The `Permissions` parameter of the `[Registry]` section when running in 64-bit install mode or when the value of the `Root` parameter ends in `64`.
  - The `regtypelib` flag of the `[Files]` section when running in 64-bit install mode or when the `64bit` flag is used.
  Note that all of the above remains unsupported on Arm64 Windows 10.
- Setup now logs the machine types supported by the system — that is, what types of EXEs can be executed, either natively or via emulation. For example, when running on an Arm64 Windows 11 system, it logs: `Machine types supported by system: x86 x64 Arm32 Arm64`.
- The `OnlyOnTheseArchitectures` message is not used anymore. Instead, the `WindowsVersionNotSupported` message is now shown when Setup is started on an architecture that is not allowed by the `ArchitecturesAllowed` expression. (But please do not remove the message from translation files.)
- Pascal Scripting change: Added new `IsArm32Compatible`, `IsX64Compatible`, `IsX64OS`, `IsX86Compatible`, and `IsX86OS` support functions. The `IsX64` support function still exists but is now deprecated as explained above. Example testing all architecture identifiers:

      [Code]
      function InitializeSetup: Boolean;
      begin
        if IsArm32Compatible then Log('IsArm32Compatible');
        if IsArm64 then Log('IsArm64');
        if IsX64OS then Log('IsX64OS');
        if IsX64Compatible then Log('IsX64Compatible');
        if IsX86 then Log('IsX86');
        if IsX86OS then Log('IsX86OS');
        if IsX86Compatible then Log('IsX86Compatible');
        if IsWin64 then Log('IsWin64');
        Result := True;
      end;

Support for #include files improved

- The Compiler IDE now opens up to 20 #include files in tabs, instead of up to 10.
- Tabs for opened #include files can now be closed: Added new Close Tab (Ctrl+F4), Reopen Tab, and Reopen All Tabs menu items to the View menu, also available by right clicking the tab bar.
  Because of this the shortcut for the Evaluate Constant menu item in the Run menu has been changed from Ctrl+F4 to Ctrl+F7.
- The selected and mouseover #include file tabs now show close buttons.
- Added a clickable panel to the Status Bar showing the amount of closed tabs if there are any.
- Removed flicker (especially visible in dark mode) when switching tabs.

Support for Windows Vista, Windows Server 2008, and the Itanium architecture removed

- OS requirements change: Windows Vista and Windows Server 2008 are no longer supported. Windows 7 and Windows Server 2008 R2 are now the minimum supported operating systems. `[Setup]` section directive `MinVersion` still defaults to `6.1sp1`, so by default Setup will still not run versions of Windows 7 and Windows Server 2008 R2 which have not been updated.
- The defunct Itanium architecture is no longer supported. The `ia64` architecture identifier has been removed, and Setup will display the `WindowsVersionNotSupported` error message if it's started on an Itanium system.
- Removed `[Icons]` section flag `foldershortcut` which was already ignored except when running on Windows Vista or Windows Server 2008, as folder shortcuts do not expand properly on the Start Menu anymore.

Compiler IDE changes

- Added toolbar buttons and shortcuts to navigate back (Alt+Left) and forward (Alt+Right). Navigating by pressing the mouse X buttons is also supported. A navigation item is added when changing tabs or moving at least 11 lines at once, similar to Visual Studio 2022.
  Because of this Alt+Right can no longer be used to initiate auto complete, instead the existing Ctrl+Space or new Ctrl+I alternative must be used. To still be able to also use Alt+Right for this activate Visual Studio-style shortcuts, see below.
- Added support for Visual Studio-style shortcuts (like Ctrl+- to navigate back, Ctrl+B to compile and F5 to run) to the Build and Run menus. To activate this use the Options menu item in the Tools menu to set the new Key Map option to Visual Studio.
- Added multiple selection support (Ctrl+Click or Ctrl+Drag). Typing, backspace, delete, undo, redo, copy, and paste all work with multiple selections added this way or via the pre-existing support for performing rectangular block selection (Alt+Shift+Arrow or Alt+Drag).
- Added a shortcut to revert multiple selections into a single one or a single selection into an empty one (Esc).
- Added dark mode support to the title bar on Windows 10 Version 2004 and later.
- Added dark mode support to the main menu bar on all versions of Windows.
- Added dark mode support to the menus on Windows 10 Version 1903 and later up to Windows 11 Version 23H2 which is currently the latest version of Windows 11.
- Updated the icons used by the editor's gutter, including the automatic use of higher quality versions in a widened gutter on higher DPI settings.
- Lines with a breakpoint are now displayed as normal lines with syntax highlighting, instead of as white text on a red background. The editor's gutter still displays an icon on such lines.
- Breakpoints are now preserved on a per-file basis between sessions.
- Added new Delete All Breakpoints (Shift+Ctrl+F5) menu item to the Run menu.
- Added icons to the menus.
- Added new Highlight occurrences of current selection and Highlight occurrences of current word options. The first is enabled by default and the second is disabled by default.
- The Allow cursor to move beyond end of lines option ("virtual space") is now disabled by default, consistent with most other editors.
- When the Allow cursor to move beyond end of lines option is enabled, pressing the left arrow key while the cursor is at the start of a line no longer moves the cursor to the end of the previous line unless the Ctrl key is also pressed, just like in Notepad++, Visual Studio, and RAD Studio.
- The New Script Wizard now offers an option to import a Windows registry .reg file.
- The New Script Wizard now automatically sets `ArchitecturesInstallIn64BitMode` and `ArchitecturesAllowed` to `x64compatible` if it detects that the chosen main executable file is 64-bit. The default main executable file is now the 64-bit MyProg-x64.exe example executable instead of 32-bit MyProg.exe.
- Added new Generate [Registry] Entries (Shift+Ctrl+R) menu item to the Tools menu to import a Windows registry .reg file as extra entries to the `[Registry]` section at the cursor position, or to a new section.
- Added new Generate [Files] Entries (Shift+Ctrl+I) menu item to the Tools menu to design and insert extra entries to the `[Files]` section at the cursor position, or to a new section.
- The Generate MsgBox/TaskDialogMsgBox Call tool (previously named MsgBox/TaskDialogMsgBox Designer) now respects the tab width and tab character settings, indents the generated Pascal script one extra level, and warns if the cursor position is not in the [Code] section.
- Minor theme color tweaks such as a different background color for the selected text.

Support for logging improved

- Added new `[Run]` and `[UninstallRun]` section flag `logoutput`. Instructs Setup and Uninstall to log the output of the executed program or batch file. Cannot be combined with the `nowait`, `runasoriginaluser`, `shellexec`, and `waituntilidle` flags. Has no effect if logging is not enabled.
- Added new `[Setup]` section directive `UninstallLogging`, which defaults to `no`. If set to `yes`, the uninstaller will always create a log file if it is launched from the Add/Remove Programs Control Panel applet. Equivalent to passing /LOG on the command line.
- Digital signing change: Sign Tool output is now always logged in the Compiler IDE's "Compiler Output" view, making it easier to debug issues. Because of this, sign tools that are console programs will now always run hidden, as their output is being captured and they would display nothing in their window.
- Pascal Scripting change: Added new `ExecAndLogOutput` support function. Can be used to log the output of the executed program or batch file to Setup and Uninstall's log, or to receive the output line by line in your own `[Code]` function, for example to read the first non-empty line from the output as shown in the help file and the new PowerShell.iss example script.
- ISPP changes:
  - Output of programs or batch files executed using the `Exec` support function is now always logged in the Compiler IDE's "Compiler Output" view.
  - Added new support function `ExecAndGetFirstLine` to execute a program or batch file and read the first non-empty line from its output which can then be placed or used in the script as shown in the new PowerShell.iss example script.

Other changes

- Console-mode compiler (ISCC) change: Added support for Unicode output.
- Added new `[Files]` section flag `signcheck`. Instructs the compiler to check the original source files for a digital signature before storing them.
- During startup Setup would always ask Windows to create any missing `{usercf}`, `{userpf}`, and `{usersavedgames}` folders. It no longer does until the script asks for the folder. Note that scripts running in administrative install mode should not do this because it violates the used user areas warning.
- Changes to further help protect against potential DLL preloading attacks.
- Added support for IIS group users identifiers (`iisiusrs`) for use in `Permissions` parameters.
- ISPP changes:
  - Added support function `AddQuotes` to add a quote character to the left and right sides of a string if the string contains a space and it didn't have quotes already.
  - Support function `Exec` no longer requires the filename parameter to be quoted if it contains spaces. Additionally it now supports ">" as a filename and now includes special platform-independent support for .bat and .cmd files, both just like for example the `[Run]` section.
- Pascal Scripting changes:
  - Added support functions `UTF8Encode` and `UTF8Decode` to encode a Unicode string into a UTF-8 encoded ANSI string and vice versa.
  - Added support functions `LoadStringFromLockedFile` and `LoadStringsFromLockedFile` to read strings from a file even if it's already opened for writing by another program.
  - Added support class `TNewLinkLabel` which can display multi-line text with embedded links and internally uses a Windows SysLink control. See the CodeClasses.iss example script for examples.
  - `TWizardForm`: Added new `AdjustLinkLabelHeight` function.
  - `TDownloadPage`: Added new `ShowBaseNameInsteadOfUrl` property.
  - It is now possible to write `var S: set of AnsiChar; begin S := ['a', 'b']; end;`. In previous versions this would result in a type mismatch error.
  - It is now possible to write `Stream.ReadBuffer(S, Length(S));` when S is of type `AnsiString`. In previous versions this would compile but not work at run time. Same applies to `Read`, `Write`, and `WriteBuffer`: all four functions now accept any type of string.
  - Added example which downloads and unzips a Zip file to the CodeAutomation.iss example script.
  - Type `TShellFolderID` was removed because it wasn't used by any support function.
- Improved the icons used by the Select Language dialog and the Select Destination Location, Select Start Menu Folder, and Preparing to Install wizard pages at 150% DPI and at 200% DPI.
- Added modern icons to the MyProg example executables, now compiled with Visual Studio 2022.
- Added official Korean translation.
- Inno Setup is now built using Delphi 11.3 Alexandria instead of Delphi 10.3 Rio.
- Inno Setup's Delphi projects have been recreated as new clean projects and have been added to a Projects\Projects.groupproj project group. This makes it a lot easier to get started with working with the Inno Setup source code and making contributions, even with the free Delphi Community Edition.
- Minor tweaks and documentation improvements.

Contributions via GitHub: Thanks to Achim Stuy, ser163, Jens Geyer, and Sergii Leonov for their contributions.

Inno Setup 6.2 Revision History