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

wsl --update --pre-release asks for admin permissions but it's hidden #11841

Closed
1 of 2 tasks
ericblade opened this issue Jul 26, 2024 · 1 comment
Closed
1 of 2 tasks

Comments

@ericblade
Copy link

Windows Version

Version 10.0.22631.3880

WSL Version

2.3.12.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

run wsl --update --pre-release when there's a new update available

Expected Behavior

When it needs admin permissions, the screen should dim, and it should prompt for admin.

Actual Behavior

The screen does not dim out, it throws a background window asking if you want to give it admin permissions. Since Windows 11 does some absolutely bizarre trash with the status bar, it is unclear that the upgrade ever asks for admin permission, unless you happen to be clicking on everything on the status bar.

Therefore, the upgrade usually fails because you haven't given permission, because you had no idea there was a window popped up asking for permission, when nearly all other operations that require admin premissions FORCE you to respond to it.

Diagnostic Logs

No response

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant