Microsoft has released an updated version of Windows subsystems for Linux, known as Windows Subsystem for Linux (WSL) 2.0.0. This update brings a number of experimental capabilities, primarily focusing on memory management and network settings. The WSL allows users to run Linux directly within the Windows interface, without the need for additional software.
One of the key features of the new version is “Automatic Memory Reclaim,” which is implemented through a virtual machine. This virtual machine acts as a “second computer” within the main system, allowing for more efficient memory usage.
Another important addition is the “Sparse VHD” option, which automatically compresses the size of the virtual hard drive in WSL. This feature is particularly useful for saving space on physical storage media.
WSL 2.0.0 also introduces a new networking mode called “Mirrored Mode Networking,” which supports modern standards such as IPV6 and Multicast. This mode simplifies the use of VPNs and enables connections to virtual machines from the local system.
Craig Loewen, the WSL project lead at Microsoft, highlights the “DNS Tunneling” function, which improves the method of recognizing internet addresses and makes it more resistant to diverse connection conditions. This means that the system can determine the correspondence between a site’s name and its address without requiring additional information exchange.
The Hyper-V Firewall security mechanism in WSL now automatically applies the same filtering rules for internet traffic as the main Windows system, protecting the network from unauthorized access. Additionally, the “Autoproxy” feature syncs proxy server settings between Windows and WSL, simplifying internet connection in various environments.
It’s important to note that some of these experimental tools are currently only available to participants in the Windows Insiders program using the latest Windows 11 22H2 build, version 22621.2359 (KB5030310).
For more information on the new version of Windows Subsystem for Linux, you can visit the official Microsoft blog post or the project’s GitHub page.