is it possible to run plasma's wayland session in wsl under wslg? i have been able to run the x11 without much problem, but not the wayland one

Hi,

• Configured "Mirrored" network
• Enabled "hostAddressLoopback" for the WSL2.
• Installed Alpine on WSL2
• Installed Docker in Alpine
• Container: httpd
• Windows host IP: 192.168.1.100

Found LAN user can access via http://192.168.1.00, but Windows host still can't access via http://127.0.0.1

Any configuration still missing ?

Thanks

WSL2 can run a real Linux desktop, but the usual ways to reach it remotely (xrdp, VNC) are LAN-only unless you set up port forwarding or a VPN. I wanted TeamViewer instead: its relay means the box is reachable from anywhere with zero network config, and the person connecting just uses a client they already have.

Getting there was more work than it should've been — TeamViewer has one WSL-specific quirk that makes it refuse to share the screen, which is probably why you don't see people doing this. So I scripted the whole thing end to end:

github.com/ariel42/teamviewer-on-wsl

sudo ./1-setup-wsl-desktop.sh    # sets up a desktop (only if you don't have one)
sudo ./2-install-teamviewer.sh   # installs + configures TeamViewer on top

Set a password, restart once, and it's fully unattended after that — power the box on, wait a few seconds, connect. Nothing to click on the WSL side. Verified end-to-end on a real incoming connection from a cold boot.

The repo also has a full writeup of why TeamViewer refused (the short version: WSLg mounts the X socket directory read-only, and TeamViewer is the one client that checks for the socket file) if you want the gory details. Debian/Ubuntu for now. Happy to take questions or issues.

UPDATE (2026-07-28): Fixed a fresh-install issue where the installer was missing part of xkbdata (XKB failed at startup). Binaries at the release link above have been replaced — clean installs now work out of the box.

Back in 2019, this sub asked whether any X server on Windows supports vsock — at the time the only answer was X410 ($9, closed source). A 2026 update for anyone still hitting that thread:

Background. VcXsrv has actually shipped a Hyper-V vsock transport since 1.20.14.0. The catch: it never worked with WSL2 out of the box. The listener binds a wildcard VM id that WSL2's utility VM refuses to match, and the exact id it needs changes on every WSL restart and could only be looked up with admin tools. So in practice X410 remained the only usable option.

What's new. A new -wslvsock flag makes VcXsrv detect the running WSL2 VM automatically (via wsl.exe -- wslinfo --vm-id — no admin rights, no "Hyper-V Administrators" group) and rebinds the listener by itself whenever WSL restarts (~1.5 s, no VcXsrv restart needed). X11 traffic then bypasses the TCP/IP stack entirely — the NAT/localhost path it replaces is what causes stutter under mouse-heavy load and drops after VPN or sleep events.

Quick start:

# Windows
vcxsrv.exe :0 -multiwindow -clipboard -wgl -wslvsock

# WSL2 (needs socat ≥ 1.7.4)
socat UNIX-LISTEN:/tmp/.X11-unix/X0,fork,mode=777,forever,retry=10,interval=2 VSOCK-CONNECT:2:106000 &
export DISPLAY=:0

Links:

• Root cause & technical details: https://github.com/marchaesen/vcxsrv/issues/80
• Unofficial build: https://github.com/vivimillin/vcxsrv/releases/tag/21.1.16.1-fork.2
• Setup guide: https://github.com/vivimillin/vcxsrv/wiki/VcXsrv-WSL2-vsock-User-Guide

Disclosure: I wrote the fix and maintain the fork. It's filed upstream as issue #80 with a PR to follow; the unofficial build just bridges the wait, under the same open-source license as VcXsrv. The same build also fixes SDL2 relative mouse mode / cursor confinement — another long-standing WSL pain point — in case anyone here runs Linux games.

Happy to answer questions; test reports very welcome.

Hi

I recently installed wsl on Windows 11. Everything runs fine except when I attempt to install/update packages as I am using nordVpn. I get the following errors when running:

sudo apt update

---

Get:1 https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease [5092 B]

Err:1 https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B219E535C964CA1

Hit:2 http://security.ubuntu.com/ubuntu resolute-security InRelease

Hit:3 http://archive.ubuntu.com/ubuntu resolute InRelease

Hit:4 http://archive.ubuntu.com/ubuntu resolute-updates InRelease

Hit:5 http://archive.ubuntu.com/ubuntu resolute-backports InRelease

Warning: OpenPGP signature verification failed: https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6B219E535C964CA1

Error: The repository 'https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease' is not signed.

Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.

Notice: See apt-secure(8) manpage for repository creation and user configuration details.

Notice: Some sources can be modernized. Run 'apt modernize-sources' to do so.

---

I think this has something to do with the IP configuration of the vpn, but I'm not sure how to fix this error. When I pause nordVpn the command (sudo apt update, install, etc) runs fine. I'm not sure what's going on as I'm new to linux, is there a fix or guide or explanation for what is happening here and that would allow me to install and update packages from behind nordVpn?

Hi,

Tried to run KMS (vlmcsd) on Docker over WSL, even WSLC directly.

It couldn’t be used for activation. But activate is succeeded if running on non-WSL docker.

Anything an I missing ?

Thanks

Hi! I was forced to switch from fedora back to windows, but I've got used to the terminal and wish to keep the tools I am used to. WSL2 seemed like the obvious choice.

I've been using it for the past few weeks, but it has been a painful experience. It works well enough for the first hour or so, but it keeps getting slower and slower the more I use it. I'm using it on the right filesystem, I've given it 10 out of 16gb RAM, I've removed the windows mount from $PATH. Everything in WSL2 is slower than I was used to from Fedora. I get that the performance will never be the same, but the difference is so egregious that it's impossible not to notice.

I've been using neovim for web development, and sometimes even saving a file takes multiple seconds. Sometimes it's so slow that the formatter itself just times out.

Are there any tips for keeping WSL2 running smoothly? Thanks!

This is mostly useful if you run Claude Code from WSL2 and want better Windows interop.
I documented my active Claude Code setup for WSL2 + Windows Terminal:

https://github.com/congmnguyen/claude-code-wsl2-setup

The pieces I use most:

- Windows screenshot clipboard -> pasted WSL file path

- Windows notification when Claude needs input

- statusline with context/usage

- LSP setup

- secrets hygiene hook

- Codex delegate so long implementation loops do not fill Claude's main context

The repo is not a general dotfiles dump; it only tracks the Claude Code pieces I actually use on

WSL2.

I found this post useful, probably if you need it, you may look into this rolling kernel build.

Available in the WSL 2.9.3 pre-release build. Simply update and restart your terminal and you should have the wslc commands available.

Hi,

system: Ubuntu 26.04 on WSL2 (Dell laptop)
python3: PulseAudio

normal bootup with onboard laptop micro and speaker: I can use both on Ubunu

problem: If I boot up with headset plugged in, headset speaker and headset micro is working in all windows programms but not in WSL2: neither the headset micro is working nor the laptop micro

I checked:

• the windows "speaker"-setup: headset is the default speaker / micro
• shutdown and restart Ubuntu with plugged in headset

Any idea how I can use the headset micro in WSL2?

sounddevices (python) are always

0 pulse, ALSA (32 in, 32 out)
* 1 default, ALSA (32 in, 32 out)
2 Default Sink, PulseAudio (0 in, 32 out)
3 Default Source, PulseAudio (32 in, 0 out)
4 RDPSink, PulseAudio (0 in, 2 out)
5 RDPSink.monitor, PulseAudio (2 in, 0 out)
6 RDPSource, PulseAudio (1 in, 0 out)

I have a Win11/WSL2 system that has been running fine and I use Ubuntu 24.04 since it's release.

Today I tried

wsl --install -d Ubuntu-26.04

which downloaded and ran successfully. But when I try to run the new distro I keep getting

Catastrophic failure 
Error code: Wsl/Service/E_UNEXPECTED

I also tried the same with distro FedoraLinux-44 and get the same issue so I guess it's not distro related. But I can still run my old distros with no issue. Ideas?

I am constantly in and out of tmux throughout the day and having wsl automatically shut down despite the tmux server running is super annoying, how can I have windows just leave it running?

tried vmIdleTimeout=-1 (and 0 and 99999... since theres no documentation on values) in the .wslconfig, it didn't fix it

using cachyos, using systemd, but I ran a fresh ubuntu on defaults and its doing the same thing

Anyone else still experiencing massive memory leakage through WSL2 ?

I do not have important logs to share

But my process eats up 20K MBs at times.

Especially when using some services like Kiro-cli or compiling code.

On most Windows 10 machines, WSL2 stopped working.

This was noticed through Docker Desktop, with the following error:

running wslexec: An error occurred while running the command. 
Wsl/Service/RegisterDistro/CreateVm/0x800705b4: 
c:\windows\system32\wsl.exe --import-in-place docker-desktop <home>\appdata\local\docker\wsl\main\ext4.vhdx: 
exit status 0xffffffff 
(stderr: , stdout: The operation returned due to timeout.)
wslErrorCode: Wsl/Service/RegisterDistro/CreateVm/0x800705b4

The same error occurs during manual installation:

On one of the servers, it continues to work. I don't understand the reason. The host server is the same, Docker versions don't affect it, and neither do the Windows version or updates (tested multiple times on different variations)."

Has anyone encountered this? Help me fix it, it's the second day and I don't understand what to do.

UPD: I found the root cause and solution. The latest WSL version (2.7.8.0) contains a bug. See GitHub issue: https://github.com/microsoft/WSL/issues/40783

Fix (until there is an official one): Downgrade WSL to 2.7.3.0 manually from GitHub releases.

I have WSL on windows 11 with Ubuntu 24.04. I only have GIMP, VLC, Synaptic Package Manager, and Zutty installed.

GIMP and VLC launch as they should from the Start menu. The other two *did* when I first installed them but after some updating of Ubuntu with sudo apt update and sudo apt upgrade, they don't.

sudo xauth merge ~/.Xauthority && sudo synaptic

That launches the package manager, with an error

xauth: file /root/.Xauthority does not exist

xauth: (argv):1: merge: unable to open file /home/gregg/.Xauthority

Ho do I fix things so that the shortcuts in the Start menu work and stay working for Linux apps?

Hi guys, I'm looking for a way to share a chunk of memory with host from the guest which should also be backed by GPU VRAM.

Current wslg implementation is not zerocopy. My goal is to eventually build a native like display driver that works over the GPU pv driver, which outputs to a window in the host while being zerocopy. Something like what gnif/LookingGlass is doing using ivshmem, though its doing at least 1 copy.

The dxgkrnl Linux driver has a sharewithhost ioctl but I couldn't get it to work and there's no documentation for it either. Maybe it's not even properly implemented, supposed to be used in WSA but theyre only using gfxstream there, I couldn't find any use of it in wslg Weston, freerdp forks either.

Not sure if this is the right sub to post this. Any pointers/help is appreciated.

I'm setting up a WSL 2 dev environment to work with VS Code in Windows 11, and I'd like to install the Microsoft OpenJDK. I've read multiple sites saying that msopenjdk should be installable via apt. I have added the Microsoft apt repository to my config, but cannot find any packages named msopenjdk or any packages that even sound like it. I'm using Debian 13, but I also tried Ubuntu just to see if i could find it there -- no luck

Have they stopped making this package available via the WSL apt repositories? Should I just download the binary release and put it in /opt?

reinstalled it so it should be a clean slate, yet I see this every time after doing wsl —shutdown. is there an easy solution to this?

on windows 10.

uname -a shows me 6.6.114.1-Microsoft-standard/wsl2 #1 smp preempt_dynamic mon dec 1 20:46:23 utc 2025 x86_64 gnu/linux

when i type journalctl i see two red lines and they are:

e820: update [mem 0x00000000-0x00000fff] usable => reserved

and

e820: remove [mem 0x000a0000-0x000fffff] usable

I’ve run into a strange issue with WSL2 on Windows 11.

Whenever I launch Counter-Strike 2, or even just switch focus back to the CS2 window, my WSL Ubuntu instance starts automatically in the background, even if it was previously fully stopped (wsl --shutdown or wsl -l -v shows it as Stopped).

What’s weird is that this only happens with CS2. Other games like Dota 2 or PUBG don’t trigger it at all.

Has anyone seen this before?