Hi, We have a retail installation package (InstallScript MSI) with multiple embedded setup types which is typically installed in large corporate environments.  Some setup types interact with a service and require elevated/administrative permissions to do their thing, while others do not...   Ideally we don't want to force all end-users to "run as administrator", as the majority will run the more benign setup type that doesn't require elevated privileges -- we'd hate for all these folks to have to engage IT just to install our product.   Is there a way to allow for dynamic administrative elevation during the install process, depending on the setup type the end-user chooses?   Perhaps some sort of scripting functionality which would popup a UAC box and allow the installation to continue on with elevated permissions? Or is this simply not how UAC works?  Does elevation absolutely have to occur prior to running any executable code in setup.exe in order to properly manage the process? Any insight is greatly appreciated! Thanks, Tim ... View more

Our installation deployment contains a significant amount of PII (personally identifiable information)...  In the past we've been wrapping our installers in WinZip to take advantage of AES-256 encryption with a random 16-character password, then wrapping the Zip as a self-extracting EXE.  This adds a lot of unnecessary steps and overhead to our build processes, and makes installation a bit less elegant for our end users... We've recently upgraded from InstallShield 2015 to 2019 so I'll ask once again, as I have for the past 15 years...  has a secure encryption mechanism finally been implemented?   ... View more