Error in 'Open with File Explorer'

[tushev]

To Reproduce
Steps to reproduce the behavior:

1. Click on 'Open with File Explorer' on any distro
2. The app attempts to open \\wsl.localhost\{DISTRO_NAME}
3. See error

Expected behavior
The correct path (well, at least on my machine) is \\wsl$\{DISTRO_NAME}

Screenshots

The correct path :

Desktop (please complete the following information):

• OS: Windows 10 21H1
• Version: 1.3.3
• Source: Windows Store

[bostrot]

This looks like a version issue as described here: #23

Try updating Windows and WSL. Also check that you are using WSL2. (Here is a guide on how to upgrade WSL1 to WSL2.

[tushev]

Yes, I can confirm that I have WSL 2. I'm also on the latest version of Windows for my branch (Education/Enterprise).

[tushev]

If I'm not mistaken, Microsoft recommends \\wsl$\... path, like in: https://docs.microsoft.com/en-us/windows/wsl/filesystems

Running explorer . in WSL shell also opens

[bostrot]

You said you are using 21H1. 21H2 should be the latest on the enterprise channel. Could you recheck that?

Also on the latest Windows 11 and the 10 builds I tested the current path works just fine:

EDIT: 22H2 seems to be out already too.

[tushev]

I've checked on another machine running 21H2, the problem still persists there, and I get the same error. I've also found the release note about the change from \\wsl$ to \\wsl.localhost\. However, this does not solve my problem.

I've also run the commands suggested here: https://superuser.com/a/1726340

user@name:~$ p='\\wsl$\Ubuntu-20.04\home'
user@name:~$ wslpath -w $(wslpath -u $p)
\\wsl$\Ubuntu-20.04\home

and I'm getting \\wsl$, not \\wsl.localhost\ 🤷‍♂️.

Ideally, I would love to have an option for choosing between \\wsl$ and \\wsl.localhost\ if auto-detection doesn't work (could be not even in UI, but somewhere in config). Thanks!

[bostrot]

I see. I guess that changes somewhere after/around 21H2 then. I just checked with a Windows 11 21H2 build 22000 and that is already changed to wsl.localhost there.

The windows build numbers are kind of confusing with older releases having higher numbers :/

According to the article it changed with build 21354 then. Can you tell me if you are using a build prior to that?
Also, could you check if the open vscode button works with your build?

[bostrot]

I quickly put together a build. Can you test if it works for you?

wsl2distromanager-v1.3.4.zip

[tushev]

Yes, it works correctly! Thanks a lot!

P.S. I tested on OS build 19044.1826.

VS Code button starts downloading its packages (both in 1.3.3 & 1.3.4). I don't want it, so I terminate it with CTRL+C before download completes.