InstallAnywhere 2026 R1
The following issues have been fixed in InstallAnywhere 2026 R1:
|
Issue Number |
Issue Summary |
|
IA-22513 |
Running an installer with JDK 25 led to the display of the following warning message: The use of the system property "java.locale.useOldISOCodes" is deprecated. It will be removed in a future release of the JDK. This issue has been fixed. |
|
IA-22522 |
Modifying the value of the $USER_INSTALL_DIR$ variable in the response file using a single backslash, such as, USER_INSTALL_DIR=C:\Program Files\SilentTest caused the installation path to be interpreted incorrectly during silent installation, which in turn led to repair and uninstallation operation failures. This issue has been fixed. |
|
IA-22525 |
A project automation failure was observed with the following error message displayed: com.zerog.ia.auto.project.ProjectAutomationException: The class 'com.zerog.ia.designer.manageexpressions.ManageExpressions' is not supported by the project automation API. This issue has been fixed. |
|
IA-22547 |
A log file displayed the following warning for both the bundled VM and internal resource directories during an uninstaller launch. Directory contains delete protected files. This issue has been fixed. |
|
IA-22573 |
Configuring the Include Debug Output (stderr and stdout) setting to Yes—in the Log Settings area of the General Settings view on the Project page—caused the installation directory to be unintentionally deleted during maintenance mode operations. This issue has been fixed. |
|
IA-22549 |
Using the System i (i5/OS) Install File action failed to install a file in the Integrated File System (IFS) on a remote i5/OS system during an installation and displayed the following warning message: Exception encountered creating directories for target. This issue has been fixed. |
|
IA-20955 |
Creating a new project or opening an existing project led to the generation of Illegal Reflective Access warning messages in the debug log output. This issue has been fixed. |
|
IA-22072 |
During an installer launch, a drop-down option—which is a subcomponent of a checkbox—appeared disabled when it was expected to be enabled. This issue occurred due to a response file usage to configure the drop-down option's appearance. This issue has been fixed. |
|
IA-22544 |
In JDK 20 and later, the background color for the Cancel button failed to render on the first GUI screen during initial rendering when a custom color scheme was used. This issue has been fixed. |
|
IA-22612 |
When an installer was executed in silent mode, it became unresponsive and failed to exit from installation with an appropriate exit code. Instead, the process waited for user interaction (such as a key press) for returning an exit code and exiting. This issue has been fixed. |
|
IA-22512 |
Silent mode installer executions failed to consistently log the installation status (success or failure) and return a reliable installation exit code. This issue has been fixed. |
|
IA-14303 |
When a warning was logged after installation, the word null was incorrectly appended to the following summary message in the log file: Summary: Installation: Successful null This issue has been fixed. |