To switch the WSL store version in Windows 11, you must use the
wsl --set-version command to convert a running distribution to WSL 2. The default installation via
wsl --install often defaults to WSL 1 for compatibility reasons, which lacks features like full Linux kernel support and native SSH daemon functionality required for certain machine configurations.
Many users encounter limitations when trying to run an SSH server within their WSL instance because WSL 1 does not fully support system services or background processes in the same way WSL 2 does. While WSL 1 is faster for simple file operations due to direct access to the Windows filesystem, it cannot run a standard Linux init system. Consequently, starting an
sshd service typically fails or behaves unpredictably. Switching to WSL 2 resolves this by providing a real Linux kernel, allowing standard Linux services to operate correctly. This guide details the exact steps to identify your current version and perform the conversion without reinstalling your distribution.
Understanding WSL Versions
Before making changes, it is crucial to understand the architectural difference between the two versions. WSL 1 translates Linux system calls into Windows calls on the fly. It does not include a Linux kernel binary. WSL 2 utilizes a lightweight utility VM that hosts a real Linux kernel. This distinction is vital for developers who need to run daemons, databases, or complex networking stacks that rely on specific Linux kernel features.
If you are struggling with connectivity issues after switching, such as being unable to connect to localhost from Windows, refer to our guide on
Troubleshooting SSH WSL Machine: Can't Connect to Localhost. Networking behavior changes slightly between versions, and understanding these nuances can save significant debugging time.
Checking Your Current Version
The first step is to verify which version of WSL your current distribution is using. Open PowerShell or Command Prompt with administrative privileges. Run the following command to list all installed distributions and their states:
wsl -l -v
This output will display the name of your distribution (e.g., Ubuntu-20.04), its state (Running, Stopped, etc.), and its version (1 or 2). If the version column shows "1", you are currently using the legacy mode. Note that if your distribution is currently running, you may see a status of "Running". You do not necessarily need to stop it manually before converting, but it is good practice to ensure no critical work is lost during the transition.
Converting to WSL 2
The primary mechanism for changing the version is the
--set-version flag. This command performs an online conversion, meaning it converts the virtual hard disk while the distribution is stopped or running. For most users, stopping the distro first ensures a cleaner process.
Stop your distribution using:
wsl --terminate <DistroName>
Replace
<DistroName> with the actual name found in the previous step, such as "Ubuntu". Once stopped, execute the conversion command:
wsl --set-version <DistroName> 2
This process may take several minutes depending on the size of your virtual hard disk. The system will migrate the files from the WSL 1 format to the WSL 2 VHDX format. Do not interrupt this process. Upon completion, you can verify the change by running
wsl -l -v again. The version should now reflect "2".
Configuring Default Version
If you plan to install new distributions in the future, you might want to set WSL 2 as the default. By default, Windows 11 may still attempt to create new distros as WSL 1 unless specified otherwise. To change the global default, run:
wsl --set-default-version 2
This ensures that any subsequent installations via
wsl --install or manual imports will automatically use the more capable WSL 2 architecture. This setting applies only to new installations and does not affect existing distributions.
Post-Conversion Considerations
After switching to WSL 2, you may notice a slight increase in RAM usage. This is because WSL 2 runs inside a Hyper-V virtual machine. However, Windows manages this memory dynamically, releasing unused RAM back to the host OS. If you find that WSL 2 is consuming too much memory, you can configure limits by editing or creating a
.wslconfig file in your Windows user profile directory (
%USERPROFILE%).
For example, to limit memory usage, add the following to
%USERPROFILE%\.wslconfig:
[wsl2]
memory=4GB
swap=0
Restart WSL completely by running
wsl --shutdown in PowerShell for these settings to take effect. Additionally, if you are mounting Windows folders into your Linux environment, be aware that performance characteristics have changed. For detailed instructions on managing these mounts, see
Mounting Windows Folder in WSL (Debian) using fstab.
FAQ
Does switching to WSL 2 delete my data?
No, the
--set-version command preserves all your files, packages, and configurations. It simply converts the underlying storage format. However, always backup important data before performing major system changes.
Why does my SSH connection fail after switching?
WSL 2 uses a dynamic IP address that changes each time the VM starts. Ensure your SSH client connects to the correct IP or uses localhost forwarding properly. Check our troubleshooting guide for common localhost connectivity issues.
Can I run WSL 1 and WSL 2 simultaneously?
Yes, you can have multiple distributions running different versions. You can keep one distro on WSL 1 for fast file access and another on WSL 2 for development tasks requiring a full kernel.
How do I revert back to WSL 1?
You can reverse the process by running
wsl --set-version <DistroName> 1. This will convert the VHDX back to the older format, though it may take longer than the initial conversion.
Is WSL 2 supported on Windows 10?
Yes, WSL 2 is supported on Windows 10 version 1903 and higher with Build 18362 or later. However, Windows 11 provides a smoother experience with better integration and default settings.