Advanced Installer 24.1 Release Notes
On October 12th, 2026 Caphyon Ltd. is proud to announce the release of Advanced Installer 24.1 in Free, Professional, Enterprise and Architect editions. This release is available for download on the Advanced Installer website.
Advanced Installer 24.1 introduces highly requested improvements, including a redesigned Custom Actions view for easier management, more flexible Azure Key Vault signing with new authentication options, and expanded PowerShell automation capabilities across multiple project areas.
It also improves the usability of generated Repackager automation scripts and provides greater flexibility when editing executable paths for Sparse Packages.
Watch the video below to see the redesigned Custom Actions view in action and learn how you can add, organize, and move custom actions more easily.
New features, bug fixes, and general improvements are included in the current release. See the full list below.
- Redesigned Custom Actions view for easier management
- Update MSIX StartUp Task
- Azure Key Vault signing improvements
Requested by customer - PowerShell automation for Dialog View
- PowerShell automation for Digital Signature in Updates project type
Requested by customer - PowerShell automation for "Store setting inside the Updater" option
Requested by customer - Added regex support to the include and exclude filters in the Synchronized Folders tab
Requested by customer - Improved notification visibility by displaying the most recent notifications first and adding timestamps
- Improved the usability of generated Repackager automation scripts
- Improved exposure of the "AiLicenseAgreementLink" property for the Serene theme in a Professional project type
Requested by customer - Support for specifying either internal and external executable paths in Sparse Packages
- Added Vietnamese dictionary
Requested by customer - Improved Repackager capture by excluding the Uninstall registry key
- Updated "ComponentName" after resource renaming (e.g. registry; folder)
- Improved name identifier for data setters
- Predefined launch conditions for Windows 11 26H2
- Updated .NET 8 prerequisites to the latest version 8.0.31
Requested by customer - Updated .NET 9 prerequisites to the latest version 9.0.20
Requested by customer - Updated .NET 10 prerequisites to the latest version 10.0.12
Requested by customer
- Setup failed when the driver's feature was set not to be installed
Reported by customer - Fixed title bar display over other windows
- Adding drivers to a mixed package led to a build crash
Reported by customer - A Main Package prerequisite was not installed when the setup was launched with /qn+
Reported by customer - The "Register product with Windows Installer" did not work on EXE packages or EUI/MSI Embedded UI
Reported by customer - Crash when clicking on a hyperlink
- The Cancel button did not stop the installation process
Reported by customer - Couldn't delete the first letter from the custom action name when editing from the middle of the name
- Adding file association to an MSIX build led to failure when parsing the package
- An error message appeared when trying to install a prerequisite using "Repair" on the main package
- /GenRegLicense command line reported "File could not be written" when custom license element value exceeded five characters
Reported by customer - The "QuestionnaireDlg" dialog couldn't be used or added to repository
Reported by customer - A formatted reference created a property with an empty name
- Updated the "SetAzureKeyVaultSecret" cmd to support the Updates project type
Reported by customer - Pressing ENTER when saving a project file opened a new project
- Button IDs differed between desktop and server when WinUI was enabled
Reported by customer - A chained prerequisite inherited the "BasicUIComLine" attribute from a previously created prerequisite
- Editing MSIX sometimes caused a silent crash
- The Search option in the Run pane was bigger than the Summary
- Registry entries from the template were removed when importing a Repackager project
- Fixed issues on the Registration details SSO dialog
- Signing a catalog file failed if its path contained the "#" character
- PowerShell automation failed to build the Updates Configuration project when the Digital Signature option was set
Reported by customer - The "Synchronize" button disappeared in Repackager
- Custom templates were duplicated after certain steps
- ConfigureDlg did not work correctly in version 24.0
Reported by customer - Crash when upgrading a project from the File Registration dialog
- Custom Templates were available even if there were no custom templates saved
- The /GenRegKeys CLI did not take the long/short parameter into consideration
- StartUp Task had no default Entry point in Windows Store project type
- Stack trace error when using the /GenerateReport command line
Reported by customer - Page Count incorrectly set to 450 for ARM64 package type setup
Reported by customer