What
Paths of the form \??\..., including ones that only take that shape after Windows normalization, now count as network paths everywhere the check is made. They are blocked for @-mention attachments and Chrome file uploads regardless of which network directories the session trusts, and deep-link working directories using them are rejected.
Details
- One shared predicate now covers both
\\UNC paths and\??\device-namespace paths;/net/<host>automounts are recognized by a separate predicate. - A per-module copy of the old check, which required a non-slash character after the two leading slashes and did no normalization, was deleted and its caller moved to the shared helper.
- The executable-path check uses the combined predicate.
Evidence
Invalid cwd in deep link: UNC / network paths are not supported, got, network path not allowed:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.