InstallShield 2026 R1
The following issues have been resolved in InstallShield 2026 R1:
|
Issue Number |
Issue Summary |
|
ISDEV-44875 |
Using the setup.exe/tempextractpath"C:\IS_temp" command failed to extract and add the PowerShell script files to the specified custom directory. Instead, those files were extracted to the Windows default temp directory. This issue has been fixed. |
|
ISDEV-44914 |
A dialog created using the SdAskOptions function failed to display the installation options when the Architecture setting, on the Build tab of a release in the Releases explorer, was set to the x64 option. This issue has been fixed. |
|
ISDEV-44975 |
The RegDBQueryKey function failed to access a registry key for its subkeys and returned -1 when the Architecture setting, on the Build tab of a release in the Releases explorer, was set to the x64 option. This issue has been fixed. |
|
ISDEV-44951 |
A log file generated after running an InstallScript installation contained truncated strings. This issue has been fixed. |
|
ISDEV-44692 |
A crash was observed when launching a 64-bit InstallScript setup.exe that included a LaunchApplication function. This issue has been fixed. |
|
ISDEV-44981 |
A security vulnerability was observed in the InstallShield 2023 R2 kit. The issue caused a standard user to execute actions that resulted into elevated privileges (SYSTEM-level access), thereby compromising the security of the target system. This issue has been fixed. |
|
ISDEV-44951 |
String truncated issues were identified in the InstallScript log file. This issue has been fixed. |
|
ISDEV-44943 |
Running an InstallScript project that was built using the SdLicense2Ex function caused the following error to be displayed during installation: In function ‘Sdlicense2Rtf’: Unable to create dialog. This issue has been fixed. |
|
ISDEV-44932 |
A failure was observed when launching a 64-bit InstallScript custom action using the LaunchAppAndWait function. This issue has been fixed. |
|
ISDEV-44926 |
Configuring an InstallScript project—using an array data type along with the ServiceGetServiceState function—to x64 architecture resulted in an installation failure. This issue has been fixed |
|
ISDEV-45046 |
When launching a 64-bit InstallScript installer—including the SdAskDestPath function—with administrative privileges, the SdAskDestPath dialog failed to accept the valid destination folder and displayed an error indicating that the selected path is invalid, incomplete, or write-protected. This issue has been fixed. |
|
ISDEV-44748 |
On a Window 11 24H2 machine, an issue was observed where printing the License Agreement failed with the following error message displayed: This file does not have an app associated with it for performing this action. Please install an app or, if one is already installed, create an association in the Default Apps Settings page. This issue has been fixed. |
|
ISDEV-45170 |
An issue was observed where setup.exe failed to recognize and process command-line arguments when launched from a mapped network drive (for example, X:\). Consequently, installation parameters provided through the command line, such as silent installation switches and custom configuration options, were ignored. This issue has been fixed. |
|
ISDEV-44759 |
Reordering subfeatures of a feature in the Setup Design view failed to save when the subfeatures were configured with the Display setting configured to Not Visible and the Advertised setting configured to Disallow Advertise. This issue has been fixed. |
|
ISDEV-45022 |
An installer failed to execute a prerequisite from the /temp directory where the installer files were extracted and instead attempted to execute it from a hard-coded path. This issue has been fixed. |