Ah, that sounds like you have an explorer window open in the release folder where the intermediate files are built. ... View more

You need to speak to Flexera tech support and ask them to de-register the old version.  It is a pain, I've had this happen a couple of times over the years, but they are usually very quick at responding to this and I don't think this requires a maintenance agreement with them. ... View more

The warning dialog box should be generated with a "SpawnDialog" event (as opposed to a "NewDialog").  That will leave the originating dialog in play.  Then when you click the OK button it's behaviour event needs to be set to EndDialog|Return ... View more

You have it open twice, shut the other one down first. ... View more

You haven't provided anywhere near enough information to answer this question properly, but it has to be one or more issues with either the version numbers of the files or the upgrade settings you are running. I'm not sure why the IDE mode works, but it is a red herring, the only thing that matters is whether your release builds work. I suspect the IDE runs in Major Upgrade mode, but you've got your release builds set to Minor or something else. Questions: . Are you running a major or minor upgrade? . Have you spun the Package and Product GUIDs? . Is the Upgrade GUID identical between the two releases . What are the relevant versions of the files being installed, compared to the existing files. . Does an upgrade actually run when you run the release or does it look like a fresh install? . Are you using the upgrade setting: "Completely uninstall old setup before installing new setup" . Are you running in UI mode or silent mode? . Have you logged the install? ... View more

Thanks for the response Jenifer. I am familiar with what should happen and I did compare the logs of a working machine versus non working one (although it stated it had completed successfully), which is how I determined that the non working one didn't think any of the features were installed. What I needed was the nut and bolts of how the MSI engine determined which features were installed and after further investigation I found that it was a set of registry settings namely. [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features\<MangledProductGUID>] "<TopLevelFeature>"="" "<SubFeature>"="<TopLevelFeature>"   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<MangledProductGUID>\Features] "<TopLevelFeature>"="<HugeRandomStringOfCharacters>" "<SubFeature>"="<HugeButDifferentRandomStringOfCharacters> <TopLevelFeature>" Where <MangledProductGUID> = 42E15F854475F1D41AD1B0543CC43EFA instead of {58F51E24-5744-4D1F-A11D-0B45C34CE3AF} On a bad machine I found the second set of entries missing, while the first set of entries appeared corrupted as follows: [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features\<MangledProductGUID>] "<TopLevelFeature>"="[ACK]" "<SubFeature>"="[ACK] <TopLevelFeature>" Further investigation found that the apparant corruption was the unicode character ACK, which is actually a valid entries used by the MSI engine to indicate that a feature in not installed. It appears that the entries for all features are added to the registry with the ACK character flagging which ones aren't installed. However, it doesn't seem possible or shouldn't be possible to have the MSI engine flag the <TopLevelFeature> as not installed. Attempting to install the product on a fresh machine and choosing no features on the CustomSetup dialog results in no install of the product, rather than a featureless install, even though the install runs to completion. At this point I don't think the problem is in the installer but an environmental issue. The problem has happened on about 100 out of 800 machines on a single customer with the last upgrade sent out. This customer installs the product via a GPO process. Other customers have no problem and some of them also use a GPO process. Although a second customer did initially report issues this turned out to be on a single machine with an unrelated problem. However, my Support department are coming to me for answers. But although I can now manually replicate the problem, I can't explain how the customer machines got into that state in the first place and the customer is adamant that there is nothing wrong with their environment. ... View more

For point 2, the error is in the String table, not the directory table. Now all strings IDs that begin ID_STRING... have been created by your actions, although you might not be aware of them at the time. When you create a variety of elements (some of which may be entries in the Directory table), InstallShield automatically adds an entry into the String table with this default ID which you can and should change to something more meaningful. Obviously you have only added this particular string in this one project, hence why other projects don't encounter the error. Just go to the string table track it down and it should be fairly obvious what is wrong. Typically you have got an excess opening or closing bracket without the corresponding opposite bracket. ... View more

The only thing I can think of that might be causing the difference in behaviour between the two installers could be the setting for "Required Execution Level" Releases View -> Setup.exe tab -> Required Execution Level ... View more

Continue to do what? If your package is a downgrade, do you want to disable downgrade prevention? If so remove the upgrade item called "PreventDowngrade" \ "ISPreventDowngrade" or the associated Error CustomAction of the same name. If you just want the installer to run to completion without showing an error message, but actually do nothing. Well that is really quite a complicated set of changes that is required and quite ridiculous too. I would never recommend attempting this. ... View more

This is a very poorly worded description, please elaborate, are you trying to upgrade or not. Have you Spun the correct GUIDs and Version number fields, did you create an Upgrade item. Do the individual files have version numbers and if so have they changed between each installation. If this is a Major Upgrade what "Major Upgrade Settings" policy have you set? ... View more