WSL: Still unable to launch windows processes from WSL when using long environment variables (see #7947 or #6420))
Version
Microsoft Windows [Version 10.0.22621.674] / WSL-Version 0.70.0.0 / WSLg-Version 1.0.45
WSL Version
- WSL 2
- WSL 1
Kernel Version
5.10.102
Distro Version
Ubuntu 22.04
Other Software
cmd.exe
Repro Steps
-
Start Ubuntu
-
Execute the attached script
$ . environment-setup-aarch64-tdx-linux_modifiedenvironment-setup-aarch64-tdx-linux_modified.zip -
Start cmd.exe
Expected Behavior
cmd.exe is started
Actual Behavior
It hangs for a moment and prints
<3>init: (3508) ERROR: UtilAcceptVsock:244: accept4 failed 110
The strace of cmd.exe says
writev(2, [{iov_base="<3>init: (3512) ERROR: UtilAccep"..., iov_len=63}, {iov_base=NULL, iov_len=0}], 2<3>init: (3512) ERROR: UtilAcceptVsock:244: accept4 failed 110
Diagnostic Logs
No response
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 26 (1 by maintainers)
I removed the Windows Features “Windows Hypervisor Platform” and “Windows Subsystem for Linux” and the “Windows Subsystem for Linux Update” and reinstalled them. But the error is still present.
Output of
wsl --version:When I try to run
wsl --update --web-downloadin a PowerShell with admin rights I got the following output:Translated to English:
When I remove WSL completly again and try to reinstall it in a powershell with admin rights:
or this:
When i try to install the WSL within the store, I get the error 0x80240066.
But maybe this is another topic.