https://flexeracommunity.force.com/customer/articles/en_US/INFO/Q106604 ... View more

The info at this link from Flexera Software might be of some help. They added some new functions in InstallScript to help you out. InstallScript Language Support for Windows 10 The following structure members and predefined constants were added to the InstallScript language: • SYSINFO.WINNT.bWin10—This is a new SYSINFO structure member. If the operating system is Windows 10, this value is TRUE. (This is applicable to InstallScript event-driven code; it is not applicable to custom actions.) • ISOSL_WIN10—This is a new predefined constant that is available for use with the FeatureFilterOS function and the SYSINFO structure variable. It indicates that the target system is running Windows 10. For more information, see FeatureFilterOS function and the SYSINFO structure variable. http://helpnet.flexerasoftware.com/installshield22helplib/helplibrary/whats_newIS2015.htm Chad ... View more

This seems to be working: NOT REMOVE AND NOT REINSTALL AND Installed ... View more

A Component that is not originally installed cannot be added like that. You can add Features during Maintenance mode, but you cannot add Components during Maintenance mode. Chad ... View more

The "correct" approach is probably either to create a transform that swaps out the file, or to refactor your setup such that the file is handled in some other way (perhaps as an auxiliary install, perhaps as a DuplicateFile and RemoveFile entry, perhaps something else). In general all files are either known by version (if they're an exe/dll/etc. file with a version block), or by file hash. Since XML files do not have PE version blocks, it will be hashed. I forget if mismatched hashes affect first-time installs, but they definitely have an impact on repairs, minor upgrades, and patching scenarios. ... View more

If your MSI setup is expected to run on Windows installations that still support 32-bit applications, InstallScript custom actions can still be used. As things currently stand, the only version of Windows that does not support 32-bit code at all is Windows 2016 Nano Server. However, since Nano Server also doesn't support MSI installations, this requirement is irrelevant. WOW64 support is optional on Windows Server 2008 R2 and newer, so there could be situations that these custom actions will not be able to run. However, since the majority of setup.exe based installers, including Microsoft's installers, are 32-bit, disabling the WOW64 feature runs the risk of not being able to install a number of software packages. This error can be ignored unless you absolutely need to ensure that your setup does not contain any 32-bit install time code. If this is a requirement, a 64-bit MSI DLL action should be used instead of InstallScript custom actions. ... View more

You can write a Custom Action to do that. Set your CA to run in the 'Install Exec Sequence' with a condition of REMOVE. ... View more

Installing the same component GUID to multiple different locations is a violation of component rules (see Changing the Component Code and the related What happens if the component rules are broken?). It's up to Windows Installer what it will do in this scenario, and I expect you need to change the component's GUID. ... View more

Thanks, I have successfully used the bitwise in InstallScript, Now, since Bit Operators works only for numeric values is there a way for testing MSI variable for a bit flag as a condition in a dialog event in Basic MSI project ? ... View more

You can probably try to check which files require/raised reboot @ PendingFileRenameOperations registry key in HKLM\SYSTEM\CurrentControlSet\Control\Session Manager ... View more

For any UI level the first install is a simple condition to write: Not Installed I am not certain how to distinguish from Maintenance mode and Repair mode. I looked at combinations of REPAIR and REPAIRMODE and ADDLOCAL but could not come up with something definitive. I could swear there is some sort of Msi property reference that can help with this but I could not find that reference quickly on MSDN. If you are concerned about a particular feature in maintenance mode then you could specify Installed AND !F < 3 and &F >=3 where F= For uninstall items you should only have to schedule the action in the execute sequence unless it has to affect your UI experience for some reason. If this is the case when you create the custom action you can specify that it should only run once. The property that I use to check for uninstall is: REMOVE ~= "ALL" The tilde operator is used to specify that the check should be case-insensitive. I will put in a plug for Robert D.'s excellent article for MSI tips: http://www.robertdickau.com/msi_tips.html#obf Here is another link that may help depending on your requirements. http://wyrdfish.wordpress.com/2012/07/20/msi-writing-guidelines-this-may-be-out-of-date/. Read down in this document as it has an excellent list of checking components and features states. ... View more

You can change the values using the ReserveCost table: http://msdn.microsoft.com/en-us/library/aa371226(v=vs.85).aspx ... View more

We have done this kind of thing two different ways: If you want to be able to start either install from short cuts and uninstall independently then yes change the GUID and include the release number in the program files install directory to keep the releases separate. You will be able to run either version and also uninstall either version. If you just want to keep the old version in case someone needs to go back to it then a way is toe script a directory name based on last version and create the directory in the BeforeUpdateUI procedure then copy the current files there. You could perhaps also script the creation of a shortcut for the copied version. Then you can install the new version in the normal way but the older version is still there and can be run if it is needed. ... View more

The request you are making would have to go to Microsoft. I once heard of an email alias "msiwish" but I don't know whether it's monitored. I suppose in theory we could build up some of what I just described in an ISShortcut table, but either that has to turn into Shortcut table entries, or it would lose support for, say, advertising. Although back to the original request in this thread, it's possible that the localized settings (Display Resource, Description Resource) might allow the desired behavior from resources that are updated as part of the application build, instead of either run-time or pre-installation-build. So that might be a better option than the ones I offered earlier. ... View more

I don't believe there is a way to edit this dialog with InstallShield as it is controlled by Windows Installer. ... View more