WSL: <3>WSL (8) ERROR: CreateProcessParseCommon:782: Failed to translate \\wsl.localhost\westie\home\mwoodpatrick
Version
WSL version: 1.0.3.0 Kernel version: 5.15.79.1 WSLg version: 1.0.47 MSRDC version: 1.2.3575 Direct3D version: 1.606.4 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22623.1020
WSL Version
- WSL 2
- WSL 1
Kernel Version
5.15.79.1
Distro Version
Fedora Linux 37 (Container Image)
Other Software
No response
Repro Steps
This is my default distro so I just ran wsl.exe
Expected Behavior
Should start distro without error
Actual Behavior
I get
<3>WSL (8) ERROR: CreateProcessParseCommon:782: Failed to translate \wsl.localhost\westie\home\mwoodpatrick ``
sometimes on distro startup and
<3>WSL (8) ERROR: CreateProcessParseCommon:782: Failed to translate \\wsl.localhost\westie\home\mwoodpatrick
when running:
wsl.exe -d Alpine mount --bind /home/mwoodpatrick/projects /mnt/wsl/projects
Diagnostic Logs
dmesg [ 733.906101] Exception: [ 733.906211] Operation canceled @p9io.cpp:258 (AcceptAsync)
[ 749.562752] EXT4-fs (sdc): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered. Quota mode: none. [ 813.030972] FS-Cache: Duplicate cookie detected [ 813.031728] FS-Cache: O-cookie c=00000053 [p=00000002 fl=222 nc=0 na=1] [ 813.032341] FS-Cache: O-cookie d=0000000066165ebb{9P.session} n=0000000046b843fd [ 813.033233] FS-Cache: O-key=[10] ‘34323935303138373434’ [ 813.033722] FS-Cache: N-cookie c=00000054 [p=00000002 fl=2 nc=0 na=1] [ 813.034112] FS-Cache: N-cookie d=0000000066165ebb{9P.session} n=000000005cb0fa82 [ 813.034607] FS-Cache: N-key=[10] ‘34323935303138373434’ [ 813.127166] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22 [ 813.128610] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22 [ 813.129539] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22 [ 813.130807] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2 [ 813.487803] Failed to connect to bus: No such file or directory [ 813.754996] Failed to connect to bus: No such file or directory [ 814.054159] systemd-journald[44]: Received client request to flush runtime journal. [ 818.108300] WSL (2): Creating login session for mwoodpatrick [ 1132.118538] WSL (1) ERROR: ConfigApplyWindowsLibPath:2469: open /etc/ld.so.conf.d/ld.wsl.conf [ 1132.121534] failed 2 [ 1132.237331] WSL (1) WARNING: /usr/share/zoneinfo/America/Los_Angeles not found. Is the tzdata package installed? [ 1133.453542] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22 [ 1133.469135] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22 [ 1133.472221] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22 [ 1133.490104] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2 [ 1148.278972] Exception: [ 1148.279060] Operation canceled @p9io.cpp:258 (AcceptAsync)
[ 1269.551546] br-6573b0dc0a4c: port 1(veth9095be4) entered blocking state [ 1269.552843] br-6573b0dc0a4c: port 1(veth9095be4) entered disabled state [ 1269.553507] device veth9095be4 entered promiscuous mode [ 1269.554708] br-6573b0dc0a4c: port 1(veth9095be4) entered blocking state [ 1269.555274] br-6573b0dc0a4c: port 1(veth9095be4) entered forwarding state [ 1269.557097] br-6573b0dc0a4c: port 1(veth9095be4) entered disabled state [ 1270.157924] eth0: renamed from vethcc6af37 [ 1270.217871] IPv6: ADDRCONF(NETDEV_CHANGE): veth9095be4: link becomes ready [ 1270.218688] br-6573b0dc0a4c: port 1(veth9095be4) entered blocking state [ 1270.219169] br-6573b0dc0a4c: port 1(veth9095be4) entered forwarding state [ 1270.219790] IPv6: ADDRCONF(NETDEV_CHANGE): br-6573b0dc0a4c: link becomes ready
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 17
- Comments: 47
I had the same issue after I installed docker desktop.
I found out that the problem was that docker desktop creates a new wsl distro and set this new distro as default. So any wsl commands in power shell would relate to the docker-distro and not work because this distro is not supose to be used by the user.
To change the default distro you can do:
For some reason, Docker set its own wsl distribution as default. Setting the default wsl to Ubuntu worked for me.
I had a similar problem but it turned out to be caused by the way I was starting the
wsl-vpnkitservice (https://github.com/sakai135/wsl-vpnkit/issues/150).same error
✅ worked for me
I resolved this by switching the default distro.
IF you’re using docker:
see how many distros you got. Docker installed its own distro and sets it as default, which can cause this issue. If you have another distro, like ubuntu, make that the default and see if the issue goes away.
If you want to try installing Ubuntu, or another distro (to see if the issue is is local to your current distro), you can
Hope this helps to whoever runs into this with Docker
my starting directory is set as
~for each of my distros, and I have the same symptoms.This worked for me…
This is the correct answer, for some reason the
defaultwas set ondocker-desktop-data. This happended after I usedwsl --shutdownand a windows updateSame here… The issue arose yesterday after updating WSL with command
wsl --updateUsing Ubuntu (Ubuntu 22.10)I found a workaround for this (I can’t remember where in order to credit them however). If you’re starting wsl-vpnkit when Ubuntu is started via an entry in your .profile, the entry needs to be: wsl.exe -d wsl-vpnkit --cd /app service wsl-vpnkit start
None of these helps me, sadly. Win 11, using the latest wsl2, I don’t have docker, wsl-vpnkit not in the mix, only have Ubuntu 22.04 installed, set the default to that just to be sure. Still:
Boo
In your case you have to install a new distro for example
You can also search for other distros in the Microsoft Store
After that you can set the new distro as the default
If you are not sure what is your distro name you can check with
If you don’t have Ubuntu in one of the lists, you’d have to download it at first
Run command
Reason is that when you do
wsl --listyou might only find the stuff from DockerSo you need to install Ubuntu then do the following:
Ubuntu-22.04 as the
<DISTRO_NAME>I am experiencing this error on a clean Windows 11 22H2 installation and default WSL using
wsl.exe --install.I saw same error message after updating to new WSL. But in my case, this happened only when launching in Windows Terminal, because the starting directory for the distro
Ubuntu-22.04is set to the one of the different distro (like\\wsl$\Ubuntu-18.04\home\).Profile for distro
Ubuntu-22/04in Windows TerminalA mutual thanks to you @BrBill ! My issue kept popping up, but then I read your stab suggestion. For anyone else struggling with this, here’s some detailed notes. modify the drives to fit your situation…
Confirmed, @adrianegraphene, this worked. Then I made it permanent by adding an
/etc/fstabentry:Thanks!
So, I switched some drives around and then started getting this issue after years of no problems. As silly as it sounds, my solution was to simply remount my native drive to the wsl path.
Before re-mounting my wsl path to my native path
After re-mounting my wsl path
If drive is completely missing.
In this case of this @BrBill below, when your drive is totally missing, I would suggest this while inside of your wsl shell. Apologies if I missed the mark, but it solved my silly issue.
Yup, this problem has not been resolved. There’s a lot of focus on Docker here, but since I’ve never had Docker on this system, that’s a red herring in my particular situation.
I’m facing the same problem described here by @BrBill, just tried to install a .tar file from a wsl --export Maybe it is my third time doing this kind of import and first time facing a problem like this
This issue just re-appeared on win10 after forced update installation yesterday.
I ran into this issue again when trying to run docker from inside a WSL distro.
Uninstalling the Microsoft store version and returning to the Windows OS version resolved the issue.
Same here with Ubuntu 20.04 after updating with
wsl --update<3>WSL (127) ERROR: CreateProcessParseCommon:782: Failed to translate \\wsl.localhost\Ubuntu-20.04\home\hj82shme too, have the same trouble, PS G:\linux> wsl -d Ubuntu-20.04 -e /bin/sh wsl: 不支持镜像网络模式,正在回退到 NAT 网络 wsl: Hyper-V 防火墙不受支持 wsl: DNS 隧道不受支持 <3>WSL (14) ERROR: CreateProcessParseCommon:711: Failed to translate G:\linux <3>WSL (14) ERROR: CreateProcessParseCommon:757: getpwuid(0) failed 2 <3>WSL (14) ERROR: UtilTranslatePathList:2866: Failed to translate D:\Python\Python312\Scripts
<3>WSL (14) ERROR: UtilTranslatePathList:2866: Failed to translate D:\Python\Python312
<3>WSL (14) ERROR: UtilTranslatePathList:2866: Failed to translate D:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\bin <3>WSL (14) ERROR: UtilTranslatePathList:2866: Failed to translate D:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\libnvvp <3>WSL (14) ERROR: UtilTranslatePathList:2866: Failed to translate D:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.1\bin … <3>WSL (14) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Administrator\AppData\Local\Microsoft\WinGet\Packages\Schniz.fnm_Microsoft.Winget.Source_8wekyb3d8bbwe Processing fstab with mount -a failed. Failed to mount C:, see dmesg for more details. Failed to mount D:, see dmesg for more details. Failed to mount E:, see dmesg for more details. Failed to mount G:, see dmesg for more details. Failed to mount H:, see dmesg for more details. Failed to mount I:, see dmesg for more details.
<3>WSL (14) ERROR: CreateProcessEntryCommon:334: getpwuid(0) failed 2 <3>WSL (14) ERROR: CreateProcessEntryCommon:505: execvpe /bin/sh failed 2 <3>WSL (14) ERROR: CreateProcessEntryCommon:508: Create process not expected to return
same error here
scenario:
\\wsl.localhost\$default_linux_distroto drive letterZ:wsl find /home -path /homeunder driveZ:error:
<3>WSL (6739) ERROR: CreateProcessParseCommon:711: Failed to translate Z:\homeI had this same issue and it was fixed by setting the default distribution wsl --set-default Ubuntu-22.04 wsl --set-default-version 2 and then restarting the terminal change “Ubuntu-22.04” to which ever distribution you’re using
My issue was due to trying to run a WSL terminal in a remote vs code window.
When selecting the folder make sure to use the vs code “open folder” UI vs your native windows file explorer. The path should start with
~and notZ:\. The former should open a bash terminal and the latter will try and fail to open a WSL terminal.Hi Folks,
Just want to drop a message and say I’m also having the same problem. I see there is some information about wsl-vpnkit which I will take a look at. I don’t remember the setup for running that I just know that it runs automatically now for me. Most of my issue came after updating wsl with
wsl --updateThis is what I’m seeing
<3>WSL (130) ERROR: CreateProcessParseCommon:789: Failed to translate \\wsl.localhost\Ubuntu\home\marzamor start-stop-daemon: wsl-vpnkit is already runningAs a matter of fact, I also saw some issues today after shutting down my PC yesterday. I went to start Windows Terminal and my default profile is Ubuntu. Kept launching a new separate windows outside of Windows Terminal and giving me these weird errors saying that it could not mount the C:\ drive. Not sure if that’s related. Shutting down WSL and restarting seemed to have gotten it to work but doesn’t make sense why on startup that’s happening.
Let me know if anyone needs additional details. If someone has a workaround as well or knows anything about these problems after updating…