Share via

WSL2: Error: 0x80040315

仙林 杨 0 Reputation points
2026-01-27T13:18:13.2566667+00:00

When I use WSL, I encounter the following issues: 

wsl: Failed to mount D:\, see dmesg for more details. 
wsl: Failed to mount D:\, see dmesg for more details. 
wsl: Failed to translate 'D:\Bandizip\' 
wsl: Failed to translate 'D:\Git\cmd'

I attempted to mount the corresponding disk directly, but this resulted in the following error:

wsl --mount \\.\PHYSICALDRIVE0  
Cannot attach disk '\\.\PHYSICALDRIVE0' to WSL2: Error: 0x80040315 
Error code: Wsl/Service/AttachDisk/MountDisk/WSL_E_ELEVATION_NEEDED_TO_MOUNT_DISK
Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Domic Vo 19,580 Reputation points Independent Advisor
    2026-01-28T11:59:35.59+00:00

    Good morning

    I hope you are doing well.

    Have you found the answer useful? If everything is okay, don't forget to share your experience with the issue by accepting the answer. Should you need more information, free free to leave a message. Happy to help! :)

    Domic Vo.

    0 comments
  2. Domic Vo 19,580 Reputation points Independent Advisor
    2026-01-27T13:50:10.95+00:00

    Hello 仙林 杨,

    The error you're seeing : WSL_E_ELEVATION_NEEDED_TO_MOUNT_DISK is not a bug. It's a strict permission requirement enforced by WSL2 when attempting to mount physical drives. The command wsl --mount \\.\PHYSICALDRIVE0 must be executed from an elevated PowerShell or Command Prompt session. If you're running it from a standard user shell, the mount will fail every time with that exact error.

    The same applies to the failed mount attempts for D:\. If you're trying to access Windows paths from inside WSL and getting translation errors like Failed to translate 'D:\Bandizip\', it usually means the drive is either not mounted properly in /mnt/, or the WSL instance lacks permission to access it due to ACL restrictions or BitLocker encryption. If the drive is encrypted or mounted with restricted access, WSL will not be able to translate or bind it.

    To resolve this, first ensure you're launching your terminal as Administrator. Then confirm that the drive is not encrypted or locked. If you're using BitLocker, the drive must be unlocked before WSL can mount it. Also, check that your /etc/wsl.conf does not contain any custom mount overrides that could interfere with auto-mount behavior.

    If you're still seeing translation failures for specific folders like D:\Git\cmd, verify that the folder exists and is accessible from Windows Explorer. If it's a junction point or symbolic link, WSL may not resolve it correctly depending on the distro and kernel version.

    Lastly, if you're using third-party antivirus or endpoint protection (Trend Micro, for example), it may interfere with WSL's disk access. Try temporarily disabling it and reattempt the mount to rule out interference.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!Domic Vo.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.