-
Notifications
You must be signed in to change notification settings - Fork 821
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
Can't access wsl in File Explorer + Possible Fix #9010
Comments
I found a workaround. The address now is \\wsl$ probably because of an update. I had to go into regedit: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{B2B4A4D1-2754-4140-A2EB-9A76D9D7CDC6}\Instance\InitPropertyBag And change the ResName from \\wsl.localhost to \\wsl$ For that I had to take full ownership of the {B2B4A4D1-2754-4140-A2EB-9A76D9D7CDC6} folder and give me full access rights, so I could change ResName. Now it's working fine. I posted this as an issue because this probably should get fixed nonetheless. Edit: After I restarted my system, it didn't work anymore. I noticed that after I access wsl through typing the address in the address bar, I can access it through the linux button again. I don't know why I need to do this, if I use another explorer app it all just works fine. So if this is explorer related and not wsl's fault, feel free to close this issue. |
Yea I'm also having this problem too. Not sure what to do either. I followed what you said as a partial workaround and that did not work for me. |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Version
Windows 11 22H2
WSL Version
Kernel Version
5.15.68.1
Distro Version
Ubuntu 20.04
Other Software
docker desktop
Repro Steps
Fresh Windows Install
Install wsl
install docker desktop
restart pc
Expected Behavior
Accessing Linux in File Explorer works fine
Actual Behavior
Can't access the linux tab in file explorer
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: