Released: Jul 21, 2023

Updates in 2023 R1

Features

• Added support for LZMA2 compression using 'Expand 7-Zip' action - The 'Expand Archive (7-Zip) action' now supports both LZMA and LZMA2 compression methods to expand a 7-Zip archive (.7z or .xz) on a target system.
• Customize Image, Label, and help settings for pre-uninstall and post-uninstall sequences - In this release, you can now enable and customize the following tabs:
  • Image settings - Customize the Image Settings tab on the Properties Customizer.
  • Label Settings - Customize the Label Settings tab on the Properties Customizer.
  • Help Settings - Customize the Help Settings tab on the Properties Customizer.
• Added support for the Microsoft Windows 11 Smart App Control - InstallAnywhere now supports the Smart App Control feature of the Windows 11 operating system.
• Added support for Apple macOS Sonoma - The Setups created with InstallAnywhere 2023 R1 can now run on macOS Sonoma.
• Customize the Choose Alias, Link, Shortcut folder - This new setting lets you to select the default options for Windows Shortcuts, UNIX Links and macOS Aliases which will be displayed during the installer run time.
• Prevent automatic reading of Default Response File - A new setting has been added to disable the installers' ability to automatically read the default response file.
• Prevent Default Response File creation in Silent Mode - A new setting has been introduced in the Project Information area which enables you to prevent end users from being able to generate the default response file in silent mode.
• Added a usage message for a missing or invalid argument - In this release, a usage message including the appropriate available options will be displayed on the console when you pass -i command-line switch without an argument or with an invalid argument for launching the installer.
• Encrypted the Notarization Information - In this release, the following notarization credential information saved in the project are now encrypted:
  • Apple user name.
  • Apple dev password.
  • Team identifier.

Fixes

• The NoVM installer failed to utilize the first suitable JRE available in the PATH environment variable.
• The Choose Install Folder panel's path displayed with / instead of Yen symbol as a path separator on a Japanese machine.
• When the icon source path was changed and the project was rebuilt, the Uninstaller icon and the Uninstaller launcher failed to appear and generate, respectively, during installation.
• The UAC prompt failed to display the consistent value for the Program Name due to the Project settings and sometimes displayed the value lax_gui_highest.
• The || (or) operator between the rules was incorrectly replaced with the && (and) operator after copying and appending the rules.
• Installation with -i command-line switch failed to write the response file with expected values.
• The Inline help for the settings Executable Icon Path and Installer Title Image in the Installer Icon area of the Look & Feel Settings view on the Installer UI page failed to mention that these settings are available if an installer builds only on Windows.
• A Java application using the LaunchAnywhere launcher was unable to launched on the macOS Ventura.
• When the Compare InstallAnywhere Variable Rule included no value for the Operand 2 and the installer launched with the Java 15 or later, there was a change in behavior.
• The SimpleRegistryManager.getRegistryKeyValue key name failed to retrieve the default value from a registry key.
• Comparison with empty string failed with the JRE for the Java 15 and later.
• The variable value in the Get User Input panel got revamped even though the condition was met. This issue has been fixed
• The does not exist already exist property in the Check File/ Folder Attributes rule was not evaluated properly.
• When the installer launched from the folder containing space on the Linux, the unexpected operator error message displayed on the console.
• The macOS installer failed to utilize the value of the lax.nl.current.vm property.
• The Move Folder action caused to remove the hidden attribute from a shortcut in the folder.
• When the installer including the Get User Input-Advanced panel action launched in the console mode on the target machine with an invalid value of DISPLAY, generated the AWTError and NoClassDefFoundError.
• Using the Set InstallAnywhere Variable-Single Variable action to set the value of an encrypted variable led to generation of the NumberFormatException.
• Copied and pasted the multiple rules with a complex rule expression from an action to a different action failed to maintain the rule expression.
• Launched the installer on the Linux without read permissions on the /etc/issue, displayed an error message on the console.
• On high DPI Get User Input-Advanced panel action with the Use fixed height for Prompt option not selected, displayed large amount of whitespace between the panel prompt and components.
• When the installed bundled virtual machine directory was copied from the $TEMP_DIR$ to the $USER_INSTALL_DIR$ using the Copy Folder action in the Install sequence, during uninstallation that installed bundled virtual machine directory was unable to removed completely.
• Native Windows libraries/executables distributed with installers, were not compiled with the Control Flow Guard enabled.
• In the console mode, the License Agreement Console panel failed to scroll through the license agreement after using the Enter key.
• The Windows desktop flickered/ refreshed each time any shortcut was installed.
• Using the -r command-line switch with a specific file name led to generate the response file with the default name.
• Using the -r command-line switch without the file name and path specification for the response file, resulted to failure in the installer launch.
• Documentation failed to describe the response file creation conditions for the installer while using -r command-line switch.
• Documentation mentioned the -productVersion build-related argument instead of the productVersion build-related argument.
• Documentation failed to mention the detail information for the Set System Environment Variable action.
• The required argument for running the Automation APIs with a JAVA 11 JRE failed to mention in the documents.
• Documentation failed to include the impact of DPI awareness and scaling on the installer size.
• Documentation failed to mention the recommended dimensions for the image displayed behind the Installer steps.
• Ability of the uninstaller to operate in silent mode was not explained in the documentation.
• Limitation of the Windows-based installers in the Maintenance mode for a cross bit installation was not mentioned in the documentation.