Guys, thank you so much! Finally a WSL I will love and will make me love Windows again! There was no solution with UDP applications in docker. I will try if UDP finally works and report again. THANK YOU SO MUCH!
Great set of features. Thanks for making them possible. There's an issue related to wsl and file explorer. When you pin a folder within a distro for faster access, it makes the explorer wait until wsl has loaded. It makes explorer to show blank page for that time. Haven't tested the new explorer build in insider channel.
May I ask in which specific build version are these features available for early use? After testing both the 22631.2271 build from the beta channel and the 22545.1000 build from the dev channel, the following errors have been identified. 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.
Yay, IPv6 in WSL2! The four year wait is over! It does indeed work fine on the latest Windows 11 non-insider build with WSL 2.0.6 and finally allows me to abandon WSL1. Thanks, Craig & team!
I moved away from windows because of this vmmem ram issue but I am ready to move back now. since its easier to have my windows and my Linux on hands with controlled ram
We are evaluating these first and will aim to make them generally available in the next couple of months, but our goal is to be data driven about its release.
Is there an ETA on the features being available on Windows 10 (not Insider Preview)? I'm the 3d printer and Debian developer who's been pestering for a simple networking feature like mirroring.
As things are right now, does WSL use its on `hosts` file that is separate from Windows? If true, does this new DNS tunneling feature make WSL use the Windows `hosts` file?
What SSH and NFS servers should you install if you use port mirroring and also have OpenSSH and Windows 11? Can you add a second IP in WSL to export a separate NFS/SSH server?
For 8:36 , If i host python server from my windows machine I can reach from my phone but if i host from wsl I cannot reach. I check firewall wsl allowed to communicate. What is the problem Could you help me guys?
Whats the version of this new WSL ? Also I dont have any c:\users\\.wslconfig So I presume you just create one ? Also my Task Manager does not show VmmemWSL (like yours), it only shows Vmmem.
Hold on I thought it was wsl2, as wsl used a translation layer, wsl2 runs the linux kernel. Anyway I'll call it wsl2. Can we have wsl2 PCIe device sharing please ? For example I want to dedicate 50% of my NVidia 4090 GPU to CUDA compute inside WSL2, whilst keeping the other 50% for windows rendering, or if the GPU device can not be split, then I'd like to use 100% of my PCIe GPU (4090), whilst using my APU/in-built GPU for Windows rendering. Also would like to mount NVMe SSD partitions into WSL2 directly without using Windows filesystem in the middle.
I managed to complete the instructions to configure the sparse VHD. However, when I check the volume of vhd, I see Used: 12GB Available 227 GB Is there anyway of getting some of that 227 back into Windows?
Sounds great - I can already see automemoryReclaim working - but the sparseVHD I'm not so sure about. I cleared out several hundred GB so my WSL2 reports internally at 105GB - but my vhdx on windows is stuck at 500GB still. pretty sure my ubuntu was from the MS store - not sure if that makes a difference or not.
@@tusharsnn thanks - I figured it might be something like that. I can see the size used and size on filesystem are different when I bring up properties in windows explorer. So how do I recreate the vhdx of my current installed distro? I don't really want to rebuild from scratch. I assume there is a way using wsl --backup the wsl --import
@@christianseibold3369 - it works - it's just that listing the file size of the vhdx on the windows file system seems to tell lies. I can see the overall free space on my windows drive increase when I delete big junk files - but the vhdx reports the same size. This is what was confusing me.
The feature shown at 8:38, i.e. accessing wsl from a local network isn't working for me, I'm on build 25951.1010, wsl 2.0.2, but I still get ERR_CONNECTION_TIMED_OUT from the smartphone, or even from Windows. What could I be missing?
I've just created an issue relating to this in thier github repo. It seems like in order to access WSL services/server from other devices you need to create a firewall rule within Windows to allow traffic on that port.
Which is probably never going to solved, unless Windows gets ext4 support (how likely is it?). It is "by design". I'm curious what's your use case that required you to copy files between wsl and windows so often 🤷♂️ ?
@@tusharsnn I ran a lot small Python scripts that interact with the file system (rename, hashing file content, create archive of small files, etc.) And I use Windows mainly for all GUI related applications (browser, games, drag and drop files). Windows GUI APIs are well supported and stable enough for me. However, the path seperator and shell scripting suck.
When I want to program minimal working GUI application (e.g. in Java, Python, or JavaScript), I prefer to spin up vmware, virtualbox, or bare metal installation for better compability and reduced debugging headache.
At 0:59, Craig says "code .wslconfig""in powershell, but I get "code : The term 'code' is not recognized as the name of a cmdlet, function, script file, or operable program.". What is this code command? Something related to Visual Code (which I haven't got)?
@@rescenic Thanks. But the thing is I haven't got that directory, as I have no VS Code installed my corporate laptop. So I created .wslconfig by hand in my home dir (including "networkingMode=mirrored"), started WSL (version 2.0.0), got an error that mirrored mode is not supported and using NAT instead ... TBC
@@Greeata Thanks! I used notepad to create a .wslconfig, and I bumped into the next problem: Mirrored Networking is still an Insiders Window function. So no go for me, for now at least. Thanks again.
![ปฏิเสธไม่ไหว (Crush on you) - LIPTA feat. No One Else [Official MV]](http://i.ytimg.com/vi/NBw1jF342vw/mqdefault.jpg)
This release has already solved 99% of the problems I had with WSL 👍👍 Amazing work!
Guys, thank you so much! Finally a WSL I will love and will make me love Windows again! There was no solution with UDP applications in docker. I will try if UDP finally works and report again. THANK YOU SO MUCH!
super helpful video, thank you
Great set of features. Thanks for making them possible.
There's an issue related to wsl and file explorer. When you pin a folder within a distro for faster access, it makes the explorer wait until wsl has loaded. It makes explorer to show blank page for that time. Haven't tested the new explorer build in insider channel.
Not a WSL issue by itself, but explorer, this happens if network shares are not available, makes it take ages to open
May I ask in which specific build version are these features available for early use? After testing both the 22631.2271 build from the beta channel and the 22545.1000 build from the dev channel, the following errors have been identified.
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.
ahhhhhh mirrored mode, thank you! I went down the ipv6 rabbit hole today and was wondering why WSL was giving me such grief. Problem solved!
Yay, IPv6 in WSL2! The four year wait is over!
It does indeed work fine on the latest Windows 11 non-insider build with WSL 2.0.6 and finally allows me to abandon WSL1. Thanks, Craig & team!
I hope this will work on windows 10 asap
thanks for keeping it post, craig :)
Great features
I moved away from windows because of this vmmem ram issue but I am ready to move back now. since its easier to have my windows and my Linux on hands with controlled ram
When can we expect it to be not pre-release? Can't run experimental as I do work on wsl 😥😥
P.S. Grea work! Only if I could I code like you people.
We are evaluating these first and will aim to make them generally available in the next couple of months, but our goal is to be data driven about its release.
Is there an ETA on the features being available on Windows 10 (not Insider Preview)? I'm the 3d printer and Debian developer who's been pestering for a simple networking feature like mirroring.
As things are right now, does WSL use its on `hosts` file that is separate from Windows? If true, does this new DNS tunneling feature make WSL use the Windows `hosts` file?
6:38, how did you get the correct size of the prompt arrow "->" ? It's displaying it very small on my PC.
Looks good. Curious - what's the main reason MS focuses on WSL2 right now?
Is all this coming to Windows 10 as well or Windows 11 only?
What SSH and NFS servers should you install if you use port mirroring and also have OpenSSH and Windows 11? Can you add a second IP in WSL to export a separate NFS/SSH server?
could you finally make WLS2 work out of the box behind corporate proxy?
Yes these features should address that exact concern!
@@craigloewen8379 love it ❤️ !
hi, any chance the mirrored network will be available for windows 10?
For 8:36 , If i host python server from my windows machine I can reach from my phone but if i host from wsl I cannot reach. I check firewall wsl allowed to communicate. What is the problem Could you help me guys?
Whats the version of this new WSL ? Also I dont have any c:\users\\.wslconfig So I presume you just create one ? Also my Task Manager does not show VmmemWSL (like yours), it only shows Vmmem.
Hold on I thought it was wsl2, as wsl used a translation layer, wsl2 runs the linux kernel. Anyway I'll call it wsl2. Can we have wsl2 PCIe device sharing please ? For example I want to dedicate 50% of my NVidia 4090 GPU to CUDA compute inside WSL2, whilst keeping the other 50% for windows rendering, or if the GPU device can not be split, then I'd like to use 100% of my PCIe GPU (4090), whilst using my APU/in-built GPU for Windows rendering. Also would like to mount NVMe SSD partitions into WSL2 directly without using Windows filesystem in the middle.
I managed to complete the instructions to configure the sparse VHD.
However, when I check the volume of vhd, I see Used: 12GB Available 227 GB
Is there anyway of getting some of that 227 back into Windows?
I tried DiskPart, but got an error:
"Virtual hard disk files must be uncompressed and unencrypted and must not be sparse."
Sounds great - I can already see automemoryReclaim working - but the sparseVHD I'm not so sure about. I cleared out several hundred GB so my WSL2 reports internally at 105GB - but my vhdx on windows is stuck at 500GB still. pretty sure my ubuntu was from the MS store - not sure if that makes a difference or not.
Have you recreated the vhdx? Existing distros needs to be updated.
@@tusharsnn thanks - I figured it might be something like that. I can see the size used and size on filesystem are different when I bring up properties in windows explorer. So how do I recreate the vhdx of my current installed distro? I don't really want to rebuild from scratch. I assume there is a way using wsl --backup the wsl --import
@@christianseibold3369 - it works - it's just that listing the file size of the vhdx on the windows file system seems to tell lies. I can see the overall free space on my windows drive increase when I delete big junk files - but the vhdx reports the same size. This is what was confusing me.
The feature shown at 8:38, i.e. accessing wsl from a local network isn't working for me, I'm on build 25951.1010, wsl 2.0.2, but I still get ERR_CONNECTION_TIMED_OUT from the smartphone, or even from Windows. What could I be missing?
I've just created an issue relating to this in thier github repo. It seems like in order to access WSL services/server from other devices you need to create a firewall rule within Windows to allow traffic on that port.
@@tusharsnx yes, at the end I figured it out. To say it was unintuitive is an understatement.
How to migrate to the store version?
did you mean 23H2?
Nope! 22H2. We are backporting these features. They're available right now in the Windows Insider release preview ring :)
Is this updaete now available in the stable version?
not working with win10 too good to be true :(
WSL is next.
I am still using the WSL 1 because of the copying/moving windows' files performance.
Which is probably never going to solved, unless Windows gets ext4 support (how likely is it?). It is "by design".
I'm curious what's your use case that required you to copy files between wsl and windows so often 🤷♂️ ?
@@tusharsnn I ran a lot small Python scripts that interact with the file system (rename, hashing file content, create archive of small files, etc.) And I use Windows mainly for all GUI related applications (browser, games, drag and drop files). Windows GUI APIs are well supported and stable enough for me. However, the path seperator and shell scripting suck.
When I want to program minimal working GUI application (e.g. in Java, Python, or JavaScript), I prefer to spin up vmware, virtualbox, or bare metal installation for better compability and reduced debugging headache.
Doesn't work with win 10
it depends of the feature.
"sparseVhd" does for instance
At 0:59, Craig says "code .wslconfig""in powershell, but I get "code : The term 'code' is not recognized as the name of a cmdlet, function, script file, or operable program.". What is this code command? Something related to Visual Code (which I haven't got)?
Add this path: C:\Program Files\Microsoft VS Code\bin to system environment variable.
@@rescenic Thanks. But the thing is I haven't got that directory, as I have no VS Code installed my corporate laptop. So I created .wslconfig by hand in my home dir (including "networkingMode=mirrored"), started WSL (version 2.0.0), got an error that mirrored mode is not supported and using NAT instead ... TBC
Ah: you need to have Insider Windows to have mirrored networking. Which I haven't.
"code" is just the name of the editor he uses. You could use notepad, textedit or something else you have installed instead.
@@Greeata Thanks! I used notepad to create a .wslconfig, and I bumped into the next problem: Mirrored Networking is still an Insiders Window function. So no go for me, for now at least. Thanks again.
How do I rollback pre-release version (2.0.4) to stable version(1.2.5)? wsl --update --rollback is not available for me so far