Released: Dec 5, 2025

2025 R2 での更新項目

機能

• Ability to Display Long Title Across Multiple Lines Without Truncation - Previously, dimensions of the inner installer frame were unexpectedly altered to display the installer's long title in full within the installer UI. Users could not control this unexpected alteration of the dimensions within the installer UI when long titles were used. In InstallAnywhere 2025 R2, on the Installer UI > Look & Feel Settings > UI Panel Settings > Custom UI Designer > Outer Installer Frame area, under the Frameless Window setting, a new subsetting named Wrap Installer Title has been introduced. This new subsetting allows you to specify whether to wrap the installer's long title across multiple lines within the installer UI, without truncation and without any alteration to the inner installer frame dimensions.
• Support to Log Warning When Search String is Missing in Text File - Previously, no warning message was logged in the log file whenever a search text string-specified under the Search For field in the Configure Search and Replace Strings or Search and Replace Strings dialog box-was not found in the target text file. InstallAnywhere 2025 R2 introduces a new checkbox or option named Warn if search string is not found on the Properties tab of the following actions: Modify Text File - In Archive, Modify Text File - Multiple Files, and Modify Text File - Single File. Selecting this checkbox or option enables InstallAnywhere to log a warning message in the log file whenever a text string-specified under the Search For field in the Configure Search and Replace Strings or Search and Replace Strings dialog box-is not found in the target text file(s). By default, this option or checkbox is cleared. The warning message notifies you that the expected text replacement is not applied to the text file(s) since the specified search string does not exist in the file.
• Ability to Manage Restore Default Display on Get User Input Panel - InstallAnywhere 2025 R2 introduces a new selection box named Remove Restore Button on the Get User Input - Advanced > Configure File Chooser Field dialog box, in the Control Properties area. This selection box allows you to specify whether the Restore Default button is displayed during installation and uninstallation. The Restore Default button typically appears on the File/Folder Chooser component in the Get User Input panel during installation and uninstallation, and is used to reset the field value based on the default variable-defined in the Result Variable field on the Configure File Chooser Field dialog box. Setting the selection box to Yes removes the Restore Default button from the File/Folder Chooser component in the Get User Input panel during installation and uninstallation. Setting the selection box to No retains the Restore Default button on the File/Folder Chooser component in the Get User Input panel during installation and uninstallation. By default, the selection box is set to No.
• Support to Perform Project-Level Check for JVM Secured Folder - InstallAnywhere 2025 R2 introduces a new setting named Secure JVM Folder Check on the Project > Platforms view, under the Windows area. This new setting allows you to specify whether to enable or disable the check in the current project that verifies whether the JVM is located within the secure or admin folder.
• Response File JVM Selection for Application Installed via Silent Installer - Previously, InstallAnywhere could not recognize or apply the JVM version specified in the response file or the installer.properties file when launching an application installed via a silent installer. Instead, the installer's default JVM version was applied. In InstallAnywhere 2025 R2, the JVM version specified in the response file or the installer.properties file is now correctly recognized or applied during the launch of application installed using a silent installer. This enhancement ensures that both the application (installed using a silent installer) and uninstaller launchers utilize only the JVM version specified in the response file, instead of the available installer's default JVM.

不具合の修正

• A build failure observed with a 'Null Pointer Exception' displayed when parsing an XML script file on a Linux machine, which was running in headless (non-GUI) mode. This issue has been fixed.
• Manual execution of code signing and notarization on a macOS-based installer-performed after extracting and repackaging the speed-folder JAR artifacts embedded within the installation package-resulted in the archive-metadata inconsistencies. These inconsistencies resulted in an Unknown archive type exception during installation. This issue has been fixed.
• Running an installer in silent mode led the application feature name variables to resolve to empty strings in the $CHOSEN_INSTALL_BUNDLE_LIST_LONG$ InstallAnywhere variable within the output file-created by the Output Debug Information action. This issue has been fixed.
• A failure was observed when attempting to load a dynamic merge module into an installer, with the Invalid CEN header (Invalid extra data field size for tag:0xedac at 0) error displayed. This issue has been fixed.
• A command execution failure was observed when migrating an installer from InstallAnywhere 2021 to InstallAnywhere 2024 R2 version. This failure may have occurred due to incorrect detection of the working directory during execution. This issue has been fixed.
• Using the ExtractToFile custom code plug-in action resulted in the java.lang.NoSuchMethodError exception for the com.zerog.ia.customcode.util.fileutils.ExtractToFile.install() method. This issue has been fixed.
• Modifying the jre_path to a relative path within a launcher's Info.plist file on the macOS platform caused the launcher to fail to locate the JVM. This also resulted in the following error message: Could not find a valid Java Virtual machine to load. This issue has been fixed.
• A progress bar in the Install progress panel failed to reflect the progress in consonance with the installation of actions, and prematurely displayed 100% before all actions were installed successfully. This issue has been fixed.
• On an IBM z, an installer failed to use the temporary directory specified by the TMPDIR and IATEMPDIR environment variables and continued to utilize the default /temp directory instead. This issue has been fixed.
• Using a relative path when attempting to generate a response file with the -r command-line switch failed to generate the same file and resulted in the following error: Resource <resource> is not accessible, Installer exiting. This issue has been fixed.
• On an IBM system i, the i5/OS actions-invoked either through custom code after setting the ia.signon.i5os JVM system property or through command line builds-failed and the following error was displayed when the supplied password contained lowercase or mixed-case characters: Signon failed: com.ibm.as400.access.AS400SecurityException: Password is incorrect. This issue has been fixed.
• The USER_REQUESTED_RESTART reboot option failed to record in a response file, which prevented this option from being used during silent mode. This issue has been fixed.