-
Notifications
You must be signed in to change notification settings - Fork 847
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
Unable to access WSL filesystem from File Explorer after updated to Win11 Insider Preview 10.0.26058.1100 #11171
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 |
Hello! Could you please provide more logs to help us better diagnose your issue? To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. 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. Thank you! |
Windows Version
Microsoft Windows [Version 10.0.26058.1100]
WSL Version
2.1.1.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-2
Distro Version
Ubuntu-22.04
Other Software
No response
Repro Steps
wsl --unregister Ubuntu-22.04
andwsl --install Ubuntu-22.04
in Windows PowershellExpected Behavior
There should be a Linux filesystem in my File Explorer and quick access to WSL folders should work
Actual Behavior
Linux filesystem and quick access disappeared
I can access WSL by
\\wsl$
but quick access linked to it does not workDiagnostic Logs
No response
The text was updated successfully, but these errors were encountered: