The Initial Preview of GUI app support is now available for the Windows Subsystem for Linux
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.
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.
The integration has certainly come a long way. I can see FreeRDP in there, does that mean it’s been extended to allow contact with the GPU ? I guess there is some new channel in there so that something like DMABuff works through it ?
For WSLg v1 we interop with Mesa/GPU through system memory (wl_shm)… so no DMABuff/EGLStream/etc…
We did extend FreeRDP to support a new VAIL (Virtualized Application Integrated Locally) protocol (called GrfxRedirection) that allow us to share system memory buffer between the guest and host so we don’t have to copy pixels over the RDP transport when the RDP server and client are physically on the same system, separated by a VM boundary. See https://devblogs.microsoft.com/commandline/wslg-architecture/ if you are interested in more details.
This is awesome! I preffer Windows 10, but it is also good to be able do use Linux and some tools that run on Linux. WSL is great.
Note that this build is only available on the Dev channel of the Windows Insiders program at the moment of writing this.
Thank you for telling!
Where can I get it
This is great progress!
That “wsl –update” is in PowerShell running as administrator, right? I tried it in the Ubuntu command line and it said I needed to install “wsl”.
when running windows executables from distros you need to add the .exe at the end of the command name
correct, you want to run “wsl –update” from an elevated command prompt or powershell console in Windows and not in Ubuntu.
If you already have WSL running, you’ll want to do “wsl –shutdown” to stop WSL and ensure none of the underlying file are in used before pulling the update. If you don’t shutdown WSL and the file are in use, the update will be stage and you’ll be asked to reboot before the change takes effect… so doing a pre-emptive wsl –shutdown can avoid you a reboot :-).
It seems the –update option is not available in WSL. What could be the reason? wsl –update dumps the manual for wsl command.
(Sorry, I come from Linux world and doesn’t have exposure to Windows world).
Are you in the Windows Insider Dev Channel? If I remember correctly the new WSL features like –update and –install are only available on recent dev channel builds.
No. That explains why I’m not seeing these options in my WSL. Thanks for the quick reply.
I mostly use x server with wsl to sync my clipboard. So if I yank or paste in vim it plumbs all the way up to windows as well. Does WSLg also sync clipboard?
yeah, WSLg support clipboard for a few different data format (plain text, html, bitmap)
Sadly i’m getting a problem, whenever i try to enter text on any of the GUI applications, the keyboard is all messed up…
Thank you for opening an issue on our github project for this (https://github.com/microsoft/wslg/issues/27), looks like you got it working after installing the gnome ui packages. Today WSL distro were built for headless/console and typically don’t pre-install UI packages like X keyboard layout. This is something we’re looking at improving in the future.
This is great. Only recently I was struggling to build desktop apps with electronjs on wsl but due to the unavailability of GUI for wsl couldn’t.
Now just looking forward for the windows update 👍🏼
Wow, now we could run WINE on Windows.
Hahaha! xD 🙂
Better than Docker in Docker. That’s real inception here 😀
you definitely can run WINE… Here’s Scott running an old version of IE in WINE in WSLg… because why not 🙂
But why stop there…
Any chance to see CBL-Mariner turning in a future basis for a new Xenix distro?