WSL: wsl 2 can not use the mount path from dev drive

Windows Version

Microsoft Windows [Version 10.0.22621.2715]

WSL Version

1.2.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.90.1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

  1. create the dev drive from dev home preview app, also from https://learn.microsoft.com/en-us/windows/dev-drive/
  2. the dev drive is set to E:, and path is set to D:\packages
  3. shutdown wsl by wsl --shutdown
  4. open the WSL2 Ubuntu 22.04 distro, input ls /mnt/d/packages
  5. error: ls: cannot access '/mnt/d/packages': Input/output error

This error affects the usage of wsl docker command from windows host directly, like:

wsl docker compose up

if there is volume binding in docker-compose.yml file from the path mount from dev drive, also failed, like: d:\packages\workdir:/opt/workdir, In before, it works and d:\packages\workdir will be converted to /mnt/d/packages/workdir in wsl distro

Besides, in the windows terminal setting, if I set the default startingDirectory to “d:\packages”, the wsl terminall will failed also, but in before, wsl terminal can tell the startingDirectory, and convert to ‘/mnt/d/packages’

Expected Behavior

wsl 2 can use the path mount from dev drive like before.

Actual Behavior

leo@LeoCao-OMEN8Pro:~$ ls /mnt/d/packages/ ls: cannot access ‘/mnt/d/packages/’: Input/output error

Diagnostic Logs

image

WslLogs-2023-11-22_22-03-38.zip

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 17
  • Comments: 45 (1 by maintainers)

Most upvoted comments

I was able to uninstall the KB using this command, which fixed WSL for me

wusa /uninstall /kb:5044384

This may have broken with a recent Win11 update; this had been working perfectly for months, and last night my system installed a Windows Update and now I can’t access anything from my Dev Drive using WSL2.

WSL version: 2.3.24.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2152

Same issue on my system after a recent system update. Seems that update breaks the compatibility. I think this worth a reopening.

win11 26100.2033 works well, after install KB5044384 , DevDriver mount failed in wsl2

I’ve just run into this error today, Windows 11 Pro 10.0.26.26100.2161, however I’m getting an Error 0x800f0825 when attempting to remove the offending kb:5044384

As everything mentioned above, there are ways to bypass the problem. But it doesn’t make sense to rollback the system for this, since we have updates based on that KB5044384. It’s impossible to keep unupdated, which will cause serious security issue.

Seems that this is solved in update KB5046617 by its release notes.

Yesterday’s windows update fixed the issue. Thanks.

Yeah I am keen for a permanent solution. I’ve had to Pause updates to prevent KB5044384 from coming back.

Reopening due to reports of the issue not being resolved.

@juchom / @kirk-marple, can you capture /logs of the issues you’re seeing ?

What’s funny is retrying the update again today - and now it worked/installed!

Finally I had to create an USB media creation tool with windows 11 and reinstall it from there. Booting directly from the USB didn’t allow me to reinstall windows 11 keeping programs and files, I had to run it directly from windows from the usb. Another nonsense, not even the included windows reinstall option works and you have to manually create an usb…

  • Reinstall windows from restore pc is not even working in 24H2
  • Booting from USB doesn’t allow you to reinstall windows as you can do by just running the installer within windows.

The usb media creation tool directly installed this update, fixed at least…

The issue is fixed with Windows 11 24H2 (the root cause of the issue is in the Windows image so the fix cannot be part of the WSL package).