InstallShield 2025 R1

The following issues have been resolved in InstallShield 2025 R1:

Issue Number	Issue Summary
ISDEV-42627	In an InstallScript project, a setup.exe file failed to resume the installation after a reboot if its name included a space. This issue has been fixed.
ISDEV-44380	The debug properties were unexpectedly detected when the release version of the ISSetup.dll file was included in InstallScript-based projects. This issue has been fixed.
ISDEV-44261	Running an Azure DevOps Build Pipeline led to displaying build warnings, although the related build process was successful. This issue has been fixed.
ISDEV-41926	When a system reboot was performed—triggered by an InstallShield prerequisite—an installer installation restarted from the first dialog instead of resuming from where it left off. This issue has been fixed.
ISDEV-44337	Executing a setup.exe with a custom command-line parameter—including an odd number of double quotation marks—led to the display of multiple instances of setup.exe in Task Manager and the creation of multiple folders in the %TEMP% directory. This issue has been fixed.
ISDEV-44421	A PowerShell crash was observed when building a Suite project using a PowerShell script and the InstallShield automation interface. This issue has been fixed.
ISDEV-44289	InstallShield failed to support Windows high contrast mode. This issue has been fixed.
ISDEV-44252	A failure was observed when executing the /z (command-line parameter for Setup.exe) with the ‘=’ symbol; specifically, the CMDLINE property failed to retain any value after the ‘=’ symbol. This issue has been fixed.
ISDEV-44255	A password value passed from CustomActionData property to a deferred managed code (C#) custom action was unexpectedly exposed in the verbose MSI log file. This issue has been fixed.
ISDEV-43996	Changing a machine’s decimal separator from a dot (.) to a comma (,) led to the installation failure of a Suite installer that included minimal wizard pages. This issue has been fixed.
ISDEV-43626	Creating or updating a 64-bit registry key in a Quick Patch project on a 64-bit target system failed to include or update the same registry key in the 64-bit directory; instead, the key was added or updated in the 32-bit directory. This issue has been fixed.
ISDEV-43254	Executing an automation script for a Suite project failed to set the DisplayName property of a newly created feature to a correct string; instead, the property was set to a string ID. This issue has been fixed.
ISDEV-42980	A Suite installer uninstallation failed to remove or delete both the cached {Suite GUID} folder and cached Setup.exe file in the C:\Program Files (x86)\InstallShield Installation Information folder directory. This issue has been fixed.
ISDEV-44389	An installer built with a customer-specific .dll file and with the .NET Assembly setting configured only as Local Assembly triggered the Windows Features dialog prompting for the .NET Framework 3.5. This issue was specific only to installers built using only InstallShield 2024 R2 and has now been fixed.
ISDEV-44418	All the required .dll files pertaining to two supported languages—Arabic (Saudi Arabia) and Hebrew—were missing from the InstallShield IDE or Standalone Build installation location. This issue has been fixed.
ISDEV-43368	A failure was observed during an automatic upgrade process when upgrading a setup.exe from an older version to a newer version if it included multiple languages in the Language column for an automatic upgrade item. This issue has been fixed.
ISDEV-44308	A failure was observed when using the SS_NOTIFY window style with static (label) controls in InstallScript dialogs. In this case, the static controls did not respond to mouse events as expected. This issue has been fixed.
ISDEV-42678	Using the Merge Module Validation suite for an empty project led to display the ICEM10, ICEM03, and ICEM103 errors. This issue has been fixed.
ISDEV-44584	Attempting to install a setup.exe using an ISO file led to an installation failure with the following error displayed: LAAW_PARAMETERS.nLaunchResult: 1203 This issue has been fixed.