search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.32k stars 814 forks source link

Can't access Linux filesystem through the Linux menu in File Explorer #7541

Open fonnesbeck opened 2 years ago

fonnesbeck commented 2 years ago

Version

Microsoft Windows [Version 10.0.22000.258]

WSL Version

Kernel Version

5.10.16

Distro Version

Debian 2

Other Software

VSCode WSL Remote extension 0.58.2 Powershell 7

Repro Steps

After having installed Debian under WSL2, click on the the Linux icon in File Explorer sidebar.

Expected Behavior

Should have been able to see the WSL file system inside the Linux folder on File Explorer.

Actual Behavior

When I click on the Linux penguin icon, I get the error in the screen shot below:

2021-10-14 (2)

Interestingly, if I call \wsl$ from File Explorer, I can access the WSL file system from inside the Network folder.

Diagnostic Logs

No response

Ryton commented 2 years ago

Likewise. i can SEE \wsl$\ maps, when browsing to \wsl$\ but cannot access /open the directories, nor are \mnt\c\ dir populated. My error message is different though, so might be a different reason: image image (Tested with Debian & Ubuntu 18.04). hmm, nvr mind, probably more related to #7488 (same message)

gbiagini commented 2 years ago

Same exact issue as @fonnesbeck, using W11, WSL2, Ubuntu 20.04.

I'm able to use explorer.exe . from the WSL terminal and get to the files also, and even pin to Quick Access. Interestingly, that does not allow access to the Linux menu in File Explorer, unlike typing \\wsl.localhost into the File Explorer address bar.

I've been using W11 since the initial Dev Channel release and this issue has been persistent (~6 months). On my other device, running Windows 11 on Arm, I'm able to access the Linux menu in File Explorer with no issue.

tetsuya-ops commented 2 years ago

I have the same problem, here I did some changes on a registry entry called: "ProviderOrder" in "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order". When I changed it, it worked again, but, as I have installed WD Discovery, it changes the key again, so I have no access again... It is a problem caused by NAS or Network Drives programs, but as it is a problem of most of all NAS or Network Drives programs, It may be solved by Microsoft, instead of all this programs... becuase they are not just one or two... They are more... Hope this is going to be fixed on the February release of W11. Best Rewards.

borisdamevin commented 9 months ago

Someone has solution plz?