search

microsoft / WSL

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

P9 Explorer Integration not working #4027

Open bushidocodes opened 5 years ago

bushidocodes commented 5 years ago

Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.

If you have a feature request, please post to the UserVoice.

If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.

Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump\".

Please fill out the below information:

Based on the recent WSL blogs, I expect to see WSL as a network drive in Explorer or to be able to open my active WSL directory by typing Explorer.exe .

When I enter the Explorer command from anywhere in the Linux filesystem, it opens my Windows Documents folder in Explorer

When I try to manually navigate to the path suggested by the blog posts, I get a 0x80004005 image

However, I can navigate to that directory from Powershell. image

If it's relevant, here is a snapshop of my network devices. I've got some VPN stuff and Hyper-V V Switches, including for Docker for Windows.

jonitis commented 5 years ago

Might be similar to https://github.com/microsoft/WSL/issues/3995

shinji257 commented 5 years ago

I've updated to 1903 18362.30 as of yesterday and I'm noticing this issue as well. What I've noticed is this.

All tests done while Ubuntu is running. Did a clean install of the Ubuntu "app".

benhillis commented 5 years ago

@SvenGroot - Could you please take a look into this?

bushidocodes commented 5 years ago

After getting the final official 1903 build (I've previously been on 1903 as an insider), I went blew away both of my Pengwin-based environments and fully disabled and re-enabled the WSL feature. This seems to have resolved this issues for me on both of my systems. Since I has having this problem consistently on both machines, this suggests that something might have misfired in applying an update to an existing WSL install.

SvenGroot commented 5 years ago

Anybody who's still in this state, can you please give me the output of the following commands:

dir %windir%\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

That would be very helpful in diagnosing this issue.

For those who are interested, here's the reason why it works in cmd or PowerShell, but not in explorer.exe. \\wsl$ is essentially treated by the system as a network file system (even though it isn't really), which consist of two components: a redirector driver, and a network provider DLL. The former handles actual file system requests, while the latter provides information about connections and paths to the system. This DLL also implements things like "share" enumeration (distribution enumeration in WSL's case), and "map drive" functionality.

The network provider DLL is not used when applications just try to create a file using a \\wsl$\distro path, which is what cmd and PowerShell do. Explorer on the other hand always tries to get information about a UNC path from the network provider DLL, and won't issue a file system call unless that's successful. So in the situation described in this thread, the redirector driver is fine, but the DLL is not working as intended for some reason.

hazzanz commented 5 years ago

Turning off and on WSL worked for me. I didn't need to delete the instance.

shinji257 commented 5 years ago

Anybody who's still in this state, can you please give me the output of the following commands:

dir %windir%\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

That would be very helpful in diagnosing this issue.

As requested.

C:\Users\shinj>dir %windir%\System32\p9np.dll
 Volume in drive C has no label.
 Volume Serial Number is 6473-A230

 Directory of C:\WINDOWS\System32

05/23/2019  01:51 AM           101,688 p9np.dll
               1 File(s)        101,688 bytes
               0 Dir(s)  50,341,449,728 bytes free

C:\Users\shinj>reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    PROVIDERORDER    REG_SZ    RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    PROVIDERORDER    REG_SZ    RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    P9NP    REG_DWORD    0x1f4

C:\Users\shinj>reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np
    Description    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-101
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider
    DeviceName    REG_SZ    \Device\P9Rdr
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100
    Name    REG_SZ    Plan 9 Network Provider
    ProviderPath    REG_EXPAND_SZ    %SystemRoot%\System32\p9np.dll

C:\Users\shinj>reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr
    DependOnService    REG_MULTI_SZ    RDBSS
    Description    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-101
    DisplayName    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-100
    ErrorControl    REG_DWORD    0x1
    ImagePath    REG_EXPAND_SZ    System32\drivers\p9rdr.sys
    Start    REG_DWORD    0x3
    Type    REG_DWORD    0x1
SvenGroot commented 5 years ago

@shinji257 Thanks, that's very interesting.

It appears that P9NP is missing from the comma-separated list under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order and HwOrder. It's present in ProviderOrder, but that doesn't do anything by itself if the value is not in the comma-separated list. This will cause Explorer and any other application that uses the network provider DLL to not consider our provider at all.

You should be able to work around this by just adding P9NP as the first entry in the comma-separated list under both keys (in your case, this would be "P9NP,RDPNP,LanmanWorkstation,webclient"). You might need to restart for that change to take effect.

This suggests there's some bug in the upgrade logic for this particular registry key. We'll investigate further and I'll keep you updated.

shinji257 commented 5 years ago

Thank you. I've checked and verified that was indeed all that was needed to workaround for this issue and it updated both Order and HwOrder at the same time when I did that.

EDIT: Restarting the system, relogging, or even reloading explorer.exe was not needed. The effect was immediate.

danluca commented 5 years ago

Have a similar issue but on the worse side - just updated to Windows 1903, had the legacy lxrun distro installed (Bash on Windows). Have wiped it out and started fresh, enabled WSL feature and installed Ubuntu distro from MS store.

The distro launches fine, but none of the "\wsl$" integration works for me - neither command prompt, nor explorer. Looking at the output to the command checks posted by shinji257 - my output looks correct, the P9NP is in the right places:

D:\> cmd /c ver
Microsoft Windows [Version 10.0.18362.145]

D:\> cmd /c dir %windir%\System32\p9np.dll
 Directory of C:\WINDOWS\System32
06.02.2019  12:18 AM           101 688 p9np.dll
               1 File(s)        101 688 bytes

D:\> reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    P9NP    REG_DWORD    0x1f4

D:\> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np
    Description    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-101
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider
    DeviceName    REG_SZ    \Device\P9Rdr
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100
    Name    REG_SZ    Plan 9 Network Provider
    ProviderPath    REG_EXPAND_SZ    %SystemRoot%\System32\p9np.dll

D:\> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr
    DependOnService    REG_MULTI_SZ    RDBSS
    Description    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-101
    DisplayName    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-100
    ErrorControl    REG_DWORD    0x1
    ImagePath    REG_EXPAND_SZ    System32\drivers\p9rdr.sys
    Start    REG_DWORD    0x3
    Type    REG_DWORD    0x1

Any ideas what to look for next?

RoguePointer80 commented 5 years ago

Similar issue here.

Microsoft Windows [Version 10.0.18362.175]

C:\Users\frivard>reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    P9NP    REG_DWORD    0x1f4

So it appears the order is correct. The other two queries are the same as @danluca . With Windows Explorer, going to \wsl$, I can see my distro correctly (Ubuntu-16.04). It is currently running bash. Trying to access \wsl$\Ubuntu-16.04 in Windows Explorer gives "Attempt to access invalid address".

With cmd:

C:\Users\frivard>dir \\wsl$\Ubuntu-16.04
The remote computer refused the network connection.

With Powershell:

PS C:\Users\frivard> dir \\wsl$\Ubuntu-16.04
dir : Cannot find path '\\wsl$\Ubuntu-16.04' because it does not exist.
At line:1 char:1
+ dir \\wsl$\Ubuntu-16.04
+ ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (\\wsl$\Ubuntu-16.04:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

Similar to other users, after upgrading to Windows 1903, I deleted my old distros, and installed a fresh one; installed a bunch of tools inside it, then I did an export of it. I remember at that point I was able to access the Linux files because I copied a file in it. Shutdown my computer, next day install a bunch of Windows updates, reboot computer... That's when I tried to use my new distro and noticed I could no longer access the Linux files with the 9P integration. I rebooted the computer again, but it did not fix the issue.

Any idea how to diagnose this? I had a look at the Windows Event Logs, but could not see anything related to WSL.

SvenGroot commented 5 years ago

Can you post the output of running dmesg in WSL? If the server encountered any problems when starting, it should be in there.

RoguePointer80 commented 5 years ago 
index@WKS-000837:~$ dmesg
[    0.020411]  Microsoft 4.4.0-18362.1-Microsoft 4.4.35
[    0.120460] <3>init: (1) ERROR: LogException:23: FS: Could not start file system server. Operation not permitted @.\plan9.cpp:33 (TranslatePath)

Ah! you're right, the server on the Linux distro simply did not start. I see TranslatePath... does it matter that I disabled the /mnt/c in my wsl.conf?

Here is my wsl.conf. If I screwed up, I'm sorry.

index@WKS-000837:~$ cat /etc/wsl.conf
[automount]
enabled = false
mountFsTab = true

[network]
generateHosts = true
generateResolvConf = true

[interop]
enabled = false
appendWindowsPath = false
SvenGroot commented 5 years ago

Yes, that would be it. :)

The \\wsl$ file system access communicates with the Plan 9 server running in WSL's init using a Unix socket, and that socket is created in in a directory under /mnt/c. So yeah, you need to enable automount for this to work (or at least explicitly mount your C: drive in fstab).

Note that this is not the case in WSL 2, since in that case we communicate over a Hyper-V socket instead.

RoguePointer80 commented 5 years ago

@SvenGroot Thank you for your quick reply. Also I wanted to let you know, Thank You to all the WSL team, it is a great product and I use it everyday. And especially that 9P thing, it is super-awesome work. Keep it up!

SvenDowideit commented 5 years ago

@SvenGroot had to add P9NP to the Order registry key on 2 systems - both were upgraded from WSL i1 n the last week :+1: :)

danluca commented 5 years ago

Still doesn't work for me, any suggestions on how to debug this issue further? How can I check whether the P9 server is running? I've attached the log files (captured with logman per the instructions) and the output of the ps aux is below: lxcore.zip

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   8892   308 ?        Ssl  13:39   0:00 /init
root         8  0.0  0.0   8904   220 tty1     Ss   13:39   0:00 /init
dan          9  0.1  0.0  16792  3464 tty1     S    13:39   0:00 -bash
root        26  0.0  0.0  17272  2536 tty1     S    13:41   0:00 sudo -s
root        27  0.0  0.0  16688  3308 tty1     S    13:41   0:00 /bin/bash
root        39  3.0  0.0  17380  1920 tty1     R    13:42   0:00 ps aux

The dmesg produces a single line output - [ 0.007696] Microsoft 4.4.0-18362.1-Microsoft 4.4.35 Ideas?

tionebrr commented 5 years ago

Ubuntu and Debian are working fine, but I can't access the subsystem files at all, and P9 doesn't seems to be there at all... I surely messed something up during the install, but can't find a fix. I also tried going backward and made a clean install trough the MS Store, didn't worked.

Windows 10.0.17134

PS C:\Users\Beubeuh> dir %windir%\System32\p9np.dll
dir : Impossible de trouver le chemin d'accès « C:\Users\Beubeuh\%windir%\System32\p9np.dll », car il n'existe pas.
Au caractère Ligne:1 : 1
+ dir %windir%\System32\p9np.dll
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\Users\Beubeu...stem32\p9np.dll:String) [Get-ChildItem], ItemNotFound
   Exception
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

PS C:\Users\Beubeuh> reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    RDPNP,LanmanWorkstation,webclient,Nfsnp

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    RDPNP,LanmanWorkstation,webclient,Nfsnp

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    nfsnp    REG_DWORD    0xfa0

PS C:\Users\Beubeuh> reg query HKLM\SYSTEM\CurrentControlSet\Control\p9np /s
Erreur : Erreur : le système n’a pas trouvé la clé ou la valeur de Registre spécifiée.
PS C:\Users\Beubeuh> reg query HKLM\SYSTEM\CurrentControlSet\Control\p9rdr /s
Erreur : Erreur : le système n’a pas trouvé la clé ou la valeur de Registre spécifiée.
PS C:\Users\Beubeuh>

Also, wsl --shutdown yields a command not found error inside the subsystems.

craigloewen-msft commented 5 years ago

@PureBasic it looks like you're using an older version of Windows that does not have the P9 feature. You need to upgrade your Windows version to 1903 or later (Windows Build 18362).

tionebrr commented 5 years ago

@mscraigloewen Thanks, it worked after updating indeed ! I thought my system was up to date, turns out I had only the critical updates enabled.

mjbright commented 5 years ago

Thanks, the registry fix worked for me.

However, I still can't access anything under home, i.e. \wsl$\Ubuntu\home is empty Why is that?

==> OK, just realized why It's been a while since I switched to WSL, I forgot that my home dir was a link to C:\tools\cygwin\home\windo

TheWhiteGuardian commented 4 years ago

I am having this same issue with explorer, and ultimately came across this thread. A big thank you to @craigloewen-msft because after your post it all started to make sense.

Looking at the output of CMD, and cross-referencing this value with a list of windows builds: https://en.wikipedia.org/wiki/Windows_10_version_history#Rings Gave the answer. As it turns out, I'm still running Windows 1809. I'll be back if I am still encountering issues after the update has finished. Big thanks to all of you, here's hoping it all goes well.

FossPrime commented 4 years ago

Not sure what happened, restarting worked :/

let me be a bit more helpful... I installed the openssh feature, MiniGW and the GNU32Utils4Win package and tried addidng a few registry edits to default to WSL bash from system32.

jbdamiano commented 4 years ago

I'm on the build 19624 but mysystem doesn't have the p9np dll

dir %windir%\System32\p9np.dll dir : Cannot find path 'D:\Users\jdamiano\Desktop\LEGATO\FDT2\%windir%\System32\p9np.dll' because it does not exist. At line:1 char:1

Why it it missing on my system ?

psgrove commented 4 years ago

Bit of a torrid time with access to wsl$ Updated to 2004 release did all the wsl 2 install and Ubuntu all looked great. Then typed explorer.exe . and all exploror did was open in the documents library folder. After much searching just couldn't access wsl$ location. Then I read that lastest insider edition had the nice linux folder in explorer. So against my better judgement switched on insider program fast ring got the update. Set up wsl2 again had to unistall kernal patch and reinstall. Clicked the linux folder in explorer to be greated with attached picture. wsl

Then I found this issue on Github, I ran the regestry checks and looks like one of the entries is incorect, see in bold below reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

**HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder PROVIDERORDER REG_SZ LanmanWorkstation,RDPNP,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order PROVIDERORDER REG_SZ LanmanWorkstation,RDPNP,webclient**

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder LanmanWorkstation REG_DWORD 0x7d0 RDPNP REG_DWORD 0x3e8 webclient REG_DWORD 0xbb8 P9NP REG_DWORD 0x1f4

reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np Description REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-101 DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider DeviceName REG_SZ \Device\P9Rdr DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100 Name REG_SZ Plan 9 Network Provider ProviderPath REG_EXPAND_SZ %SystemRoot%\System32\p9np.dll TriggerStartCompleteNotification REG_BINARY 7510BCA3541EC641 TriggerStartNotification REG_BINARY 7508BCA3541EC641 TriggerStartPrefix REG_SZ wsl$

reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr DependOnService REG_MULTI_SZ RDBSS Description REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-101 DisplayName REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-100 ErrorControl REG_DWORD 0x1 ImagePath REG_EXPAND_SZ System32\drivers\p9rdr.sys Start REG_DWORD 0x3 Type REG_DWORD 0x1

Registry key updated now all fixed

rwerning-skyline commented 4 years ago

Not sure if anyone is still monitoring this issue, but wanted to document that there is still some issue here. I haven't found a solution.

I'm having a similar issue. My Ubuntu WSL2 instance doesn't show up with an icon or way to quick access in file explorer, however I am able to access it manually by opening \wsl$\Ubuntu in explorer.

In Ubuntu:
$ cd ~ $ explorer.exe #opens explorer to quick access

Just opens Explorer in Windows to the Quick Access folder. I updated this computer to W10 2004, then set up WSL2, It did not have WSL or VM Platform installed previously, still doesn't have Hypervisor installed.

Per the request by SvenGroot May 24, 2019:

C:\Users\rwerning>dir %windir%\System32\p9np.dll Volume in drive C is Local Disk Volume Serial Number is 9803-CC04

Directory of C:\WINDOWS\System32

12/07/2019 06:19 AM 107,048 p9np.dll 1 File(s) 107,048 bytes 0 Dir(s) 388,012,908,544 bytes free

C:\Users\rwerning>reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder ProviderOrder REG_SZ P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order ProviderOrder REG_SZ P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder LanmanWorkstation REG_DWORD 0x7d0 RDPNP REG_DWORD 0x3e8 webclient REG_DWORD 0xbb8 P9NP REG_DWORD 0x1f4

C:\Users\rwerning>reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np Description REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-101 DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider DeviceName REG_SZ \Device\P9Rdr DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100 Name REG_SZ Plan 9 Network Provider ProviderPath REG_EXPAND_SZ %SystemRoot%\System32\p9np.dll TriggerStartCompleteNotification REG_BINARY 7510BCA3541EC641 TriggerStartNotification REG_BINARY 7508BCA3541EC641 TriggerStartPrefix REG_SZ wsl$

C:\Users\rwerning>reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr DependOnService REG_MULTI_SZ RDBSS Description REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-101 DisplayName REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-100 ErrorControl REG_DWORD 0x1 ImagePath REG_EXPAND_SZ System32\drivers\p9rdr.sys Start REG_DWORD 0x3 Type REG_DWORD 0x1

shinji257 commented 4 years ago

The visibility to quick access in explorer directly with an icon was added in the insider builds.

RJWerning commented 4 years ago

That explains why I see it on my personal laptop w/insider, but not on my work one with 2004. :) Thanks for the info

michael-imbeault commented 4 years ago

I have this issue, but my reg keys are fine as far as I can tell:

PS C:\WINDOWS\system32> reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder ProviderOrder REG_SZ P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order ProviderOrder REG_SZ P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder LanmanWorkstation REG_DWORD 0x7d0 RDPNP REG_DWORD 0x3e8 webclient REG_DWORD 0xbb8 P9NP REG_DWORD 0x1f4

PS C:\WINDOWS\system32> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np Description REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-101 DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider DeviceName REG_SZ \Device\P9Rdr DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100 Name REG_SZ Plan 9 Network Provider ProviderPath REG_EXPAND_SZ %SystemRoot%\System32\p9np.dll TriggerStartCompleteNotification REG_BINARY 7510BCA3541EC641 TriggerStartNotification REG_BINARY 7508BCA3541EC641 TriggerStartPrefix REG_SZ wsl$

PS C:\WINDOWS\system32> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr DependOnService REG_MULTI_SZ RDBSS Description REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-101 DisplayName REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-100 ErrorControl REG_DWORD 0x1 ImagePath REG_EXPAND_SZ System32\drivers\p9rdr.sys Start REG_DWORD 0x3 Type REG_DWORD 0x1

hariharan382 commented 4 years ago

reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np Description REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-101 DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider DeviceName REG_SZ \Device\P9Rdr DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100 Name REG_SZ Plan 9 Network Provider ProviderPath REG_EXPAND_SZ %SystemRoot%\System32\p9np.dll TriggerStartCompleteNotification REG_BINARY 7510BCA3541EC641 TriggerStartNotification REG_BINARY 7508BCA3541EC641 TriggerStartPrefix REG_SZ wsl$

C:\Users\jvija>reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr DependOnService REG_MULTI_SZ RDBSS Description REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-101 DisplayName REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-100 ErrorControl REG_DWORD 0x1 ImagePath REG_EXPAND_SZ System32\drivers\p9rdr.sys Start REG_DWORD 0x3 Type REG_DWORD 0x1

lpleausing wsl2 but unable to solve the isuues ,in above comments svenroot said to add p9np but how completely helpless since i am newbie

jkomyno commented 4 years ago

I added the P9NP entry at the beginning of the lists in Order and HWOrder, but I'm missing the P9NP service altogether.

C:\Users\jkomyno>reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    P9NP    REG_DWORD    0x1f4

C:\Users\jkomyno>reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s
ERROR: The system was unable to find the specified registry key or value.
jscssphtml commented 3 years ago 
dir %windir%\System32\p9np.dll
 Verzeichnis von C:\WINDOWS\System32

07.12.2019  17:06           107.048 p9np.dll
               1 Datei(en),        107.048 Bytes
----------------------------------------
reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    P9NP    REG_DWORD    0x1f4
----------------------------------------
reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np
    Description    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-101
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider
    DeviceName    REG_SZ    \Device\P9Rdr
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100
    Name    REG_SZ    Plan 9 Network Provider
    ProviderPath    REG_EXPAND_SZ    %SystemRoot%\System32\p9np.dll
    TriggerStartCompleteNotification    REG_BINARY    7510BCA3541EC641
    TriggerStartNotification    REG_BINARY    7508BCA3541EC641
    TriggerStartPrefix    REG_SZ    wsl$
----------------------------------------
reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr
    DependOnService    REG_MULTI_SZ    RDBSS
    Description    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-101
    DisplayName    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-100
    ErrorControl    REG_DWORD    0x1
    ImagePath    REG_EXPAND_SZ    System32\drivers\p9rdr.sys
    Start    REG_DWORD    0x3
    Type    REG_DWORD    0x1
madhankumar388 commented 3 years ago

Turning off and on WSL worked for me. I didn't need to delete the instance.

This is the only fix that worked for me .. Cheers for posting . Simple and easy fix .

felipeportella commented 2 years ago

Just reporting that I had the exact same issue today with Windows [Version 10.0.22000.194]. The P9NP was missing in the registry:

reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    PROVIDERORDER    REG_SZ    RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    PROVIDERORDER    REG_SZ    RDPNP,LanmanWorkstation,webclient`

I just did as @SvenGroot suggested here: added P9NP as the first entry in both keys and performed a boot. Then it started working as expected (including the new Linux icon that seems a alias to it).

Thanks for the workaround but something in the upgrade logic is still broken :(

If any other info / log could help to track down the root cause, just let me know and I could share.

rstanuwijaya commented 2 years ago

My registry list already has P9NP in it, but I still encountered the bug.

I finally found a fix that worked for me. As mentioned by @SvenGroot here,

Yes, that would be it. :)

The \wsl$ file system access communicates with the Plan 9 server running in WSL's init using a Unix socket, and that socket is created in in a directory under /mnt/c. So yeah, you need to enable automount for this to work (or at least explicitly mount your C: drive in fstab).

Note that this is not the case in WSL 2, since in that case we communicate over a Hyper-V socket instead.

I appended the following entries to my /etc/wsl.conf

[automount]
enabled = true
mountFsTab = true

Thanks to everyone for contributing to resolving this bug!

ghoztdog commented 2 years ago

I additionaly had to remove the cbfs entry ("cbfsconnect2017" or "cbfs6") from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order and HwOrder to make it work.

XboxBedrock commented 2 years ago

I had P9NP however I had to remove cbfsconnect2017 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder

rstanuwijaya commented 2 years ago

I still have this issue occurring again from time to time. I read from another thread (sorry I can't find the source again atm) that it is caused by calling a script that calls init.d on startup; in my case, it is a script that forwards the WSL port to my Windows, for example:

wsl.exe sudo /etc/init.d/ssh start
$wsl_ip = (wsl hostname -I).trim()
Write-Host "WSL Machine IP: ""$wsl_ip"""
netsh interface portproxy add v4tov4 listenport=2222 connectport=2222 connectaddress=$wsl_ip

Can anyone else check whether disabling this kind of script (if it exists) helps to resolve this problem?

kczx3 commented 2 years ago

@shinji257 Thanks, that's very interesting.

It appears that P9NP is missing from the comma-separated list under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order and HwOrder. It's present in ProviderOrder, but that doesn't do anything by itself if the value is not in the comma-separated list. This will cause Explorer and any other application that uses the network provider DLL to not consider our provider at all.

You should be able to work around this by just adding P9NP as the first entry in the comma-separated list under both keys (in your case, this would be "P9NP,RDPNP,LanmanWorkstation,webclient"). You might need to restart for that change to take effect.

This suggests there's some bug in the upgrade logic for this particular registry key. We'll investigate further and I'll keep you updated.

It took me so long to find this resolution. Thank you!

On a side note, my File Explorer doesn't show the Linux penguin icon on the left side panel. Is there a similar configuration that might be missing for me? Or does that just need to be manually added?

shinji257 commented 2 years ago

Recently I dug into this again after someone mentioned cbfs being the root cause for them. Today I noticed cbfs6 was listed in my ProviderOrder. Removing it allows the Linux item to function properly however now RaiDrive can't render cloud "drive" information in explorer properly anymore. Just shows Disconnected status. With that said the drives themselves are still accessible anyways.

benyaminl commented 2 years ago

Anybody who's still in this state, can you please give me the output of the following commands:

dir %windir%\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

Related to https://github.com/microsoft/WSL/issues/5718

Microsoft Windows [Version 10.0.19044.1826]
(c) Microsoft Corporation. All rights reserved.

C:\Users\benli
> dir %windir%\System32\p9np.dll
 Volume in drive C has no label.
 Volume Serial Number is 1E72-4CB0

 Directory of C:\WINDOWS\System32

20/11/2021  15:32           107.048 p9np.dll
               1 File(s)        107.048 bytes
               0 Dir(s)  352.364.744.704 bytes free

C:\Users\benli
> reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    WinFsp.Np,P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    WinFsp.Np,P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    P9NP    REG_DWORD    0x1f4
    WinFsp.Np    REG_DWORD    0xfa

C:\Users\benli
> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np
    Description    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-101
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider
    DeviceName    REG_SZ    \Device\P9Rdr
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100
    Name    REG_SZ    Plan 9 Network Provider
    ProviderPath    REG_EXPAND_SZ    %SystemRoot%\System32\p9np.dll
    TriggerStartCompleteNotification    REG_BINARY    7510BCA3541EC641
    TriggerStartNotification    REG_BINARY    7508BCA3541EC641
    TriggerStartPrefix    REG_SZ    wsl$

C:\Users\benli
> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr
    DependOnService    REG_MULTI_SZ    RDBSS
    Description    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-101
    DisplayName    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-100
    ErrorControl    REG_DWORD    0x1
    ImagePath    REG_EXPAND_SZ    System32\drivers\p9rdr.sys
    Start    REG_DWORD    0x3
    Type    REG_DWORD    0x1

Then the dmesg 

BEN-TP-X220:[~]$ dmesg
[    0.000000] Linux version 5.10.102.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Wed Mar 2 00:30:59 UTC 2022
[    0.000000] Command line: initrd=\initrd.img panic=-1 pty.legacy_count=0 nr_cpus=2
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000e0fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000001fffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x0000000000200000-0x00000000f7ffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000107ffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] Hypervisor detected: Microsoft Hyper-V
[    0.000000] Hyper-V: privilege flags low 0x2e7f, high 0x3b8030, hints 0x62c2c, misc 0x20bed7b2
[    0.000000] Hyper-V Host Build:19041-10.0-1-0.1826
[    0.000000] Hyper-V: LAPIC Timer Frequency: 0x1e8480
[    0.000000] Hyper-V: Using hypercall for remote TLB flush
[    0.000000] clocksource: hyperv_clocksource_tsc_page: mask: 0xffffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns: 440795202120 ns
[    0.000001] tsc: Marking TSC unstable due to running on Hyper-V
[    0.000005] tsc: Detected 2790.932 MHz processor
[    0.000015] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000019] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000023] last_pfn = 0x108000 max_arch_pfn = 0x400000000
[    0.000063] MTRR default type: uncachable
[    0.000064] MTRR fixed ranges enabled:
[    0.000065]   00000-3FFFF write-back
[    0.000066]   40000-7FFFF uncachable
[    0.000067]   80000-8FFFF write-back
[    0.000069]   90000-FFFFF uncachable
[    0.000070] MTRR variable ranges enabled:
[    0.000071]   0 base 000000000 mask F00000000 write-back
[    0.000073]   1 base 100000000 mask 000000000 write-back
[    0.000073]   2 disabled
[    0.000074]   3 disabled
[    0.000075]   4 disabled
[    0.000075]   5 disabled
[    0.000076]   6 disabled
[    0.000077]   7 disabled
[    0.000096] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.000117] last_pfn = 0xf8000 max_arch_pfn = 0x400000000
[    0.000917] RAMDISK: [mem 0x03835000-0x03844fff]
[    0.000920] ACPI: Early table checksum verification disabled
[    0.000943] ACPI: RSDP 0x00000000000E0000 000024 (v02 VRTUAL)
[    0.000948] ACPI: XSDT 0x0000000000100000 000044 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000956] ACPI: FACP 0x0000000000101000 000114 (v06 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000965] ACPI: DSDT 0x00000000001011B8 01E184 (v02 MSFTVM DSDT01   00000001 MSFT 05000000)
[    0.000970] ACPI: FACS 0x0000000000101114 000040
[    0.000974] ACPI: OEM0 0x0000000000101154 000064 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000979] ACPI: SRAT 0x000000000011F33C 000230 (v02 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000984] ACPI: APIC 0x000000000011F56C 000058 (v04 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000989] ACPI: Reserving FACP table memory at [mem 0x101000-0x101113]
[    0.000990] ACPI: Reserving DSDT table memory at [mem 0x1011b8-0x11f33b]
[    0.000991] ACPI: Reserving FACS table memory at [mem 0x101114-0x101153]
[    0.000992] ACPI: Reserving OEM0 table memory at [mem 0x101154-0x1011b7]
[    0.000993] ACPI: Reserving SRAT table memory at [mem 0x11f33c-0x11f56b]
[    0.000994] ACPI: Reserving APIC table memory at [mem 0x11f56c-0x11f5c3]
[    0.001007] ACPI: Local APIC address 0xfee00000
[    0.001460] Zone ranges:
[    0.001462]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.001465]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.001466]   Normal   [mem 0x0000000100000000-0x0000000107ffffff]
[    0.001468]   Device   empty
[    0.001469] Movable zone start for each node
[    0.001470] Early memory node ranges
[    0.001472]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.001473]   node   0: [mem 0x0000000000200000-0x00000000f7ffffff]
[    0.001475]   node   0: [mem 0x0000000100000000-0x0000000107ffffff]
[    0.001477] Initmem setup node 0 [mem 0x0000000000001000-0x0000000107ffffff]
[    0.001479] On node 0 totalpages: 1048223
[    0.001480]   DMA zone: 59 pages used for memmap
[    0.001481]   DMA zone: 22 pages reserved
[    0.001483]   DMA zone: 3743 pages, LIFO batch:0
[    0.001484]   DMA32 zone: 16320 pages used for memmap
[    0.001485]   DMA32 zone: 1011712 pages, LIFO batch:63
[    0.001486]   Normal zone: 512 pages used for memmap
[    0.001488]   Normal zone: 32768 pages, LIFO batch:7
[    0.001914] On node 0, zone DMA: 1 pages in unavailable ranges
[    0.001968] On node 0, zone DMA: 352 pages in unavailable ranges
[    0.056205] ACPI: Local APIC address 0xfee00000
[    0.056218] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[    0.060462] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
[    0.060470] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.060474] ACPI: IRQ9 used by override.
[    0.060477] Using ACPI (MADT) for SMP configuration information
[    0.060490] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[    0.060505] [mem 0xf8000000-0xffffffff] available for PCI devices
[    0.060506] Booting paravirtualized kernel on Hyper-V
[    0.060509] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.081356] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:2 nr_node_ids:1
[    0.083298] percpu: Embedded 56 pages/cpu s190040 r8192 d31144 u1048576
[    0.083307] pcpu-alloc: s190040 r8192 d31144 u1048576 alloc=1*2097152
[    0.083309] pcpu-alloc: [0] 0 1
[    0.083329] Hyper-V: PV spinlocks enabled
[    0.083334] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.083338] Built 1 zonelists, mobility grouping on.  Total pages: 1031310
[    0.083340] Kernel command line: initrd=\initrd.img panic=-1 pty.legacy_count=0 nr_cpus=2
[    0.088841] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.090524] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.090601] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.199443] Memory: 4013364K/4192892K available (16404K kernel code, 2544K rwdata, 9048K rodata, 1580K init, 2772K bss, 179272K reserved, 0K cma-reserved)
[    0.199495] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.199503] Kernel/User page tables isolation: enabled
[    0.199521] ftrace: allocating 51665 entries in 202 pages
[    0.250484] ftrace: allocated 202 pages with 4 groups
[    0.251045] rcu: Hierarchical RCU implementation.
[    0.251047] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2.
[    0.251049]  Rude variant of Tasks RCU enabled.
[    0.251050]  Tracing variant of Tasks RCU enabled.
[    0.251052] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.251053] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.262759] Using NULL legacy PIC
[    0.262764] NR_IRQS: 16640, nr_irqs: 440, preallocated irqs: 0
[    0.263449] random: get_random_bytes called from start_kernel+0x3ac/0x56c with crng_init=0
[    0.263482] Console: colour dummy device 80x25
[    0.263497] printk: console [tty0] enabled
[    0.263504] ACPI: Core revision 20200925
[    0.263691] Failed to register legacy timer interrupt
[    0.263692] APIC: Switch to symmetric I/O mode setup
[    0.263720] Hyper-V: Using IPI hypercalls
[    0.263721] Hyper-V: Using enlightened APIC (xapic mode)
[    0.263878] Calibrating delay loop (skipped), value calculated using timer frequency.. 5581.86 BogoMIPS (lpj=27909320)
[    0.263882] pid_max: default: 32768 minimum: 301
[    0.263908] LSM: Security Framework initializing
[    0.263935] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.263943] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.264368] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
[    0.264370] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
[    0.264375] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.264377] Spectre V2 : Mitigation: Full generic retpoline
[    0.264378] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.264379] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.264381] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.264383] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.264386] MDS: Mitigation: Clear CPU buffers
[    0.264552] Freeing SMP alternatives memory: 56K
[    0.268331] smpboot: CPU0: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz (family: 0x6, model: 0x2a, stepping: 0x7)
[    0.268489] Performance Events: unsupported p6 CPU model 42 no PMU driver, software events only.
[    0.268542] rcu: Hierarchical SRCU implementation.
[    0.269119] smp: Bringing up secondary CPUs ...
[    0.269234] x86: Booting SMP configuration:
[    0.269236] .... node  #0, CPUs:      #1
[    0.383898] smp: Brought up 1 node, 2 CPUs
[    0.383902] smpboot: Max logical packages: 1
[    0.383904] smpboot: Total of 2 processors activated (11163.72 BogoMIPS)
[    0.413963] devtmpfs: initialized
[    0.413963] x86/mm: Memory block size: 128MB
[    0.414244] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.414244] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    0.418762] NET: Registered protocol family 16
[    0.418931] thermal_sys: Registered thermal governor 'step_wise'
[    0.423912] cpuidle: using governor menu
[    0.423940] ACPI: bus type PCI registered
[    0.423964] PCI: Fatal: No config space access function found
[    0.425960] Kprobes globally optimized
[    0.425979] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.473927] raid6: skip pq benchmark and using algorithm sse2x4
[    0.473930] raid6: using ssse3x2 recovery algorithm
[    0.473949] ACPI: Added _OSI(Module Device)
[    0.473950] ACPI: Added _OSI(Processor Device)
[    0.473951] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.473953] ACPI: Added _OSI(Processor Aggregator Device)
[    0.473954] ACPI: Added _OSI(Linux-Dell-Video)
[    0.473956] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.473957] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.483874] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    0.514318] ACPI: Interpreter enabled
[    0.514325] ACPI: (supports S0 S5)
[    0.514327] ACPI: Using IOAPIC for interrupt routing
[    0.514345] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.514520] ACPI: Enabled 2 GPEs in block 00 to 0F
[    0.516694] iommu: Default domain type: Translated
[    0.516809] SCSI subsystem initialized
[    0.516814] ACPI: bus type USB registered
[    0.516829] usbcore: registered new interface driver usbfs
[    0.516837] usbcore: registered new interface driver hub
[    0.516845] usbcore: registered new device driver usb
[    0.533914] hv_vmbus: Vmbus version:5.2
[    0.534096] PCI: Using ACPI for IRQ routing
[    0.534098] PCI: System does not support PCI
[    0.534153] clocksource: Switched to clocksource hyperv_clocksource_tsc_page
[    0.538187] hv_vmbus: Unknown GUID: c376c1c3-d276-48d2-90a9-c04748072c60
[    1.106531] VFS: Disk quotas dquot_6.6.0
[    1.106547] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.106572] FS-Cache: Loaded
[    1.106602] pnp: PnP ACPI init
[    1.106861] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
[    1.106880] pnp: PnP ACPI: found 1 devices
[    1.148961] NET: Registered protocol family 2
[    1.149057] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    1.153653] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    1.153665] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    1.153714] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)
[    1.153787] TCP: Hash tables configured (established 32768 bind 32768)
[    1.154276] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    1.154289] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)[    1.154326] NET: Registered protocol family 1
[    1.174473] RPC: Registered named UNIX socket transport module.
[    1.174476] RPC: Registered udp transport module.
[    1.174477] RPC: Registered tcp transport module.
[    1.174478] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.174483] PCI: CLS 0 bytes, default 64
[    1.174537] Trying to unpack rootfs image as initramfs...
[    1.174600] Freeing initrd memory: 64K
[    1.174602] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    1.174605] software IO TLB: mapped [mem 0x00000000f4000000-0x00000000f8000000] (64MB)
[    1.174721] kvm: no hardware support
[    1.174723] has_svm: not amd or hygon
[    1.174724] kvm: no hardware support
[    1.259452] Initialise system trusted keyrings
[    1.261834] workingset: timestamp_bits=46 max_order=20 bucket_order=0
[    1.263020] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.263944] NFS: Registering the id_resolver key type
[    1.263953] Key type id_resolver registered
[    1.263955] Key type id_legacy registered
[    1.263958] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.263961] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.263962] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.281091] Key type cifs.idmap registered
[    1.281173] fuse: init (API version 7.32)
[    1.281336] SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, no debug enabled
[    1.288600] 9p: Installing v9fs 9p2000 file system support
[    1.288613] FS-Cache: Netfs '9p' registered for caching
[    1.288681] FS-Cache: Netfs 'ceph' registered for caching
[    1.288685] ceph: loaded (mds proto 32)
[    1.315940] NET: Registered protocol family 38
[    1.315945] xor: automatically using best checksumming function   avx
[    1.315949] Key type asymmetric registered
[    1.315950] Asymmetric key parser 'x509' registered
[    1.315969] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    1.316743] hv_vmbus: registering driver hv_pci
[    1.320497] ACPI: AC Adapter [AC1] (on-line)
[    1.321617] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.322293] Non-volatile memory driver v1.3
[    1.325284] battery: ACPI: Battery Slot [BAT1] (battery present)
[    1.337294] brd: module loaded
[    1.353004] loop: module loaded
[    1.353086] hv_vmbus: registering driver hv_storvsc
[    1.357323] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    1.357325] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[    1.357346] tun: Universal TUN/TAP device driver, 1.6
[    1.361118] PPP generic driver version 2.4.2
[    1.361255] PPP BSD Compression module registered
[    1.361257] PPP Deflate Compression module registered
[    1.361262] PPP MPPE Compression module registered
[    1.361264] NET: Registered protocol family 24
[    1.361283] usbcore: registered new interface driver cdc_ether
[    1.361295] usbcore: registered new interface driver cdc_ncm
[    1.361296] hv_vmbus: registering driver hv_netvsc
[    1.456583] scsi host0: storvsc_host_t
[    1.596119] VFIO - User Level meta-driver version: 0.3
[    1.598631] random: fast init done
[    1.598781] usbcore: registered new interface driver cdc_acm
[    1.598782] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    1.598798] usbcore: registered new interface driver ch341
[    1.598803] usbserial: USB Serial support registered for ch341-uart
[    1.598808] usbcore: registered new interface driver cp210x
[    1.598812] usbserial: USB Serial support registered for cp210x
[    1.598817] usbcore: registered new interface driver ftdi_sio
[    1.598821] usbserial: USB Serial support registered for FTDI USB Serial Device
[    1.598886] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[    1.598889] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 1
[    1.598896] vhci_hcd: created sysfs vhci_hcd.0
[    1.598932] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    1.598934] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.598935] usb usb1: Product: USB/IP Virtual Host Controller
[    1.598937] usb usb1: Manufacturer: Linux 5.10.102.1-microsoft-standard-WSL2 vhci_hcd
[    1.598938] usb usb1: SerialNumber: vhci_hcd.0
[    1.599447] hub 1-0:1.0: USB hub found
[    1.599456] hub 1-0:1.0: 8 ports detected
[    1.599553] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[    1.599555] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 2
[    1.599599] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.599624] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    1.599626] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.599627] usb usb2: Product: USB/IP Virtual Host Controller
[    1.599628] usb usb2: Manufacturer: Linux 5.10.102.1-microsoft-standard-WSL2 vhci_hcd
[    1.599630] usb usb2: SerialNumber: vhci_hcd.0
[    1.600769] hub 2-0:1.0: USB hub found
[    1.600784] hub 2-0:1.0: 8 ports detected
[    1.603913] hv_vmbus: registering driver hyperv_keyboard
[    1.604399] rtc_cmos 00:00: RTC can wake from S4
[    1.652872] rtc_cmos 00:00: registered as rtc0
[    1.656174] rtc_cmos 00:00: setting system clock to 2022-08-02T01:55:27 UTC (1659405327)
[    1.656195] rtc_cmos 00:00: alarms up to one month, 114 bytes nvram
[    1.659639] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
[    1.663201] device-mapper: raid: Loading target version 1.15.1
[    1.663260] usbcore: registered new interface driver usbhid
[    1.663261] usbhid: USB HID core driver
[    1.663306] hv_utils: Registering HyperV Utility Driver
[    1.663308] hv_vmbus: registering driver hv_utils
[    1.663322] hv_vmbus: registering driver hv_balloon
[    1.663370] hv_vmbus: registering driver dxgkrnl
[    1.663378] (NULL device *): dxgk: dxg_drv_init  Version: 2216
[    1.663401] drop_monitor: Initializing network drop monitor service
[    1.663420] Mirror/redirect action on
[    1.663571] IPVS: Registered protocols (TCP, UDP)
[    1.663587] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
[    1.663620] IPVS: ipvs loaded.
[    1.663621] IPVS: [rr] scheduler registered.
[    1.663622] IPVS: [wrr] scheduler registered.
[    1.663623] IPVS: [sh] scheduler registered.
[    1.663668] ipip: IPv4 and MPLS over IPv4 tunneling driver
[    1.668338] hv_utils: cannot register PTP clock: 0
[    1.676405] hv_utils: TimeSync IC version 4.0
[    1.676511] hv_balloon: Using Dynamic Memory protocol version 2.0
[    1.690512] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[    1.701553] Free page reporting enabled
[    1.701556] hv_balloon: Cold memory discard hint enabled
[    1.701577] Initializing XFRM netlink socket
[    1.702071] NET: Registered protocol family 10
[    1.705875] Segment Routing with IPv6
[    1.745957] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    1.746107] NET: Registered protocol family 17
[    1.746134] Bridge firewalling registered
[    1.746144] 8021q: 802.1Q VLAN Support v1.8
[    1.746171] sctp: Hash tables configured (bind 256/256)
[    1.746240] 9pnet: Installing 9P2000 support
[    1.746255] Key type dns_resolver registered
[    1.746263] Key type ceph registered
[    1.751028] libceph: loaded (mon/osd proto 15/24)
[    1.758781] NET: Registered protocol family 40
[    1.758785] hv_vmbus: registering driver hv_sock
[    1.758826] IPI shorthand broadcast: enabled
[    1.758843] sched_clock: Marking stable (1758253400, 466700)->(1791933000, -33212900)
[    1.768205] registered taskstats version 1
[    1.768220] Loading compiled-in X.509 certificates
[    1.768492] Btrfs loaded, crc32c=crc32c-generic
[    1.770415] Freeing unused kernel image (initmem) memory: 1580K
[    1.813941] Write protecting the kernel read-only data: 28672k
[    1.821724] Freeing unused kernel image (text/rodata gap) memory: 2024K
[    1.824410] Freeing unused kernel image (rodata/data gap) memory: 1192K
[    1.824443] Run /init as init process
[    1.824444]   with arguments:
[    1.824445]     /init
[    1.824446]   with environment:
[    1.824446]     HOME=/
[    1.824447]     TERM=linux
[    1.869728] random: crng init done
[    1.907266] scsi 0:0:0:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    1.957047] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.063369] sd 0:0:0:0: [sda] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    2.063372] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    2.068107] sd 0:0:0:0: [sda] Write Protect is off
[    2.068110] sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00
[    2.086349] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.373939] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    2.526154] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.936877] EXT4-fs (sda): recovery complete
[    2.965129] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[    3.788307] init: (1) ERROR: ConfigApplyWindowsLibPath:2129: open /etc/ld.so.conf.d/ld.wsl.conf
[    3.788312]  failed 2
[    3.923167] init: (1) ERROR: UpdateTimezone:97: Asia/Bangkok timezone not found. Is the tzdata package installed?
[    3.923176] init: (1) ERROR: InitEntryUtilityVm:2434: UpdateTimezone failed
[   50.548048] hv_balloon: Max. dynamic memory size: 4096 MB
[   62.875342] WSL2: Performing memory compaction.
[  483.881618] WSL2: Performing memory compaction.
[ 1564.891382] WSL2: Performing memory compaction.
[ 2105.900122] WSL2: Performing memory compaction.
[ 2797.434748] hv_utils: TimeSync IC version 4.0
[ 2826.911740] WSL2: Performing memory compaction.

@SvenGroot

myusrn commented 1 year ago

I just recently took a clean win11 enterprise 22h2 22623.1028 setup and enabled wsl using "wsl --install" which led to the wsl and ubuntu store apps being installed. I rebooted and was able to open ubuntu terminal using both the winkey | ubuntu app shortcut and the terminal app drop down for Ubuntu.

Running wsl --version i get WSL version: 1.0.3.0 | Kernel version: 5.15.79.1 | WSLg version: 1.0.47 .

I found that attempts to use \wsl.localhost\Ubuntu was producing the network address is invalid results. I landed on the details in this thread, added P9NP, prefix to hklm\System\Ccs\Control\NetworkProvider\HwOrder & \Order PROVIDERORDER values and problem was resolved.

Attaching output from the data gathering commands outlined above, i.e. dir $env:windir\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 output.

wsl-issue-4027.log

Is the P9NP provider not being included in these lists as part of wsl --install processing a known issue on clean install setups or an anomaly with yet to be determined host setup requirements that lead to it not getting inserted?

benyaminl commented 1 year ago

Last time I check, it's the new ISO of windows is corrupted

You can try download new ISO, and reburn it. If you still face the problem, then report the known broken ISO Checksum

myusrn commented 1 year ago

@benyaminl in my case i started out with a clean company device image install that was win10 enterprise 20h2 and then ran Microsoft up to get to win11 enterprise 22h2 and then enrolled in insider beta to get to the 22623.1028 release.

It was at that point that I ran "wsl --install" to get the Ubuntu 22.04 distro in place with the expected p9np provider entries missing.

Given that it would seem issue isn't arising from iso I used to get initial win11 enterprise install in place right?

benyaminl commented 1 year ago

@myusrn I also the same,but from Win 10 to Win 10 from Windows Update... it end up broken... and need clean install with next ISO (on uni lab), and after using new ISO, it works as it's, I think they need to take it seriusly when Windows Update/ISO is broken :/

benyaminl commented 1 year ago

@therealkenc Seems Some of Windows Folk accidentally fix this issue on Windows 10 22H2... after update, for some reason it working now, since December Weekly update 2022. Could people in MS release what are they changging that lead to this working?

image image image

2nd suspect is from VS Code WSL, between both, because I don't do any clean install

jscssphtml commented 1 year ago

Same here... since last Win10 Patch Day it is working now, but i have absolut no clue why... But it must came with a seperate smaller side patch since i'm running 21H2 and not 22H2...

HectorOses commented 1 year ago

Unfortunately this is not working for me. Any suggestion?

PS C:\Windows\system32> reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder ProviderOrder REG_SZ P9NP,cbfsconnect2017,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order ProviderOrder REG_SZ P9NP,cbfsconnect2017,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder LanmanWorkstation REG_DWORD 0x7d0 P9NP REG_DWORD 0x1f4 RDPNP REG_DWORD 0x3e8 webclient REG_DWORD 0xbb8 cbfsconnect2017 REG_DWORD 0xfa

PS C:\Windows\system32> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np Description REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-101 DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider DeviceName REG_SZ \Device\P9Rdr DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100 Name REG_SZ Plan 9 Network Provider ProviderPath REG_EXPAND_SZ %SystemRoot%\System32\p9np.dll TriggerStartCompleteNotification REG_BINARY 7510BCA3541EC641 TriggerStartNotification REG_BINARY 7508BCA3541EC641 TriggerStartPrefix REG_MULTI_SZ wsl.localhost\0wsl$

PS C:\Windows\system32> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr DependOnService REG_MULTI_SZ RDBSS Description REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-101 DisplayName REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-100 ErrorControl REG_DWORD 0x1 ImagePath REG_EXPAND_SZ System32\drivers\p9rdr.sys Start REG_DWORD 0x3 Type REG_DWORD 0x1

PS C:\Windows\system32>

As well after reboot the registry order is changed again

HectorOses commented 1 year ago

Same here, not working anymore

PS C:\Windows\system32> reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder ProviderOrder REG_SZ P9NP,cbfsconnect2017,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order ProviderOrder REG_SZ P9NP,cbfsconnect2017,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder LanmanWorkstation REG_DWORD 0x7d0 P9NP REG_DWORD 0x1f4 RDPNP REG_DWORD 0x3e8 webclient REG_DWORD 0xbb8 cbfsconnect2017 REG_DWORD 0xfa

PS C:\Windows\system32> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np Description REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-101 DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider DeviceName REG_SZ \Device\P9Rdr DisplayName REG_EXPAND_SZ @%systemroot%\system32\p9np.dll,-100 Name REG_SZ Plan 9 Network Provider ProviderPath REG_EXPAND_SZ %SystemRoot%\System32\p9np.dll TriggerStartCompleteNotification REG_BINARY 7510BCA3541EC641 TriggerStartNotification REG_BINARY 7508BCA3541EC641 TriggerStartPrefix REG_MULTI_SZ wsl.localhost\0wsl$

PS C:\Windows\system32> reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr DependOnService REG_MULTI_SZ RDBSS Description REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-101 DisplayName REG_SZ @%SystemRoot%\System32\drivers\p9rdr.sys,-100 ErrorControl REG_DWORD 0x1 ImagePath REG_EXPAND_SZ System32\drivers\p9rdr.sys Start REG_DWORD 0x3 Type REG_DWORD 0x1

PS C:\Windows\system32>

and after rebook the order is reset

HectorOses commented 1 year ago

I managed to make it work like this

At first I was getting no access, then making this changes in registry made it:

  1. have P9NP first for both HwOrder and Order
  2. remove from both the "cbfsconnect2017"
PS C:\Windows\system32> reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    P9NP    REG_DWORD    0x1f4
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    cbfsconnect2017    REG_DWORD    0xfa

PS C:\Windows\system32>

After reboot it gets somehow reset, cbfsconnect2017 becomes first again, but now P9NP is second, but access works

PS C:\Windows\system32> reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    cbfsconnect2017,P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    cbfsconnect2017,P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    P9NP    REG_DWORD    0x1f4
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    cbfsconnect2017    REG_DWORD    0xfa

PS C:\Windows\system32>