Dear all, InstallShield 2014 > Advanced UI project > InstallationFeatures Wizard > Install button In the "InstallationFeatures Wizard" I have set a script  action to the Install button which will test if the selected features combination is valid or not.(ValidateFeatureSelection). The above function sets the IS_VALID_INPUT property via the script. Next actions are: 1. Show Secondary Window  IS_VALID_INPUT not equal to True 2. Set Active Page to InstallationFeatures if IS_VALID_INPUT not equal to True 3. Set Active Page to InstallationProgress if IS_VALID_INPUT equal to True Steps 1-3 are working correctly however when I enter the InstallationProgress  windows the install is stuck in "Initializing" and does not progress. The log shows function ended successfully and shows the window entering info. What could be the problem? Could it be that the information about the selected features are lost when I set "Set Active Window" to "InstallationProgress"?   Thank you. Angela ... View more

Dear support, I have an Install Shied Suite and I need to find the feature selection at run time via installscript action: i have unsuccessfully tried the following: *Using FeatureIsItemSelected  rel1= FeatureIsItemSelected (MEDIA, "Feature1"); rel2= FeatureIsItemSelected (MEDIA, "Feature2"); * FEATURE[name].actionState I can make it work only in the actions but not via installScript * Read the value of ISFeatureInstall . However it does not reflect the modification the user makes in the UI after it was set by command line Thank you in advance. Angela ... View more

InstallShield 2014 Premier Edition  In the basic msi package  we use InstallShield pre-defined check for PowerShell by searching the following registry: HKLM\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine Value: PowerShellVersion   This registry entry does not exist in some  Server even though a new Powershell version is installed. Is there any InstallShield recommendation for this? Or should I use following advice: https://devblogs.microsoft.com/powershell/windows-powershell-2-0-deprecation/ ============================================================================= Installation Checks for Windows PowerShell 2.0 You may also have a legacy application that checks for the existence of Windows PowerShell on the box via the registry, particularly for the existence of HKLM:\Software\Microsoft\Windows\PowerShell\1\PowerShellEngine. As long as your application only targets supported versions of Windows and Windows Server (7/8.1/10 and Server 2008R2/2012/2012R2/2016), you can remove this validation altogether. If not, you should instead check for the existence of the file %systemroot%\system32\WindowsPowerShell\v1.0\powershell.exe. If your installer absolutely requires a registry-based validations, you should first check for HKLM:\Software\Microsoft\PowerShell\3\PowerShellEngine (note the 3) before falling back to HKLM:\Software\Microsoft\PowerShell\1\PowerShellEngine. =======================================================================================   ... View more