InstallShield 2024 R1
The following issues have been resolved in InstallShield 2024 R1:
|
Issue Number |
Issue Summary |
|
ISDEV-43799 |
When the Signing Type setting was set to the Custom option, the Sign files in package setting failed to digitally sign the package payload files. This issue has been fixed. |
|
ISDEV-43797 |
When the Custom option was selected in the Signing Type setting, the .mst files were digitally signed twice, which led to an increase in the build time. This issue has been fixed. |
|
ISDEV-43824 |
For setups that were configured with the registry and file permissions options, a vulnerability was reported in the Basic MSI and InstallScript MSI (64-bit) setups. This issue has been fixed. |
|
ISDEV-43745 |
The InstallShield interface failed to display the correct characters if the Beta: Use Unicode UTF-8 for worldwide language support checkbox was selected in the Windows locale settings. This issue has been fixed. |
|
ISDEV-43718 |
An InstallScript MSI project build failure was observed with the ISDEV : fatal error -1027: Failed signing _isuser_0x0409.dll error message when the InstallScript User Interface Type setting was set to the New Style (Requires Windows Installer 4.5) option. This issue has been fixed. |
|
ISDEV-43694 |
A failure was observed when returing a borrowed license. This issue has been fixed |
|
ISDEV-43589 |
After a successful silent installation, the ResultCode value in the [ResponseResult] section of the setup.log file failed to update. This issue has been fixed. |
|
ISDEV-42676 |
Usage of the InstallShield Self-Registration (ISSelfReg) method to register the .dll files in a project led to a vulnerability. This issue has been fixed. |
|
ISDEV-42638 |
While launching the installer in the Japanese language, if the user name included multiple byte characters, the image failed to appear in the Sd dialog. This issue has been fixed. |
|
ISDEV-42629 |
The database column, which was initially set to the MAX value, changed to 0 value while importing the database to the SQL Server view. This led to a setup installation failure with the Length or precision specification 0 is invalid. (1001) error message. This issue has been fixed. |
|
ISDEV-41935 |
After rebooting, the installer installation failed to remove all files from the temp directory due to the included prerequisites. This issue has been fixed. |
|
ISDEV-43875 |
Using the /tempextractpath argument failed to extract files to a customized directory. This issue has been fixed. |
|
ISDEV-38622 |
Deletion of the SRCDIR source folder led to the display of the Please insert disk 1 that contains the file data2.cab prompt message during an InstallScript installer repair. This issue has been fixed. |
|
ISDEV-43807 |
Documentation failed to mention the non-operational behavior of the /extract_all command-line parameter when used in the Setup Command Line box on the General Options panel of the Release Wizard. This issue has been fixed. |
|
ISDEV-43804 |
Documentation failed to describe the requirements for the proper functionality of the system search for the default value of the Registry key. This issue has been fixed. |
|
ISDEV-42799 |
The official Microsoft terminology for .NET attributes failed to appear consistently in the documentation. This issue has been fixed. |