You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
map \wsl$ to a network drive, used to work but no longer works. I get an error message wsl.localhost is not accessible. \wsl$ redirects to \wsl.localhost which is not accessible.
using explorer I can browse to Linux to get the distro list but when I double-click on Debian I get an error message "Attempt to access invalid address"
This is after a recent update to WSL2
Expected Behavior
WSL2 share should work like it used to and should be able to be mapped to a network drive
Actual Behavior
wsl.localhost is inaccessible, attempt to access an invalid address.. no further info provided
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered:
Update: I was able to fix this, but it is still a BUG with the product.
For anyone else running into this issue:
in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order and HwOrder the P9NP value should be the 1st one in the comma separated list.
After the change you need to restart the computer.
Thanks to the original poster of this tip here: #4027 (comment)
Version
Microsoft Windows [Version 10.0.22000.1455]
WSL Version
Kernel Version
5.15.79.1-microsoft-standard-WSL2
Distro Version
Debian 11
Other Software
No response
Repro Steps
map \wsl$ to a network drive, used to work but no longer works. I get an error message wsl.localhost is not accessible. \wsl$ redirects to \wsl.localhost which is not accessible.
using explorer I can browse to Linux to get the distro list but when I double-click on Debian I get an error message "Attempt to access invalid address"
This is after a recent update to WSL2
Expected Behavior
WSL2 share should work like it used to and should be able to be mapped to a network drive
Actual Behavior
wsl.localhost is inaccessible, attempt to access an invalid address.. no further info provided
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: