Bug: VMWare in-VM shared folders trigger "Network folder error" "ERROR_BAD_NET_NAME"

### Description

Folders shared and mapped by VMWare on Windows client VMs when accessed by `Files` will result in a "Network folder error" "ERROR_BAD_NET_NAME" error. These drives are typically mapped to `Z:`, and the actual share is typically mounted from "\\vmware-host\Shared Folders"

Also, attempting to access the root of the VMWare shared folder at `\\vmware-host` will throw the same error.

### Steps To Reproduce

1. Run the test in a windows VM Client hosted using `VMWare Workstation 17` (any version)
2. Install (or make sure it's installed) `VMWare Tools` provided by `VMWare Player` or `VMWare Workstation` in the client VM
2. Inside the client windows, install the `Files` app
3. Share a host folder with the client windows VM
4. Attempt to access the VMWare mapped `Z:`
5. Attempt to access the VMWare shared folder root at `\\vmware-host`

### Files Version

4.1.1.0

### Windows Version

Win10 19045.4529

### User ID

46719796-b353-47af-baa3-0df7ebf5ff6d

### Log File

[debug.log](https://github.com/user-attachments/files/28844388/debug.log)