A year ago at BUILD 2020 we introduced our goal to bring Linux GUI applications to the Windows Subsystem for Linux (WSL) to run Linux GUI applications. We are proud to announce the first preview of this highly anticipated and open source feature! We’ve given this feature the nickname: “WSLg”. Please check out the video below or keep reading to see what you can use this feature for, how it works, and how to install it.
What can I use GUI application support for?
WSL lets you run a Linux environment, and up until this point has focused on enabling command line tools utilities and applications. GUI app support now lets you use your favorite Linux GUI applications as well. WSL is used in a wide variety of applications, workloads, and use cases, so ultimately, it’s up to you on what you’d like to use GUI app support for. Below, we’ve highlighted some key scenarios to help you fall in love with running applications in a Linux environment.
Use your IDE of choice to develop Linux projects
Visual Studio Code has an amazing experience using VS Code Remote to create a way for you to have a full-fledged Linux IDE directly on your Windows machine, keep extensions and settings across both Windows and different WSL distros (you can view our getting started with VS Code tutorial here. WSLg will let you run other IDEs such as gedit, JetBrains based editors, gvim, etc., to test, build, and debug your Linux applications in a performant manner.
Here’s an example of running gedit and gvim to edit Linux files directly in WSL.
Run Linux only applications, or Linux specific use cases like testing
You can use this feature to run any GUI application that might only exist in Linux, or to run your own applications or testing in a Linux environment. This could be incredibly useful for developers who want to test their cross-platform app, as they can now run it directly on Windows 10, and then easily inside of Linux without ever needing to change machines or manage a virtual machine.
Let’s look at an example of running TestCafe Studio in WSL to do some web testing from a Microsoft Edge browser running in Linux.
Build, test and use Linux applications that use audio or the microphone with built in audio support
Linux GUI applications on WSL will also include out of the box audio and microphone support. This exciting aspect will let your apps play audio cues and utilize the microphone, perfect for building, testing, or using movie players, telecommunication apps, and more.
Here’s an example of using Audacity running on Linux to record some audio and play it back.
Bonus: Leverage WSL’s GPU access to run Linux applications with 3D acceleration
As part of this feature, we have also enabled support for GPU accelerated 3D graphics! Thanks to work that was completed in Mesa 21.0, any applications that are doing complex 3D rendering can leverage OpenGL to accelerate these using the GPU on your Windows 10 machine. This will make some of your more complex applications run smoothly, such as running Gazebo, a robotics simulation tool. This experience will soon be included by default with different WSL distributions, however you can gain access to it right away by following the instructions in this blog post to get the right graphics driver and to ensure your distro has a compatible Mesa version..
Below you can see the Gazebo application simulating a robot exploring a virtual cave, as well as the Rviz application visualizing the camera feed of the robot and its laser field sensor’s output. Thanks to GPU accelerated 3D graphics we can run this demo at 60 FPS!
How does this feature work?
From the demos above, you might have noticed we didn’t need to start an X server manually. That’s because with this feature we are automatically starting a companion system distro, containing a Wayland, X server, pulse audio server, and everything else needed to make Linux GUI apps communicate with Windows. After you’re finished using GUI applications and terminate your WSL distribution the system distro will automatically end its session as well.
Like with the rest of WSL plumbing, our intention is for this component to be fully managed and seamless for users. Our intentions are for this system distro to be as invisible to the user as possible, and this is why you won’t see this system distro when you run wsl -l -v. Lastly, we’re excited to present that we are using Microsoft’s CBL-Mariner distribution for this system distro! CBL-Mariner is an internal Linux distribution used traditionally for Microsoft’s cloud infrastructure and edge products and services, and we are now extending its use to support GUI apps inside of WSL. You can view the diagram below to see an overall summary of the architecture of this feature.
For a full in depth view of what we did to make this feature possible and the deep technical details, please view this blog post written by the developers who made this feature possible.
Getting started with this feature
We are starting the rollout of this feature as an initial preview before we fully roll it into the WSL experience. To get started using Linux GUI app support, you’ll need to make sure you’re on Windows 10 Insiders preview build 21364 or higher. If you already have WSL installed, all you need to do is run wsl --update and you’ll be set to use GUI apps. If you don’t have WSL enabled, running wsl --install will install WSLg automatically as part of the initial WSL setup.
You can find the full install instructions at the GitHub repositories’ README: https://github.com/microsoft/wslg . We also highly recommend that you have GPU compute support enabled in WSL for the best performance, please see this section of the install instructions to see how you can ensure that feature is enabled.
Feedback
Please file any technical issues, or feature requests for GUI application support on the WSLg Github repository. For general WSL issues, please file them at the WSL repository. You can also follow up with me on Twitter @craigaloewen and all WSL team members that are on Twitter using this list. Please stay tuned to this blog for more exciting WSL announcements, and we can’t wait to hear what you think about this new feature.
Another great advancement from windows
it's a great tool, really. some important issues for development:
</ul
OMG this is so cool. I can barely believe my eyes! It performs much better than I would expect for a v1. Congrats
I honestly can’t wait for this feature to get out of the dev channel, since it keeps moving my taskbar every time I restart. amongst some other issues
Is it possible to run an X Window manager, or Gnome or one of the other full blown Linux desktop environments? As much as it is very cute that you can run Linux and Windows programs in the Windows environment, what I really want to do is run a full blown Linux gui environment, with all the features that entails under Windows. A few people have experimented doing this on WSL2 by running an xrdp...
"wsl - -update" returns "Invalid command-line option: - -update". - -install option returns the same error
I don't have any idea how to solve this and I couldn't find any information on Google. Any help would be appreciated.
WSL2 works normally here and I can run command-line apps and some apps that run in browser (like Jupyter Notebook) without any problem.
PS: I have enabled Insider Program and not success :(
Is there a way to start windowed programs from the shell? So far I can only do this with the Start menu.
Thanks for this great post, Craig. WSLg is looking great!
I decided to give it a go. Updated to Insiders Dev and installed WSLg using the instructions in Github.
I was able to run Gedit, Edge, Chrome, and some Cypress Tests, very nice! One thing I haven't managed to run was Android Studio. It worked, but I haven't been able to start the Emulator.
One thing I'm wondering... When WSLg we will be able to use...
when will it be available for non insiders?
I can open wireshark GUI using WSL2 however the screen resolution is smaller than the normal Windows10 apps. Is there a way to adjust it easily?
This is incredibly awesome folks – well done! 👍 How / when will this work on Windows Server? And would it work in an RDS (session host) or VDI (hosting W10) environment?