6.7.0-dev (?)

Using Inno Setup commercially? Please purchase a license.

Setup now allows you to specify a custom background color and optionally also a background image. This supports blending the color and image with each other, and optionally supports using a separate background color and image if dark mode is active.

Custom background colors are also supported by Uninstall.

These changes are backward compatible: if you do not set any of the new directives, then your installers and uninstallers will look the same as before.

• Added new WizardStyle modifier excludelightcontrols. Disables custom styling of all controls (including buttons) when a light style is active, except when styling is required to achieve transparency.
• Added new WizardStyle modifier hidebevels. Hides all bevels (horizontal lines) across Setup and Uninstall, except those in native system dialogs.
• Added new [Setup] section directives WizardBackColor and WizardBackColorDynamicDark to specify custom background colors to use for wizard pages and all other windows such as the Select Language dialog, in both Setup and Uninstall.
  If you set this directive but a custom style is not specified by WizardStyle, it will automatically activate custom style windows11 with modifier excludelightcontrols.
• Added new [Setup] section directives WizardBackImageFile and WizardBackImageFileDynamicDark to specify custom images to display as the background of wizard pages in Setup, but not in Uninstall.
  Supports specifying multiple files for high-quality results on all DPI settings.
  If you set this directive but a custom style is not specified by WizardStyle, it will automatically activate custom style windows11 with modifiers excludelightcontrols and hidebevels.
  Note that in light mode, the windows11 custom style uses an off-white background color. To revert this, set WizardBackColor to white.
  Example screenshot of Setup using a background image in dark mode, at 150% DPI.
  Example screenshot of Setup using a background image in light mode, at 150% DPI.
  Example screenshot of a task dialog using a background color, at 125% DPI.
• [Setup] section directives WizardImageFile and WizardSmallImageFile can now be set to blank values when you want the background image (or color) to stand on its own. Doing so does not change the layout of the wizard.
  Alternatively, set WizardImageOpacity to blend these images with the background image (or color). Can be used with the built-in wizard images as well.
• Added new [Setup] section directive WizardBackImageOpacity to specify the opacity (non-transparency) of the background image.
  This is useful if you want to use an identical regular and DynamicDark background image.
• Examples:

  ; Use separate background images for light and dark appearances
  WizardBackImageFile=MyBackImage.png
  WizardBackImageFileDynamicDark=MyBackImage_Dark.png
  ; Hide the large and small wizard images
  WizardImageFile=
  WizardSmallImageFile=
  
  ; Use the same background image for both light and dark appearances
  WizardBackImageFile=MyBackImage.png
  WizardBackImageFileDynamicDark=MyBackImage.png
  ; Apply transparency to the background image so it works well in
  ; both light and dark appearances
  WizardBackImageOpacity=150
  ; Keep large and small wizard images, applying transparency so they
  ; blend with the background image
  WizardImageOpacity=150
  
  ; Use a background image in the wizard, and also use custom
  ; background colors on other windows, and in Uninstall
  WizardBackImageFile=MyBackImage.png
  WizardBackImageFileDynamicDark=MyBackImage.png
  WizardBackColor=#ffc0cb
  WizardBackColorDynamicDark=#570c22
  ; On wizard pages blend the background image and color together
  WizardBackImageOpacity=150

• Pascal Scripting: Added new support function WizardSetBackImage to set, update, or remove the background image at runtime. It can be used not only in Setup, but also in Uninstall.
  See the new help topic for an example, and see new function BackImageButtonOnClick in CodeClasses.iss for another example.

Autocomplete now cuts [Setup] section directive lookup time, and #include tabs are more manageable, even in large projects.

• Added autocomplete support in the [Setup] section for directive values with fixed options, such as all yes/no directives and others like WizardStyle.
• The Compiler IDE now opens up to 50 #include files in tabs, instead of up to 20.
• Added a new Keep new #include files closed option, disabled by default.
  When enabled, newly discovered #include files during compilation remain closed until you explicitly reopen their tabs via, for example, the View menu.
• Added new Go to File menu item to the Edit menu to go to a file (Ctrl+F12 or Ctrl+P).
• When opening a file that is an #include file of the current main file using the Open menu item of the File menu, the IDE now offers to go to its tab instead of opening it as the new main file.
• Ctrl+W now closes the current tab (in addition to Ctrl+F4), consistent with other modern editors. Previously, Ctrl+W was assigned to Target Uninstall in the Run menu, which is now reassigned to Alt+Q.

Updating is recommended, even if you don't plan to use the other enhancements right away. We continually add extra checks to make your installers safer and more reliable. In this version:

• Setup and Uninstall now always try to enable Windows RedirectionGuard by default.
  This mitigation, currently available only on Windows 11, blocks traversal of NTFS junctions created by non-admin users, to prevent path redirection vulnerabilities when privileged installers touch attacker-controlled directories.
  Can be disabled by setting new [Setup] section directive RedirectionGuard to no, and can also be disabled or enabled using new Setup and Uninstall command line parameters '/NOREDIRECTIONGUARD' and '/REDIRECTIONGUARD'.
  When no command line parameter is specified, Uninstall enables or disables RedirectionGuard based on the latest install.
  RedirectionGuard status is logged, so you can verify whether the mitigation was active.
• Experimental: Added support for using a 64-bit version of the "Setup Loader" program by setting existing [Setup] section directive UseSetupLdr to x64.
  Using x64 does not mean that Setup itself will also be 64-bit: Setup itself is currently always built as a 32-bit x86 binary.
  Using x64 anyway has several benefits: your installer initially presents itself as a native 64-bit executable, the 64-bit loader has high-entropy ASLR enabled, and it no longer uses the WOW64 emulation layer. Additionally, it can help satisfy policy or third-party requirements that mandate 64-bit installers, even while the main Setup program is still 32-bit.
  The downside is that your installer will no longer load on systems running x86 Windows.

• Added retry mechanisms to the compiler to make the compilation process more robust against temporary file access issues, such as when antivirus software or other processes temporarily lock output files.
• [Setup] section directives such as WizardImageBackColor and WizardBackColor now also accept color names like white and black, in addition to clWhite, clBlack, #ffffff, and #000000.
• Fix: File and directory controls in Setup should always use left-to-right reading order, even when a right-to-left language is active, but this has not been the case since version 6.5.2.
• Pascal Scripting:
  • Added support functions PathCombine, PathEndsWith, PathHasInvalidCharacters, PathIsRooted, PathNormalizeSlashes, PathSame, and PathStartsWith to make path handling easier.
  • Added support class TNewPathEdit, a TNewEdit descendant that always uses left-to-right reading order and provides filesystem autocompletion.
    You should use TNewPathEdit instead of TNewEdit for file and directory controls, but using TInputFileWizardPage and TInputDirWizardPage instead is still recommended.
  • Added support function RPos.
• ISPP:
  • Fix: Support function SameStr is now properly case-sensitive.
  • Fix: Support function RPos now properly returns 0 for empty substrings.
  • Using support function ExtractFileDir no longer triggers a warning about RemoveBackslash.
• The various options for [Setup] section directive DisablePrecompiledFileVerifications have had their dll/e32/exe postfixes removed. Options setupldre32 and setuplde64 have been merged into a single setupldr option.
• Other minor improvements.

6.6.1 (2025-11-20)

• Changes related to custom styles:
  • Previously, when displaying any RTF text with a custom style active (including the built-in custom dark style), all foreground colors were replaced by the style's foreground color. This has been improved to only replace default foreground colors, preserving any custom colors.
  • Added new [Setup] section directive WizardImageOpacity to specify the opacity of wizard images. This is useful if you want to use identical regular and DynamicDark wizard images. For example, you can set it to 150 to achieve partial transparency. Defaults to fully opaque (non-transparent).
  • The compiler now stores identical regular and DynamicDark wizard images only once.
  • Documentation fix: The prototype of Pascal Scripting support function CreateCustomForm was changed in the previous version, but its documentation was not updated accordingly. This has now been corrected.
• Security improvement:
  • Added new [Files] section flag notimestamp, preventing the file from being stored with a timestamp. Use this flag to help make builds reproducible, even if you are unable to preserve timestamps on source files.
• Other minor improvements.

6.6.0 (2025-11-11)

Setup and Uninstall now both support dark mode, forced or automatic. Custom styles are also supported.

This new feature does not increase the size of Setup if not used and is fully backward compatible.

• Enhanced [Setup] section directive WizardStyle with new appearance modes:
  • Added appearance modes: light (default, forced light mode, same appearance as previous versions), dark (forced dark mode, new appearance), and dynamic (automatically follows Windows system settings).
  • For example, to use the modern look and automatically switch between light and dark appearance based on the user's Windows system settings:

    WizardStyle=modern dynamic

  • Dark mode automatically replaces icons, wizard images, and colors while maintaining a consistent user experience. It still allows a custom main icon, and custom images and colors. Includes support for styled task dialogs.
    Example screenshot of Setup using the built-in dark style, at 150% DPI.
    Example screenshot of a task dialog using the built-in dark style, at 125% DPI.
    Includes full right-to-left support.
  • See the updated WizardStyle help topic for more information, special considerations, and example screenshots.
• Added four new DynamicDark directives to the [Setup] section, for specifying separate custom images and colors used specifically when dynamic mode switches to dark appearance:
  • For example, to specify two custom colors, one for light mode and one for dark mode:

    WizardStyle=modern dynamic
    WizardImageBackColor=white
    WizardImageBackColorDynamicDark=#2b2b2b

    Note: Forced dark mode (dark) does not use the DynamicDark settings; it uses the standard settings. Example:

    WizardStyle=modern dark
    WizardImageBackColor=#2b2b2b

• The default style can be customized by specifying a VCL Styles file using the new WizardStyleFile directive and a fifth DynamicDark directive:
  • For example, to specify two custom styles, one for light mode and one for dark mode:

    WizardStyle=modern dynamic
    WizardStyleFile=MyStyleLight.vsf
    WizardStyleFileDynamicDark=MyStyleDark.vsf

    Example screenshot of Setup using the Polar Light style, at 150% DPI.
    Example screenshot of Setup using the Polar Dark style, at 150% DPI.
    Example screenshot of a task dialog using the Zircon style, at 125% DPI.
  • When a custom style (including the built-in custom dark style) is active, all text labels, except for the label associated with the BeveledLabel message, are transparent rather than opaque.
  • The Polar style shown above is available built-in and directly supported by the WizardStyle directive. For example:

    WizardStyle=modern dynamic polar

  • Three more custom styles are available built-in and directly supported by the WizardStyle directive: slate, windows11 and zircon. slate uses medium gray for both the light and dark appearances, windows11 enables a light counterpart of the built-in dark style, and zircon is an alternative light-only style with cyan accents, shown above. For example:

    WizardStyle=modern zircon

  • Also supported is an includetitlebar modifier: Enables custom styling of both title bars and borders. By default, the system's native light or dark title bar is used instead. For example:

    WizardStyle=modern dynamic polar includetitlebar

  • Also supported is an excludelightbuttons modifier: Disables custom styling of all buttons (including command link buttons, as used in task dialogs) when a light style is active. For example:

    WizardStyle=modern dynamic windows11 excludelightbuttons

• Custom styles (including the built-in custom dark style) are not activated when the user's system is set to a high-contrast theme or when new command line parameter '/NOSTYLE' is used.
• Compiler IDE: Added a new Wizard Style page to the New Script Wizard, allowing to choose a style and view example screenshots.
• Pascal Scripting:
  • Added new support functions IsWinDark and IsDarkInstallMode.
  • Added new StyleElements and StyleName properties to support class TControl. See CodeClasses.iss for an example, which also demonstrates the use of IsDarkInstallMode.

The default look and feel of Setup and Uninstall has been further modernized by switching to the Segoe UI font, along with other improvements.

• Setup now always uses high-quality, system-defined icons instead of custom ones on the Select Destination Location and Preparing to Install wizard pages, and on the Setup Needs the Next Disk form.
• [Setup] section directive WizardSizePercent now always defaults to 120,120, instead of only when you are using WizardStyle=modern. As a result, if you are using WizardStyle=classic, your Setup windows will increase in size by 20% by default.
• [Setup] section directive WizardSizePercent is now supported by Uninstall. As a result, your uninstaller window will increase in size by 20% by default.
• Setup and Uninstall now keep the original aspect ratio of their windows when scaling for DPI. As a result, your Setup and Uninstall windows will by default be 16% wider at 125% DPI or higher.
  Can be disabled by setting new [Setup] section directive WizardKeepAspectRatio to no.
• Support for [Setup] section directive WizardResizable has been dropped, so the user will no longer be able to resize the main Setup wizard window.
• The default regular font used by Setup and Uninstall has been changed from 8-point Tahoma to 9-point Segoe UI, for a more modern appearance.
  To use 8-point Tahoma again, use:

  [LangOptions]
  DialogFontName=Tahoma
  DialogFontSize=8
  DialogFontBaseScaleHeight=13
  DialogFontBaseScaleWidth=6

  If you were already using 9-point Segoe UI, you will notice a change in scaling when you update. To use your previous scaling, use:

  [LangOptions]
  DialogFontName=Segoe UI
  DialogFontSize=9
  DialogFontBaseScaleHeight=13
  DialogFontBaseScaleWidth=6

• The default large font used by Setup on the Welcome and Setup Completed wizard pages has been changed from 12-point Verdana to 14-point Segoe UI, for a more modern appearance.
  To use 12-point Verdana again, use:

  [LangOptions]
  WelcomeFontName=Verdana
  WelcomeFontSize=12

• Pascal Scripting:
  • Added support functions InitializeBitmapButtonFromStockIcon and InitializeBitmapImageFromStockIcon. Can be used to display various high-quality, system-defined icons, on all versions of Windows.
    See CodeClasses.iss for an example, and Microsoft Learn for an overview of all available icons.
    Example screenshot of the new CodeClasses.iss example, at 125% DPI and in dark mode.
  • Wizard form sizing for WizardSizePercent is now done before event function InitializeWizard is called, instead of after, consistent with scaling for system DPI or for a custom DialogFontSize.
    If you have custom controls that must grow with WizardSizePercent, and those controls use the Anchors property to achieve this (that is, they have both akLeft and akRight set, or both akTop and akBottom set), and they do not use SurfaceWidth or SurfaceHeight, you must either start using the new SurfaceExtraWidth and SurfaceExtraHeight properties (as demonstrated by the updated CodeClasses.iss example script), or switch to using SurfaceWidth and SurfaceHeight.
    Existing custom code that assigns the Anchors property can be removed from your scripts.
  • The prototype of support function CreateCustomForm has changed. Support class TSetupForm has changed as well: function FlipSizeAndCenterIfNeeded has been renamed to FlipAndCenterIfNeeded, property SizeAndCenterOnShow has been renamed to CenterOnShow, and property KeepSizeX is now read-only. See CodeClasses.iss for an updated CreateCustomForm/TSetupForm example.

Updating is recommended, even if you don't plan to use the other enhancements right away. We continually add extra checks to make your installers safer and more reliable. In this version:

• In temporary directory/file names, the number of random base-36 digits has been doubled from 5 to 10, and the digits are now generated using a CSPRNG function (BCryptGenRandom). This is intended to provide defense against an attack that might depend on the generated names being predictable.
• Uninstall now uses a random name for its temporary directory (is-XXXXXXXXXX-uninstall.tmp), instead of attempting to re-use a fixed name whenever possible (usually iu-14D2N.tmp in previous versions). This is primarily intended to add defense-in-depth. Additionally, this change addresses a non-security issue in previous versions — extremely unlikely to be seen in practice — where if two uninstallers were started near-simultaneously, one could potentially overwrite the other's temporary file.
• In previous versions, before Uninstall deleted a pre-existing temporary directory (usually named iu-14D2N.tmp), it checked for the FILE_ATTRIBUTE_REPARSE_POINT attribute to ensure it wasn't following a junction or symbolic link. However, this check had a TOCTOU problem — it was theoretically possible for the directory to be changed into a junction or symbolic link between the check and the deletion. We are not aware of any way to practically exploit the race condition, and this issue is only potentially relevant when other, untrusted users have write access to the temporary directory, which is not common. (Before Inno Setup 6.5, when Setup/Uninstall ran under the SYSTEM account, the world-writable C:\Windows\Temp directory was often used, but beginning in Inno Setup 6.5, C:\Windows\SystemTemp is used instead on Windows 11 and up-to-date Windows 10 systems.)

• Compiler IDE:
  • Improved the contrast ratio for various syntax highlighting colors, particularly in dark mode.
  • Updated the default dialog font from 8-point Segoe UI to 9-point Segoe UI.
  • Enabled dark mode support for the menus on Windows 11 Version 25H2 (2025 Update).
• [Setup] section directive WizardImageBackColor and the other three BackColor directives now accept the #rrggbb color format in addition to $bbggrr.
• Setup command line parameter '/SUPPRESSMSGBOXES' can now suppress additional early fatal error messages and the final restart error message. The parameter still only has an effect when combined with '/SILENT' or '/VERYSILENT'.
• Pascal Scripting:
  • Added support for command link buttons (the button style used in task dialogs). See CodeClasses.iss for an example.
  • Added support functions Round, Trunc, Int, and MulDiv.
  • Added support function StrToColor.
  • Undid the change made to the CurPageChanged event function in version 6.5.0.
• If Windows returns a temporary directory that does not exist, Setup and Uninstall will now recreate it, but only if they detect the specific scenario described in the linked article. Starting with version 6.5.0, Setup and Uninstall could not run in this scenario. Prior to version 6.5.0, they would select a different temporary directory, which was also undesirable.
• Minor improvements and fixes.

6.5.4 (2025-09-24)

• Fix: Pascal Scripting: Using event function CurInstallProgressChanged would result in runtime errors.

Using Inno Setup commercially? Please purchase a license.

6.5.3 (2025-09-11)

• Fix: Compiler IDE: The New Script Wizard would generate [Files] section entries with random values for the ExternalSize parameter.

6.5.2 (2025-09-10)

It's now possible to use .png files in Setup and Uninstall, and use of transparency has been increased.

• Added support for .png files to [Setup] section directives WizardImageFile and WizardSmallImageFile.
• Improved support for stretching 32-bit .bmp files with transparency.
• The built-in wizard images and icons now have transparent backgrounds, allowing their background colors to be customized again using Setup section directives WizardImageBackColor and WizardSmallImageBackColor, which are no longer obsolete.
  The default values of these directives match previously used colors, so the appearance of all images and icons remains unchanged by default.
• Pascal Scripting:
  • Added new TPngImage support class.
  • Added new PngImage property to support classes TBitmapButton and TBitmapImage.

The size limit of 2 GB for a single Setup.exe and for disk slices has been removed.

• The maximum size for a single Setup.exe without disk spanning has increased from almost 2 GB to nearly 4 GB, which is near the maximum Windows supports.
  However, disk spanning is still recommended for large executables due to slow startup times imposed by Windows, especially when the executables are digitally signed.
• With disk spanning enabled, the maximum disk slice size has been increased from almost 2 GB to effectively unlimited (9223 PB).
  The default disk slice size is still 2100000000, which is almost 2 GB. To update, you can simply set [Setup] section directive DiskSliceSize to max.

• All download functionality now supports TLS 1.3 when available. Support for TLS 1.0 and 1.1 has been removed on all versions of Windows.
• Archive extraction now supports the RAR5 format. Requires Setup section directive ArchiveExtraction to be set to full.
• Compiler IDE: The New Script Wizard and the Generate [Files] Entries tool now support adding files to be downloaded. They will prompt you if the downloaded file is an archive that should be extracted.
• Fix: Using [Files] section flags download and extractarchive on an entry that also has a Tasks parameter now works as expected.

• Compiler IDE:
  • Added new Automatically reload files and Allow Undo after reload options. Both are enabled by default, consistent with most other modern editors, and improving integration with tools like Claude Code.
  • Added dark mode support for command line options /cc and /wizard.
• Pascal Scripting: Added new HighContrastActive and LogFmt support functions.
• Minor tweaks and fixes.

6.5.1 (2025-08-18)

• Downloads are now performed from a secondary thread, just as was first introduced for archive extraction in the previous version. This ensures Setup stays responsive, even if the system fails to report progress.
• Fix: Using the /cc command line option of the Compiler IDE to compile a script no longer causes an error.
• Minor tweaks.

6.5.0 (2025-08-12)

Over the years, a number of users have expressed to us a desire to see their organizations support the ongoing development of Inno Setup, but have found that organization policies often make it difficult or impossible to approve a donation. By introducing a commercial license option, we aim to provide a straightforward and familiar way for organizations to contribute to the project's sustainability.

Additionally, many organizations prefer having official licenses on record for all software they use, as it helps with audits and internal compliance checks.

Finally, your support through license purchases directly enables us to improve and maintain Inno Setup.

For these reasons we are introducing commercial licenses. If you or your organization benefit from using Inno Setup in a commercial context, we kindly ask that you purchase a license. Thank you for helping ensure the continued development of this software.

Licenses can be purchased from our new order page, which includes more questions and answers. All commercial licenses are perpetual and require a single payment. They include two years of updates, major and minor. After this period, your current version will remain licensed and functional as-is.

It's now possible to extract password-protected archives, multi-volume archives, and multiple extra archive formats such as .zip.

Additionally, the [Files] section now supports archive extraction. Writing Pascal Script to extract an archive is no longer necessary.

All of this is optional and does not increase the size of Setup if not used.

• Updated [Setup] and [Files] section:
  • Added new [Setup] section directive ArchiveExtraction to specify the method of archive extraction used by new [Files] section flag extractarchive (see below) and support functions ExtractArchive and CreateExtractionPage:
    • basic (default) is the method introduced by Inno Setup 6.4.0. It only supports .7z archives that are not password-protected.
    • enhanced/nopassword is a new method and internally uses 7zxr.dll from the 7-Zip source code by Igor Pavlov, as-is, except that it was recompiled, code-signed, and renamed to is7zxr.dll. Compared to basic, it has lower memory requirements for archives that contain large files but increases the size of the Setup file(s). It still only supports .7z archives that are not password-protected.
    • enhanced uses 7zxa.dll instead of 7zxr.dll, recompiled, code-signed, and renamed to is7zxa.dll. It still only supports .7z archives, but they may be password-protected.
    • full uses 7z.dll instead of 7zxa.dll, recompiled, code-signed, and renamed to is7z.dll. It supports multiple archive formats (.7z, .zip, .rar, and more), although not as many as the original 7z.dll, to reduce its size. Additionally, it supports multi-volume archives.
    New documentation topic ArchiveExtraction has a table summarizing the differences between these methods.
  • Added new [Files] section flag extractarchive and parameter ExtractArchivePassword, intended to enable the seamless integration and extraction of archives.
    • The supported archive formats, beyond .7z, and the support for password-protected and multi-volume archives, depend on the aforementioned ArchiveExtraction directive, that must not be set to basic.
    • Flag extractarchive must be combined with the external and ignoreversion flags. It is usually also combined with the recursesubdirs and createallsubdirs flags.
    • Using a solid archive is not recommended; extraction performance may degrade depending on the solid block size.
    • Archive extraction otherwise behaves the same as external file copying. For example, it supports automatic uninstallation of extracted files and can be combined with same other flags and parameters.
    • Example script:

      [Setup]
      ArchiveExtraction=enhanced/nopassword
      
      [Files]
      Source: "{tmp}\MyProg-ExtraReadmes.7z"; DestDir: "{app}"; \
        Flags: external extractarchive recursesubdirs createallsubdirs ignoreversion

  • Archive extraction now honors the file system redirection state set by 64-bit install mode, entry flags, and support function EnableFsRedirection.
• Updated Pascal Scripting:
  • New support function ExtractArchive replaces the deprecated Extract7ZipArchive. ExtractArchive includes an additional parameter to optionally specify a password.
  • ExtractArchive and CreateExtractionPage now overwrite read-only files which already exist in the destination directory without prompting the user. Previously this would cause an extraction error.
  • Added new MapArchiveExtensions support function to allow the extraction of archives with custom extensions, such as self-extracting archives.
  • Added new AddEx function to support class TExtractionWizardPage to add password-protected archives.

The [Files] section now supports file downloads. Writing Pascal Script to download a file is no longer necessary and is in fact less efficient since it requires an intermediate temporary file which this new download support doesn't.

• Updated [Files] section:
  • Added new [Files] section flag download and parameters DownloadUserName and DownloadPassword, intended to enable the seamless integration of downloaded files.
  • Supports HTTPS (but not expired or self-signed certificates) and HTTP. Redirects are automatically followed and proxy settings are automatically used. Safe to use from services.
  • Flag download must be combined with the external and ignoreversion flags. Additionally, the DestName and ExternalSize parameters must be set.
    It can also be combined with the new issigverify flag (see below) for efficient and highly secure verification of the download file.
    It cannot be combined with the comparetimestamp, recursesubdirs and skipifsourcedoesntexist flags.
  • File download otherwise behaves the same as external file copying. For example, it supports automatic uninstallation of downloaded files and can be combined with same other flags and parameters.
  • When combined with the new extractarchive flag (see above), the archive will be downloaded and, if the issigverify flag is also used, verified at the start of the Preparing to Install step. The archive is then extracted normally during the actual installation process.
    In this case, the value of DestName is used to determine the archive format and for display and logging purposes.
  • Example script:

    [Files]
    Source: "https://jrsoftware.org/download.php/is.exe?dontcount=1"; \
      DestName: "innosetup-latest.exe"; DestDir: "{app}"; \
      ExternalSize: 7_000_000; Flags: external download ignoreversion
    Source: "https://jrsoftware.org/download.php/myprog-extrareadmes.7z"; \
      DestName: "MyProg.ExtraReadmes.7z"; DestDir: "{app}"; \
      ExternalSize: 275; Flags: external download extractarchive ignoreversion

  • Added example script DownloadFiles.iss to demonstrate how to use a single [Files] entry to download a file, or to download and extract an archive, with verification.

Inno Setup now includes an integrated signature-verification capability that can be used to detect corruption or tampering in your files at compile time, before files are included in an installer being built, or during installation, before Setup copies external files onto a user's system.

Any type of file may be signed and verified, and creation of signatures does not require a certificate from a certificate authority. There is no cost involved.

Note, however, that these signatures cannot be used to eliminate an "Unknown publisher" warning message shown by Windows when an installer or other EXE file is started. That requires a completely different kind of signature (Authenticode) embedded inside the EXE file by a different tool (Microsoft's signtool.exe), and it does require a (usually expensive) code-signing certificate from a certificate authority.

A more detailed summary:

• New [ISSigKeys] section:
  • Added a new optional [ISSigKeys] section for defining keys used by the compiler and Setup to verify file signatures.
  • Supports parameters Name (required) and Group to identify keys, parameters KeyFile, PublicX, and PublicY to specify the key values, parameter KeyID to double-check the key values, and parameter RuntimeID for runtime identification of the key.
  • Key files are human-readable and can be created using Inno Setup Signature Tool (see below).
  • Example section:

    [ISSigKeys]
    Name: anna; KeyFile: "anna.ispublickey"; Group: exesigner
    Name: ryan; KeyFile: "ryan.ispublickey"; Group: exesigner
    Name: ivan; KeyFile: "ivan.ispublickey"; Group: docsigner
    ; max is trusted for both exe and doc signing
    Name: max; KeyFile: "max.ispublickey"; Group: exesigner docsigner
    ; the boss also has a key
    Name: bosskey; KeyFile: "boss.ispublickey"

• Updated [Files] section:
  • Added a new issigverify flag for enforcing cryptographic signature verification of source files using a key from the [ISSigKeys] section, enhancing security during both compilation and installation.
  • When used without the external flag, verification is performed during compilation, aborting if it fails. When used with the external flag, verification occurs during installation, ensuring the integrity of files as they are copied.
  • Requires an .issig signature file to be present in the same directory as the source file. Signature files are human-readable files and can be created using the Inno Setup Signature Tool.
  • Has little performance impact since verification occurs while source files are being compressed/copied and each file's contents are only read once; the only extra I/O comes from reading the tiny .issig files. Only archives and downloaded files are read a second time.
  • The verification process is protected against the Time-Of-Check to Time-Of-Use (TOCTOU) problem.
  • Can be used to verify downloaded files, offering flexibility over SHA-256 checks as script changes aren't needed for file updates. See the new DownloadFiles.iss example script for an example.
  • Added a new and optional ISSigAllowedKeys parameter to restrict which keys or groups of keys from the [ISSigKeys] section are permitted for signature verification using the issigverify flag.
  • Note: The issigverify flag cannot be combined with the sign or signonce flags. Use signcheck instead.
  • Example section:

    [Files]
    Source: "MyProg.exe"; DestDir: "{app}"; \
      ISSigAllowedKeys: "exesigner bosskey"; Flags: issigverify 
    Source: "MyProg.chm"; DestDir: "{app}"; \
      ISSigAllowedKeys: "docsigner bosskey"; Flags: issigverify
    Source: "{src}\Extra\*.chm"; DestDir: "{app}"; \
      ISSigAllowedKeys: "docsigner bosskey"; Flags: issigverify external; \
      Excludes: "*.issig"
    Source: "https://jrsoftware.org/download.php/is.exe?dontcount=1"; DestDir: "{app}"; \
      ISSigAllowedKeys: "exesigner bosskey"; \
      Flags: issigverify external download ignoreversion; \
      DestName: "innosetup-latest.exe"; ExternalSize: 7_000_000

• New Inno Setup Signature Tool:
  • Added ISSigTool.exe, a new command-line utility designed to sign files using ECDSA P-256 cryptographic signatures.
  • Offers commands to sign and verify files, to export public keys and to generate private keys.
  • Example commands:

    issigtool --key-file="MyKey.isprivatekey" generate-private-key
    issigtool --key-file="MyKey.isprivatekey" sign "MyProg.dll"
    issigtool --key-file="MyKey.isprivatekey" export-public-key "MyKey.ispublickey"
    issigtool --key-file="MyKey.ispublickey" verify "MyProg.dll"

• Updated documentation:
  • Added new [ISSigKeys] section topic.
  • Updated [Files] section topic.
  • Added new .issig Signatures: Introduction topic.
  • Added new Inno Setup Signature Tool topic.
• Other related changes:
  • The compiler now verifies additional precompiled files, such as Setup.e32 and SetupLdr.e32, to ensure they remain unchanged before using them. Can be disabled using new [Setup] section directive DisablePrecompiledFileVerifications, though doing so is not recommended.
  • Added new [Files] section parameter Hash. Instructs the compiler or Setup to do a simple SHA-256 hash check instead of a full signature verification, as an alternative to using the issigverify flag.
    Example script:

    [Files]
    Source: "https://jrsoftware.org/download.php/iscrypt.dll?dontcount=1"; \
      DestName: "ISCrypt.dll"; DestDir: "{app}"; \
      Hash: "2f6294f9aa09f59a574b5dcd33be54e16b39377984f3d5658cda44950fa0f8fc"; \
      ExternalSize: 2560; Flags: external download ignoreversion

  • Pascal Scripting:
    • Added new ISSigVerify and DownloadTemporaryFileWithISSigVerify support functions.
    • Added new AddWithISSigVerify and AddExWithISSigVerify functions to support class TDownloadWizardPage. See updated example script CodeDownloadFiles.iss for an example.

• Compiler IDE:
  • The Find in Files result list will now update its line numbers when you add or delete lines.
  • The Highlight occurrences of current word option (which is disabled by default) no longer highlights a section's directive names, parameter names, or Pascal keywords. The Highlight occurrences of current selection option (which is enabled by default) still does.
  • Dark mode is now supported throughout.
  • Improved support for high-contrast themes.
  • Improved support for screen readers.
• [Setup] section directive Encryption can now be set to full, which will encrypt the entire installation and requires the password to be specified using the /PASSWORD= command line parameter.
• Increased the maximum value of [Setup] section directive LZMANumBlockThreads from 32 to 256.
• [Files] section parameter Excludes can now be combined with the external flag.
• Parameters ExternalSize, ExtraDiskSpaceRequired, and UninstallDisplaySize now support digit separators. Example: UninstallDisplaySize=1_073_741_824.
• ISPP changes:
  • Added predefined variable __DIR__. Returns the directory of the current include file.
  • Renamed predefined variables __FILE__ to __FILENAME__ and ISPPCC_INVOKED to ISCC_INVOKED. The old names still work.
  • Renamed support function RemoveBackslash to RemoveBackslashUnlessRoot. The old name still works.
  • Fix: The return value of support function ExtractFilePath did not always include a trailing backslash as intended.
• Pascal Scripting changes:
  • Added new TBitmapButton support class which works just like TBitmapImage, but is accessible by keyboard and compatible with screen readers. Make sure to set the Caption property, even if it isn't visible. See updated example script CodeClasses.iss for an example.
  • Added new InitializeBitmapButtonFromIcon and GetSHA256OfStream support functions.
  • Added new LastBaseNameOrUrl property to support class TDownloadWizardPage. See updated example script CodeDownloadFiles.iss for an example.
  • Fix: Event function CurPageChanged is now always only triggered when the current page actually changes. Before it was called twice in a row for wpPreparing when the script had a PrepareToInstall event function which returned a non empty string to instruct Setup to stop.
• When available, Setup now retrieves the temporary directory path using the GetTempPath2 API, which was first introduced in Windows 11 and later backported to Windows 10 and Windows Server 2016 via monthly updates. When running under the SYSTEM account, GetTempPath2 returns a private directory (typically C:\Windows\SystemTemp), potentially enhancing security. On older versions of Windows or systems that haven't been updated, Setup falls back to the original GetTempPath API. (This change adds defense-in-depth; it does not address a known vulnerability.)
• Inno Setup 6.4.3 increased the maximum width of all task dialogs by about 50%, which helps to keep long paths from being truncated with ellipses. It now only does this if the task dialog's content actually contains a path.
• All official translations which still had an UTF-8 BOM had their BOM removed. Using a BOM in UTF-8 encoded files is not needed and not recommended since Inno Setup 6.3.0.
• Inno Setup is now built using Delphi 12.3 Athens instead of Delphi 12.1 Athens. Thanks to Ian Barker from Embarcadero for providing us with a license!
• Documentation improvements.
• Minor tweaks.

Some messages have been added and removed in this version: (View differences in Default.isl.)

• New messages:
  • DownloadingLabel2, ExtractingLabel.
  • ArchiveIncorrectPassword, ArchiveIsCorrupted, ArchiveUnsupportedFormat.
  • RetryCancelSelectAction, RetryCancelRetry, RetryCancelCancel.
  • StatusDownloadFiles.
  • SourceVerificationFailed, VerificationSignatureDoesntExist, VerificationSignatureInvalid, VerificationKeyNotFound, VerificationFileNameIncorrect, VerificationFileTagIncorrect, VerificationFileSizeIncorrect, VerificationFileHashIncorrect.
  • ErrorDownloading, ErrorExtracting.
• Removed messages:
  • ErrorFileHash1, ErrorFileHash2.
  • DownloadingLabel, ExtractionLabel.

Note: The official Icelandic translation has been reclassified as unofficial due to the absence of a maintainer.

6.4.3 (2025-05-03)

• Compiler IDE change: The editor now restores selections on undo and redo.
• Inno Setup now includes a new command-line tool, ISSigTool.exe. This tool is designed to sign files using ECDSA P-256 cryptographic signatures. Compil32, ISCC, and ISCmplr use these signatures to verify a number of DLL files before loading them. This is a "technology preview" that is subject to change (e.g., any signatures you create now may have to be recreated when upgrading to the next version).
  Note: ISSigTool.exe does not replace Microsoft's signtool.exe in any way and is in fact not related to Authenticode Code Signing at all.
• Fix: Autocomplete support for parameter names in the [Components] and [Dirs] sections was broken since 6.1.1.
• Fix: Pascal Scripting support function Extract7ZipArchive which was introduced by 6.4.0 would fail with error 11 on older versions of Windows, at least Windows 8.1 and Windows Server 2016.
• The maximum width of all task dialogs was increased by about 50%, which helps to keep long paths from being truncated with ellipses. This was done by setting Windows' TDF_SIZE_TO_CONTENT flag.
• Minor tweaks and documentation improvements.

6.4.2 (2025-03-12)

• Added [Setup] section directive CloseApplicationsFilterExcludes.
• Inno Setup is now built using Delphi 12.1 Athens instead of Delphi 11.3 Alexandria.
• Inno Setup is now signed using a new code signing certificate.

6.4.1 (2025-02-12)

Compiler IDE changes

• Added mouseover tooltips for all Pascal Scripting support functions and class members showing their prototype. Always shows all classes' members instead of just those of the current object's class.
• Autocompletion lists now use the same font as the editor.
• Fix: When the IDE was started for the first time on a system with a DPI setting over 100%, the editor's initial font size was larger than expected.

Other changes

• {reg:...} constants can now also embed REG_DWORD-type registry values.
• Fix: In 6.4.0, using "Shift+" in a HotKey parameter in the [Icons] section didn't work and required "Shift" instead, so for example "Ctrl+ShiftM" instead of "Ctrl+Shift+M".
• Fix: In 6.4.0, a custom form shown using [Code] didn't have a taskbar button if Setup's wizard was not visible at the time.
• Added official Arabic translation.
• Some minor tweaks and improvements.

6.4.0 (2025-01-09)

Compiler IDE changes

Updated the Scintilla editor component used by the Compiler IDE to the latest version.

Multiple selection editing has been improved:

• Added new Add Next Occurrence menu item to the Edit menu to add the next occurrence of the current word or selected text as an additional selection (Shift+Alt+. or Ctrl+D, see below).
• Added new Select All Occurrences menu item to the Edit menu to select all occurrences of the current word or selected text (Shift+Alt+; or Ctrl+Shift+L).
• Added new Select All Find Matches menu item to the Edit menu to select all matches of the last find text (Alt+Enter).
  Additionally, the Find (Ctrl+F) and Replace (Ctrl+H) dialogs now both support being closed by Alt+Enter to directly select all matches.
• Added shortcuts to add a cursor or selection up or down (Ctrl+Alt+Up and Ctrl+Alt+Down). For multi-line selections this extends the selection up or down and never shrinks.
• Added shortcut to add cursors to line ends (Shift+Alt+I). Behaves the same as in Visual Studio Code, so for example does nothing if all selections are empty.
• Added shortcuts to add a word or line as an additional selection (Ctrl+Double Click and Ctrl+Triple Click or Alt+Double Click and Alt+Triple Click).
• Added shortcut to remove a selection by clicking it (Ctrl+Click or Alt+Click).
• Multiple selection now works over Left, Right, Up, Down, Home and End navigation and selection commands.
• Multiple selection now works over word and line deletion commands, and line end insertion.
• Multiple selection now works better with Copy and Paste commands.
• Left, Right, etc. navigation with rectangular selection is now allowed.
• The Find and Replace dialogs and the tools from the Tools menu which generate script text now all work better with multiple selections present.

Other editor changes:

• Added support for Visual Studio Code-style editor shortcuts, like Ctrl+D to Add Next Occurrence, Ctrl+Shift+K to delete a line and Alt+Click to add an additional cursor or remove a selection.
  To activate this use the Options menu item in the Tools menu to set the new Keys option in the Editor group to Visual Studio Code.
  The updated Compiler IDE Keyboard And Mouse Commands help topic lists all differences with the classic keyboard and mouse shortcuts.
• Only if Visual Studio Code-style editor shortcuts have been activated: Added shortcuts to copy line down (Shift+Alt+Down) and to indent or unindent lines (Ctrl+] and Ctrl+[).
• Added parameter hints for all Pascal Scripting support functions for quick reference to the function's parameter names, types, and order. Parameter hints can be invoked manually by pressing Ctrl+Shift+Space or automatically by using the new Invoke parameter hints automatically option which is enabled by default.
• Added autocompletion support for all Pascal Scripting support functions, types, constants, etcetera. Existing option Invoke autocompletion automatically controls whether the autocompletion suggestions appear automatically or only when invoked manually by pressing Ctrl+Space or Ctrl+I.
• Added parameter hints and autocompletion support for all Pascal Scripting support class members and properties. Both always show all classes' members and properties instead of just those of the current object's class.
• Added autocompletion support for all Pascal Scripting event function parameters. Always shows all parameters instead of just those of the current event function.
• Added autocompletion support for the [Messages] section.
• Improved autocompletion support for all Flags parameters: now works for multiple flags instead of for the first only.
• Added new Enable section folding option which allows you to temporarily hide sections while editing by clicking the new minus or plus icons in the editor's gutter or by using the new keyboard shortcuts (Ctrl+Shift+[ to fold and Ctrl+Shift+] to unfold) or menu items. Enabled by default.
• The editor's gutter now shows change history to keep track of saved and unsaved modifications. Always enabled.
• The editor's font now defaults to Consolas if available, consistent with most other modern editors.
• The editor can now be scrolled horizontally instead of vertically by holding the Shift key while rotating the mouse wheel. Horizontal scroll wheels are now also supported.
• Cut (Ctrl+X or Shift+Delete) and Copy (Ctrl+C or Ctrl+Insert) now cut or copy the entire line if there's no selection, consistent with most other modern editors.
• Added new shortcuts to move selected lines up or down (Alt+Up and Alt+Down).
• Added new shortcut and menu item to the Edit menu to toggle line comment (Ctrl+/).
• Added new shortcut and menu item to the Edit menu to go to matching brace (Ctrl+Shift+\).
• Moved the Word Wrap option to the View menu and added a shortcut for it (Alt+Z).
• Added a right-click popup menu to the editor's gutter column for breakpoints.
• Added dark mode support to autocompletion lists and also added a minimum width.
• Added new Show whitespace option. Disabled by default.
• Improved brace highlighting.
• Fixed an issue when the Auto indent mode and Allow cursor to move beyond end of lines options are both enabled.

Other Compiler IDE changes:

• Shortcuts Alt+Left and Alt+Right now always navigate back and forward even if Visual Studio-style menu shortcuts have been activated.
  Because of this Alt+Right can no longer be used to initiate auto complete, instead the existing Ctrl+Space or Ctrl+I alternatives must be used.
• Moved the list of recently opened files into a new Open Recent submenu of the Files menu.
• Added new Use Regular Expressions option to the Edit menu to enable or disable the use of regular expressions for all find and replace operations and added a shortcut for it (Ctrl+Alt+R or Alt+R). Also added a small panel to the statusbar to indicate the current state.
• The Find and Replace dialogs now support using Shift+Enter to temporarily search in the opposite direction.
• Added shortcuts to select a tab (Ctrl+1 through Ctrl+9).
• Added alternative shortcut for the Compile menu item in the Build menu (Shift+F9 or F7).
• Added shortcut to the Options menu item in the Tools menu (Ctrl+,).
• Removed the length limitation when entering a Sign Tool command and increased control height.
• Added a banner which is displayed to each user after each update and links to this revision history.
• Enabled dark mode support for the menus on Windows 11 Version 24H2 (2024 Update).

Other changes

• Updated the LZMA SDK used by Inno Setup to the latest version, increasing the speed of LZMA and LZMA2 compression (by 10% in a test with default settings) without changing the compression ratio. Compression memory requirements have increased by about 4%. This also made it possible to add support for extracting 7-Zip archives, see below.
• Updated the encryption algorithm and key derivation function used by Inno Setup to XChaCha20 and PBKDF2-HMAC-SHA256 respectively, increasing security. This code is built-in: the separate ISCrypt.dll "encryption module" is no longer used and will be automatically deleted when you update.
• Added [Setup] section directive EncryptionKeyDerivation to change the number of PBKDF2-HMAC-SHA256 iterations to use from the default of 200000 to another value.
• Replaced all remaining use of MD5 and SHA-1 hashes with SHA-256 hashes, without removing the MD5 and SHA-1 Pascal Scripting and ISPP support functions.
• At long last, Setup's wizard window now shows a thumbnail image on its taskbar button, and animates correctly when minimized and restored. As part of this work, support for the long-deprecated [Setup] section directive WindowVisible, which was used to enable a 1990s-style blue gradient background behind the wizard window, has been dropped. For the same reason Pascal Scripting support object MainForm has been removed.
• The aspect ratio of Setup's large and small wizard images (as specified by WizardImageFile and WizardSmallImageFile) is now maintained when the window is scaled. Previously, depending on the font and font size used, they could have appeared horizontally stretched or squished.
• The size of the small wizard image area has been extended to 58×58 (at standard DPI with the default font). Previous versions used a non-square 55×58 size, which made the default image look slightly stretched.
• When disk spanning is enabled and Setup cannot find the needed disk slice file (e.g., setup-2.bin) in the source directory, it no longer automatically searches for it in a directory named DISKx one level up, where x is the disk number. Though consistent with old installers from the 16-bit era, this behavior wasn't documented.
• The New Script Wizard now sets UninstallDisplayIcon when an .exe is chosen as the main executable file.
• Merged the Inno Setup Preprocessor documentation into the main documentation instead of being separate.
• Added a dark mode version of the documentation, automatically used by the Compiler IDE if a dark theme is chosen.
• Pascal Scripting changes:
  • Added new Extract7ZipArchive support function to extract a 7-Zip archive, based on the "7z ANSI-C Decoder" from the LZMA SDK by Igor Pavlov. See the new help topic for information about its limitations.
    Added new CreateExtractionPage support function to easily show the extraction progress to the user.
  • Added new ExecAndCaptureOutput support function to execute a program or batch file and capture its stdout and stderr outputs separately.
  • Added new StringJoin, StringSplit, and StringSplitEx support functions.
  • Output logging now raises an exception if there was an error setting up output redirection (which should be very rare). The PowerShell.iss example script has been updated to catch the exception.
  • Added new NewFolderName property to support class TInputDirWizardPage update the initial value passed to CreateInputDirPage.
  • Added new PopupMode and PopupParent properties to support class TForm.
  • Documented support functions VarArrayGet and VarArraySet which were already available but not documented.
  • Renamed the FileCopy support function to CopyFile. The old name is still supported, but it is recommended to update your scripts to the new name and the compiler will issue a warning if you don't.
  • Fixed support function TStream.CopyFrom by adding a BufferSize parameter which was required but missing. Using $100000 as the value is recommended.
  • Condensed the logging of DLL function imports.
  • Added new Debugging support function.
• ISPP change: Added support functions GetSHA256OfFile, GetSHA256OfString, and GetSHA256OfUnicodeString.
• Inno Setup's Delphi source code has been reorganized to use unit scope names and additionally various units have been renamed for clarity. 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.
• Added official Swedish and Tamil translations.
• Various tweaks and improvements.

Contributions via GitHub: Thanks to Sergii Leonov, John Stevenson, and jogo- for their contributions!

Thanks to Neil Hodgson and Igor Pavlov for their continued work on Scintilla and the LZMA SDK!

Some messages have been added and changed in this version: (View differences in Default.isl.)

• New messages:
  • ExtractionLabel, ButtonStopExtraction, StopExtraction, ErrorExtractionAborted, ErrorExtractionFailed.

Note: The official Icelandic translation has not yet been updated for these changes.

6.3.3 (2024-07-12)

• Improved support for ASLR.

6.3.2 (2024-06-28)

• Pascal Scripting change: Fixed support function TStream.Seek.

6.3.1 (2024-06-10)

• Fixed 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.