Released: Dec 6, 2023

2023 R2 中的更新

特性

• New Setting to Enable 64-Bit Signing Framework
  • This release introduces a new setting named 'Use 64-Bit Signing' on the Signing tab of the Releases explorer on the Media view, that enables you to use the 64-bit signing framework to digitally sign a package. Available options are:
    • Yes - Enables the 64-bit signing framework to digitally sign.
    • No - Enables the 32-bit signing framework to digitally sign.
    • By default, this setting is set to No.
• Automation Interface Support to Override the Setup.exe Version
  • This release introduces an automation interface support named LauncherFileVersion, to override the default file version with a custom file version for the Setup.exe. This read-write string property of the ISWiReleases object is available in the Basic MSI, InstallScript, and InstallScript MSI projects.
• Setup.exe's New Parameter to Customize Temporary Extraction Directory
  • For the Setup.exe launcher, this release introduces a new command-line parameter named /tempextractpath.
  • By default, the InstallShield setup extracts temporary files to the %TEMP% directory, loads these files to complete the installation, and then removes them once installation is completed. These temporary files include support files, billboards, and other InstallShield engine files used for executing custom actions. There are a few environment restriction scenarios, such as an antivirus which blocks an application from running executables from this %TEMP% extracted directory.
  • Using this parameter is recommended to customize the extraction directory in these scenarios. Security aspects have been considered by InstallShield while extracting and loading these files and binaries from a customized location.
• Support for Digitally Signing .mst Files Using Build Events
  • Previously, there was no option to sign .mst files from build events that were generated during build time. This prevented the customers from using the alternative signing scripts from build events instead of the InstallShield built-in signing option.
  • This release includes support to digitally sign .mst files, by enabling you to specify the script for signing them using the Precompression Event setting on the Event tab for a release in the Releases explorer on the Media view.
• Missing Components Now Displayed in Build Errors
  • In previous releases, when upgrading to the latest version of InstallShield, if some files are unavailable in a specific directory, the build errors that were generated specified only the missing files, not their missing components.
  • In this release, to improve troubleshooting, build errors now list both missing component names and missing files.
• New Prerequisite for Microsoft SQL Server 2022
  • This release introduces a prerequisite named Microsoft SQL Server 2022 Express (x64) for SQL Server 2022. This prerequisite has been added in the Redistributables explorer of the Application Data view. This applies to the following project types:
    • Basic MSI.
    • InstallScript.
    • InstallScript MSI.

修補程式

• 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.
• 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).
• The ARPPRODUCTICON.exe file was not digitally signed and therefore the Smart App Control on the Windows 11 blocked files/executables.
• 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.
• Building a QuickPatch project with the Extract COM Information checkbox checked led to crash the InstallShield IDE.
• A project with a merge module built successfully while using the InstallShield IDE, but failed with the InstallShield Standalone build.
• 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.
• Possibility 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.
• InstallShield Symlink vulnerability issue led to the Disk operating system corruption.
• InstallShield observed a crash while exporting the specific VBScript custom action stored in the Custom Action option.
• Silent installation of a Suite project failed to display the exit condition message and instead displayed only error numbers.
• 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).
• SAB2023 installation failed to include the InstallShield.Task.x64.dll file in the 2023 folder.
• 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.
• A Setup.exe crash was observed when a Suite project built with the Show Add or Remove Programs Entry setting was set to No.
• Building a Suite project with the Show Add or Remove Programs Entry setting set to No led the setup to stay on the initializing dialog without any response and displayed a build error.
• The InstallWelcome dialog displayed black-box text on the RebootDialog window while installing setup.exe on Windows 10 and 11 Japanese editions.
• 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.
• 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.
• A Suite/Advanced UI installer installation displayed a yellow progress bar if reboot was skipped on the target machine.