This post has been republished via RSS; it originally appeared at: MSDN Blogs.

The next Windows update is coming soon and we’re bringing exciting new updates to WSL with it! These include accessing the Linux file system from Windows, and improvements to how you manage and configure your distros in the command line.

Accessing Linux files from Windows

In the past, creating and changing Linux files from Windows resulted in losing files or corrupting data. Making this possible has been a highly requested and long anticipated feature. We’re proud to announce you can now easily access all the files in your Linux distros from Windows.

Linux Files inside of File Explorer

The best way to get started with this feature is to open your Linux files in File Explorer! To do this, open your favorite distro, make sure your current folder is your Linux home directory, and type in:

explorer.exe .

This will open a File Explorer window, located inside of your Linux distro.

From here you can access whatever Linux files you would like, just like you would any other file through File explorer. This includes operations such as: dragging files back and forth to other locations, copy and paste, and even interesting scenarios like using the context menu to open VSCode in a WSL directory!

Improvements coming soon to the File Explorer experience

When using this feature you’ll notice the distro files are exposed through the path: \wsl$<running_distro_name>. This is due to the way Windows accesses the files inside of each distro (which you can learn the details of in the following section!) The WSL team is actively investigating ways to improve the discoverability of your Linux files inside of File Explorer.

In command line

WSL is primarily a command line tool, and so of course this feature also works in the command line. You can find your distro’s files by accessing \wsl${distro name} where {distro name} is the name of a running distro. Here’s what it looks like to access Debian with PowerShell.

How it works

To put it briefly: a Plan 9 server facilitates file related requests, with Windows acting as the client.

We’ve modified the WSL init daemon to include a Plan9 server. This server contains protocols that support Linux metadata, including permissions. There is a Windows service and driver that acts as the client and talks to the Plan9 server (which is running inside of a WSL instance). Client and server communicate over AF_UNIX sockets, since WSL allows interop between a Windows application and a Linux application using AF_UNIX as described in this post.

Known issues

This is a new feature, and some pieces of it may not work perfectly. Here are some known issues that we want to make you aware of when using this feature:

• As of right now, the distros files will only be accessible from Windows when the distro is running (We aim to add support for non-running distros in a future update)
  Since the Plan9 file server runs inside of each distro, it is only accessible when that distro is running. The team is looking into ways to help resolve this.
• Accessing Linux files is treated the same as accessing a network resource, and any rules for accessing network resources will still apply
  e.g: When using CMD, cd \wsl$Ubuntuhome will not work (as CMD does not support UNC paths as current directories), however copy \wsl$Ubuntuhomesomefile.txt C:dev will work
• The old rules still apply, you should NOT access your Linux files inside of the AppData folder!
  If you try to access your Linux files through your AppData folder, you are bypassing using the Plan9 server, which means that you will not have access to your Linux files, and you could possibly corrupt your Linux distro.

Where to file feedback

Our team is incredibly invested in hearing your feedback, in fact this whole feature was created based on our great community feedback! Please file any issues you that you may find on our Github page: https://github.com/Microsoft/WSL and we will do our best to address them.

We can’t thank the community enough for helping make WSL an amazing tool!

Improved wsl.exe command line experience

We’ve also improved the command line experience in this latest update by consolidating our commands to wsl.exe and adding more command line functionality. You can now use wsl.exe to perform all the necessary commands you would need to configure and control WSL on your machine. You can always check all the commands you can run from wsl.exe by running wsl.exe --help

New commands

We’ve also added some new commands that will give you more functionality when using wsl.exe.

You can now run commands as different users, terminate running distributions, and even export and import different distros! Exporting a distro is accomplished by passing in --export as an argument and will output a tar file of your current distro. For example, you could use this functionality to share your distro setup with other people. Additionally, if you pass in --import as an argument you can import a tar file that contains the root file system of a Linux distro, which allows you to import any distro you’d like, with any configuration you’d like.

Here is the full list of commands that we’ve added to wsl.exe.

Newly added commands

• --user, -u <UserName>
  Run as the specified user
• --export <DistributionName> <FileName>
  Exports the distribution to a tar file.
  The filename can be – for standard output.
• --import <DistributionName> <InstallLocation> <FileName>
  Imports the specified tar file as a new distribution.
  The filename can be – for standard input.
• --terminate, -t <DistributionName>
  Terminates the distribution.

Consolidated commands

The commands that existed inside of wslconfig.exe have been added to wsl.exe to allow you to configure your distros more easily. Our goal is to consolidate how you interact with WSL to a single binary.

Commands Added to wsl.exe from wslconfig.exe

• --list , -l
  Lists all distributions available on your machine
  Can also contain further options:
  • --all
    Lists all distributions, including distributions that are currently being installed or uninstalled
  • –running
    Lists only distributions that are currently running
• --setdefault, -s <DistributionName>
  Sets the distribution as default.
• --unregister <DistributionName>
  Unregisters the distribution
• --upgrade <DistributionName>
  Upgrades the distribution to the WslFs file system format.

Console improvements

The Windows Console team has also made some improvements that you’ll notice when using WSL. The Console team will post an update of what’s new in Windows 10, version 1903 very soon. Stay tuned!

Thanks and feedback

As always, we want to thank you for providing your feedback and encourage you to keep doing so! You can file issues on our Github at Microsoft/WSL or reach out to a team member on Twitter.

Here are our WSL team members who are on Twitter:

Taylor Brown @Taylorb_msft

Sarah Cooley @VirtualScooley

Yosef Durr @yosefdurr

Sven Groot @svengroot_ms

Ben Hillis @benhillis

Craig Loewen @craigaloewen

Sunil Muthuswamy @SunilMut

Brian Perkins

Palkesh Soni @sonipalkesh

John Starks @gigastarks

Craig Wilhite @CraigWilhite

We’re looking forwards to seeing the fantastic work that you’ll do with this update.

Sincerely,

The WSL Team

Q&A

• Why is the WSL resource name in the filepath called wsl$?

Since wsl is a short acronym we realize that some resources on networks may already have that name. So we’ve added a dollar sign, since a machine name can’t have a dollar sign in it, which ensures that the name will be accessible with any existing network configuration.