<3>WSL (8) ERROR: CreateProcessParseCommon:782: Failed to translate \\wsl.localhost\westie\home\mwoodpatrick

[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

• [X] 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

[castorfou]

Same here with an ubuntu-22.04 image

Version WSL : 1.0.3.0
Version du noyau : 5.15.79.1
Version WSLg : 1.0.47
Version MSRDC : 1.2.3575
Version direct3D : 1.606.4
Version de DXCore : 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
version Windows : 10.0.19044.2364

Here are all dmesg lines with errors

...
[    0.086228] PCI: Fatal: No config space access function found
...
[    0.112251] kvm: no hardware support
...
[    1.247265] FS-Cache: Duplicate cookie detected
[    1.247510] FS-Cache: O-cookie c=00000005 [p=00000002 fl=222 nc=0 na=1]
[    1.247751] FS-Cache: O-cookie d=00000000f0f75736{9P.session} n=00000000e2a414ec
[    1.248042] FS-Cache: O-key=[10] '34323934393337343135'
[    1.248233] FS-Cache: N-cookie c=00000006 [p=00000002 fl=2 nc=0 na=1]
[    1.248540] FS-Cache: N-cookie d=00000000f0f75736{9P.session} n=000000000f10eae8
[    1.248893] FS-Cache: N-key=[10] '34323934393337343135'
...
[    2.572699] /sbin/ldconfig:
[    2.572701] /usr/lib/wsl/lib/libcuda.so.1 is not a symbolic link
...
[    2.761704] /sbin/ldconfig.real:
[    2.761707] /usr/lib/wsl/lib/libcuda.so.1 is not a symbolic link

[    2.909855] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    2.910248] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    2.910572] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    2.911051] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
...
[    4.623011] WSL (1) ERROR: ConfigApplyWindowsLibPath:2469: open /etc/ld.so.conf.d/ld.wsl.conf
[    4.623014]  failed 2
...

Hope it could help. I have not yet seen any impact from this error message.

[mssayari]

Same here with Ubuntu 20.04 after updating with wsl --update

[   20.355013] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   20.356142] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   20.357059] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   20.358123] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[   61.479585] hv_balloon: Max. dynamic memory size: 2048 MB
[   91.130445] scsi 0:0:0:3: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[   91.132706] sd 0:0:0:3: Attached scsi generic sg3 type 0
[   91.151997] sd 0:0:0:3: [sdd] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[   91.152859] sd 0:0:0:3: [sdd] 4096-byte physical blocks
[   91.153772] sd 0:0:0:3: [sdd] Write Protect is off
[   91.154290] sd 0:0:0:3: [sdd] Mode Sense: 0f 00 00 00
[   91.155991] sd 0:0:0:3: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   91.173268] sd 0:0:0:3: [sdd] Attached SCSI disk
[   91.191845] EXT4-fs (sdd): recovery complete
[   91.202104] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered. Quota mode: none.
[   91.309635] hv_pci 76f76c9a-5471-4c80-b6de-0d1e71122bc6: PCI VMBus probing: Using version 0x10003
[   91.547675] hv_pci 76f76c9a-5471-4c80-b6de-0d1e71122bc6: PCI host bridge to bus 5471:00
[   91.548851] pci_bus 5471:00: root bus resource [mem 0xbffe10000-0xbffe12fff window]
[   91.549625] pci_bus 5471:00: No busn resource found for root bus, will use [bus 00-ff]
[   91.560215] pci 5471:00:00.0: [1af4:1049] type 00 class 0x010000
[   91.563366] pci 5471:00:00.0: reg 0x10: [mem 0xbffe10000-0xbffe10fff 64bit]
[   91.565426] pci 5471:00:00.0: reg 0x18: [mem 0xbffe11000-0xbffe11fff 64bit]
[   91.567447] pci 5471:00:00.0: reg 0x20: [mem 0xbffe12000-0xbffe12fff 64bit]
[   91.574880] pci_bus 5471:00: busn_res: [bus 00-ff] end is updated to 00
[   91.576692] pci 5471:00:00.0: BAR 0: assigned [mem 0xbffe10000-0xbffe10fff 64bit]
[   91.578360] pci 5471:00:00.0: BAR 2: assigned [mem 0xbffe11000-0xbffe11fff 64bit]
[   91.580169] pci 5471:00:00.0: BAR 4: assigned [mem 0xbffe12000-0xbffe12fff 64bit]
[   91.781226] WSL (1) ERROR: ConfigApplyWindowsLibPath:2469: open /etc/ld.so.conf.d/ld.wsl.conf
[   91.781316]  failed 2
[   91.803977] hv_pci 72330be6-9a93-45f6-824f-2d8c9df7704f: PCI VMBus probing: Using version 0x10003
[   91.815941] WSL (1) WARNING: /usr/share/zoneinfo/Europe/Istanbul not found. Is the tzdata package installed?
[   91.922891] hv_pci 72330be6-9a93-45f6-824f-2d8c9df7704f: PCI host bridge to bus 9a93:00
[   91.923698] pci_bus 9a93:00: root bus resource [mem 0xbffe14000-0xbffe16fff window]
[   91.924320] pci_bus 9a93:00: No busn resource found for root bus, will use [bus 00-ff]
[   91.926277] pci 9a93:00:00.0: [1af4:1049] type 00 class 0x010000
[   91.928118] pci 9a93:00:00.0: reg 0x10: [mem 0xbffe14000-0xbffe14fff 64bit]
[   91.929483] pci 9a93:00:00.0: reg 0x18: [mem 0xbffe15000-0xbffe15fff 64bit]
[   91.930843] pci 9a93:00:00.0: reg 0x20: [mem 0xbffe16000-0xbffe16fff 64bit]
[   91.936449] pci_bus 9a93:00: busn_res: [bus 00-ff] end is updated to 00
[   91.936975] pci 9a93:00:00.0: BAR 0: assigned [mem 0xbffe14000-0xbffe14fff 64bit]
[   91.938159] pci 9a93:00:00.0: BAR 2: assigned [mem 0xbffe15000-0xbffe15fff 64bit]
[   91.939505] pci 9a93:00:00.0: BAR 4: assigned [mem 0xbffe16000-0xbffe16fff 64bit]
[   91.961467] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   91.962877] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   91.963805] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   91.964759] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[   93.928767] Exception:
[   93.928772] Operation canceled @p9io.cpp:258 (AcceptAsync)

[   94.079351] EXT4-fs (sdd): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered. Quota mode: none.
[   94.341160] WSL (1) ERROR: ConfigApplyWindowsLibPath:2469: open /etc/ld.so.conf.d/ld.wsl.conf
[   94.341167]  failed 2
[   94.395891] WSL (1) WARNING: /usr/share/zoneinfo/Europe/Istanbul not found. Is the tzdata package installed?
[   94.738081] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   94.741222] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   94.746227] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   94.747532] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[   95.673918] scsi 0:0:0:4: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[   95.688373] sd 0:0:0:4: Attached scsi generic sg4 type 0
[   95.700536] sd 0:0:0:4: [sde] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[   95.707366] sd 0:0:0:4: [sde] 4096-byte physical blocks
[   95.713743] sd 0:0:0:4: [sde] Write Protect is off
[   95.724224] sd 0:0:0:4: [sde] Mode Sense: 0f 00 00 00
[   95.733801] sd 0:0:0:4: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   95.857991] sd 0:0:0:4: [sde] Attached SCSI disk
[   97.219100] EXT4-fs (sde): recovery complete
[   97.222906] EXT4-fs (sde): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered. Quota mode: none.
[   97.269985] hv_pci 0e949f79-8f68-4512-afa5-6e3f7c66ed11: PCI VMBus probing: Using version 0x10003
[   97.373530] hv_pci 0e949f79-8f68-4512-afa5-6e3f7c66ed11: PCI host bridge to bus 8f68:00
[   97.374297] pci_bus 8f68:00: root bus resource [mem 0xbffe18000-0xbffe1afff window]
[   97.374974] pci_bus 8f68:00: No busn resource found for root bus, will use [bus 00-ff]
[   97.377158] pci 8f68:00:00.0: [1af4:1049] type 00 class 0x010000
[   97.379027] pci 8f68:00:00.0: reg 0x10: [mem 0xbffe18000-0xbffe18fff 64bit]
[   97.380608] pci 8f68:00:00.0: reg 0x18: [mem 0xbffe19000-0xbffe19fff 64bit]
[   97.382081] pci 8f68:00:00.0: reg 0x20: [mem 0xbffe1a000-0xbffe1afff 64bit]
[   97.387891] pci_bus 8f68:00: busn_res: [bus 00-ff] end is updated to 00
[   97.388541] pci 8f68:00:00.0: BAR 0: assigned [mem 0xbffe18000-0xbffe18fff 64bit]
[   97.389856] pci 8f68:00:00.0: BAR 2: assigned [mem 0xbffe19000-0xbffe19fff 64bit]
[   97.391282] pci 8f68:00:00.0: BAR 4: assigned [mem 0xbffe1a000-0xbffe1afff 64bit]
[   97.467096] WSL (2) ERROR: UtilCreateProcessAndWait:661: /bin/mount failed with 2
[   97.486318] WSL (1) ERROR: UtilCreateProcessAndWait:683: /bin/mount failed with status 0xff00

[   97.490675] WSL (1) ERROR: ConfigMountFsTab:2521: Processing fstab with mount -a failed.
[   97.549978] WSL (1) ERROR: ConfigApplyWindowsLibPath:2469: open /etc/ld.so.conf.d/ld.wsl.conf
[   97.549984]  failed 2
[   97.955935] WSL (1) WARNING: /usr/share/zoneinfo/Europe/Istanbul not found. Is the tzdata package installed?
[   97.960767] hv_pci 4ad0ae14-7c0e-4507-8c95-b0c3b73d13d4: PCI VMBus probing: Using version 0x10003
[   98.261013] hv_pci 4ad0ae14-7c0e-4507-8c95-b0c3b73d13d4: PCI host bridge to bus 7c0e:00
[   98.261969] pci_bus 7c0e:00: root bus resource [mem 0xbffe1c000-0xbffe1efff window]
[   98.262760] pci_bus 7c0e:00: No busn resource found for root bus, will use [bus 00-ff]
[   98.273575] pci 7c0e:00:00.0: [1af4:1049] type 00 class 0x010000
[   98.276565] pci 7c0e:00:00.0: reg 0x10: [mem 0xbffe1c000-0xbffe1cfff 64bit]
[   98.278955] pci 7c0e:00:00.0: reg 0x18: [mem 0xbffe1d000-0xbffe1dfff 64bit]
[   98.281775] pci 7c0e:00:00.0: reg 0x20: [mem 0xbffe1e000-0xbffe1efff 64bit]
[   98.295554] pci_bus 7c0e:00: busn_res: [bus 00-ff] end is updated to 00
[   98.296887] pci 7c0e:00:00.0: BAR 0: assigned [mem 0xbffe1c000-0xbffe1cfff 64bit]
[   98.303169] pci 7c0e:00:00.0: BAR 2: assigned [mem 0xbffe1d000-0xbffe1dfff 64bit]
[   98.305069] pci 7c0e:00:00.0: BAR 4: assigned [mem 0xbffe1e000-0xbffe1efff 64bit]
[   98.351356] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   98.405029] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   98.455345] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[   98.542616] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[  106.039705] loop0: detected capacity change from 0 to 880252
[  106.110606] ISO 9660 Extensions: Microsoft Joliet Level 3

[aleixjf]

Same here... The issue arose yesterday after updating WSL with command wsl --update Using Ubuntu (Ubuntu 22.10)

[jelez]

Same issue: <3>WSL (124) ERROR: CreateProcessParseCommon:782: Failed to translate \\wsl.localhost\Amazon2\home\test

[dp1795]

Same issue. New wsl --update and kernel seems to be causing several problems. Other big one is wslg not working with glxinfo -B segmentation fault.

nerdctl --version

<3>WSL (5156) ERROR: CreateProcessParseCommon:782: Failed to translate \\wsl.localhost\Ubuntu\home\userme 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.22000.1335

[horihiro]

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.04 is set to the one of the different distro (like \\wsl$\Ubuntu-18.04\home\).

Profile for distro Ubuntu-22/04 in Windows Terminal

[castorfou]

my starting directory is set as ~ for each of my distros, and I have the same symptoms.

[hj82sh]

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\hj82sh

[andrew-dias]

I had a similar problem but it turned out to be caused by the way I was starting the wsl-vpnkit service (https://github.com/sakai135/wsl-vpnkit/issues/150).

[mschnee]

I am experiencing this error on a clean Windows 11 22H2 installation and default WSL using wsl.exe --install.

[afilp]

I have "segmentation fault" most of the times (if I reboot the PC it does not show, but it will show later on).

I updated the wsl and all these problems started now.

Windows 10.

[markarnott]

I have this problem as well on an Ubuntu 20.04.5 LTS distribution.

From the WSL bash prompt, when I execute wslpath -a -u 'C:\users' it just echoes back what I give it.

e.g. wslpath -a -u 'C:\users\Public' wslpath: C:\users\Public

[markarnott]

This issue is related to following previously reported issue https://github.com/microsoft/WSL/issues/8723

I was able to resolve my issue by removing the following from /etc/wsl.config

[automount] enabled = false

[interop] enabled = false appendWindowsPath = false

[markarnott]

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.

[bitemarcz]

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 --update

This 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 running

As 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....

[carlfroomcgi]

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

[elvinasp]

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

Confirming it works! Thanks!

[ajaxStardust]

I experience this issue as well when wsl is launched in an elevated terminal.

I recognize the paths shown as those in my MS Windows %PATH% environment variable.

so it makes sense that:

appendWindowsPath = false might "resolve" the issue

What is the cause of the issue, and how is it properly resolved?

[gregmaxin]

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 not Z:\. The former should open a bash terminal and the latter will try and fail to open a WSL terminal.

[markarnott]

@craigloewen-msft I have installed the WSL prerelease version 1.2.5. That version has resolved this issue for me.

[md84419]

I've started getting this today, since applying the latest cumulative patch for Windows 10. I note @Sebazzz's comment in #4122 that in recent cumulative patches, a Windows 11 WSL is installed which has a different way of communcating between host and WSL.

My wsl version is 1.2.5.0.

[nerdola-de-cartola]

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:

wsl --list
wsl --setdefault <DISTRO_NAME> 

[DerTyp7]

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:

wsl --list
wsl --setdefault <DISTRO_NAME> 

For some reason, Docker set its own wsl distribution as default. Setting the default wsl to Ubuntu worked for me.

[sameera-karunaratne]

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:

wsl --list
wsl --setdefault <DISTRO_NAME> 

For some reason, Docker set its own wsl distribution as default. Setting the default wsl to Ubuntu worked for me.

This worked for me...

[arash-nykbakht-thelist]

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:

wsl --list
wsl --setdefault <DISTRO_NAME> 

For some reason, Docker set its own wsl distribution as default. Setting the default wsl to Ubuntu worked for me.

This is the correct answer, for some reason the default was set on docker-desktop-data. This happended after I used wsl --shutdown and a windows update

[elchemist705]

I 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

[junaga]

same error

wsl --list
wsl --setdefault <DISTRO_NAME> 

✅ worked for me

[hexxone]

This issue just re-appeared on win10 after forced update installation yesterday.

[gelodefaultbrain]

same error

wsl --list
wsl --setdefault <DISTRO_NAME> 

✅ worked for me

Hi , what's an example value for ?

[gelodefaultbrain]

If you don't have Ubuntu in one of the lists, you'd have to download it at first

Run command

wsl --install -d Ubuntu-22.04

Reason is that when you do wsl --list you might only find the stuff from Docker

Windows Subsystem for Linux Distributions:
docker-desktop
docker-desktop-data

So you need to install Ubuntu then do the following:

wsl --list
wsl --setdefault <DISTRO_NAME> 

Ubuntu-22.04 as the <DISTRO_NAME>

[Hakureiremu]

VScode could not connect to docker container, found error message:

[527 ms] Start: Run: wsl -d docker-desktop-data -e /bin/sh -c echo ~
[751 ms] Could not connect to WSL.
[751 ms] Command failed: wsl -d docker-desktop-data -e /bin/sh -c echo ~
[752 ms] 
[752 ms] <3>WSL (28) ERROR: CreateProcessParseCommon:708: Failed to translate D:\Microsoft VS Code

How to solve it in windows?

[iamyb]

same error here

scenario:

1. map\\wsl.localhost\$default_linux_distro to drive letter Z:
2. execute wsl find /home -path /home under drive Z:

error: <3>WSL (6739) ERROR: CreateProcessParseCommon:711: Failed to translate Z:\home

[mena234]

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:

wsl --list
wsl --setdefault <DISTRO_NAME> 

The only distros I have are

docker-desktop-data (Default)
docker-desktop

So, how could I update my distro?

[nerdola-de-cartola]

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:

wsl --list

wsl --setdefault <DISTRO_NAME> 

The only distros I have are

docker-desktop-data (Default)

docker-desktop

So, how could I update my distro?

In your case you have to install a new distro for example

wsl --install -d Ubuntu-22.04

You can also search for other distros in the Microsoft Store

After that you can set the new distro as the default

wsl --set-default Ubuntu-22.04

If you are not sure what is your distro name you can check with

wsl -- list

[stolenLeaf]

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:

wsl --list

wsl --setdefault <DISTRO_NAME> 

The only distros I have are

docker-desktop-data (Default)

docker-desktop

So, how could I update my distro?

In your case you have to install a new distro for example

wsl --install -d Ubuntu-22.04

You can also search for other distros in the Microsoft Store

After that you can set the new distro as the default

wsl --set-default Ubuntu-22.04

If you are not sure what is your distro name you can check with

wsl -- list

this works for me, thanks

[BrBill]

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:

D:\>wsl
<3>WSL (318) ERROR: CreateProcessParseCommon:711: Failed to translate D:\

Boo

[madushans]

I resolved this by switching the default distro.

IF you're using docker:

wsl --list

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.

wsl --setdefault Ubuntu

If you want to try installing Ubuntu, or another distro (to see if the issue is is local to your current distro), you can

wsl --install -d Ubuntu
# once done, set it as default as well
wsl --setdefault Ubuntu

Hope this helps to whoever runs into this with Docker

[mgteus]

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:

D:\>wsl
<3>WSL (318) ERROR: CreateProcessParseCommon:711: Failed to translate D:\

Boo

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

[BrBill]

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.

[zijinyuan]

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:

D:\>wsl
<3>WSL (318) ERROR: CreateProcessParseCommon:711: Failed to translate D:\

Boo

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

me 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

[elchemist705]

For the WSL errors

For some of your issues it would seem like solving your problems would be to Uninstall Windows Subsystem For Linux restart your computer and reinstall WSL 2 following these instructions Microsoft Learn - Installing WSL

For anyone wanting to export import using administrator cmd console follow the below photo

I hope this is helpful and I'm willing to further trouble shoot anyone needing any further help