![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 88%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,545 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(9.6, 83%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAC%3C/text%3E%3C/svg%3E)
Sure, I can help you with that. The errors you’re seeing are related to the Windows Subsystem for Linux (WSL) having issues with translating Windows paths and mounting drives. Here are some steps you can take to resolve these issues:
Failed to Translate Paths: This error usually occurs when there are obsolete entries in your system’s PATH environment variable1. You can resolve this by:
Opening **`SystemPropertiesAdvanced.exe`**
Clicking on **`Environment variables`**
Double-clicking **`Path`** under **`System variables`**
[Deleting the obsolete entries and clicking ](https://www.winhelponline.com/blog/ubuntu-wsl-utiltranslatepathlist-failed-translate/)**[`OK`](https://www.winhelponline.com/blog/ubuntu-wsl-utiltranslatepathlist-failed-translate/)**[1](https://www.winhelponline.com/blog/ubuntu-wsl-utiltranslatepathlist-failed-translate/)
**[getpwuid(0) failed 2](https://superuser.com/questions/1761555/3wsl-12-error-createprocessentrycommon570-execvpe-usr-bin-zsh)**[: This error might occur if the default shell is not properly set](https://superuser.com/questions/1761555/3wsl-12-error-createprocessentrycommon570-execvpe-usr-bin-zsh)[2](https://superuser.com/questions/1761555/3wsl-12-error-createprocessentrycommon570-execvpe-usr-bin-zsh). You can try setting it to bash using the command: **`wsl ~ -e chsh`**. [Set it to ](https://www.winhelponline.com/blog/ubuntu-wsl-utiltranslatepathlist-failed-translate/)**[`/usr/bin/bash`](https://www.winhelponline.com/blog/ubuntu-wsl-utiltranslatepathlist-failed-translate/)**[ and then try starting again](https://www.winhelponline.com/blog/ubuntu-wsl-utiltranslatepathlist-failed-translate/)[2](https://superuser.com/questions/1761555/3wsl-12-error-createprocessentrycommon570-execvpe-usr-bin-zsh).
**[Failed to Mount Drives](https://linuxnightly.com/mount-and-access-hard-drives-in-windows-subsystem-for-linux-wsl/)**[: If WSL is unable to mount your drives (C:, D:, S:), you can manually mount them using the following commands](https://linuxnightly.com/mount-and-access-hard-drives-in-windows-subsystem-for-linux-wsl/)[3](https://linuxnightly.com/mount-and-access-hard-drives-in-windows-subsystem-for-linux-wsl/)[4](https://stackoverflow.com/questions/63010412/docker-desktop-with-wsl2-unable-to-start):
First, create a directory for the drive: **`sudo mkdir /mnt/d`**
Then, mount the drive: **`sudo mount -t drvfs D: /mnt/d`**
Replace **`D:`** with the appropriate drive letter.
**[CreateProcessEntryCommon Errors](https://stackoverflow.com/questions/77890139/windows-sub-system-for-linux-failure-to-load-by-fstab-has-failed-to-mount)**[: These errors might be related to the default distribution set in WSL](https://stackoverflow.com/questions/77890139/windows-sub-system-for-linux-failure-to-load-by-fstab-has-failed-to-mount)[5](https://stackoverflow.com/questions/77890139/windows-sub-system-for-linux-failure-to-load-by-fstab-has-failed-to-mount). [You can change the default distribution using the command: ](https://stackoverflow.com/questions/77890139/windows-sub-system-for-linux-failure-to-load-by-fstab-has-failed-to-mount)**[`wsl --set-default Ubuntu`](https://stackoverflow.com/questions/77890139/windows-sub-system-for-linux-failure-to-load-by-fstab-has-failed-to-mount)**[5](https://stackoverflow.com/questions/77890139/windows-sub-system-for-linux-failure-to-load-by-fstab-has-failed-to-mount).
Please note that you might need to restart your WSL instance or your computer for these changes to take effect. If the problem persists, please let me know so I can assist you further.