Can't access WSL P9 Network Linux Filesystem Share #5307
Comments
|
If you run the command |
|
|
Yes, the distro is installed, shows up, and is otherwise usable as expected.
The distro is running, and manually navigating to |
Yeah, maybe it's to be expected like that. Similar to computer in a network, how can we access it if the computer is turned off. |
It is not. Despite the
|
|
I have this exact same issue and my p9np.dll and registry keys look identical. |
|
But calling 9p access is a bit weird: PS C:\> wsl -l -v
NAME STATE VERSION
* Ubuntu-20.04 Running 2
Ubuntu-20.04.wsl1 Stopped 1
Alpine Stopped 2
PS C:\> cd \\wsl$\Alpine
PS Microsoft.PowerShell.Core\FileSystem::\\wsl$\Alpine>I can only do |
|
@philg @gloy-atromitos Only |
|
I don't know if I can be any more clear on this, access to the distros filesystem from Windows doesn't work ever.
It does not work if the |
|
I've read there are two 9p running servers, one for admin and the other for the user. |
|
Have previously done so, just verified it now, no change in behaviour across the board. |
|
I have seen more users with the same problem. They can use Maybe @SvenGroot has an idea what's happening. |
|
try |
Not necessary, the executable is found. |
|
Can you post the output of |
|
|
I'm seeing this problem also. Can Interestingly launching explorer.exe . from within WSL2 works but always ends up opening my Documents folder in Windows filesystem instead. This works however. |
I got exactly the same issue. Nobody found a better solution yet? |
|
Got the same issue after upgrading Windows: |
|
Fixed now: |
This is very clearly different than the issue I am having; this already doesn't work for me.
This also doesn't seem to be related to my problem, as the |
|
Today I again un- and reinstalled WSL2 with a reboot in-between every step, the issue persists exactly as described in my original comment. |
|
I installed via chocolatey and have the same issue: |
|
My issue turned out to be that via Chocolatey WSL Ubuntu is installed to require admin rights ( It was solved by:
Afterward:
|
|
FWIW, I'm seeing the same issue as well. I installed Ubuntu 20.04 from the Windows Store. I can |
Very same issue on my computer as well. |
|
So, to add another twist to this, if I use the url |
That definitely doesn't work for mine (
For reference I'm running Edit: for completeness: |
I'm now checking back, tried a new fresh install and update of Windows 11 on a new machine with build 22000.739 and WSL kernel version 5.10.102.1 Still same error, There's still no way to run WSL on Windows 11 and have interactivity with Windows or networking. WSL has been abandoned for very very long time now. Almost a year, and I really wish at some point soon it will be usable for us running Windows 11 and not just Windows 10. It's an incredibly nice tool when working with Windows specific stuff in parallel, and would add value to the Windows 11 ecosystem. |
|
I dont know maybe it will work for u guys but It helped me to enter the file system simply by typing in the start menu "\wsl$"(with 2 \) and then pressing the execute command, if it helped, I would be glad :) |
|
I have had the same problem in my wsl2 environment, I fixed it by doing the following:
If it worked for you let me know :) |
|
I'm trying to understand exactly what problems people are still having now, in the summer of 2022. The original statement is a bit stale (for example, nobody should have to install kernel updates before testing whether things work). I am able to access files across the WSL/Windows boundaries in both Windows 10 and WIndows 11, as well as use networking on both, so if someone can summarize the current state of the problem, I can try to think this through. Otherwise, re-stating the problem will at least help you think through it again with more knowledge than this group had back in 2022, and it will help other people like me who stumble into this thread via a misdirected Google match to understand the current nature of the problem better. I'm a little hesitant to give any advice based on a problem description from 2020, because while there's been good discussion about ongoing investigation, there has not been much restatement or modification of the problem statement itself. So, here are some "ice breaker" ideas.
Information like this and any other information that hasn't yet been captured might give us a better idea of where to look and where not to look. Any takers? :) As I said, my system is working, but if I can get to where I can repro the issue myself, I might be able to find a fix for it, or at least an explanation. Also, for what it's worth, while this must be extremely frustrating, I don't think that Microsoft has abandoned WSL. Not at all, in fact. We use it a lot at work, and it has become a key part of developer workflow around the world. Its ability to let people develop for Windows and Linux on a single workstation is really valuable, and the integrations of WSL in products like VS Code that let you do that seamlessly have become valuable enough in the dev community that Microsoft would have a high-priority problem on their hands if this were misbehaving for a large number of devs. The problem here is to figure out why it's misbehaving so badly for this group of people. I hope we can figure that out so that you can enjoy its benefits again. I'd hate to see you have to use a full VM for Linux when you really shouldn't have to. |
|
I'm not at work now, but this is what we tried last week. There are at a minimum one reboot between each point.
We can access \wsl$... in explorer, but can't run windows apps from wsl that opens a wsl path. I wish I remembered the path it uses from wsl, it's not \wsl but something like \wsl.localhost instead. Edit: this \wsl.localhost is not accessible directly from explorer either, just \wsl$ is. Also, using explorer.exe . in wsl might work first time, we've had false moments of happiness when restarting wsl service and so on, it lasts for maybe a minute. |
|
Thanks! I'm not at work either. It is the weekend! We might have a cadence where you folks will post things during the week, and if (that's a big if) I have something to contribute, that might wait until the weekend. So this is a clean Windows 11, fully patched. Then you run If you could verify the Ubuntu version, that would help. I have all 20.04 currently on my own laptop. I will install 22.04 (Ubuntu 22.04.1 LTS) and see what happens. |
|
I can confirm that it works the same with Ubuntu 20.04 and Debian, we've had this problem since windows 11 release when 22.04 wasn't released yet. I don't think the dist matters. Also, yes code is vscode, but I don't need to run it for the problem to happen. It has been how we tested, but I've tried reinstalling without installing the remote vscode before the problem occurred. In my eyes it just looks like the rights to wsl.localhost doesn't work properly and should be wsl$ instead, but I've no idea how to force wsl to use another network path. |
|
Thanks @TTSKarlsson. Currently, I am unable to repro. this. This is what I did. First I ran through the steps in WIndows 10, and then I did the same things in Windows 11. The first thing I did was to install Ubuntu 22.04.1 LTS from the Windows Store on both laptops, as it was not installed on either. For Windows 10, in addition to performing the steps that are in the large code block below, I also opened locations in Windows Explorer and from Installation successful!
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Welcome to Ubuntu 22.04.1 LTS (GNU/Linux 5.10.102.1-microsoft-standard-WSL2 x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
/etc/update-motd.d/50-landscape-sysinfo: 17: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
7 updates can be applied immediately.
To see these additional updates run: apt list --upgradable
This message is shown once a day. To disable it please create the
/home/cleonard/.hushlogin file.
cleonard@LTTC-74HJCK3:~$ # THIS IS ON WINDOWS 10
cleonard@LTTC-74HJCK3:~$ # we expect this to work:
cleonard@LTTC-74HJCK3:~$ ls -ald /mnt/c/Program*
drwxrwxrwx 1 cleonard cleonard 512 Aug 13 15:39 /mnt/c/ProgramData
dr-xr-xr-x 1 cleonard cleonard 512 Aug 5 08:50 '/mnt/c/Program Files'
dr-xr-xr-x 1 cleonard cleonard 512 Aug 2 11:30 '/mnt/c/Program Files (x86)'
cleonard@LTTC-74HJCK3:~$ # it appears that the following is currently working for me:
cleonard@LTTC-74HJCK3:~$ explorer.exe .
cleonard@LTTC-74HJCK3:~$ # ... and I have run it from / and other directories
cleonard@LTTC-74HJCK3:~$ # ... I'm not going to post screenshots b/c that would bloat the post,
cleonard@LTTC-74HJCK3:~$ # ... but will be happy to post any you want to see
cleonard@LTTC-74HJCK3:~$ # let's see if some others work:
cleonard@LTTC-74HJCK3:~$ notepad.exe ./.bashrc
cleonard@LTTC-74HJCK3:~$ # that did work
cleonard@LTTC-74HJCK3:~$ # let's try something more interesting...
cleonard@LTTC-74HJCK3:~$ # since beyond compare is a Windows program, I have to give it file
cleonard@LTTC-74HJCK3:~$ # references it understands, so I'll use \\wsl$ references. since
cleonard@LTTC-74HJCK3:~$ # backslash is an escape character in bash, I will have to escape
cleonard@LTTC-74HJCK3:~$ # those by doubling them up. let's see if this works...
cleonard@LTTC-74HJCK3:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe \\\\wsl$\\Ubuntu-22.04\\home\\cleonard\\.bashrc \\\\wsl$\\Ubuntu-22.04\\home\\cleonard\\.bash_logout
cleonard@LTTC-74HJCK3:~$ # it took me three tries, but that worked. terrible typing experience, though.
cleonard@LTTC-74HJCK3:~$ # it seems like single-quoting the filenames would be easier:
cleonard@LTTC-74HJCK3:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe '\\wsl$\Ubuntu-22.04\home\cleonard\.bashrc' '\\wsl$\Ubuntu-22.04\home\cleonard\.bash_logout'
cleonard@LTTC-74HJCK3:~$ # that _was_ much easier, though still no tab completion. blech.
cleonard@LTTC-74HJCK3:~$ # this might be the easiest way to run that particular command. it comes down to personal preference, I suppose.
cleonard@LTTC-74HJCK3:~$ alias bcompare='/mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe'
cleonard@LTTC-74HJCK3:~$ bcompare $(wslpath -w ~/.bashrc) $(wslpath -w ~/.bash_logout)
cleonard@LTTC-74HJCK3:~$ # that also worked, yayOn to WIndows 11, I did exactly the same steps, except that I also accessed folders from both WIndows Explorer and Installation successful!
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
Welcome to Ubuntu 22.04.1 LTS (GNU/Linux 5.10.102.1-microsoft-standard-WSL2 x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage
/etc/update-motd.d/50-landscape-sysinfo: 17: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
7 updates can be applied immediately.
To see these additional updates run: apt list --upgradable
This message is shown once a day. To disable it please create the
/home/chris/.hushlogin file.
cleonard@caerdydd:~$ # THIS IS ON WINDOWS 11
chris@caerdydd:~$ # we expect this to work:
chris@caerdydd:~$ ls -ald /mnt/c/Program*
drwxrwxrwx 1 chris chris 512 Aug 9 15:55 /mnt/c/ProgramData
dr-xr-xr-x 1 chris chris 512 Jul 11 16:24 '/mnt/c/Program Files'
dr-xr-xr-x 1 chris chris 512 Jul 15 21:20 '/mnt/c/Program Files (x86)'
chris@caerdydd:~$ # it appears that the following is currently working for me:
chris@caerdydd:~$ explorer.exe .
chris@caerdydd:~$ # ... and I have run it from / and other directories
chris@caerdydd:~$ # ... I'm not going to post screenshots b/c that would bloat the post,
chris@caerdydd:~$ # ... but will be happy to post any you want to see
chris@caerdydd:~$ # let's see if some others work:
chris@caerdydd:~$ notepad.exe ./.bashrc
chris@caerdydd:~$ # that worked, but took longer to load on Windows 11 than it did on Windows 10.
chris@caerdydd:~$ # that might or might not be a repeatable result - i'm not going to check things like that now.
chris@caerdydd:~$ # on to the Beyond Compare tests!
chris@caerdydd:~$ # these all worked just like they did on Windows 10.
chris@caerdydd:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe \\\\wsl$\\Ubuntu-22.04\\home\\cleonard\\.bashrc \\\\wsl$\\Ubuntu-22.04\\home\\cleonard\\.bash_logout
chris@caerdydd:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe \\\\wsl$\\Ubuntu-22.04\\home\\chris\\.bashrc \\\\wsl$\\Ubuntu-22.04\\home\\chris\\.bash_logout
chris@caerdydd:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe '\\wsl$\Ubuntu-22.04\home\chris\.bashrc' '\\wsl$\Ubuntu-22.04\home\chris\.bash_logout'
chris@caerdydd:~$ alias bcompare='/mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe'
chris@caerdydd:~$ bcompare $(wslpath -w ~/.bashrc) $(wslpath -w ~/.bash_logout)So for the time being, I am in the "it's working so far" group. I will try to get my dotfiles and git repos ported over to 22.04.1 in the next week or so in order to use it as my daily repo and see if it will break for me. Let me know what I may have missed, misunderstood, or left out in trying to recreate the problem. Thanks! |
|
I would say it works for you, at least if you let the wsl run for quite some time and it still worked. I'll do the same, when I'm at my test setup, follow the same format and post results here. I personally really want this to work. |
|
Ok, I'm in position. I didn't reinstall windows this time as it's newly installed anyway. I uninstalled previous Ubuntu before doing this.
I logged out from wsl for 1 minute here.
I can right now access |
|
For completeness I also installed 22.04 from the store with the graphical installer.
I suspect enough time has passed for
And I get the same denied message.
|
|
In an open explorer window, I can access
But not any of the wsl roots
Restarting the computer doesn't help, I've had success with restarting the entire service but this happens after a few minutes again. |
|
My network setup to this machine is nothing weird, a normal router with normal dns on a 200/200 fiber connection. No proxies or vpns.
There are network shares on the network, like ssh and samba, but they shouldn't change this machines settings in any way.
|
|
@cleonard-godaddy , Do you need more info? |
|
@TTSKarlsson, thanks for the nudge. I don't think I need more info. My "problem" is that I still cannot reproduce the problem on Windows 10, with either Ubuntu 20.04 LTS or 22.04 LTS. I haven't used my Windows 11 laptop this week. Actually, I do have one question: what Windows build were you on when you sent your last set of comments? And @Ninili, what version and build of WIndows, WSL version(s), and Linux distribution versions are you running? You probably know this, but just in case it helps you or someone else:
|
|
Windows 11 build 22000.856 PS C:\Windows\System32> wsl -l -v
NAME STATE VERSION
* Ubuntu Stopped 2
Ubuntu-22.04 Stopped 2testing@upstairs:~$ cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS"
NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focaland tkarlsson@upstairs:~$ cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS"
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammyImportant things you should know:
|
Actually I could resolve the issue by calling "explorer.exe ." from within the wsl, from my home path like @onomatopellan suggested! I didn't even know you could just call explorer.exe from within the WSL. But this kind of "broke the barrier". And I'm on 21H2 (Build 19044.1889), the WSL2 distros are all kinds of versions (16.xx, 18.04, 20.04, they all run now) |
|
Any updates or workarounds on this issue? Experiencing the same problem with WSL 2, Ubuntu 22.04.1 and Windows 11 22h2 (Build 22621.521) |
I tried this again with a new install, and now it works. I've revisited a couple of days to make sure it is stable and it keeps on working, which is a first since the launch of Win11 one year ago. I'll do the same on a couple other machines again now, and if it works there too I won't come back to this thread.
|
Could you solve the issue? |
So far no good. |
|
Unfortunately same here with wsl2. |
I was able to resolve my issue by editing the registry entries Source: #4027 (comment) |
|
@MisterTimn method worked for me. |
|
I am having this issue, but my
|
|
You can also set the regex order directly in the windows interface so that it will persist after reboot: https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/network-provider-settings-removed-in-place-upgrade |
|
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! |
and others
Your Windows build number: (Type
verat a Windows Command Prompt)Microsoft Windows [Version 10.0.19041.264]
What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
wsl --set-default-version 2\\wsl$\Ubuntu\Attempt to access invalid addressWhat's wrong / what should be happening instead:
Additional information
The Ubuntu share shows in Explorer, but trying to access it fails.
No
/etc/wsl.conffile in use.dir \\wsl$ordir \\wsl$\Ubuntuin PowerShell fail withCannot find path ...apt-get update && apt-get upgradewere ran including WSL restartsdmesg
From #4027 (comment):
dir C:\Windows\system32\p9np.dll
reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s
reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s
reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s
The text was updated successfully, but these errors were encountered: