Frequently Asked Questions

What is Windows Subsystem for Linux (WSL)?

The Windows Subsystem for Linux (WSL) is a new Windows 10 feature that enables you to run native Linux command-line tools directly on Windows, alongside your traditional Windows desktop and modern store apps.

See the about page for more details.

Who is this for?

This is primarily a tool for developers -- especially web developers and those who work on or with open source projects. This allows those who want/need to use Bash, common Linux tools (sed, awk, etc.) and many Linux-first tools (Ruby, Python, etc.) to use their toolchain on Windows.

What can I do with WSL?

WSL provides an application called Bash.exe that, when started, opens a Windows console running the Bash shell. Using Bash, you can run command-line Linux tools and apps. For example, type lsb_release -a and hit enter; you’ll see details of the Linux distro currently running:

You can also access your local machine’s filesystem from within the Linux Bash shell – you’ll find your local drives mounted under the /mnt folder. For example, your C: drive is mounted under /mnt/c:

What is Bash?

Bash is a popular text-based shell and command-language. It is the default shell included within Ubuntu and other Linux distros, and in MacOS. Users type commands into a shell to execute scripts and/or run commands and tools to accomplish many tasks.

How does this work?

Check out our blog where we go into detail about the underlying technology.

Why would I use WSL rather than Linux in a VM?

WSL requires fewer resources (CPU, memory, and storage) than a full virtual machine. WSL also allows you to run Linux command-line tools and apps alongside your Windows command-line, desktop and store apps, and to access your Windows files from within Linux. This enables you to use Windows apps and Linux command-line tools on the same set of files if you wish.

Why would I use, for example, Ruby on Linux instead of on Windows?

Some cross-platform tools were built assuming that the environment in which they run behaves like Linux. For example, some tools assume that they are able to access very long file paths or that specific files/folders exist. This often causes problems on Windows which often behaves differently from Linux.

Many languages like Ruby and node are often ported to, and run great, on Windows. However, not all of the Ruby Gem or node/NPM library owners port their libraries to support Windows, and many have Linux-specific dependencies. This can often result in systems built using such tools and libraries suffering from build and sometimes runtime errors or unwanted behaviors on Windows.

These are just some of issues that caused many people to ask Microsoft to improve Windows’ command-line tools and what drove us to partner with Canonical to enable native Bash and Linux command-line tools to run on Windows.

What does this mean for PowerShell?

While working with OSS projects, there are numerous scenarios where it’s immensely useful to drop into Bash from a PowerShell prompt. Bash support is complementary and strengthens the value of the command-line on Windows, allowing PowerShell and the PowerShell community to leverage other popular technologies.

Read more on the PowerShell team blog -- Bash for Windows: Why it’s awesome and what it means for PowerShell

Can I run ALL Linux apps in WSL?

No! WSL is a tool aimed at enabling users who need them to run Bash and core Linux command-line tools on Windows.

WSL does not aim to support GUI desktops or applications (e.g. Gnome, KDE, etc.)

Also, even though you will be able to run many popular server applications (e.g. Redis), we do not recommend WSL for server scenarios – Microsoft offers a variety of solutions for running production Ubuntu workloads in Azure, Hyper-V, and Docker.

What Windows SKUs is WSL included in?

Windows Subsystem for Linux is available on the desktop version of Windows for the Anniversary and Creators update or later.
Beginning in the Fall Creators update WSL will be available on both the desktop and server SKUs of Windows.

What processors do we support?

We only support x64 CPUs.

How do I access my C drive?

Mount points for hard drives on the local machine are automatically created and provide easy access to the Windows filesystem.

/mnt/<drive letter>/

Example usage would be cd /mnt/c to access c:\

How do I use a Windows file with a Linux app?

One of the benefits of WSL is being able to use the same file with both Windows and Linux apps or tools.

One of the main limitations of using WSL is that changing Linux files with a Windows app or tool is not allowed. See: Do not change Linux files using Windows apps and tools

However changing Windows files with a Linux app or tools is allowed.

One way to use a Windows file with a Linux app is to use an absolute path, e.g. /mnt/c/Users/<Windows User>/Documents/Projects/<filename>.

However not all Linux apps or tools can access a file using /mnt.

A solution is to create a symbolic link.

Windows directory: C:\Users\<Windows User>\Documents\Projects Note: This directory exist.

Linux directory: /home/<Linux User>/Projects Note: This directory does not exist.

ln -s "/mnt/c/Users/<Windows User>/Documents/Projects" /home/<Linux User>/Projects

Now in WSL you can access the Windows directory as /home/<Linux User>/Projects or a specific file as /home/<Linux User>/Projects/<filename>, and if in WSL the current directory is ~ then Projects/<filename>.

Are files in the Linux drive different from the mounted Windows drive?

  1. Files under the Linux root (i.e. /) are controlled by the subsystem. This allows for Linux specific behavior including but is not limited to:

    • Files which contain invalid Windows filename characters
    • Symlinks created for non-admin users
    • Changing file attributes through chmod and chown
    • Support case sensitivity
  2. Files in mounted drives are controlled by Windows and have the following behaviors:

    • Support case sensitivity
    • All permissions are set to best reflect the Windows permissions

Why are there so many errors when I run apt-get upgrade?

Some packages use features that we haven't implemented yet. udev, for example, isn't supported yet and causes several apt-get upgrade errors.

To fix issues related to udev, follow the following steps:

  1. Write the following to /usr/sbin/policy-rc.d and save your changes.

    #!/bin/sh
    exit 101
    
  2. Add execute permissions to /usr/sbin/policy-rc.d

    chmod +x /usr/sbin/policy-rc.d
    
  3. Run the following commands

    dpkg-divert --local --rename --add /sbin/initctl
    ln -s /bin/true /sbin/initctl
    

How do I uninstall WSL?

Open a command prompt and run:

lxrun /uninstall /full

Why does ping require admin privileges?

Fixed in Build 14926 and later.

How do I run an OpenSSH server?

Administrator privileges in Windows are required to run OpenSSH in WSL. To run an OpenSSH server, run Bash on Ubuntu on Windows as an administrator, or run bash.exe from a CMD/PowerShell prompt with administrator privileges.

Why do I get "Error: 0x80040306" when I try to install?

This has to do with the fact that we do not support legacy console. To turn off legacy console:

  1. Open cmd.exe
  2. Right click title bar -> Properties -> Uncheck Use legacy console
  3. Click OK

Why do I get "Error: 0x80040154" when I run bash.exe after upgrading Windows?

The Windows Subsystem for Linux feature may be disabled during a Windows update. If this happens the Windows feature must be re-enabled. Instructions for enabling the Windows Subsystem for Linux can be found in the Installation Guide.

How do I change the display language of WSL?

WSL install will try to automatically change the Ubuntu locale to match the locale of your Windows install. If you do not want this behavior you can run this command to change the Ubuntu locale after install completes. You will have to relaunch bash.exe for this change to take effect.

The below example changes to locale to en-US:

sudo update-locale LANG=en_US.UTF8

Why do I get a Permission Denied error when using ping?

Executing the PING command no longer requires admin privileges since Build 14926.

Why do I not have internet access from WSL?

Some users have reported issues with specific firewall applications blocking internet access in WSL. The firewalls reported are:

  1. Kaspersky
  2. AVG
  3. Avast

In some cases turning off the firewall allows for access. In some cases simply having the firewall installed looks to block access.

Where can I provide feedback?

You can share feedback and ask questions through multiple channels: Feedback and questions should be directed to: