I've authored an MSI package that uses a CustomAction to launch an application after install completes. The package requires elevation but the CustomAction is scheduled after InstallFinalize to launch the application as the Standard User, not elevated.
When installing the MSI alone using msiexec.exe, things work as expected, and my application launches correctly as the Standard User. However, we're using the WIX Standard BA bootstrapper to chain this package in a install bundle. The problem is, when this MSI package runs as part of the BA, it runs elevated, and so too does the CustomAction, which in turn launches the app elevated, which is not what we want. It seems that the BA launches msiexec.exe elevated. Is there a way to keep the BA from launching the MSI elevated? Thanks in advance, Ryan ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
