Advanced Installer 22.3 Release Notes
On December 10th, 2024 Caphyon Ltd. is proud to announce the release of Advanced Installer 22.3 in Free, Professional, Enterprise and Architect editions. This release is available for download on the Advanced Installer website.
Advanced Installer 22.3 introduces built-in support for Windows Server 2025, enabling seamless configuration of Windows Features and Server Roles directly within your installation packages.
We’ve also updated the Prerequisites and Launch Conditions views with predefined configurations for Windows Server 2025 and .NET 9, so you can start building compatible packages immediately.
This release also introduces eight powerful enhancements, including PowerShell automation support for licensing and command-line functionality for adding .NET Core launch conditions, each designed to streamline and optimize your packaging and deployment process.
Explore the full list of what’s new, improved, and fixed below, and watch the video tutorial to see how to leverage these new capabilities for Windows Server 2025 installations.
New features, bug fixes, and general improvements are included in the current release. See the full list below.
- Windows features bundle support for Windows Server 2025
Requested by customer - Predefined launch condition for Windows Server 2025
- PowerShell automation support for licensing
Requested by customer - Command-line support for adding .NET Core launch conditions
Requested by customer - Enabling the selection of different COM registration extraction methods
Requested by customer - Configurable option to include or exclude custom actions from certain builds
- Enhanced multiline text editor with scrolling for full-text visibility
- "Terminate Process" custom action can close processes for all users when running in immediate mode
- Improved "Evaluate Condition" option, now easier to access in the Custom Launch Condition tab
- Changed default file replacement setting to "Always Overwrite Existing Files" for new projects
- Update .NET Core 8 prerequisites to version 8.0.11
- Predefined prerequisite for .NET 9
Requested by customer - Predefined Launch Conditions for .NET Core 9.0
- Fixed an issue in the "Prerequisite UI Level Switches" window where an EditBox was incorrectly displayed instead of a Static Text control
- Error notifications rendered with WinUI were not using the correct font color
- Fixed filter issues in the "Move to Component" window
Reported by customer - Crash when deleting a folder with component policy set "One component per folder"
- The UAC appeared hidden in the taskbar when the setup contained chained packages
Reported by customer - Fixed initialization issue on the Start Page
- Fixed prerequisite repair issue where incorrect file versions were not updated during the main installer repair
Reported by customer - An unexpected message box popped up during installation on Windows Server 2022
Reported by customer - The "Create a new component" option from the Synchronize folder did not work as expected
- The slideshow progress dialog was not displaying as expected in the App Installer and Serene themes
Reported by customer - Patch project is checked as modified after navigating in the Add/Remove (Control Panel) view
- Crash in a merge module project if using "Go to Location" for Property.ARPCOMMENTS localization ID
- Addressed flickering issue in Edit Box content on the "ProgressDlg" dialog
Reported by customer - Scrollable Text Control jumped to the end when switching focus
Reported by customer - The default button option in the message box custom actions was not updating for each new custom action added
- Corrected unexpected behavior of the "Test URL" function for prerequisites
Reported by customer - Fixed issue where the "Uninstall MSIX/Appx Package" action failed to save the Publisher ID string
Reported by customer - Resolved multiple prompts during build-time synchronization of registration data from a file
- Addressed a potential memory leak related to GDI handles
Reported by customer - The reboot prompt was not displayed when the package used Embedded UI
- Fixed issue where importing registry entries resulted in incorrect paths due to bitness discrepancies
Reported by customer - Fixed issue where moving standard actions in the Custom Actions view could result in a stack trace error
- The second prerequisite was incorrectly launched in the background instead of in the foreground
Reported by customer