Hmm, that's interesting. And you have definitely configured the install package to use the setup.exe launcher? You shouldn't have to apply any setting; it automatically displays that message when you use the setup launcher but leave the files uncompressed. If you search the string table for the message I quoted earlier (or just search for "setup.exe"), you will see where it is stored. If you have configured the installer to use setup.exe, and can still run the install via the msi, then I am at a loss. Maybe someone else out there has seen this. Could you in that case consider compressing everything into setup.exe? ... View more

When the user double-clicks on the msi file, they don't see the message "This installation cannot be run by directly launching the MSI package. You must run setup.exe."? We've distributed a few basic MSI installs like this (using the setup.exe launcher but leaving the files uncompressed), and I haven't encountered this problem--the user sees the aforementioned message and can't proceed if they try to launch the install via the .msi file. ... View more

Hi, That's precisely what I ended up doing. Thanks for your input! I just need to be kept in the loop when production distributes these patch versions. :rolleyes: ... View more

I would put it after Cost Finalize in the UI sequence, but I often find myself playing around with sequencing my CAs because I haven't yet got a good grasp on it, so please take that suggestion with a pinch of salt. 😉 And again, disabling this constant may make not a difference on the Program Files folder. Let us know how it goes... ... View more

Hi Tim, Using Disable(WOW64FSREDIRECTION) in an Installscript custom action might allow for this. The documentation mentions that this constant applies to the Windows system folder, but it may be worth a shot in this case, too. ... View more

Has anyone run into this situation? ... View more

I'd love to see automatic "clean up" of an installation's locally cached msi during Remove and Major Upgrade. I've added a CA to take care of this during an uninstall, but in the case of performing major upgrades, these pile up. It's almost inevitable that some of our end users (or at least their system admins) are going to complain about this use of disk space. ... View more

For the custom action, defining "Not Installed" for the Condition explicitly states that the CA is to execute only during a first-time install. That should resolve your issue... ... View more

Hi Tim, Absolutely, I'll let you know if I learn anything new on this. Thanks for your response... ... View more

Hello, is there any update as to whether patches can be chained? I have a situation similar to Tim's: we would like to distribute a service pack as one tidy Update.exe file rather than multiple Update.exes for each installation. Thanks for any help. ... View more

Well, the user can alter INSTALLDIR during the first-time installation, and though the default setting is the x64 Program Files directory, someone decided to install under PF (x86), leading to this. But yes, henceforth, installing under (x86) will not be permitted. ... View more

Hi Snip, Yes, I am including some system DLLs with this install. It's for backwards compatibility for some old VB apps that are still included with this (Java) application. That aspect certainly needs a look-see. However, I disassociated these file components from the parent features, so that they did not install, and still the over-all application does not get removed. Oddly, if I pick a random component ID such as the following: Disallowing uninstallation of component: {8652057E-EB78-7955-3971-B8E632457783} since another client exists. and then search for that component GUID earlier in the log to see which file component that is, it does not exist. I have no idea what that component is. I am using dynamic file linking, which may have something to do with it. Thanks for your questions and observations. ... View more

Hi, The components are not marked as permanent. I have attached the log file, thank you. ... View more

Hi Vijay, thanks. Yes, and the INSTALLDIR has the correct value, i.e., C:\Program Files (x86)\ . I'm just not sure what the problem is. ... View more