WSL2 is not able to access mounted dev drive in up to date 24H2

[lafe]

Windows Version

Microsoft Windows [Version 10.0.26100.3194]

WSL Version

2.4.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-microsoft-standard-WSL2

Distro Version

Ubuntu 24.24

Other Software

No response

Repro Steps

1. Create Dev Drive in Windows
2. Mount it as a folder at C:\Code
3. Open WSL and try to navigate to this folder

Expected Behavior

WSL should be able to navigate to the contents of a mounted dev drive.

Actual Behavior

The system is unable to navigate to that folder and returns "Input/Output" error:

lafe@Thinkpad:/mnt/c$ cd Code
-bash: cd: Code: Input/output error

The issue seems to be similar/identical to #10792, however the system is up to date and has all Windows 11 updates installed. Windows 11 was reinstalled recently using the up to date Windows ISO available in the Visual Studio benefits (en-us_windows_11_business_editions_version_24h2_updated_feb_2025_x64_dvd_a7fb58bd.iso) which should include KB5046617. When I try to manually install that update it just tells me that it is not applicable to my system.

Diagnostic Logs

No response

[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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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'.

[lafe]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'

[hach-que]

I've discovered that if the Dev Drive doesn't have a drive letter - i.e. it's only mapped to an NTFS path, then you'll still get Input/Output error. If you set a drive letter in addition to mapping the path, then you'll be able to access it via the path.