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
Plan9FileSystem hogging external USB drive with open handle #7972
Comments
I just ran into this as well:
WSL version: 0.51.2.0 |
I also have this problem. The DLLHost. With Proccessid {DFB65C4C-B34F-435D-AFE9-A86218684AA8} locks my external drive, even this drive have NEVER been used by WSL. Win 10 21H2: 19044.2006 Also why are you (WSL devs) running this under a dllhost.exe, it seems like a bad approach. When I need to troubleshoot my PC, I do not want to go lookup GUIDs in the hunt of the actual problem in context of a dllhost. What is the reason for this? |
Is a fix for this in the horizon? Right now I have to keep killing dllhost.exe, then executing it again after ejecting the drive, and then I need to reboot WSL for it to get back access to Window's filesystem. |
same issue on win11 DllHost.exe /Processid:{DFB65C4C-B34F-435D-AFE9-A86218684AA8} WSL version: 1.1.3.0 |
You can try the following: open
Reference: https://learn.microsoft.com/en-us/windows/wsl/wsl-config#automount-settings But is doesn't work for my Docker Container, because Docker Desktop rewrite wsl.conf after restart, and I don't know where I can adjust appropriate Docker setting to disable automount. |
This is incredibly annoying. Shutting down WSL allowed me to safely remove the drive though. |
Version
WSL version: 0.51.2.0 Kernel version: 5.10.81.1 WSLg version: 1.0.30 Windows version: 10.0.22000.434
WSL Version
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
Don't know exactly how to reproduce, but right now there is a
dllhost.exe
having an open handle onD:\
(which is an external USB drive) and preventing it from ejecting.It was started with the commandline
C:\WINDOWS\system32\DllHost.exe /Processid:{DFB65C4C-B34F-435D-AFE9-A86218684AA8}
, a registry search pointed toHKEY_CLASSES_ROOT\CLSID\{AFC7B6DE-D642-41B7-AB0C-A01019510741}
which has an entry namedPlan9FileSystem
so it's probably WSL2 related.The handle is still open after
wsl --shutdown
.Expected Behavior
WSL2 file system bridge should not prevent external drives from ejecting
Actual Behavior
External drives cannot be ejected
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: