Wsl: wsl : The term 'wsl' is not recognized as the name of a cmdlet,

[geeksupport1]

Hi,

I cannot run wsl.

I have install ubuntu18.02 through windows store and running it.

I am using Window 10 home on a Corei7 4720HQ

OS build 18995.1

My windows version is
Microsoft Windows [Version 10.0.18995.1]

I have followed instructions on
https://docs.microsoft.com/en-us/windows/wsl/wsl2-install

When in powershell as admin i type in

PS C:\WINDOWS\system32> wsl
wsl : The term 'wsl' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ wsl
+ ~~~
    + CategoryInfo          : ObjectNotFound: (wsl:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

I cannot see wsl in the path
dir C:\Windows\System32\wsl*

Any hints?

I have tried all the commands in the links.
https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
https://github.com/MicrosoftDocs/WSL/issues/405

Thanks in advance.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: b19a43be-b16a-d903-b69d-75dffce6c329
• Version Independent ID: f9d4a118-1251-8d6b-43f5-2e64808dc527
• Content: Install WSL 2
• Content Source: WSL/wsl2-install.md
• Product: dev-environment
• Technology: windows-subsystem-for-linux
• GitHub Login: @craigloewen-msft
• Microsoft Alias: crloewen

[geeksupport1]

Strange as it is.

wsl -l v works in CMD but not powershell.

So issued is resolved.

wsl is visible in cmd.exe but not in powershell.

Do not know why.

The rest of the commands relating to wsl wslconfig work in cmd but not powershell.

I have restarted the PC many times.

regards

[plassa]

I have same issue where wsl works invoked from cmd.exe, but not from powershell

@geeksupport1, why did you close this?

PS C:WINDOWSsystem32> wsl
wsl : The term 'wsl' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

• wsl
• ~~~
  
  
  
  • CategoryInfo : ObjectNotFound: (wsl:String) [], CommandNotFoundException
  
  
  • FullyQualifiedErrorId : CommandNotFoundException
  
  

PS C:WINDOWSsystem32>

[timgilbert]

I was seeing the same behavior in Windows 10.0.19025.1, but after I installed an Ubuntu distribution from the MS Store, the wsl command started working for me in both Powershell and cmd.exe.

[tkr789]

I have done all of the above in Windows [Version 10.0.19041.172]. Reinstalled Ubuntu 18.04. In powershell:

> wsl -l:
wsl : The term 'wsl' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.

> wsl --set-version <Ubuntu-18.04> 2:
At line:1 char:19
wsl --set-version 2
The '<' operator is reserved for future use.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : RedirectionNotSupported

In cmd:

> wsl -l:
NAME STATE VERSION
Ubuntu-18.04 Stopped 1

wsl --set-version <Ubuntu-18.04> 2:
The system cannot find the file specified.

I have not found anything that fixes this.

[JayElOpia]

@tkr789
If this command :

Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -eq "Microsoft-Windows-Subsystem-Linux"} | Format-Table

shows you the, state as 'Enabled' while running powershell as Admin, try using the 64Bit version of Powershell (powershell 6) instead. That worked for me.

[JayElOpia]

@tkr789 For this command : wsl --set-version 2 the angle brackets shouldn't be around the OS name.

[octy40]

@JayElOpia - 64bit version worked. Thank you!

[cheater]

After installing the latest version of powershell (7.1.0-preview.7 - 2020-09-08, 64-bit version) wsl is still not being found.

[raajpackt]

same issue here.