Summary: This article shows how to automate passing the license information to a silent install of the InstallShield Standalone Build (SAB). Resolution: Download the InstallShield Standalone Build. For example: InstallShield2021R2StandaloneBuild.exe Open an Administrator command prompt. Run the following command: InstallShield2021R2StandaloneBuild.exe /S /v/qn /VSERVERNAME=<IPADDRESS OR LICENSE_SERVER_NAME> /VPORTNUMBER=<LICENSE_SERVER_PORT> /VLICENSETYPE=2 /VADDLOCAL=ALL The following tasks will be completed and the install will be done silently without displaying any wizard: 1. Specifying of concurrent license options 2. Specifying of the license server name 3. Installing of all the features In the aforementioned command (see above): The value of 1 for the LICENSETYPE property indicates that you are using a node-locked license of the InstallShield SAB. The value of 2 for the LICENSETYPE property indicates that you are using a concurrent license of the InstallShield SAB. The value of 3 for the LICENSETYPE property indicates that you are using a Cloud License Server (CLS) concurrent license of the InstallShield SAB. Additional Information: Click here for the documentation about the command line parameters that the InstallShield SAB (ISCmdBld.exe) takes. ... View more

Summary: The driver package from the driver store is not removed during uninstall. Synopsis: This article will provide steps for removing the driver package from the driver store during uninstall. Discussion: 1. Set Permanent to No for the component to which the driver is associated. If Yes is selected, none of the component's data (such as files, registry entries, and shortcuts) are removed from the target system when the component's parent feature is uninstalled. As the name Permanent indicates, a component marked Permanent is permanent, meaning that it is not removed during uninstall. 2. For the component that contains the file or folder, right-click the file and click Add Removal. Make sure there is an entry created in the Direct Editor in the RemoveFile MSI Table. 3. Change the General Information > Template Summary to "x64;1033" (the value for a 64-bit installer). 4. On a 64-bit machine, [System64Folder] needs to be used to target the C:\Windows\System32 folder, because this is the 64-bit location. The C:\Windows\SysWOW64 folder is the 32-bit location for the System folder. Example: 1. Create a Basic MSI Project. 2. Add a feature and a component. 3. Set General Information > Template Summary to "x64;1033". 4. Go to the Property Manager and create a new property named "XXXXBUS" with a value of "C:\Windows\System32\xxxxbus". 5. Go to the RemoveFile MSI Table and add the following values: FileKey = Removexxxxbus, Component = xxxbus, FileName = xxxxbus.inf, DirProperty = XXXXBUS, InstallMode=3 6. Build the project. 7. Run the installer. 8. Go to the target machine and create the following folder: C:\Windows\System32\xxxxbus 9. Make sure that the xxxxbus.inf file is in the C:\Windows\System32\xxxxbus folder. 10. Run the installer on the target machine. 11. Run the uninstaller on the target machine. During uninstall the driver package will be removed from driver store at the following location: C:\Windows\System32\DriverStore\FileRepository ... View more

Summary: This article discusses how to launch / run an .exe file if the .exe file is found by using a System Search and how to force a restart / reboot of the machine. Resolution: 1. Create a Basic MSI Project. 2. Navigate to Behavior and Logic > System Search. 3. Add a File path, by searching folders System Search. 4. Click Next. 5. Enter the .exe filename and the full path, in the System Search Wizard, by finding the full path in File Explorer then specifying the same path in the wizard. The full path to the Notepad++ installer .exe file in File Explorer (C:\Windows): The System Search Wizard represents C:\Windows with [WindowsFolder]: 6. Specify the property to store the value of the search result in. 7. Navigate to the InstallScript View. 8. Create a Setup.rul file with the following InstallScript code: #include "ifx.h" export prototype Func1(HWND); function Func1(hMSI) STRING PropertyName; NUMBER nResponse,nvSize; begin nvSize=MAX_PATH; nResponse=MsiGetProperty (hMSI,"TEST",PropertyName,nvSize); MessageBox("PropertyName:"+PropertyName,INFORMATION); if (nResponse==0) then LaunchApp(WINDIR ^ "npp.8.3.3.Installer.x64.exe", ""); MessageBox(WINDIR^ "npp.8.3.3.Installer.x64.exe",INFORMATION); else MessageBox ("Setup will now exit.", INFORMATION); endif; end; 9. Add an InstallScript custom action. 10. Schedule the InstallScript custom action in the Execute Sequence (Install Exec Sequence) after the standard CostFinalize Action. 11. In the Property Manager, set a property named: REBOOT to a value of: Force 12. Build the project. 13. Run the installer. The Notepad++ installer will be launched if it is found in the Windows folder. Additional Information: Here is a link to the official Microsoft documentation about the standard CostFinalize Action: https://docs.microsoft.com/en-us/windows/win32/msi/costfinalize-action ... View more

Summary : This article explains how to use a powershell custom action to access an MSI property with deferred custom action. This information applies to the following InstallShield project types: Basic MSI InstallScript MSI Solution: 1. Create Basic MSI Project 2. Create powershell script file names shell.ps1 function Show-CustomActionData { param ($propertyName) $myProps = get-property -name $propertyName $myPropArray = $myProps.split(";") $ARPINSTALLLOCATION = $myPropArray[0] $INSTALLDIR = $myPropArray[1] $TEST = $myPropArray[2] #$wshell = New-Object -ComObject Wscript.Shell #$wshell.Popup("ARPINSTALLLOCATION: $ARPINSTALLLOCATION",0,"Property Value",0x1) #$wshell.Popup("INSTALLDIR: $INSTALLDIR",0,"Property Value",0x1) #$wshell.Popup("TEST: $TEST",0,"Property Value",0x1) "Test" | Out-File -FilePath C:\Test\testtest.txt $installdir | Out-File -FilePath C:\Test\testinstalldir.txt $user | Out-File -FilePath C:\Test\testuser.txt 3. Create feature called Power and add the shell.ps1 file 4. Create Custom Action(POWERCAS) and select the shell.ps1 file, Deferred Execution in system context and After SetCustomActionData. 5. Create SetCustomActionData and set the below, 6. Build and Run the project. 7. The file C:\Test\testinstalldir.txt is created with the expected Value. ... View more

Summary: Execution failed with exit code -2147213312 Synopsis : During a silent Installation the following error may be seen:  "Execution failed with exit code -2147213312" Discussion: This error has been seen to occur due to a corrupted or missing  .iss file. Resolution: We can pass /r switch, which should create the silent install response file and then use the –s swtich to look for the silent response file as system account needs a setup.iss (answer/response) file to write to / read from. Example: Setup.exe /r /f1”C:\temp\Install.iss” ... View more

Summary: We can use the InstallShield Automation Interface to change the Package GUID of all of the packages included in a suite project. Steps: 1. Create a suite project with a suite project filename of Guidtest.issuite and include a primary package, a .exe or .msi package. 2. Open a text editor or a VBScript Editor, such as VbsEdit, and create a file named Guid.vbs then add the following VBScript code: Dim pProject Set pProject = CreateObject ("ISWiAutoSuite27.ISWiProject") pProject.OpenProject "C:\InstallShield 2021 Projects\My Suite Name-1.issuite", False Dim sp for each sp in pProject.ISWiSuitePackages Wscript.Echo sp.Name sp.Name = pProject.GenerateGUID() Wscript.Echo sp.Name Next pProject.SaveProject pProject.CloseProject 3. Run the VBScript automation interface script (automation script) with the following command: "C:\Windows\SysWOW64\cscript.exe" "C:\Guid.vbs" where cscript.exe (the main 32-bit VBScript console-based executable) is located in the "C:\Windows\SysWOW64" folder, then check the Package GUID for the included package. There will be an updated Package GUID for the package. Note: wscript.exe (the main 32-bit VBScript GUI-based executable) is also located in the "C:\Windows\SysWOW64" folder. If the VBScript author only wants console-based output, cscript.exe needs to be used. If the VBScript author wants GUI-based output, wscript.exe needs to be used. ... View more

Summary: Internal error in the file DataTargetFile.cpp,line:86: "Cannot create a file when that file already exists." Synopsis: This article will show you how to resolve the Error Code:132. Discussion: Generally, this error occurs while InstallShield is moving temporary files generated from the build to the respective files, such as the .hdr file and .cab files in the DISK1 folder. Deleting a file on the machine may fail due to one or more of the following reasons: The user is not an Administrator. The user does not have write access to the target path(Network Location etc). Antivirus software or security-related software or both is interfering with the file deletion process. Here are some possible, corresponding resolutions: Make sure to build as an Administrator. Make sure that the current user has write access to the target path(Network Location etc). As a test, temporarily disable antivirus software and security-related software to see if the issue still occurs. If the issue no longer occurs, re-enable the antivirus software and security-related software and add an exclusion / exception for the InstallShield build output folder so that the antivirus software and / or security-related software does not interfere with the build process and allows the file deletion process. ... View more

Description: This article will discuss folder permissions. This article will discuss how to set folder permissions so only an Administrator can access a specific folder. All other users will be denied access. Solution: This can be done by using the following command: icacls "C:\Program Files (x86)\Folder" /inheritance:r /grant Administrators:F Via InstallScript: Steps: 1. Create a Basic MSI project. 2. Create a feature and a component then add files. 3. In the General Information View, confirm the folder you want to restrict (for example, INSTALLDIR). 4. Create one batch file for the command (Permission.bat) with the following batch file contents: @echo off title folderpermission icacls "C:\Program Files (x86)\Folder" /inheritance:r /grant Administrators:F echo "Done!" 5. Navigate to the InstallScript View and add the following InstallScript code in the InstallScript Setup.rul: #include "ifx.h" export prototype Icacls(HWND); function Icacls(hMSI) // To Do: Declare local variables. STRING szCmdline,szProgram; begin szProgram = "C:\\Users\\Administrator\\Desktop\\Permission.bat"; szCmdline = SystemFolder+"\\cmd.exe /c"; LaunchApp (szProgram,szCmdline); end; 6. Build the project then run the installer. 7. Log in as a non-admin user and check the folder permissions by trying to access the C:\Program Files\Folder folder. Only Administrators will have access to view the contents of the folder.   Via PowerShell: PowerShell Script: Invoke-Expression -Command:"icacls 'C:\Program Files (x86)\Permission' /inheritance:r /grant Administrators:F" Steps: 1. Create a Basic MSI project. 2. Create a feature and a component then add files. 3. In the General Information View, confirm the folder you want to restrict (for example, Permission). 4. Create the following PowerShell script with the following contents (test.ps1): Invoke-Expression -Command:"icacls 'C:\Program Files (x86)\Permission' /inheritance:r /grant Administrators:F" 5. Configure a PowerShell custom action. 6. Build the project then run the installer. 7. Only an Administrator will be able to access the C:\Program Files\Permission folder to view the contents of the folder and a non-admin user will not be able to access the C:\Program Files\Permission folder. ... View more

Description: This article will discuss about SDFeatureDialog not showing size(only with required feature) Replication Step: 1. Create Installscript MSI project. 2. Create Features like aaa,bbb,ccc and also add component then add files. 3. Create Feature named ddd(without include component) 4. Add the Following code in an InstallScript View, function OnBegin() STRING szTitle, szMsg, svDir; begin svDir = TARGETDIR; szTitle = "Select Features"; szMsg = "Select the features you want to install on your computer."; SdFeatureDialog2 (szTitle, szMsg, svDir, ""); end; 5. Goto Feature ddd-> Required Features-> add the features aaa,bbb and ccc 6. Build and run the project.   Enunciation: When any feature is selected, its required features are automatically selected.ex: When 'ddd' is selected, all of its required features are also selected and grayed out to indicate those are required features. Hence It will be confusing with the total size required if sizes are shown for the main feature and as well as for its required features especially when one feature is set as a required feature for multiple features. SdFeatureTree (szTitle, szMsg, svDir, "", 2); dialog can be used instead of SDFeatureDialog. https://docs.revenera.com/installshield26helplib/LangRef/LangrefSdFeatureTree_example.htm?Highlight=SdFeatureTree ... View more

Description:  This article will discuss how to store a return/error code generated by a custom action. Ex: If the exe file is displaying its own message to the user The error message that's being displayed when the error code returns may be undesirable. Solution: 1. Create a custom action with deferred execution. 2. Installscript code to store the error code: Function CheckProduct(hMSI) String returnCodeStr; Number nvSize,returnCode; begin nvSize=250; //Run exe SprintfMsiLog("path="+INSTALLDIR+"\\AAA.exe"); returnCode=LaunchApplication(INSTALLDIR+ "\\AAA.exe", "/c", INSTALLDIR, SW_NORMAL,LAAW_PARAMETERS.nTimeout,LAAW_OPTION_WAIT); NumToStr(returnCodeStr,returnCode); //Return Value SprinfMsiLog("returnCode="+returnCodeStr); if(returnCode=0)then SprintfMsiLog("Result Success"); return ERROR_SUCCESS; else SprintfMsiLog("Result Failure"); return ERROR_INSTALL_FAILURE; endif; end; Where AAA.exe if the exe file which displays its own message to the user. You can use your own exe. 3. C reate a SetPropertyTask and use the CustomActionData to get the property into InstallScript. SetProperty that will copy the value to the CustomActionData property. More Info, https://www.revenera.com/blog/software-installation/it-wants-me-to-do-what-some-notes-on-customactiondata-in-installshield/ ... View more

Summary This article discusses how to specify a condition for checking the Windows Registry in the case of a variable Windows Registry path. Project Type Basic MSI Problem Description During installation of software, the DatabaseFolder Dialog is displayed and the user may choose a folder and that folder path is stored in the [DATABASEDIR] property. From this, a registry value is created: Path = "HKEY_LOCAL_MACHINE\SOFTWARE\TEST Abc\[REGISTRY_SETUP_PATH]" where [REGISTRY_SETUP_PATH] is a property that will be set to different values depending on release flags The value name = "CommonFilesPath" The value data = "[DATABASEDIR][CommonFilesDirectoryName]" [DATABASEDIR]= Value entered in dialog "DatabaseFolder" [CommonFilesDirectoryName]= Property that will be set to different values depending on release flags. What is the condition if this Windows Registry value "CommonFilesPath" on path "HKEY_LOCAL_MACHINE\SOFTWARE\TEST Abc\[REGISTRY_SETUP_PATH]" already exists before then install starts? In this case this Windows Registry value should not be modified and the DatabaseFolder Dialog should not be displayed. Solution This can be achieved by using the following InstallScript code: 1. RegDBGetKeyValueEx - Use this function to get the Windows Registry value. function CheckIfCFRegistryValueExists(hMSI) STRING sRegistrySetupPath; NUMBER nRegistrySetupPathSize, nType; STRING sRegKey, sRegName, sRegValue, sErrorCode, szMsg; NUMBER nRegType, nRegSize, nErrorCode; STRING sCFRegistryValueExists; NUMBER nCFRegistryValueExistsSize; begin //Find exact path to registry. MsiGetProperty (hMSI, "REGISTRY_SETUP_PATH", sRegistrySetupPath, nRegistrySetupPathSize); RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE); REGDB_OPTIONS = REGDB_OPTION_WOW64_64KEY; sRegKey = "SOFTWARE\\TEST Abc\\" + sRegistrySetupPath; sRegName = "CommonFilesPath"; sRegValue = "NONE"; nRegType = REGDB_STRING; nRegSize = -1; //Get value from registry if (RegDBGetKeyValueEx (sRegKey, sRegName, nRegType, sRegValue, nRegSize) < 0) then //Registry value doesn't exists. Set CFRegistryValueExists to "FALSE" MsiSetProperty(hMSI, "CFRegistryValueExists", "FALSE"); else //Registry value exists. Set CFRegistryValueExists to "TRUE" MsiSetProperty(hMSI, "CFRegistryValueExists", "TRUE"); endif; MsiGetProperty (hMSI, "CFRegistryValueExists", sCFRegistryValueExists, nCFRegistryValueExistsSize); end; Note: The InstallScript code is triggered by an InstallScript custom action configured for Immediate Execution. 2. Add a condition for the DatabaseFolder Dialog. The condition should be specified for the NewDialog Event the Next button that navigates to the DatabaseFolder Dialog. In this case, the condition would be: NOT CFRegistryValueExists ... View more

Summary This article discusses a scenario when the installer lays down components, such as DLLs, Windows Registry entries, or shortcut files, these components are getting installed as dynamic components. Project Type Basic MSI Symptoms When trying to not install any component as a dynamic component, there are duplicate components prefixed with a double underscore with a 65 appended and the components are being installed as dynamic components anyway. MSI (s) (28:C4) [18:00:52:463]: Component: Shortcut; Installed: Absent; Request: Local; Action: Local; Client State: Unknown MSI (s) (28:C4) [18:00:52:463]: Component: __ServerDLL65; Installed: Null; Request: Local; Action: Local; Client State: Null MSI (s) (28:C4) [18:00:52:463]: Component: __JDProcessorDLL65; Installed: Null; Request: Local; Action: Local; Client State: Null MSI (s) (28:C4) [18:00:52:463]: Component: __ProcessorDLL65; Installed: Null; Request: Local; Action: Local; Client State: Null MSI (s) (28:C4) [18:00:52:463]: Component: __Registry65; Installed: Null; Request: Local; Action: Local; Client State: Null MSI (s) (28:C4) [18:00:52:463]: Component: __NotificationReg65; Installed: Null; Request: Local; Action: Local; Client State: Null MSI (s) (28:C4) [18:00:52:463]: Component: __Shortcut65; Installed: Null; Request: Local; Action: Local; Client State: Null MSI (s) (28:C4) [18:00:52:463]: Component: JDProcessorDLL; Installed: Absent; Request: Local; Action: Local; Client State: Unknown MSI (s) (28:C4) [18:00:52:463]: Component: JDProcessorINI; Installed: Absent; Request: Local; Action: Local; Client State: Unknown MSI (s) (28:C4) [18:00:52:463]: Component: ProcessorDLL; Installed: Absent; Request: Local; Action: Local; Client State: Unknown Discussion There are cases where a component can install resources into locations other than the location referenced in the Directory_ column. In order to account for that and to more accurately adjust costing when a Directory's target location changes, such as when the user alters the install location, the installer uses a mechanism called cost-linking. For each alternate target folder for the component, the installer creates a new subcomponent. Cost-linking is used to account for the following MSI tables: Shortcut, RemoveFile, MoveFile, DuplicateFile, Registry,IniFile. Cost-linking is also used for all global/shared assembly components. Action start <time>: InstallValidate. MSI (s) <process info>: Feature: Simple; Installed: Absent; Request: Local; Action: Local MSI (s) <process info>: Component: Simple7890123456789012345678901234567890123456789012345; Installed: Absent; Request: Local; Action: Local MSI (s) <process info>: Component: __ Simple789012345678901234567890123456789065; Installed: Null; Request: Local; Action: Local For example, let's look again at the InstallValidate action dump from above for an example setup where the component installs both a file and a registry key. Note the subcomponent. That component was created to account for cost associated with the registry key. It's a cost-linked component for the component + WindowsFolder directory. The component's current cost (for the parent) is associated with the SimpleDir directory which is the authored directory for the component in the Component table. At this point, the component doesn't have any previously created child components so it starts with a suffix of 65. Also, only the first 40 characters were used of the component name (which had 55 characters). ... View more

Description: The suite installation is not resumed after a reboot prompt if the user clicks No on the reboot / restart prompt. Clicking Yes resumes the installation and the Basic MSI installer also resumes the installation after reboot, after the user clicks Yes or No on the reboot prompt. Steps to Reproduce:  Basic MSI Project: Create a Basic MSI project (ex. BMSITest.ism). Configure the ForceReboot Action by placing it after the RegisterProduct Action. Build the project. Run the installer. At the reboot prompt, click Yes or No. After the reboot the installation resumes in both the cases, after clicking Yes or No. Suite Project: Create a suite project. Add the Basic MSI project as a package in the suite installer. Build the project. Run the suite installer. After the restart, the suite installation resumes if the user clicks Yes at the reboot prompt. If the user clicks No at the reboot prompt, the installation is not resumed after the reboot. Behavior: The suite installer handles clicking No as equivalent to clicking Cancel. Explanation of the behavior: Note: The ForceReboot action must be given a condition of NOT AFTERREBOOT; otherwise, the reboot will get stuck in a loop. Test Scenario# 1: A compressed MSI package built from the Basic MSI project: Launch the MSI setup with the following command line: ForceRebootMSI.msi /l*v "C:\Log\ForceRebootBasicYes.log" The user needs to click Yes at the reboot prompt. The Windows Registry entry will created under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\RunOnceEntries with a value of: {3BC02749-19DA-4FA7-A3DC-5B172C36D7FC}" AFTERREBOOT=1 RUNONCEENTRY="!94720CB3AD917AF43ACDB571C2637D" /qF /lmewuifsoarpcv+ "c:\tmp\ForceRebootBasicYes.log" The Windows Registry RunOnce entry value clearly indicates that the MSI package will be launched in Full UI (/qf) Mode. More details on MSI command line parameters can be found here.  Test Scenario# 2: The same as Test Scenario# 1, except for the user clicking No during the reboot prompt. The same Windows Registry entry gets added to the RunOnce Windows Registry entry. The only difference is that the user needs to manually restart in this scenario. After restart, the user can see the same MSI setup being launched. Test Scenario# 3: Add a compressed MSI package to the suite installer. Enable logging support under the Packages -> Package -> Common Tab with the following options selected: Enable Logging Support: Yes LogFile: SuiteForceRebootMSIYes Log Options: *v Enable logging option for the suite project as well by navigating to Releases -> Release -> Setup.exe -> Set Always Create Debug Log: Yes and  specify a Log File Name. Build the project. Launch the suite installer's setup.exe with the following command line: Setup.exe /log"C:\Log" Note: Only the log folder has to be specified, since the filename was already configured. Select Yes at the reboot prompt. The Windows Registry entry will be added under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\RunOnceEntries with a value of:                                                              "{3BC02749-19DA-4FA7-A3DC-5B172C36D7FC}" AFTERREBOOT=1 RUNONCEENTRY="!94720CB3AD917AF43ACDB571C2637D" /qN /lewuioarpcv+ "c:\tmp\SuiteForceRebootMSIYes.log"  The MSI setup starts and MsiInstallProduct returns code 1641 which means: ERROR_SUCCESS_REBOOT_INITIATED 1641 The installer has initiated a restart. This message is indicative of a success. 0x669 0x80070669   The suite installer will create a Windows Registry entry under: HKEY_CURRENT_USER\Software\InstallShield\SuiteInstallers\<Suite-GUID>\REBOOT with value 1 After restart, the suite installer will get launched and finish the execution. The MSI package will be installed silently. Test Scenario# 4: Add a compressed MSI package to the suite installer. Click No at the reboot prompt. After the user clicks No at the reboot prompt, the suite installer will be interrupted with error code 1602 from MsiInstallProduct which means: ERROR_INSTALL_USEREXIT 1602 The user cancels installation. 0x642 0x80070642   No suite installer REBOOT Windows Registry entry will be created. The suite handles this test case differently than the MSI setup. The suite installation does not take place, but the MSI installation takes place. This is because Windows Installer (MSI) handles reboots differently. After a manual reboot, the MSI package gets installed silently. But the suite installation does not take place because the suite installer assumes that the user canceled the installation. ... View more

As a courtesy Installshield provides many common Prerequistes already built and to used straight away within your project. Sometimes however a prerequisite that you require may not be available - or you may need to create your own custom prerequisite. In these cases you can use Installshield's Prerequiste Editor to create your own using the steps below: 1. Select Tools → Start Prerequisites Editor       2.Go to File→ Save as → Name the file (ex:Notepad++), save that .prq file into C:\Program files\InstallShield\2019\SetupPrerequisites. 3. Condition: 4.  Select Files to include→ click on add and browse the file which you want to add it as a prerequisites file,                                                                                    5.On the Application to run tab, Select the application you wish to launch               5.Save and close the window.         6.Go to Redistributables View- > Refresh and search notepad, now you can see the Notepad++ prerequisites available                                                                                                             ... View more

Summary: This article discusses the difference between a public MSI property and a global InstallScript variable. Public Property (Basic MSI Project): Public properties have names that contain only uppercase letters. For example, INSTALLDIR is a public property. Public properties can be specified at the command line used to launch the installation or chosen by using an authored user interface. If you are creating your own properties, use all uppercase letters if you want end-users to have access to these properties. In order to allow the end-user or administrator to change the destination via the user interface or from the command line, the Directory Identifier for the component’s destination must be a public property. Note: Only public properties have their values preserved from an installation’s user interface and User Interface Sequence to the point where the installation is changing the target system, known as the Execute Sequence. If you set the value of a property in a dialog box displayed to the end-user, use a public property (for example, MY_PUBLIC_PROPERTY) if you want its value written to a file or to the Windows Registry. The value of a public property is passed on from the User Interface Sequence (in which the dialogs are shown) to the Execute Sequence (in which the system is modified). Additionally, only public properties can be specified at the command line as parameters passed to msiexec.exe which is the main executable for running an MSI (Windows Installer) package. Therefore, make sure that you use a public property to store the value for a UI control (EditBox, ComboBox, etc.) if you want its value to be available in the Execute Sequence, for instance, if the value of this property is written to the Windows Registry. Global Variable (InstallScript Project): A global variable in the program is a variable defined outside the subroutine or function. It has a global scope means it holds its value throughout the lifetime of the program. Hence, it can be accessed throughout the program by any function defined within the program, unless it is shadowed. If you want to use the global variable in another .rul file, you have to include the .rul file which declares the global variable. Global Variable (InstallScript MSI Project): OnFirstUIAfter is called by the InstallScript engine after the MSI finishes, so you can't access MSI properties with public properties. It's possible with setting a global variable in OnFirstUIBefore and using that in OnFirstUIAfter. ... View more