WSL: Windows programs hang when started from WSL2
Windows Build Number
Microsoft Windows [Version 10.0.19042.1165]
WSL Version
- WSL 2
- WSL 1
Kernel Version
4.19.128
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Start any Windows executable, for example wsl.exe:
$ wsl.exe
<freeze>
Expected Behavior
Windows executable starts normally or fails with expected error message.
Actual Behavior
Program freezes. Impossible to interrupt with Ctrl-C. Only kill -9 can stop the process.
Diagnostic Logs
WSL2 integration with Windows, which allows execution of Windows programs [1], stops working.
Every new executable (wsl.exe in this example) remains blocked:
$ ps ax | grep /tools/init
1109 pts/0 S+ 0:00 /tools/init /mnt/c/WINDOWS/system32/cmd.exe /c autohotkey.bat
2148 pts/1 S+ 0:00 /tools/init /mnt/c/WINDOWS/system32/wsl.exe
2319 pts/2 S+ 0:00 /tools/init /mnt/c/WINDOWS/system32/wsl.exe
2633 pts/3 S+ 0:00 grep --color=auto /tools/ini
Typical state - process waits in accept4(…)
d057039:~$ strace -p 1109
strace: Process 1109 attached
accept4(4,
File descriptor 4 is s AF_VSOCK, a socket for host-vm communication. All processes looks the same:
d057039:~$ sudo lsof -p 1109
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
cmd.exe 1109 d057039 cwd DIR 0,42 4096 1407374884823550 /mnt/c/WINDOWS/system32
cmd.exe 1109 d057039 rtd DIR 8,16 4096 2 /
cmd.exe 1109 d057039 txt REG 0,18 632048 844424931918031 /tools/init
cmd.exe 1109 d057039 0u CHR 136,0 0t0 3 /dev/pts/0
cmd.exe 1109 d057039 1u CHR 136,0 0t0 3 /dev/pts/0
cmd.exe 1109 d057039 2u CHR 136,0 0t0 3 /dev/pts/0
cmd.exe 1109 d057039 3u CHR 136,0 0t0 3 /dev/pts/0
cmd.exe 1109 d057039 4u sock 0,8 0t0 23751 protocol: AF_VSOCK
cmd.exe 1109 d057039 5u unix 0x000000009215753c 0t0 23752 type=SEQPACKET
Blocked process can only be killed with kill -9
Other observations
-
Interestingly, if the process is started with root privileges, all works as expected - processes starts, responds etc.
-
If WSL2 is shutdown (
wsl.exe --shutdown), execution of Windows programs starts working for a while, but ends soon with the same. -
Rebooting the systems helps only temporary. After a while blocking reappear again.
-
Where is no difference in behavior, if I use Windows Terminal or wsl.exe as my console. Windows programs freeze in both.
-
Both Windows console apps and GUI programs hang.
Logs
Refs
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 3
- Comments: 18 (1 by maintainers)
Have the same / similar issue myself - am using
npiperelay.exeto bridge access from Linux -> Windows for ssh agent. At some point into a session, runningnpiperelay.exefrom within WSL2 will just hang, where as previously you could run it and get the default help output. Running the binary from the Windows side works as expected.I can see the process, but it’s just blocked,
Restarting WSL doesn’t seem to fix the issue, however fully rebooting does resolve it temporarily. I’m running Windows 11 and using WSL installed via the MS Store.
@AaronFriel confirm mine is installed from Windows Store and running
wslservice.exefromC:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemforLinux_0.51.3.0_x64__8wekyb3d8bbwe.It usually happens after my laptop went to sleep.
However, it doesn’t work by restarting the WSL service.
Followed by starting Ubuntu, then run
cmd.exeinside. It will hang again.Will be great if anyone got a workaround other than rebooting.
Looks like this is a duplicate of #7883 which has just been solved.
Same issue on Windows 11 22000.376, happens once per day.
Restarting WslService in Windows seems to resolve it. Any hanging processes will be killed, but after that I can
cmd.exefrom WSL fine.I wonder if a common feature of @ZedG2, @mands, & @0anton is that we’re all running WSL distributed through the store instead of Windows. If you open up services.msc and examine the Windows Subsystem for Linux Preview service, is the path a Store path like this?
C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemforLinux_0.50.2.0_x64__8wekyb3d8bbwe\wslservice.exeI have the same issue, and as @AaronFriel said, I also have WSL installed from Microsoft Store.