User Experience Changes Between WSL 1 and WSL 2

This page goes over the user experience differences between WSL 1 and the WSL 2 preview. The key changes to be aware of are:

  • Place files that your Linux apps will access in your Linux root file system for faster file performance speed
  • In initial builds of the WSL 2 preview you will need to access network applications using an IP address and not using localhost

And below is the full list of other changes that you may notice:

  • WSL 2 uses a Virtual Hardware Disk (VHD) to store your files and if you reach its max size you may need to expand it
  • When starting, WSL 2 will now use a small proportion of memory
  • Cross OS file access speed will be slower in initial preview builds

Place your Linux files in your Linux root file system

Make sure to put the files that you will be accessing frequently with Linux applications inside of your Linux root file system to enjoy the file performance benefits. These files have to be inside of the Linux root file system to have faster file system access. We have also made it possible for Windows apps to access the Linux root file system (like File Explorer! Try running: explorer.exe . in the home directory of your Linux distro and see what happens) which will make this transition significantly easier.

Accessing network applications

In the initial builds of the WSL 2 preview, you will need to access any Windows server from Linux using the IP address of your host machine.

Accessing Windows applications from Linux

To access a Windows network application you'll need to use the IP address of your host machine. You can do so with these steps:

  • Obtain the IP address of your host machine by running the command cat /etc/resolv.conf and copying the IP address following the term nameserver.
  • Connect to any Windows server using the copied IP address.

The picture below shows an example of this by connecting to a Node.js server running in Windows via curl.

Accessing Linux network applications from Windows

Accessing Linux applications from Windows (only in builds lower than 18945)

If you have a server in a WSL distro, you'll need to find the IP address of the virtual machine powering your distro and connect to it with that IP address. You can do that by following these steps:

  • Obtain the IP address of your distro by running the command ip addr inside of your WSL distro and finding it under the inet value of the eth0 interface.
    • You can find this more easily by filtering the output of the command using grep like so: ip addr | grep eth0.
  • Connect to your Linux server using the IP you found above.

The picture below shows an example of this by connecting to a Node.js server using the Edge browser.

Accessing Linux network applications from Windows

If your build is 18945 or higher, you can use localhost just like normal.

Other networking considerations

When using remote IP addresses to connect to your applications, they will be treated as connections from the Local Area Network (LAN). This means that you will need to make sure your application can accept LAN connections, i.e: You might need to bind your application to instead of For example in python using flask this can be done with the command:''). Please keep security in mind when making these changes, as this will allow connections from your LAN.

Understanding WSL 2 uses a VHD, and what to do if you reach its max size

WSL 2 stores all your Linux files inside of a VHD that uses the ext4 file system. This VHD automatically resizes to meet your storage needs. This VHD also has an initial max size of 256GB. If your distro grows in size to be greater than 256GB you will see errors stating that you've run out of disk space. You can fix these by expanding the VHD size. Instructions on how to do so are below:

  1. Terminate all WSL instances using the wsl --shutdown command
  2. Find your distro installation package name 'PackageFamilyName'
    • In a powershell prompt (where 'distro' is your distribution name) type:
      • Get-AppxPackage -Name "*<distro>*" | Select PackageFamilyName
  3. Locate the VHD file fullpath used by your WSL 2 installation, this will be your 'pathToVHD':
    • %LOCALAPPDATA%\Packages\<PackageFamilyName>\LocalState\<disk>.vhdx
  4. Resize your WSL 2 VHD by completing the following commands
    • Open a command prompt Window with admin privileges and run the following commands:
      • diskpart
      • Select vdisk file="<pathToVHD>"
      • expand vdisk maximum="<sizeInMegaBytes>"
  5. Launch your WSL distro
  6. Make WSL aware that it can expand its file system's size
    • Run these commands in your WSL distro:
      • sudo mount -t devtmpfs none /dev
      • mount | grep ext4
        • Copy the name of this entry, which will look like: /dev/sdXX (with the X representing any other character)
      • sudo resize2fs /dev/sdXX
        • Make sure to use the value you copied earlier, and you may need to use: apt install resize2fs.

Please note: In general do not modify, move, or access the WSL related files located inside of your AppData folder using Windows tools or editors. Doing so could cause your Linux distro to become corrupted.

WSL 2 will use some memory on startup

WSL 2 uses a lightweight utility VM on a real Linux kernel to provide great file system performance and full system call compatibility while still being just as light, fast, integrated and responsive as WSL 1. This utility VM has a small memory footprint and will allocate Virtual Address backed memory on startup. It is configured to start with a small proportion of your total memory.

Cross OS file speed will be slower in initial preview builds

You will notice slower file speeds compared to WSL 1 when accessing Windows files from a Linux application, or accessing Linux files from a Windows application. This is a result of the architectural changes in WSL 2, and is something that the WSL team is actively investigating on how we can improve this experience.