Wsl: wsl --set-default-version 2

[CeciAc]

Hi team,
I moved this from here: https://github.com/MicrosoftDocs/WSL.zh-CN/issues/16

The comments below were machine-translated

@alabohai commented 10 hours ago — with docs.microsoft.com

This command is not valid.
PS C: slwsl--set-default-version 2
Command-line option sits invalid: --set-default-version
Copyright (c) Microsoft Corporation. All rights reserved.

Usage: wsl.exe (parameters) (options... ) (CommandLine)

Arguments for running Linux binaries:

If no command line is provided, wsl.exe starts the default shell.

--exec, -e and commandLine
Execute the specified command without using the default Linux shell.

---

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

[cotneit]

Your version of Windows doesn't support WSL 2. For now, it's only available in Slow ring of Windows Insider builds (Current version - 2004, OS Build 19041).
You can check your version of Windows by running "winver" (without quotes) in cmd or Run window.

As far as I know, version 2004 is expected to be released to public in May 2020.

[liuyongAlive]

Execute wsl --set-version 2 in cmd, only the following prompts are not effective.

Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2

When cmd was executed as administrator, the command worked.

[OvrCafn8d]

@cotneit - you mention that 19041 is required but the page says 18917.. I also found that I could not execute wsl -l -v until i moved myself to the insiders ring as the verbose option was not being recognized.

[JDoes]

Are there videos of this being done successfully? I dont think these instructions are correct. I would like to see it actually happen with my own eyes. Gotta see it to believe it.

[cotneit]

@OvrCafn8d page says "build 18917 or higher", I meant that current Windows Insider build in the Slow ring is 19041.

[OvrCafn8d]

Ugh.. I got mixed up with version and build numbers for windows.

[parkerault]

~@cotneit I'm having the same issue and I'm on the required build number.~

~I have all the correct features turned on and I have virtualization enabled in the BIOS (I've been using several other VM platforms without issue):~

~Edit: I also tried turning Hyper-V features on in case that was the problem, but it still doesn't work.~

Edit: I discovered that my BIOS had two different settings for virtualization, one in the CPU "Virtual Machine Support" and another in advanced settings "VT-d". Turning on VT-d solved the issue.