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
The library currently does not support "extended path" identifiers, but it has no length requirement (other than the max length of a .Net string). If you find yourself needing this feature, make a comment here.
I was hoping to be able to use this library for scanning over a file share. I noticed this comment that appears to suggest that it's possible to use \\?\UNC\ paths:
// please note that the following line won't work if you try this on a network folder, like \\Machine\C$
// simply remove the \\?\ part in this case or use \\?\UNC\ prefix
However, I'm receiving the following error: Error during directory scan: System.IO.IOException: Unable to enter directory <directory>.
Workaround
For the next user who runs into this, I was able to reverse engineer a workaround: replace \\?\UNC\ in your base path with, UNC\, since WalkDir will prepend the path you provide with \\?\.
Activity
nzbart commentedon Dec 2, 2025
I was hoping to be able to use this library for scanning over a file share. I noticed this comment that appears to suggest that it's possible to use
\\?\UNC\paths:pathlib/PathLib/Windows/WindowsPath.cs
Lines 357 to 358 in 98f8b91
However, I'm receiving the following error:
Error during directory scan: System.IO.IOException: Unable to enter directory <directory>.Workaround
For the next user who runs into this, I was able to reverse engineer a workaround: replace
\\?\UNC\in your base path with,UNC\, sinceWalkDirwill prepend the path you provide with\\?\.