Advanced Installer 20.0 Release Notes

On October 18th, 2022 Caphyon Ltd. is proud to announce the release of Advanced Installer 20.0 in Free, Professional, Enterprise and Architect editions. This release is available for download on the Advanced Installer website.

We are pleased to announce the release of Advanced Installer 20.0, a new chapter where we commit to further strengthening our vision of application packaging technology - providing you with valuable knowledge and tools.

The new release brings the Repackager Automation & MSIX Compatibility Framework which will enable your team to convert and analyze a set of applications to MSIX automatically.

The framework will give you an overview of your application portfolio and will help you in defining your packaging and deployment strategy. You will see the status of your applications in the final report, such as how many failed packaging, failed to install or were a success.

To better understand how the Repackager Automation & MSIX Compatibility Framework works, check out the video:

New features, bug fixes, and general improvements are included in the current release. See the full list below.

New features
  • Repackager Automation & MSIX Compatibility Framework
  • Parallel downloading and installation (with progress) of prerequisites

  • Requested by customer
    Customize running location for PowerShell scripts

  • Requested by customer
    PowerShell automation support to add "PowershellScriptFile"

  • Requested by customer
    PowerShell automation support to add chained packages

  • Requested by customer
    Security improvement: protect the EXE setups from loading tampered versions of the decoder.dll file

  • Requested by customer
    Synchronize paths written in INI with APPDIR path and setup install type

  • Requested by customer
    New Installer Analytics parameter to distinguish between installs and uninstalls

  • Requested by customer
    "Run PowerShell script file" custom action now supports script parameters

  • Requested by customer
    Improved the "Select a Component" dialog
  • PowerShell custom actions are now digitally signed by default

  • Requested by customer
    "Add/SetUwpAppxPackageProperties" command line support for Windows Store App and Modification Package projects
  • Generate a new unique folder name for New, Duplicate, and Copy/Paste build operations
  • Updated package-related icons and images for a refreshed look and improved rendering on high DPI
  • Show warnings on using some Repackager options
  • Symbolic link support in MSI Editor Mode

  • Requested by customer
    Synchronize the file extension icon between MSI and MSIX build

  • Requested by customer
    New option to disable WinUI transitions

  • Requested by customer
    Improved fields validation in Repackager GUI

  • Requested by customer
    Improvements for Copy file/folder action
  • Predefined prerequisite for Python installer
  • Update MSIX platforms to Windows 11 version 22H2
  • Update .NET & .Net Core prerequisites to latest versions (6.0.10 & 3.1.30)
  • Predefined launch condition for Windows 11 version 22H2 x64 (Preview)
Bug fixes
  • File search failure when using the "Entire Project" criteria

  • Reported by customer
    The translation string cannot exceed 260 characters
  • Visual glitches between dialogs on the Surface theme

  • Reported by customer
    Custom name is still used when the "Register product with Windows Installer" option is disabled

  • Reported by customer
    PowerShell script signing fails if "ProductName" contains double quotes
  • Control conditions for the "Styled Progress" control do not work

  • Reported by customer
    The "Synchronize property's value with the value from a JSON file" option displays malfunction on high DPI resolutions
  • Invalid input error when pressing the TAB key on the Set Installer Property custom action field

  • Reported by customer
    The prerequisite's search done by custom executable doesn't work
  • The custom action from the SQL/ IIS/ Users and Groups browse gets deleted because the focus is on the custom action instead of the browse
  • On high DPI displays, the PowerShell custom action execution properties are not clearly visible