It's been quite a while since WSL is hitting mainstream. Less people need help getting it up and running, and I'm curious how eveyrone is doing here. What issues are you running into? What are you using it for. Let's have a check in.
I want to give an update to Weaselway, a virtual monitor for WSL2.
Besides the first class nix support, I've added an install script for Ubuntu and Arch/CachyOS.
It now supports multimonitor setup, over 150 fixes and improvements to mesas d3d12 (gl) and dzn (vulkan). Performance increased by a lot, I now run it daily in 4k at 120hz at $work. It ships with support for bluetooth dongles over usbip (supports auto attach), allowing to use headphones and, important for some work places, passkeys with your phones. Video hardware encoding and decoding is partially working, but buggy due to driver issues. But a msteams call with software encoding and decoding works perfectly fine.
Also, as other seem to use this as a comparison: vkmark reports 4000fps on a recent laptop gpu and 400fps on an Nvidia 640m from 2012. ;)
Hello, I'm connecting to server running on Windows with SSH in VSCode. I need to open folder that is in WSL filesystem on that server, but VSCode only shows me Windows filesystem folders. Is there any way to show WSL filesysystem folders too?
Good day, I have been using WSL recently and for the most part I've been able to use shift + arrows to make text selections in the terminal and in Vim. For some reason it stopped working and now i can't do that? I looked all around and the only thing people mention is trying other terminal emulators or saying that it wasn't a thing in the first place. But I was able to. now I no longer can.
All I ever changed was the appearance once and after that it stopped working. Any ideas what it might be?
I'm pretty new to linux btw so it may be something obvious i should be able to find but for the life of me i can't.
Edit: I'm using Windows Terminal if that helps. Also it wasn't Mark Mode.
Alternatively: if it shouldn't work and it worked for a while why was this the case?
If you have tried to use a webcam from WSL2 for OpenCV or ROS, you know the routine: attach the camera with usbipd-win, discover the stock kernel has no uvcvideo, rebuild the kernel, and then watch raw 1080p collapse to ~5 fps over USB 2.0 anyway.
I built a different path. hvcam captures the camera on the Windows side with Media Foundation and streams frames into WSL2 over Hyper-V sockets (VMBus) — no IP discovery, no firewall prompts, no NAT. The Linux side is a small C library plus a Python binding; your code pulls the newest frame when it is ready, so nothing stale ever queues up.
Two details made the difference:
- Negotiation is scored, not guessed. Every native media type is ranked once, before streaming: reaching the 30 fps plateau beats resolution, and at ≥720p MJPEG wins ties — a raw 1080p YUY2 frame is 4.15 MB, an MJPEG frame is ~0.2 MB. The camera that negotiated YUY2 @ ~5 fps now negotiates 1920×1080 MJPEG @ 30.
- --reverse is zero-admin. In the normal direction, guest→host vsock needs a one-time registry entry. With --reverse the host dials out to a listener in the guest instead, and no admin step exists at all.
Measured on a USB 2.0 UVC camera (Windows 11 + WSL2): ~19–20 fps delivered with default exposure, and 30.8 real fps with --exposure -6 — the remaining gap was the sensor's low-light shutter stretch, not the bus.
One honest limitation: frames arrive through the hvcam library / Python binding (numpy arrays), not through /dev/video0. If your code reads a V4L2 device today, this replaces the capture source, not the device.
Code, build instructions and the wire protocol are here: https://github.com/santleme/hvcam — happy to answer questions about the vsock/VmId pinning or the media-type scoring.
I've always been a builder of various custom kernels for WSL, including the live-on-the-bleeding-edge can-we-get-the-latest-Linux-kernel-to-work-in-WSL2 series. For those interested in such things, this little article points at my kernel 7.3 build, the necessary patches to make virtiofs and Consommé networking play with your custom kernel and silence the slightly irritating warning, and detailed instructions on how to build your own. Thought it might be of interest to y'all.
Over the past year or so I've been working on Ika (イカ, Japanese for squid or cuttlefish), a free and open-source Android emulator. Originally it was developed for Asahi Linux on Apple Silicon, which at the time didn't have an Android emulator with GPU acceleration.
Ika runs LineageOS 23.2 (Android 16), built as a desktop operating system in a Cuttlefish virtual machine, as opposed to QEMU. Imagine GoogleBook OS with less Google, and you've got a decent approiximation of what we're working with.
With much of the hard work already done to get gfxstream working with the Apple Silicon Linux driver, I figured it wouldn't be too much of a leap to get it working on Windows 11 with WSL. That turned out to be a gross underestimation of what needed to be done, but I'm finally pleased to announce that I've got something useable and ready to share with everyone.
Ika's Features:
Android Desktop or TV mode: Android runs in a virtual desktop console with resizable app windows, or as a big-screen TV interface. Third-party TV launchers work too.
GPU acceleration: OpenGL ES 3.2 and Vulkan run on your real GPU through gfxstream.
Native app windows: Android apps can open in their own windows on your desktop, side-by-side with your regular Windows apps. Android apps have Windows 11 decorations, and get their own Start Menu entries.
Startup options per app: Display density, fullscreen start, keyboard and mouse handling, gamepad emulation and touch simulation are all configurable options.
Storage visible on your PC: Android's /sdcard appears in Windows Explorer under My PC.
Installing on Windows
The ika-wsl.ps1 script provisions a new WSL instance and installs the standard Ika packages for Debian Linux:
Enables WSL2, sets up nested virtualization and installs any pre-requisites.
Installs a minimal Debian 13 distribution named "Ika".
Installs the Mesa backports from Debian and the Ika packages.
Starts Android on your desktop.
What manner of sourcery gets Direct3D GPU drivers working with Android?
Under WSL2, the only way to reach the GPU is Direct3D 12. Ika ships its own extensively modified build of Mesa's Dozen driver (Vulkan on D3D12).
Vulkan 1.3: Upstream Dozen stops at Vulkan 1.2 and has received very few updates over the years. Ika's Dozen is updated to support Vulkan 1.3 on GPUs whose D3D12 driver has shader model 6.6 and wave operations. It adds the 1.3 core features, among them the Vulkan memory model, maintenance4, inline uniform blocks, extended dynamic state 1 and 2, image robustness, format feature flags 2, and demote to helper invocation.
Stability and speed: a pile of fixes and optimizations lets gfxstream, ANGLE and Chrome's renderer run on Dozen reliably. They work around driver crashes, lost devices and GPU resets, and include a shader pipeline disk cache, faster fence waits, and per-thread descriptor staging.
Benchmarks
The chart below shows Android benchmarks run inside Ika 261111 on Windows, with native Linux on the same machines for comparison:
GPU
Benchmark
Windows (WSL2)
Linux
Windows vs Linux
RTX 4080 Laptop
3DMark Wild Life Extreme
12,813
28,664
45%
3DMark Steel Nomad Light
4,568
14,720
31%
3DMark Sling Shot Extreme
84.9 fps
143.9 fps
59%
Geekbench GPU (Vulkan)
71,924
140,564
51%
Radeon 780M
3DMark Wild Life Extreme
4,265
5,085
84%
3DMark Steel Nomad Light
2,444
2,459
99%
3DMark Sling Shot Extreme
58.7 fps
60.0 fps
98%
Geekbench GPU (Vulkan)
16,178
33,106
49%
Intel UHD 770
3DMark Wild Life Extreme
1,558
1,414
110%
3DMark Sling Shot Extreme
33.6 fps
42.6 fps
79%
On the Radeon 780M, Windows comes within a few percent of Linux in Steel Nomad Light and Sling Shot Extreme. nVidia GPUs under WSL run well behind native Linux, but I'm working to close that gap and improve Intel GPU compatibility.
Nevertheless, even in these early stages of development, the results deliver a very smooth Android user experience and many games are already playable.
Requirements and limitations:
An x86-64 PC running Windows 11, and a CPU with nested virtualization support.
At least 8GB RAM recommended.
A modern(-ish) DirectX 12 compatible GPU: nVidia RTX series or higher, AMD RDNA3 and newer, or Intel UHD/Xe graphics. Older cards may work to varying degrees, but I have not tested them. Reports of your success or failure on other GPUs are welcome.
On Windows there's no hardware gamepad or camera support. Gamepad emulation with the keyboard does work.
Windows on ARM is not supported; It probably could work but I have no hardware to test on.
Additional info:
Outside of WSL, packages exist for Fedora 44, Debian 13, Ubuntu 26.04, and Arch Linux, on both x86-64 and Apple Silicon. Apple Silicon Macs require an Asahi kernel. Other ARM64 hardware has not been tested.
I've been working on a project called USBWarp, an experimental USB passthrough implementation for WSL2.
The idea is to avoid the traditional network-based USB/IP transport and exchange USB requests directly between Windows and Linux kernel components using Hyper-V HDV shared memory.
It includes a Windows kernel driver, a device capture driver, a Windows service, and a Linux virtual USB host controller.
The latest version is v0.2.1-alpha.
So far, I've validated USB 3.0 mass-storage transfers with data-integrity checks, as well as device capture and recovery. Earlier versions were also tested with a Raspberry Pi Pico CDC ACM device.
There's still a lot to do. USB 1.1/2.0 hardware coverage, isochronous peripherals, and UASP devices need more testing.
I've hit a hardware testing limitation with my current setup, so I'm opening the project up for feedback and community testing.
One important caveat: this is experimental kernel software, and the Windows drivers require test signing.
I'm trying to install a distro but it's not in the WSL distros list. The script file on this page which is mentioned to edit can't be run in WSL if there no distro install to begin with. Therefore how do you get a distro on the WSL list to install ?
I dual boot Kubuntu (second NVMe) and Windows 11, and I wanted *one* Linux install: same home, packages and Docker data whether I boot it bare metal or open it from Windows. On a work laptop with two 256 GB SSDs, keeping a second full Linux inside an `ext4.vhdx` also eats space I don't have. Stock WSL can only boot a distro from an `ext4.vhdx`; `wsl --mount` attaches a disk but never as a distro root (#6290 has been open since 2020).
Since WSL is open source now, I patched it: the service attaches the authorized disk as PassThrough and `mini_init` mounts the GPT partition (found by PARTUUID, ext4 superblock checked) as the distro root before WSL's own init runs. Everything after that is stock WSL.
What works from a normal non-elevated session: `wsl -d`, `\\wsl.localhost` cold start, systemd, VS Code Remote WSL, Docker with localhost ports, WSLg (with audio — the screenshot is KDE's Konsole opened by WSLg), clean shutdown when Windows reboots, and the native boot is untouched.
It's six patches (~500 lines) on WSL 3.0.3 plus a systemd generator that masks desktop/network/hardware units only under WSL. No binaries — you build it. It boots a real disk read-write from a second kernel, so read the safety section first.
Switching projects can mean starting containers, waiting for the database, opening terminals, and remembering which commands to run. I built dwork to handle those steps together, including opening project commands in Windows Terminal.
cd ~/projects
dwork scan
dwork list
dwork switch my-app
Existing Compose projects work without a separate configuration file. You can add a dwork.yml to define terminal commands, health checks, and browser URLs to open when ready.
Switching shows a plan and asks for confirmation. It can stop other registered workspaces and resume the selected project’s existing containers. Locked workspaces and projects you haven’t registered stay running.
It doesn’t create containers, rebuild images, or run your initial setup—you still handle those through your normal project workflow.
Deleting files inside WSL doesn't give the space back to Windows. I moved about 20 GB of project data out of my distro to another drive, and ext4.vhdx stayed at 66.7 GB. C: was down to 21 GB free, while the distro itself now held about 33 GB.
The fix is known (clean up, wsl --shutdown, Optimize-VHD), but I was doing it with 8 different scripts and kept forgetting a step. So I merged them into one tool:
maint audit / maint space - what is taking the space, per cache rule and per folder, plus how much a compact would return. Deletes nothing.
maint clean - cleans caches from a rules file (npx, pip, the journal, Playwright browsers no project pins any more, and so on), with --dry-run
maint docker - prunes the build cache and anonymous dangling volumes. Named volumes only if you opt in, and db-data/mysql/postgres-like names are never touched
maint.bat full - clean, export the distro to a zstd archive, verify it, rotate old backups, shut WSL down, compact both ext4.vhdx and docker_data.vhdx
Result on that run (clean, then winclean for %TEMP% and the recycle bin, then compact): ext4.vhdx 66.7 -> 42.8 GB, docker_data.vhdx 33.3 -> 31.0 GB, about 3.8 GB from TEMP and the bin, C: free 21 -> 56 GB.
Things to know before you run it:
full and compact shut WSL down and need admin (UAC prompt)
compact needs the Hyper-V PowerShell module, so on Windows Home only the cleanup and backup parts work
the shipped rules.conf is from my machine, review it first. audit and --dry-run are safe to try
Bash on the WSL side, PowerShell 5.1 on the Windows side, one shared config. MIT.
I’m not a developer. I tried to install an AI CLI (Composio) on Windows and the installer said “Windows is not supported. Use WSL.” Then I hit error after error. Here’s every fix, so you don’t lose an afternoon like I did:
1.0x80370102when installing WSL Turn on virtualization in BIOS (Intel VT-x / AMD SVM), tick Virtual Machine Platform and Windows Subsystem for Linux in Windows Features, restart, then wsl --update.
3.Could not resolve host (Ubuntu has no DNS) printf '\n[network]\ngenerateResolvConf = false\n' | sudo tee -a /etc/wsl.conf then wsl --shutdown in PowerShell, reopen Ubuntu, and: sudo rm -f /etc/resolv.conf && echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf (On a VPN? Try networkingMode=mirrored + dnsTunneling=true in .wslconfig instead.)
4.command not foundright after installing source ~/.bashrc or close and reopen Ubuntu.
5.Duplicated config keywarning Harmless. Remove the extra lines with sudo nano /etc/wsl.conf.
By hacking mesa and having a kernel module that implements the necessary parts of drm and kms, we can get the compositor to belive that a monitor exists and we can get the application to transfer their rendered gpu surfaces directly to the compositor. The updated regions from the monitor are then read back to cpu memory and transfered to a patched freerdp client via shared memory. Similar to how WSLg does it.
You can download and try a NixOS based GNOME and KDE image directly from the github releases.
Before someone screams slop: it works perfectly fine, I now know more than before I started the project and it might even reduce the entry hurdle for people to try out a Linux Desktop.
I am pleased to announce a free X Window Server in the Microsoft Store. See https://apps.microsoft.com/detail/9N4VVR1BD0Z5 This works great with WSL, especially in single-window mode. Ming64x uses Overlapped-IO, so it's lightning-fast!! Also has a built-in ssh terminal and X11/forwarding.
Yesterday I updated from WSL2 to WSL3 using `wsl --update`, first I noticed that it uses so much RAM about 7GB while the usage inside Ubuntu is 3GB-ish, then I limit the RAM to 4GB in WSL Settings and now the disk read/write is at 1200MB/s.
I don't know what is going on, I'm just doing my regular workflow like when I was using WSL2, there's nothing suspicious on what I run inside Ubuntu. Never had this problem before.
Most WSL guides assume Ubuntu. We needed a RHEL-compatible distro because that's what our servers run, so we built our dev environment on AlmaLinux 10 under WSL 2. (Disclosure: I'm on the team that maintains it.)
The setup:
Check WSL 2 is enabled: `wsl -v`
Install the distro: `wsl --install -d AlmaLinux-10`
Inside AlmaLinux, clone the repo, fill in `config.yml`, and run:
That gives you Apache, PHP (switchable 8.1–8.5), MariaDB, phpMyAdmin, Node.js (switchable 18–24) and Composer. Every `*.localhost` domain routes to its own virtualhost without editing the Windows hosts file.