1.3.14

[benhillis]

• Update Microsoft.WSL.Kernel to version 5.15.90.3-1
• Update MSRDC to 1.2.4419
• Update Microsoft.WSLg to version 1.0.55
• Fix /run/user/ being hidden when a new login session is created by symli... (solves WSL login nukes systemd/dbus user session / contents of /run/user/1000 #10205)
• Implement a --no-distribution option in wsl --install

---

This discussion was created from the release 1.3.14.

[samuk190]

auto reclaim still works on this version ?

[crramirez]

About Implement a --no-distribution option in wsl --install

It is already implemented in the built-in wsl version. Why is necessary to implement here? To install WSL1? Or you are in a case that the user installed the Store application directly without installing WSL?

Is this change associated to an issue here in the repo?

[g2flyer]

Not sure to which of above changes this is related but since upgrading from 1.3.11 to 1.3.14 on my win11 (10.0.22621) a few days ago i get notification "An Http proxy change has been detected on the host. Please restart WSL to apply the chaneg" each time my (host) vpn connects or disconnects. Besides wondering why i should have to restart WSL -- it worked before in such situations and it works since ... -- the more annoying aspect is that on vpn connects (but not on disconnects, or at least not always ..) all my X11-windows disappear, also from taskbar. As soon as i start a new x-app, e.g. an xterm, though, all re-appear but also all move to the current virtual desktop (whereas before i had them spread over several ones).

Any thoughts? I can create an issue but thought i mention it here first for some initial sights (e.g., at least if i should create issue for wslg or wsl :-)

[khusika]

Not only you :)
See #10305 (comment)

[g2flyer]

Ah, i looked at title of issues with nothing relevant and searched also issues for proxy, but i guess github search is not smart enough yet to search also text in embedded images :-) That said, i don't seem to see the original problem with the linked issue. But thanks for the link, will monitor that ...

[GXC2356]

Guys can anyone help me plz about xfce4 on wsl
at first I was facing this error ' System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Failed to talk to init daemon ' (was an issue and I wanted to solve to prevent any problem while building ROM)

After solving it (by downloading wsl app) wen I try to launch xfce 4 it says ' Starting xrdp (via systemctl): xrdp.service ' and doesn't launch in remote desktop, before it was saying ' Starting protocol server ( ok ) ' and was working fine

Can anyone help me, I will be thankful also sry if I breaked any rule I'm new here 😅

[muratyurdakul75]

wsl2 still does not support more than 64 processors. There are so many complaints about it. I hope this will be fixed in the first update.

[muratyurdakul75]

In some projects, the computer only runs wsl. Therefore, it is important that we can use more processors. My computer has 2 x E5 2698 V4 processor. But unfortunately wsl uses half of it. A computer running wsl with Docker Dosktop. He has no other job. Therefore, it would be very beneficial if we could use more processors.

[zcobol]

@muratyurdakul75 if your computer only runs wsl why not install Linux on it and take advantage of all the hardware? Running WSL on a Windows host has serious limitations.

[muratyurdakul75]

@zcobol There are 2 applications that monitor the container I use. Unfortunately, these applications can run on Windows. There are no Linux versions. That's why I have to use Windows.