It only work with properties, not String Identifiers ... View more

I have a cached MSI file for the install and that was done because one user would log in to a Windows 7/10 PC to install and another would log in to do the uninstall or an upgrade.  This caused issues and Flexera said to cache the MSI.  Now I have the same problem as Mescalero.  I just want to remove the most recent cache folder when I uninstall.  I have tried a CA but it seems to never fire on an uninstall even though my condition is REMOVE = "ALL: ... View more

mano.n.s75 wrote: If you want the patch to update the file no matter what is installed previously, set always overwrite attribute and that will just do the work. Hi, My files are dynamically linked, so there is no "Overwrite" attribute. User has applied manual patch by replacing some files like .aspx, .css etc. Now when we run our latest patch installer, then all the files are getting updated except the manually replaced files. Please share me if you have any idea about the solution. Thanks in advance. ... 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

This looks like only occurring on my test machine. No idea why, but it otherwise works, so I can overlook this outlier. 😉 ... View more

Thank you for the links. I found that being unable to include the back-slash character after the property name in the Component destination field wasn't a problem: I was able to add the trailing character in the "Set Directory" CAs, and the directory structure on the target machine is now correct. ... View more

The EstimatedSize stored in an uninstall key in the registry was only used for display purposes in Add/Remove Programs for MSI installations prior to Windows 7. Because InstallScript MSI uses its own uninstall key for Add/Remove Programs, the size value would be ignored on any Windows version earlier than Windows 7. This could explain the behavior with InstallScript MSI (or any non-MSI installer) on Vista/2008 or earlier. ... View more

For anyone who encounters this, the problem in my case was consecutive semi-colons (i.e., ";;") in the SecureCustomProperties MSI property; removing one resolved the issue. ... View more

The problem was that I had left the subject to the default value in the merge module project. I didn't recognise it, as it was called “Blank Merge Module Project Template” in the Redistributables view. A descriptive subject field resolved it. Knew it had to be something simple. :rolleyes: ... View more

Thanks, Josh. We ended up getting round this by running the following from a command line: cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1 After that, the installation could complete. ... View more

Thanks, Hidenori, that is quite helpful. I wish there was an easier way to differentiate/isolate the instance data, as I may allow the user up to 10 or so instances of this application. But so long as there is indeed a way... 😉 Thanks again. ... View more

Glad you've got it working! ... View more

Thanks, Lurean, works great! ... View more

It was indeed due to that Shared flag being set to Yes and the application being installed elsewhere on the target system. (The first thing I had checked when I first noticed this was the "Permanent" setting. 😄 ) Thanks, Lurean for your help. ... View more

Thanks very much for the suggestions, I'll check it out! ... View more