cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
nectar
Level 2

Non-admin updates

We have recently succeeded in making our InstallShield project for an existing product output an MSI (and setup.exe) that can run without admin privileges. However, using a setup.exe of a further version to perform an upgrade fails. It seems that the MSI wrapped within the original install is still on the system, and trying to access it causes UAC to kick in with an admin prompt. We have tried different settings:

- Using the user's app data instead of ProgramData still caused the prompt.

- Removing MSI caching made it go to the Temp folder instead, but it's still there and the upgrade still tries to read it, prompting.

- We have an EV certificate we use to sign our deployment files, however it seems that signing the Setup.exe will not sign the MSI wrapped within.

- Using the Signing tab within the Releases section with an ordinary certificate yielded no improvement.

Labels (2)
0 Kudos
(0) Replies