"\\wsl.localhost not accessible" *fixed*

[james28909]

Ok, so I just read a few threads about how to fix this error. None of them worked for me, my reg was already good to go and everything else seemed to be in working order except for accessing this server at \\wsl.localhost (the Linux shortcut in navigation pane).

Well guess what?

TURN ON NETWORK DISCOVERY!!!! xD

Did that for private networks, and now it is working seamlessly. I can finally click “Linux” in explorer quick access again and see all my distros.

[thistlillo]

It dos not work any more on Windows 11 Pro. Or, at least, it did not work on mine, together with the solutions published here: https://www.tenforums.com/tutorials/49652-turn-off-network-discovery-windows-10-a.html (for Win 10).

[Frushtration]

Hey, for all the Windows 11 Pro People,

This link resolved my issues.

As a quick note for clarity, change the keys of "ProviderOrder" in both the "Order" and "HwOrder" sections. Even If you see the "P9NP" if that line, you need to move that key to the front, or else it won't work. Mine "P9NP" key wasn't missing, it was just at the back, which caused this issue.

Hope that helps!

[HectorOses]

Thanks. I tried, but that didn't make it for me. Any other ideas?
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>

[HectorOses]

Finally I got it working doing 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>

[paulsybrandy]

That was the final trick my friend! My savior. Thankies.

[niladrishekhardutta]

Thanks. This trick worked.

[StuCjk]

same error, same fix, thanks! XD

[tehido]

upvote, thanks

[mucsi96]

For the following solution resolved the issue: #7499 (comment)