On Tue, 18 May 2021 at 10:13, Marco Atzeri via Cygwin wrote: > > On 17.05.2021 23:12, Jason Pyeron wrote: > >> -----Original Message----- > >> From: Jon Turney > >> Sent: Monday, May 17, 2021 4:41 PM > >> > > > > > My real issue was the user was not an admin - doh! > > that could be due to "setup" in the program name. > > It is one of the "security" ideas of MS
I believe it's nothing to do with the program name, and everything to do with how the UAC permissions work: if you run the setup program with the -B argument so it won't check it's running with Administrator permissions, or run it from a parent process that already has Administrator permissions, you'll get the behaviour you might expect. If you run it without -B and from an unelevated context, then the installer will elevate to Administrator before it does anything else, and that means the calling context -- cmd or anything else -- won't get any feedback from the installer, so it returns straight away. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
