-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wsl 2 can not use the mount path from dev drive #10792
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. 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. Thank you! Open similar issues:
Closed similar issues:
|
/logs |
Hi I uploaded the logs~ |
Thank you @leolcao. Looking at the logs I can see that you have a custom kernel. Can you see if you can reproduce the issue with the official kernel ? If so, please collect /logs again |
I just updated the wsl to 2.0.9, and remove the custom kernel, unlucky, this issue still there~
btw, the dev-drive is mount to F:, and it is no error if I use command like Actually, I have 2 dev drives: Both them has same issue. |
@craigloewen-msft: Looks like we need to update p9rdr.sys to follow dev-drive mounts. |
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). |
Dev drive must have "Drive Letter". |
I tried the 24H2 release candidate Win11 build but the |
Agree. Issue still.
|
This issue is still present with 24H2, could you please reopen it : Windows information
Docker information
DevDrive information
If you run this command :
You will have this output
I also tried this according to this doc : https://learn.microsoft.com/en-us/windows/dev-drive/#filters-for-common-scenarios Adding filters for Docker: Running containers out of Dev Drive
Make sure they are present
Full reboot of the system and same issue. |
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 |
Same issue on my system after a recent system update. Seems that update breaks the compatibility. I think this worth a reopening. |
Reopening due to reports of the issue not being resolved. @juchom / @kirk-marple, can you capture /logs of the issues you're seeing ? |
another +1 on the pile Edition Windows 11 Education |
Here are the logs for my case
|
Same issue on linux. (Ubuntu 24.10)
|
My logs are linked to my report of this issue: |
I met same problem after update to win11 26100.2161 |
Another +1, went from a working setup on win11 insider previer (10.0.26120.2130) to a fresh win11 enterprise install (10.0.26100.2161). |
win11 26100.2033 works well, after install |
Also confirming, doing a System Restore to before KB5044384 (2024-10 Cumulative Update Preview for Windows 11 Version 24H2, build 26100.2161) was installed solved this for me. It will not be listed in the Uninstall Updates page, and trying to do so manually with wusa.exe will say it's "required by your computer and cannot be uninstalled". I also disabled "Get the latest updates as soon as they're available" after the reboot. The release notes list a new feature for VHDs that I could imagine is related to the issue. |
I was able to uninstall the KB using this command, which fixed WSL for me
|
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. |
@PhiliaTheCat can you describe the bypasses? Would be nice to have workarounds, that doesn't require to leave REFS drivces and copy all to another drive |
Yeah I am keen for a permanent solution. I've had to Pause updates to prevent KB5044384 from coming back. |
Exactly same issue here. I had to revert update KB5044384 as being unable to access files stored in a windows dev drive within WSL. After that I completely lost internet connectivity in Ubuntu under latest version of WSL (2.3.24) And I had to downgrade WSL to 2.2.4 and restart the computer. Now everything works. I was going crazy with this, as I thought it was permissions problem. |
I can confirm this works |
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 |
It works for me. You saved my day |
The uninstall worked - however now there's a new update - KB5046617 - that seems to fix dev drive issue - however since I did |
just a random thought, does /install work instead of uninstall?
|
Unfortunately no it doesn't work that way. I also tried downloading the KB5044384 files from Windows catalog and installing them (and then hoping to install latest) - but it fails with same error on trying to install KB5044384. Has anyone else been able to update with today's update that had uninstalled KB5044384? |
Seems that this is solved in update KB5046617 by its release notes. |
Just a guess, if Windows Update works in a way like git, where deltas between different versions are logged, then perhaps a full rollback will solve the problem. |
I'm unable to install the new update or reinstall the prior one... God... Error - instalación 0x800f081f |
I can confirm after installing the new update it has been fixed 💐 (KB5046617) |
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...
The usb media creation tool directly installed this update, fixed at least... |
Yesterday's windows update fixed the issue. Thanks. |
What's funny is retrying the update again today - and now it worked/installed! |
Windows Version
Microsoft Windows [Version 10.0.22621.2715]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
wsl --shutdown
ls /mnt/d/packages
ls: cannot access '/mnt/d/packages': Input/output error
This error affects the usage of
wsl docker
command from windows host directly, like: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 andd:\packages\workdir
will be converted to/mnt/d/packages/workdir
in wsl distroBesides, 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
WslLogs-2023-11-22_22-03-38.zip
The text was updated successfully, but these errors were encountered: