public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ilya Basin <basinilya@gmail.com>
To: cygwin@cygwin.com
Subject: Re: requestedExecutionLevel "asInvoker" is ignored for setup-x86_64.exe
Date: Tue, 31 Aug 2021 18:57:43 +0300	[thread overview]
Message-ID: <c6a04bf8-7e94-1ca9-9848-87d9e46d3f67@gmail.com> (raw)
In-Reply-To: <b12f2d11-85e4-ac9e-64b1-f98194e080a8@gmail.com>

Never mind. Just found in the FAQ that the installer tries to spawn an elevated child instead of using the manifest. So in "setup-x86_64.exe -B" the "-B" switch does the trick. 

On 31.08.2021 18:38, ilya Basin wrote:
> Hi.
> I noticed that despite having:
> 
>     <requestedExecutionLevel level="asInvoker"            uiAccess="false"/>
> 
> in setup-x86_64.exe the UAC prompt is not bypassed and when I click Cancel the program is not started.
> 
> Previously I used the same binary to install Cygwin for "Just me" on a host where regular users are simply not allowed to trigger a UAC prompt.
> 
> I have downloaded some other software installers and they work as intended:
> 
>     cf7_installer.exe
>     Git-2.33.0-64-bit.exe
>     pgadmin4-5.6-x64.exe
> 
> The following env var also failed:
> 
>     set __COMPAT_LAYER=RunAsInvoker
> 
> Then I tried to un-UPX and remove the manifest with ResHacker and I also renamed "setup-x86_64.exe" to "putes-x86_64.exe" because I heard that UAC looks for keyword in .exe name without a manifest, but the resulting binary still triggers the UAC.
> 
> 
> Reproducible on:
> Windows 10 20-H2 build 19042.746
> Windows 7 sp1 buld 7601
> 

      reply	other threads:[~2021-08-31 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 15:38 ilya Basin
2021-08-31 15:57 ` Ilya Basin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c6a04bf8-7e94-1ca9-9848-87d9e46d3f67@gmail.com \
    --to=basinilya@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).