Bug: Accessing a path whose length exceeds `MAX_PATH` (via a BTRFS `wsl --mount`) causes a network resource access error.

[RokeJulianLockhart]

Description

https://github.com/user-attachments/assets/005ef77e-c937-45ea-9dd6-edb4144962f8

As the aforementioned demonstrates, accessing a path whose length exceeds MAX_PATH (ascertained by attempting to access \\wsl.localhost\fedoraremix\mnt\rjlb_data\@{'Name'='Entities'}#.dir\@{'Status'='Commenced'; 'Name'='In Use'}#.dir\@{'Person'='Beedell'; 'Identifier'='S21AIB'}#.dir\@{'Name'='Entity-Specific'}#.dir\@{'Person'='Roke'; 'Identifier'='S1EV2L'}#.dir\@{'Name'='Technical'}#.dir via a BTRFS wsl --mount) causes a network resource access error:

Steps To Reproduce

1. Create the undermentioned structure:

   RokeJulianLockhart@sfjgsi:~$ sudo lsblk -f
   [sudo] password for RokeJulianLockhart:
   NAME   FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
   sda
   sdb
   sdc                                           [SWAP]
   sdd                             954.8G     0% /mnt/wslg/distro
                                                 /
   sde
   ├─sde1
   ├─sde2
   ├─sde3
   └─sde4                            1.4T    24% /mnt/test
   sdf
   └─sdf1                          184.3G    90% /mnt/rjlb_data
   

   To do so, create a BTRFS-formatted filesystem on a blank storage device, then mount it:

   #!/usr/bin/env pwsh
   #Requires -PSEdition Core
   If ($IsWindows) {
   	sudo wsl --mount \\.\PHYSICALDRIVE1 --bare
   }
   

2. When mounted, create the hideous path aforementioned. If you attempt to access it via the Files GUI, it should display the aforementioned error modal.

This probably isn't a minimal reproduction list, because I've yet to narrow the cause.

Files Version

3.9.9.0

Windows Version

10.0.26120.0

User ID

353b71b8-86f9-4fe0-ac0e-e1da114b9349

Log File

debug.log