WSL: "Failed to translate" errors in CreateProcessParseCommon and UtilTranslatePathList
Version
WSL version: 0.65.3.0 Kernel version: 5.15.57.1 WSLg version: 1.0.41 MSRDC version: 1.2.3213 Direct3D version: 1.601.0 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22000.856
WSL Version
- WSL 2
- WSL 1
Kernel Version
Linux version 4.4.0-22000-Microsoft (Microsoft@Microsoft.com) (gcc version 5.4.0 (GCC) ) #653-Microsoft Wed Apr 27 16:06:00 PST 2022
Distro Version
Debian 11
Other Software
A functioning JDK build/test setup
Repro Steps
make TEST='test/jdk/tools/launcher/ClassPathWildCard.sh' test
Expected Behavior
No WSL errors occur
Actual Behavior
The following occurs on stderr:
<3>WSL (206) ERROR: CreateProcessParseCommon:731: Failed to translate E:\Repositories\com.github\jdk\build\windows-x86_64-server-release\test-support\jtreg_test_jdk_tools_launcher_ClassPathWildCard_sh\scratch\0
<3>WSL (206) ERROR: UtilTranslatePathList:2509: Failed to translate e:\repositories\com.github\jdk\build\windows-x86_64-server-release\images\jdk
<3>WSL (206) ERROR: UtilTranslatePathList:2509: Failed to translate e:\repositories\com.github\jdk\build\windows-x86_64-server-release\images\jdk
<3>WSL (206) ERROR: UtilTranslatePathList:2509: Failed to translate E:\Repositories\com.github\jdk\test\jdk
<3>WSL (206) ERROR: UtilTranslatePathList:2509: Failed to translate e:\repositories\com.github\jdk\build\windows-x86_64-server-release\images\test\jdk\jtreg\native
sh: 0: Can't open /mnt/e/Repositories/com.github/jdk/test/jdk/tools/launcher/ClassPathWildCard.sh
Diagnostic Logs
strace-ff.zip WslLogs-2022-08-14_10-40-46.zip strace-no-ff.log
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 38
@OneBlue
This issue still exists. I just updated WSL to the store version per the startup text recommendation in WSL. After this, my Ubuntu2004 installation now won’t mount /mnt/c or /mnt/d. Manaually attempting to mount them throws this message (the same one that’s found in dmesg).
This has broken my vscode integration as well and my entire development workflow depended on these translations being functional. Is there a workaround? I’ve tried several of the above methods in this thread.
As I mentioned in #4122:
To give some context on this:
If the drives are not mounted, WSL cannot translate between Windows and Linux path. If that’s what you want, you can set:
in
/etc/wsl.confand the warnings will go away.If automount is disabled but you have manual mounts in
/etc/fstab, the distribution needs to restarted for path translation to work.Closing since this should cover both scenarios.
My fairly old wsl2 setup also failed to mount the windows drives at some point. running
wsl --updatein a windows admin shell fixed the issue.<3>WSL (70) ERROR: CreateProcessParseCommon:782: Failed to translate D:\Kali Linux UIUX <3>WSL (70) ERROR: UtilTranslatePathList:2671: Failed to translate D:\Programma\Java\bin <3>WSL (70) ERROR: UtilTranslatePathList:2671: Failed to translate D:\Fullter\src\bin <3>WSL (70) ERROR: UtilTranslatePathList:2671: Failed to translate D:\Fullter\flutter_windows_3.3.7-stable\flutter\bin <3>WSL (70) ERROR: UtilTranslatePathList:2671: Failed to translate D:\Fullter\flutter\bin <3>WSL (70) ERROR: UtilTranslatePathList:2671: Failed to translate D:\Programma\Vs Code\Microsoft VS Code\bin Failed to mount D:, see dmesg for more details.
┏━(Message from Kali developers) ┃ ┃ This is a minimal installation of Kali Linux, you likely ┃ want to install supplementary tools. Learn how: ┃ ⇒ https://www.kali.org/docs/troubleshooting/common-minimum-setup/ ┃ ┗━(Run: “touch ~/.hushlogin” to hide this message) ┌──(code-x13㉿WIN-6G2CFD61UB7)-[~]
<<WHAT IS MY D: >>
@flipkickmedia
In my case I tried to get rid of the standard mounts so WSL can’t interfere with the actual Windows system. I believe I did nothing except for disabling the auto mounts. And I’m also not sure if I’ve installed it via Windows Store. At least none of the Ubuntu “Apps” in the store says “Installed already”
Im seeing this in WSL2 when attempting to unmount the WSL partition. I also had a BSOD during a termination/unregistration of a newly imported instance after an unmount.
The vhdx for this WSL instance is also in a none standard location.
The ACL for C:\Windows\system32
And then again when logging into the WSL instance