2.0.0

[benhillis]

• Added support for new opt-in experimental features to %USERPROFILE%\.wslconfig. For full info see the WSL docs update: https://aka.ms/wslsep2023updatedocspage
  • experimental.autoMemoryReclaim - Makes the WSL VM shrink in memory as you use it by reclaiming cached memory
  • experimental.networkingMode - A new networking mode for WSL that adds new features and improves network compatibility
  • experimental.dnsTunneling- Changes how WSL resolves DNS requests to improve network compatibility
  • experimental.firewall- Applies Windows firewall rules to WSL, and allows for advanced firewall controls for the WSL VM
  • experimental.autoProxy- Makes WSL automatically use the proxy information from Windows to improve network compatibility

[experimental]
autoMemoryReclaim=gradual | dropcache | disabled
networkingMode=mirrored
dnsTunneling=true
firewall=true
autoProxy=true

• Store WSL is now accessible from Session 0 (solves Store WSL isn't accessible from Session 0 #9231)
• All binaries shipped in the WSL package are now signed
• Introduce experimental.autoMemoryReclaim setting to %USERPROFILE%\.wslconfig
• Prompt the user to enable VMP if HNS isn't available on the machine
• Fix localhost relay failing if ipv6 is disabled
• Improve error message for WSL1 disabled policy to provide upgrade instructions
• Fix microk8s scenario for mirrored networking
• Create shared mounts when init sets up the distro namespace (solves WSL install k8s init calico err #10410)
• Detach user block devices before terminating the VM
• Protect '.wslconfig' from being incorrectly translated
• Add logic to generate a systemd unit to protect the binfmt interpreter (solves [WSL2][systemd][interop] Unable to Execute Windows Binary when systemd enabled #8843)
• Fix potential wslservice.exe crash.
• Retry plan9 mounts on IO error
• Update Microsoft.WSL.Kernel version 5.15.123.1-1
• Display a notification prompting the user to install missing optional components
• Add --manage <distro_name> --set-sparse to wsl.exe
• Fix various issues with the 'Update available' notification logic
• Update WSLg to 1.0.57
  • WSL GUI apps now have Windows snapping with the keyboard (Press WIN + an arrow key to snap to the side)
• Update MSRDC to 1.2.4485

---

This discussion was created from the release 2.0.0.

[jamietre]

Hi! The link above: https://aka.ms/wslsep2023updatedocspage just redirects to bing.com.

Edit: Looks like it's already fixed, thank you!

[craigloewen-msft]

Haha yes you caught it right away while we were still making the docs PR public :)

[peteromio]

In the devblog article it is written "autoMemoryReclaim=drop", here "autoMemoryReclaim=dropcache" which would be correct?

[onomatopellan]

I just tested and autoMemoryReclaim=dropcache is the one that actually works.

[peteromio]

ty

[craigloewen-msft]

Fixed in the article!

[wr0nggg]

How do i revert this update? docker doesnt work

[jbdamiano]

Ok I don't use docker-desktop. I used docker-ce and systemd to start the docker services.

[jbdamiano]

Issue #10497, autoMemoryReclaim=dropcache works with docker-ce as well.

[cdccentral-sourcecontrol]

Docker daemon has this error “failed to start daemon: Devices cgroup isn’t mounted”

[Mr-Bridge-0]

@wr0nggg did you end up getting the 2.0.0 update to work with docker desktop?

[ZhangTianrong]

Append cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0 to /etc/fstab and add kernelCommandLine=cgroup_no_v1=all to the wsl2 section in .wslconfig. Then, dockerd seems to be starting correctly. This workaround was mentioned here.

[daddycocoaman]

Hi. Pretty excited for this update, particularly the mirrored network. Thanks for the work. Is this update compatible with ARM64 builds?

psh ❯ type .wslconfig
[experimental]
autoMemoryReclaim=gradual
sparseVhd=true
networkingMode=mirrored
dnsTunneling=true
firewall=false
autoProxy=true

psh ❯ wsl --version
WSL version: 2.0.0.0
Kernel version: 5.15.123.1-1
WSLg version: 1.0.57
MSRDC version: 1.2.4485
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.23545.1000

psh ❯ wsl
wsl: Hyper-V firewall is not supported
wsl: Mirrored networking mode is not supported, falling back to NAT networking
wsl: DNS Tunneling is not supported

[daddycocoaman]

Insiders build --> Windows version: 10.0.23545.1000

Also, I should point out that this was after a wsl --shutdown and a reboot too.

[iosub]

Hi

Same error with the same windows version

[dducm]

Hello, same problem :

WSL version: 2.0.0.0
Kernel version: 5.15.123.1-1
WSLg version: 1.0.57
MSRDC version: 1.2.4485
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25880.1000-230602-1350.main
Windows version: 10.0.22631.2115

-> Hyper-V firewall is not supported
-> Mirrored networking mode is not supported, falling back to NAT networking

:(

[benhillis]

You need Windows version 25885 or later for the experimental networking features.

[daddycocoaman]

@benhillis That build number isn't on the chart (https://learn.microsoft.com/en-us/windows-insider/flight-hub/) but assuming that's true, then the features are only available in the Canary Channel? 😭

[iosub]

Insiders build --> Windows version: 10.0.23545.1000

Also, I should point out that this was after a wsl --shutdown and a reboot too.
Hi

Same error with the same windows version

[flundstrom2]

The million dollar question:

Is the bug #6982 which causes WSL to occupy 100% CPU finally fixed?

If not, me and hundreds of others who have commented in that thread, are going to be very disappointed.

[stephanwehr]

For me, still 100% CPU usage after upgrade to version 2.

[niemsoen]

It's unclear to me, if I can use the networkMode=mirrored with Windows 10 22H2 if I am on a Windows Insider Program channel, or whether I have to be on Windows 11. In your blog post @craigloewen-msft you say

this feature is currently only available to Windows Insiders canary and Release Preview Channel with the latest Windows 11, version 22H2

However in your youtube tutorial you say that networkingMode=mirrored is available on the Insiders Program, but don't specify the Windows version explicitly.

Does it work on Windows 10 Insider? Thank you so much for your reply :)

[craigloewen-msft]

Actually this is available only on the Windows Insiders canary channel and release preview channel right now. It will be going to Windows 11 22H2 eventually.

[crnolan]

Hi folks, bit late to this one, but does this mean there's no plan for a backport to Windows 10 for the new mirrored network mode?

[pleaselouis]

In my service program(session 0) execute command "wsl -l -v"
get response: Access is denied. Error code: Wsl/E_ACCESSDENIED

my pc: win10 professionals 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)

WSL version： 2.0.0.0
kernel version： 5.15.123.1-1

But release note said: Store WSL is now accessible from Session 0 (solves #9231)
Does anyone know why??

---

update: in my win 11 pc , The result is the same

[craigloewen-msft]

Try running wsl.exe from this location: C:\Program Files\WSL\wsl.exe if you're running in session 0.

[pleaselouis]

I still got same error code.
Access is denied. Error code: Wsl/E_ACCESSDENIED

//this is my c# code

    Process process = new Process();
    process.StartInfo.FileName = @"C:\Program Files\WSL\wsl.exe";
    process.StartInfo.Arguments = String.Format("-l -v");
    process.StartInfo.UseShellExecute = false;
    process.StartInfo.RedirectStandardOutput = true;
    process.StartInfo.RedirectStandardError = true;
    process.StartInfo.CreateNoWindow = true;

    process.StartInfo.StandardOutputEncoding = System.Text.Encoding.Unicode;

    process.Start();

    String result = process.StandardOutput.ReadToEnd();
    this.EventLog.WriteEntry(String.Format("cmd:{0} result:\n{1}\n", "wsl test", result));

    String error = process.StandardError.ReadToEnd();
    this.EventLog.WriteEntry(String.Format("cmd:{0} error:\n{1}\n", "wsl test", error));

[kingp0dd]

I am getting the same error even after running from C:\Program Files\WSL\wsl.exe

C:\Program Files\WSL>wsl.exe  --manage riserdev2 --set-sparse true
Conversion in progress, this may take a few minutes.
Access is denied.
Error code: Wsl/Service/E_ACCESSDENIED

[g2flyer]

Something in this update made reverting to an older version (1.3.11.0) failing: I get now an error "App installation failed with error message: error 0x80073D27: While processing the request, the system failed to register the windows.service extension due to the following error: The package installation failed because a version of the service exists outside of APPX ". Anybody has any idea how to overcome that error?

[ChGen]

When will be the next major public release of WSL2 in the MS Store?

[alvin-7]

The Wireguard cannot run as expected.

[nlvw]

In this case you probably need to run wireguard in Windows and not in your WSL instance. I tested this with Cisco AnyConnect and it worked pretty well.

It sounds like the new mirror mode ties the WSL instance directly to the windows networking state/stack. Which is desirable for most use cases but doesn't sound like it would be compatible with running a VPN inside of WSL itself.