No support \\wsl$

[hzwwe]

https://devblogs.microsoft.com/commandl ... sion-1903/

[nas8e9]

Can you be more specific about what doesn't work? I understand this functionality appeared in the 1903 version of Windows 10, which many don't have yet (I'm still on 1809 myself, so can't test.).

[jlahijani]

I experimented last night with Windows fast ring and WSL2. Here is a screenshot explaining the current limitation. I'm not sure if the final release of WSL2 may fix this however (whenever that is... 6 months?).

Direct link to full image for convenience:
download/file.php?id=13597

[jlahijani]

Keep in mind, Microsoft purposely made the path have a ($) dollar sign even though that's an invalid character. They did that for WSL only as to not conflict with any existing network paths. This was mentioned in one of their videos.

So, I'm not sure if that is related.

[Jeeves]

For what it's worth, I am running into (what I believe) is this same issue. Computers randomly are not accessible when browsed to via UNC paths (some are accessible, some aren't, seems to change between XY launches). All of them state "Location currently not available." I thought it had to do with Administrative/hidden shares, but noticed that if I browsed to a PC I knew to be online, it still was shown as inaccessible.

This occurs when simply browsing to \\testpc, adding the share \\testpc\sharedirectory doesn't change the outcome.

Testing under a fresh copy of XY (xyplorer.exe /fresh) yields the same outcome, inaccessible shares.

This changed sometime during the last round of betas, but I don't update to each so I can't say exactly when it broke.

@jlahijani, $ is a perfectly valid character for a share (or file) name. In Windows it denotes a hidden share.

[nas8e9]

This changed sometime during the last round of betas, but I don't update to each so I can't say exactly when it broke.

You're running 20.60? There was a lot of debugging on the way to 20.60.

[Jeeves]

This changed sometime during the last round of betas, but I don't update to each so I can't say exactly when it broke.

You're running 20.60? There was a lot of debugging on the way to 20.60.

20.60.0002.

I didn't think much of it until I ran into a situation where I knew the machine was on, and administrative shares were inaccessible.

[tomuser]

I have same issue with v20.60. When typing \\SERVER on address bar - "Location currently not available." So I have to mount network share to be able to connect network shares. And it works fine with 20.50.100 and on Windows Explorer too. Win 10 v1809 64bit.

[Borut]

This is the same problem being currently described in a misleadingly entitled old thread: ""Location currently not available" on mapped network drive", where actually, as you write, the problem arises with a UNC path, most probably only when server sits in another subnet, or in some similar setting.

[tomuser]

Yeah I saw other post as well but by mentioning not working with mapped drives in title I thought this one here would be better to describe my problem as it's working fine with "mapped drive" with assigned drive letter . Also in my case that \\SERVER is same subnet, just different IP (192.168.1.10 & 192.168.1.15).

EDIT: Fixed in 20.60.0006

[admin]

Is the \\wsl$ thing fixed as well?

[yuxt]

can't access wsl path in 20.60.0200 portable version. checked that it could be accessed in explorer.

[admin]

Replace X by your wsl path, then paste this script into the XYplorer address bar and press ENTER:

Code: Select all

exist "X";

What is returned?

[yuxt]

As follows:

Exist
\\wsl$\Debian

XYplorer 20.60.0200 - Windows 10 Enterprise, 64-bit, Release 2004, Build 19037.1 - 2019-12-08 15:25:00

Path: \\wsl$\Debian
Real Path: \\wsl$\Debian
ExistFile: False
ExistPath: True
ExistFolder: False
ExistItemFF: False
ExistPathFF: True
ExistPathOrFile: True
ExistPathOrFileShell: True
ExistIcon: True
IsNetworkLocation: True
GetDriveType: 0 (DRIVE_UNKNOWN)
GetItemType: 5
GetFileAttributes: 0x10 (16)
Owner:
This path available in Tree: False
Current node available in Tree: True
Watchable: False
FilenamesCaseSensitive: False

FastNetworkEnumeration: 0
AssumeServersExist: 0
PrecheckServers: 0
CacheServers: 0

CheckServerMethod: 0
CheckServer3: 0
NetworkCapsCheck: 0
ShowAllServers: 0

MiniTreeVerifyOnSelect: 0
TreeSkipVerifyOnSelect: 0

ExistItemUNC: False
ExistPathUNC: False
ExistPathUNCQuick: False

ExistServer: False - AccessDenied: False - AccessErrorCode: 1707
IsShareAccessDenied: False - AccessErrorCode: 1707
IsServerConnected: False - Return/BufferType: 1707/0

[admin]

Hm, that's a weird result. The path exists, but the server does not? So the subfolder exists, but the folder does not?

1) Is "wsl$" listed under Network in Explorer?
2) What if you tick "Configuration | General | Safety Belts, Network | Network | Assume that servers are available"?