Check your event viewer. It should list what component is being triggered when the repair is executed. Also enable logging in the registry and the temp directory will contain a MSI log file I would expect. Perhaps it is not what you are expecting. I am in agreement with you, if the EXE is present and healthy, then it should not care if the associated text files are present or not present. It should only be concerned for its key file. I don't know if this will help you better debug the situation or not. ... View more

Also in the case of .Net certain versions are side-by-side products and not updates. So yes typically we test for the version we need prior to installing the package (if it is not found). Installing .Net typically takes a long time so we don't want to install it if it is not necessary. Another approach is to design the application so that it can use various version of .Net. In the simplest case this involves modifying the app.config file to support multiple versions of the framework. Then depending on which OS you target there may be a default configuration which already includes .Net. But if you target v6.1 Server class OS (or later) you will need to be prepared to install .Net using DISM.exe. (And DISM.exe should be used for configuring 6.0 or later workstation or server configurations, if needed.) ... View more

This could be made simple by making it available from the redistributal downloader in the Tools menu, but in case anyone else has this issue, you candownload and install the InstallShield 2010 Expansion Pack patch found here: http://kb.flexerasoftware.com/selfservice/documentLink.do?externalID=Q209084 The patch includes it. ... View more

These links don't work. DebbieL wrote: The following help topic explains that option: Returning a License to Your Account on the Activation Server The following help topic may also be helpful: Uninstalling and Reinstalling InstallShield ... View more

So based on your answer, it is not necessary to include MSI in my install. ... View more