Failed to attach disk '\\192.168.1.123\ext4.vhdx' to WSL2: The user name or password is incorrect.

[jebarpg]

Windows Version

Microsoft Windows [Version 10.0.19045.4598]

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

clearlinux

Other Software

No response

Repro Steps

I have a network shared drive mapped.

In PowerShell (administrator mode)

I have ran this command successfully:

wsl --import-in-place my_distro_name "\path_to_my_NAS_share_directory\ext4.vhdx"

and it imports just fine.

then when I run

wsl -d my_distro_name

I get the following error:

Failed to attach disk '\path_to_my_NAS_share_directory\ext4.vhdx' to WSL2: The user name or password is incorrect.

Error code: Wsl/Service/CreateInstance/MountVhd/HCS/0x8007052e

I don't know where to look for setting the credentials for WSL to be able to access the NAS directory location. Any direction or help would be greatly appreciated.

Expected Behavior

To actually start the distribution.

Actual Behavior

getting the error message

Failed to attach disk '\path_to_my_NAS_share_directory\ext4.vhdx' to WSL2: The user name or password is incorrect.

Error code: Wsl/Service/CreateInstance/MountVhd/HCS/0x8007052e

Diagnostic Logs

WslLogs-2024-07-03_18-30-20.zip

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

• WSL cannot mount VHD located on network share (smb) (#7803), similarity score: 0.72

Closed similar issues:

• Network share subdirectory mounting issue (#9163), similarity score: 0.74
• Failed to attach disk 'C:\Program Files\WSL\system.vhd' to WSL2: The system cannot find the file specified (#11703), similarity score: 0.71

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[jebarpg]

Diagnostic logs:
WslLogs-2024-07-03_18-30-20.zip

[github-actions]

Diagnostic information

Detected appx version: 2.0.14.0
Detected user visible error: Wsl/Service/CreateInstance/MountVhd/HCS/0x8007052e

[github-actions]

Diagnostic information

Issue was edited and new log file was found: https://github.com/user-attachments/files/16092250/WslLogs-2024-07-03_18-30-20.zip
Detected appx version: 2.0.14.0
Detected user visible error: Wsl/Service/CreateInstance/MountVhd/HCS/0x8007052e

[ghost]

This is a limitation of the current hcs apis that wsl is built on top of.

[jebarpg]

I see you added the features label. Does this mean that it will be looked over for future development? And if so what is the timeline for when features like this get evaluated as worth implementing by the contributors?