-
-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Ask Only Once For Administrator Priviledges Broken #3297
Comments
The prompts you are seeing are from UniGetUI Elevator or from the package installers themselves? |
I get the UAC prompt from UniGetUI, but then I also get UAC prompts for
each individual package being installed. So to answer your question, I get
both. The first one from UniGetUI used to be the only one I'd see.
…On Wed, Feb 12, 2025 at 9:14 AM Martí Climent ***@***.***> wrote:
The prompts you are seeing are from UniGetUI Elevator or from the package
installers themselves?
—
Reply to this email directly, view it on GitHub
<#3297 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXQ44XDDZW2GCEEKX3CJJT2PNJKXAVCNFSM6AAAAABW7W6XXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJTHAZTCNZUHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
But those prompts, what do you see on the screen? Do you see the UniGetUI Logo, with the text "UniGetUI Elevator", or you see the name and logo of the package being updated at the time? |
I see the UniGetUI elevator first, then I see the name and logo of each
individual package being updated. This is pretty easy to test. Steps are
laid out in the ticket. I've tested on multiple machines, including brand
new Windows installs, same behavior. It's done this the past few versions.
Prior to that, I'd only see the UniGetUI elevator prompt and that's it.
…On Wed, Feb 12, 2025 at 9:20 AM Martí Climent ***@***.***> wrote:
I also get UAC prompts for each individual package being installed. So to
answer your question, I get both. The first one from UniGetUI used to be
the only one I'd see.
But those prompts, what do you see on the screen? Do you see the UniGetUI
Logo, with the text "UniGetUI Elevator", or you see the name and logo of
the package being updated at the time?
—
Reply to this email directly, view it on GitHub
<#3297 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXQ44V3FZK4BGHVTANTOKL2PNKC7AVCNFSM6AAAAABW7W6XXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJTHA2DQNRRHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'll have to let you know when I have multiple updates again.
…On Wed, Feb 12, 2025 at 9:31 AM Martí Climent ***@***.***> wrote:
When updating the packages, do you see a "shield" logo on the left side of
the operations?
image.png (view on web)
<https://github.com/user-attachments/assets/37f9da60-9e4c-4930-b981-eecd30863fdc>
—
Reply to this email directly, view it on GitHub
<#3297 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXQ44TGXQZ2QWEWHMQM5LT2PNLKPAVCNFSM6AAAAABW7W6XXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJTHA3TQOBXHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Please confirm these before moving forward
UniGetUI Version
3.1.6
Windows version, edition, and architecture
Windows 11 Pro 10.0.26100.2894 x64
Describe your issue
I have the option to "Ask only once for administrator priviledges" when updating multiple winget packages, however, I am getting a UAC prompt for each individual package. I've tested on a machine that had Unigetui updated and another machne that was a fresh install (brand new Windows install). Same behavior on both.
Steps to reproduce the issue
Enable the "Ask only once for administrator priviledges" option, upgrade multiple packages at once, get multiple admin/UAC prompts.
UniGetUI Log
Package Managers Logs
Relevant information
This used to work perfectly on an earlier build, but the last few releases have broken this feature.
Screenshots and videos
No response
The text was updated successfully, but these errors were encountered: