InstallShield 2023 R2
The following issues have been resolved in InstallShield 2023 R2:
|
Issue Number |
Issue Summary |
|
ISDEV-43405 |
Built a Suite project with the Show Add or Remove Programs Entry setting set to No, led to a build failure and displayed an error message: ISDEV : error -7385: Add and Remove Programs in General Information should be set to Yes as installer is configured to Check for Updates. This issue has been fixed. |
|
ISDEV-43364 |
InstallShield Standalone build with a Docker container failed and displayed an error message: docker: Error response from daemon: container <Container ID> encountered an error during hcs::System::Start: failure in a Windows system call: The virtual machine or container exited unexpectedly. (0xc0370106). This issue has been fixed. |
|
ISDEV-43342 |
The ARPPRODUCTICON.exe file was not digitally signed and therefore the Smart App Control on the Windows 11 blocked files/executables. This issue has been fixed. |
|
ISDEV-42983 |
Configured the Reboot Request setting to the Always reboot the machine in a Suite project which contains a prerequisite, resulted to prompt a dialog: a restart is required and are given the option to reboot now or later, after prerequisite installation. This issue has been fixed. |
|
ISDEV-43354 |
Building a QuickPatch project with the Extract COM Information checkbox checked led to crash the InstallShield IDE. This issue has been fixed. |
|
ISDEV-43284 |
A project with a merge module built sucessfully while using the InstallShield IDE, but failed with the InstallShield Standalone build. This issue has been fixed. |
|
ISDEV-43196 |
An installer failed to launch with an error message because the ISSetup.dll file was not digitally signed when the Compile script option was selected. This issue has been fixed. |
|
ISDEV-43500 |
Possiblity for the DLL hijacking security vulnerability to be observed due to a malicious DLL being copied into the Disk1 folder of a built installer which included the setup.exe with a different name. This issue has been fixed. |
|
ISDEV-43476 |
InstallShield Symlink vulnerability issue led to the Disk operating system corruption. This issue has been fixed. |
|
ISDEV-43403 |
InstallShield observed a crash while exporting the specific VBScript custom action stored in the Custom Action option. This issue has been fixed. |
|
ISDEV-43437 |
Silent installation of a Suite project failed to display the exit condition message and instead displayed only error numbers. This issue has been fixed. |
|
ISDEV-43575 |
A vulnerability was reported in the Zlib library (v1.2.13) used in InstallShield. Now, the Zlib is upgraded to the latest version (v1.3.0.1). |
|
ISDEV-43490 |
SAB2023 installation failed to include the InstallShield.Task.x64.dll file in the 2023 folder. This issue has been fixed. |
|
ISDEV-43445 |
Windows Server 2019 update resulted in a build failure with an error message: ISDEV : error -6003: An error occurred streaming 'C:\Program Files (x86)\InstallShield\2022\SetupPrerequisites\Microsoft .NET Framework 4.8 Full.prq' into setup.exe. This issue has been fixed. |
|
ISDEV-43442 |
A Setup.exe crash was observed when a Suite project built with the Show Add or Remove Programs Entry setting was set to No. This issue has been fixed. |
|
ISDEV-43438 |
Building a Suite project with the Show Add or Remove Programs Entry setting set to No led the setup to stay on the intializing dialog without any response and displayed a build error. This issue has been fixed. |
|
ISDEV-43396 |
The InstallWelcome dialog displayed black-box text on the RebootDialog window while installing setup.exe on Windows 10 and 11 Japanese editions. This issue has been investigated and a resolution has been documented. For information on resolution, see Dialog Functions in the InstallScript Reference Guide. |
|
ISDEV-43265 |
All locally copied items were included in the File MSI table when an installer was built with Visual Studio, but one locally copied item was not included in the File table when an installer was built with MSBuild. This issue has been fixed. Note:Locally copied MSBuild target is available only for MSBuild shipped with Visual Studio 2019 or later. Therefore, this fix is only applicable to MSbuild shipped with Visual Studio 2019 or later. |
|
ISDEV-43059 |
If an installer was built with Visual Studio, the NLog.dll was installed to the TARGETDIR; however, if an installation was built using MS Build, the NLog.dll was not installed to the TARGETDIR. This issue has been fixed. Note:Locally copied MSBuild target is available only for MSBuild shipped with Visual Studio 2019 or later. Therefore, this fix is only applicable to MSbuild shipped with Visual Studio 2019 or later. |
|
ISDEV-43431 |
A Suite/Advanced UI installer installation displayed a yellow progress bar if reboot was skipped on the target machine. This issue has been fixed |