You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the end of installation, you are given an option to run the program. However the program is run as an administrator user, rather than the user that initially launched the installer.
@ccw808, do you mean "Run DB Browser for SQLite" checkbox on "Complete DB Browser for SQLite Setup" page?
I think it is standard behaviour when you run the application from the NSIS installer.
New process inherits permissions from the parent process - in this case installer, which was elevated using Windows UAC.
Possible solution: get rid ability to run the app from installer.
It would probably an easy fix if we had a standalon NSIS script, but our script is generated by CMAKE/CPACK and there are some settings and variables that can be tuned, but I didn't have time to look at them.
Activity
justinclift commentedon Jun 3, 2015
Oh, that doesn't sound good. Which OS are you using, and which version of DB4S?
ccw808 commentedon Jun 3, 2015
Windows 7 64 bit and version 3.6.0
schdub commentedon Jun 3, 2015
@ccw808, do you mean "Run DB Browser for SQLite" checkbox on "Complete DB Browser for SQLite Setup" page?
I think it is standard behaviour when you run the application from the NSIS installer.
New process inherits permissions from the parent process - in this case installer, which was elevated using Windows UAC.
Possible solution: get rid ability to run the app from installer.
ccw808 commentedon Jun 3, 2015
The UAC plug-in for NSIS has a UAC_AsUser_ExecShell macro which can be used instead of ExecShell
justinclift commentedon Jun 4, 2015
Ahhh, that sounds like it might do the trick. @rp- Sounds like an easy fix?
rp- commentedon Jun 9, 2015
It would probably an easy fix if we had a standalon NSIS script, but our script is generated by CMAKE/CPACK and there are some settings and variables that can be tuned, but I didn't have time to look at them.
chrisjlocke commentedon May 2, 2017
Posted this in #974, so a bit of cross-posting.... ;)
This might help.
http://stackoverflow.com/questions/16555625/how-to-launch-an-executable-on-the-end-of-installation-correctly
Launch DB4S as user not Admin for Win installer
justinclift commentedon May 2, 2017
In theory 😉, that last commit should mean the installer launches DB4S in user mode, not admin mode.
In testing here in a local VM it seems to work ok, but it'd be useful to have other people test and confirm it before I'm confident about it.
@ccw808 @chrisjlocke Would either of you have the time/interest in trying tomorrow's nightly build (3rd May or later) to check?
chrisjlocke commentedon May 3, 2017
Will do. 😸
chrisjlocke commentedon May 3, 2017
Now works fine. 🥇
justinclift commentedon May 3, 2017
Thanks @chrisjlocke, really appreciate you taking the time for this. 😄