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 --list is not a command #4045

Closed
shogerr opened this issue May 16, 2019 · 8 comments
Closed

wsl --list is not a command #4045

shogerr opened this issue May 16, 2019 · 8 comments
Labels

Comments

@shogerr
Copy link

shogerr commented May 16, 2019

As the topic states: wsl --list is not a command.

Use wslconfig /l instead.

PS C:\> wsl --list
Invalid command line option: --list
Usage: wsl.exe [option] ...
Options:
    -d, --distribution <DistributionName>
        Launch the specified distribition.

    -e, --exec <CommandLine>
        Execute the specified Linux command. The remainder of the arguments are
        used as the command line to execute.

    -u, --user <UserName>
        Run as the specified user.

    --help
        Display this usage information.

    --
        Stop parsing arguments and pass the remainder to the Linux process.
@craigloewen-msft
Copy link
Member

Hi @shogerr !

What version of Windows are you running? To find this, if you open up cmd.exe and type in ver what's the output?

@therealkenc
Copy link
Collaborator

Since the output was pasted in the OP, whatever winver, it is demonstrably a pre-18305 wsl.exe. So, same by-design closure regardless of the specifics (let's say it is 17763 for sport).

[As an aside, both wsl.exe and /init lack a --version CLI param. Not exactly a showstopping gap in functionality, but it's a longstanding convention.]

@Biswa96
Copy link

Biswa96 commented May 17, 2019

Speaking of CLI params, do we need wslconfig.exe now? Because wslconfig.exe params are same as wsl.exe.

@benhillis
Copy link
Member

Nope it will be depreciated eventually.

@SharakPL
Copy link

SharakPL commented Jun 10, 2019

Could someone explain why was this closed and labeled bydesign? Is it Microsoft's intention to use command wsl -l or wsl --list all over the docs and then block it completely in final product? Does this have something to do with switching default console terminal from bash to zsh? Should I import all rules from .bashrc to .zshrc for this to work properly?

E: nevermind. I've found out it's for next windows release which I didn't get yet

@Nakilon
Copy link

Nakilon commented Apr 20, 2022

Is it Microsoft's intention to use command wsl -l or wsl --list all over the docs and then block it completely in final product?

Yes, this is absolutely lame. The commands are in the "How to install WSL" https://docs.microsoft.com/en-us/windows/wsl/install and they just don't work. Such a Windows experience.

wslconfig /l doesn't work either.

How to make it work?! How to list my WSL instances?
Microsoft Windows [Version 10.0.19042.1645]

@Nakilon
Copy link

Nakilon commented Apr 20, 2022

It needs a reboot. Why isn't it written in docs?

@realyukii
Copy link

@Nakilon I tried to reboot but it still not work, it didn't print any error though, just print the help message instead of list something

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

No branches or pull requests

8 participants