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 2.4.x is not showing which is the default distro (Regression) #12302

Closed
2 tasks
crramirez opened this issue Nov 20, 2024 · 4 comments
Closed
2 tasks

WSL 2.4.x is not showing which is the default distro (Regression) #12302

crramirez opened this issue Nov 20, 2024 · 4 comments

Comments

@crramirez
Copy link
Contributor

crramirez commented Nov 20, 2024

Windows Version

Microsoft Windows [Version 10.0.26100.2033]

WSL Version

2.4.4.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

PS > wsl echo '$WSL_DISTRO_NAME'
MyPengwin
PS > wsl --set-default WLinux
The operation completed successfully.
PS > wsl echo '$WSL_DISTRO_NAME'
WLinux

PS > wsl --list --verbose
  NAME                      STATE           VERSION
  MyPengwin                 Running         2
  WLinux                    Running         2
  docker-desktop            Stopped         2
  docker-desktop-data       Stopped         2
PS > wsl --status
Default Version: 1

Expected Behavior

wsl --list --verbose should show an asterisk next the name of the default distro
wsl --status should say the name of the default distro

Actual Behavior

The default distro does not show neither --list or --status commands

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'.

@borjamunozf
Copy link

Yes, I can confirm:

Image

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

@benhillis
Copy link
Member

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

4 participants