View forum topic

I've been developing the installer for my application for the last several days, which includes using the updater to check for and install updates to my application. Up until recently, update.exe would not trigger the UAC prompt. Now all of a sudden it does, but I haven't changed anything in my Update Script, so it's a bit puzzling why it's appearing all of a sudden.

The only thing about my installer itself that I suspect may have led to a higher level of scrutiny by UAC is that I had it delete a couple of shortcuts from the desktop and the Start Programs menu that were left over from an older version of my application but are now obsolete. But I don't know why this would cause update.exe to trigger a UAC prompt, rather than just my Setup.exe. I rebuilt my installer without having it delete those shortcuts, but update.exe still triggers the UAC prompt.

I can handle requiring my users to answer a UAC prompt when they install updates, but not every time they run update.exe. Any insight would be much appreciated.

I got past the problem by selecting "Administrator rights are not required" for the Update Script. I never had that option selected before, though, so I'm not sure why the UAC prompt didn't appear earlier when I tried to run setup.exe.

Oops, I mean, I'm not sure why the UAC prompt didn't appear earlier when I tried to run UPDATE.EXE.

By default, Update Script - Update root has the checked 'Adminstrative rights are not required'.
The previous versions of CreateInstall created update.exe without UAC, by default too.

I see that when I create a new installer project, which is how I created the one I've been using (rather than converting one from an older version). Odd. I don't know how it got turned off, since I don't remember touching it.