Skip to content
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] 3.0.0 Beta 1 can not be started "Run as Administrator" by a standard/limited account? #1870

Closed
4 tasks done
RonnyTNL opened this issue Mar 8, 2024 · 13 comments
Closed
4 tasks done
Assignees
Labels
bug Something isn't working ready-to-go

Comments

@RonnyTNL
Copy link

RonnyTNL commented Mar 8, 2024

Please confirm these before moving forward

  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have tested that this issue has not been fixed in the latest (beta or stable) release.
  • I have checked the FAQ section for solutions
  • This issue is about a bug (if it is not, please use the correct template)

Describe your issue

As a standard user I can no longer WingetUI "Run as Administrator"
This does work when logged in as Admin account and allow UAC prompt, in that case it also shows "RUN AS ADMINISTRATOR" in the title bar.

Steps to reproduce the issue

Login as standard/limited user account, right mouse -> Run as Administrator on the WingetUI desktop Icon, nothing happens.

WingetUI Log

N/A

Package Managers Logs

N/A

Relevant information

Win10, x64

Screenshots and videos

No response

@RonnyTNL RonnyTNL added the bug Something isn't working label Mar 8, 2024
@marticliment
Copy link
Owner

Login as standard/limited user account, right mouse -> Run as Administrator on the WingetUI desktop Icon, nothing happens.

This would work on previous WingetUI versions?

@RonnyTNL
Copy link
Author

RonnyTNL commented Mar 8, 2024

On 2.2. for sure, not sure if I tested this on previous 3.x Beta/Alpha's.
But it's regular Windows behavior, I don't know any other application that won't launch as Admin when started from standard/limited user.

@marticliment
Copy link
Owner

So you are seeing the UAC prompt and then happens nothing?

@RonnyTNL
Copy link
Author

RonnyTNL commented Mar 8, 2024

No, a standard account needs elevation under a Admin userID/Password, so I get a dialog to elevate to a real admin account, no UAC involved in this use-case.

@marticliment
Copy link
Owner

This is still UAC dialog. So I undertstand the dialog still shows, but nothing happens afterwards

@RonnyTNL
Copy link
Author

RonnyTNL commented Mar 8, 2024

correct

@RonnyTNL
Copy link
Author

RonnyTNL commented Mar 8, 2024

2.2. would display this;

image

Just upgraded that machine to 3.x Beta1 and after the password dialog nothing happens.

@RonnyTNL
Copy link
Author

RonnyTNL commented Mar 8, 2024

Procmon process exit status;

image

@marticliment
Copy link
Owner

Please try running PowerToys as administrator in the same way you do with WingetUI (PowerToys uses similar libraries to WingetUI). What happens?

@RonnyTNL
Copy link
Author

RonnyTNL commented Mar 9, 2024

That works, powertoys starts as admin when launched from a limited/standard account.

@marticliment
Copy link
Owner

Hello,

I have been doing further testing, and this issue is caused by the Windows App Sdk not being compatible with the "Run as other user". Therefore, this issue can't be fixed from WingetUI. More info here: microsoft/WindowsAppSDK#2555

Please remember that WingetUI should not be run as administrator, and the ability to auto elevate operations is already there

@marticliment marticliment closed this as not planned Won't fix, can't repro, duplicate, stale Mar 9, 2024
@cjohn-murphy
Copy link

Not all applications are installed for all users. Before 3.0, it was possible to use WingetUI to update apps installed under the admin account from a standard user account by doing a run-as.

" the ability to auto elevate operations is already there"
Only for applications that are visible to the account being used.
The list of visible applications a standard user sees vs what an admin account see is different.

@marticliment
Copy link
Owner

I am afraid the App Sdk is simply incompatible with running as administrator from an account without administrator rights.
It was not my choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ready-to-go
Projects
None yet
Development

No branches or pull requests

3 participants