<3>WSL (8) ERROR: CreateProcessParseCommon:782: Failed to translate \\wsl.localhost\westie\home\mwoodpatrick #9252
Comments
|
Same here with an ubuntu-22.04 image Here are all dmesg lines with errors Hope it could help. |
|
Same here with Ubuntu 20.04 after updating with |
|
Same here... The issue arose yesterday after updating WSL with command |
|
Same issue: |
|
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 WSL version: 1.0.3.0 |
|
I saw same error message after updating to new WSL. Profile for distro |
|
my starting directory is set as |
|
Same here with Ubuntu 20.04 after updating with
|
|
I had a similar problem but it turned out to be caused by the way I was starting the |
|
I am experiencing this error on a clean Windows 11 22H2 installation and default WSL using |
|
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. |
|
I have this problem as well on an Ubuntu 20.04.5 LTS distribution. From the WSL bash prompt, when I execute e.g. |
|
This issue is related to following previously reported issue I was able to resolve my issue by removing the following from /etc/wsl.config [automount] [interop] |
|
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. |
|
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 This is what I'm seeing 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.... |
|
I found a workaround for this (I can't remember where in order to credit them however). |
Confirming it works! Thanks! |
|
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:
What is the cause of the issue, and how is it properly resolved? |
|
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 |
|
@craigloewen-msft |
|
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. |
This worked for me... |
This is the correct answer, for some reason the |
|
I had this same issue and it was fixed by setting the default distribution |
|
same error wsl --list
wsl --setdefault <DISTRO_NAME> ✅ worked for me |
|
This issue just re-appeared on win10 after forced update installation yesterday. |
Hi , what's an example value for <DISTRO_NAME>? |
|
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 So you need to install Ubuntu then do the following: Ubuntu-22.04 as the |
|
VScode could not connect to docker container, found error message: How to solve it in windows? |
|
same error here scenario:
error: |
The only distros I have are So, how could I update my distro? |
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 |
this works for me, thanks |
|
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. Boo |
|
I resolved this by switching the default distro. IF you're using docker: see how many distros you got. 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 |
I'm facing the same problem described here by @BrBill, just tried to install a .tar file from a wsl --export
|
|
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. |
me too, have the same trouble, <3>WSL (14) ERROR: CreateProcessEntryCommon:334: getpwuid(0) failed 2 |
For the WSL errorsFor 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 photoI hope this is helpful and I'm willing to further trouble shoot anyone needing any further help |
|
Note, if you're seeing that error in VS Code while trying to run terminal as WSL then you need to be sure you opened your project using WSL and not Windows. Therefore, if you navigated to your project folder in VS Code using Windows, then you're in the Windows OS and you'll get the aforementioned |
|
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 pathAfter re-mounting my wsl pathIf 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.
|
Confirmed, @adrianegraphene, this worked. Then I made it permanent by adding an Thanks! |
|
I had this issue as well. In my case I was executing a command from the linux command prompt in a different wsl distro than the current one (current one named
and the error was Further, the reported path it failed to translate was always the current working directory in the running distro ( In any case, the
|
|
A 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.. |
and others
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
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\mwoodpatrickwhen 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
The text was updated successfully, but these errors were encountered: