Error starting wsl-vpnkit 0.3.8

[adalsa91]

I get an error when tried to start release wsl-vpnkit 0.3.8, no problem with previous versions. I'm using Windows 10 22H2 (OS Build 19045.2673)

PS > wsl --version
WSL version: 1.1.3.0
Kernel version: 5.15.90.1
WSLg version: 1.0.49
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2673

PS > wsl -d wsl-vpnkit038
Processing fstab with mount -a failed.

<3>WSL (8) ERROR: CreateProcessEntryCommon:368: getpwuid(0) failed 2
<3>WSL (8) ERROR: CreateProcessEntryCommon:372: getpwuid(0) failed 2
<3>WSL (8) ERROR: CreateProcessEntryCommon:574: execvpe /bin/sh failed 2
<3>WSL (8) ERROR: CreateProcessEntryCommon:583: Create process not expected to return

[sakai135]

Does this happen even after a full restart of your machine?

[adalsa91]

Yes, I did. It's a fresh installation of windows and WSL is up to date so I have no idea what could be the problem.

[slatsinoglou]

Hi, I have noticed the same issue after updating to the latest version (tag) as you can see below.

❯ wsl.exe -d wsl-vpnkit service wsl-vpnkit start
<3>WSL (788) ERROR: CreateProcessParseCommon:786: Failed to translate \wsl.localhost\Ubuntu\home\toor
❯ pwd
/home/toor

Note that wsl-vpnkit works fine after start, The path (Failed to translate) always refers to the current dir. I was just curious why this started showing up.

[sakai135]

@slatsinoglou Your error message is a different issue, #150.

It occurs because wsl.exe tries to open the current directory in the WSL distro, which makes sense when you're in a Windows dir but not when running wsl.exe from within another WSL2 distro.

[sakai135]

@adalsa91 can you try the suggestions in microsoft/WSL#9018 ?

[sakai135]

Closing due to inactivity

[Baljak]

Just to mention that I couldn't get v0.4.1 to work properly (wget example.com didn't work, nor did nslookup 1.1.1.1), so I tried v0.3.8 which didn't work with the same error messages as @adalsa91. However, v0.3.7 works perfectly. My company's VPN is Pulse Secure 9.1.13 and a proxy is used. Previously, I've used other 0.3.x versions without any problem (v0.3.8 is the only one that doesn't work at all).