{"version":"2.1.232","anchor":"windows-device-namespace-paths-rejected-as-socket-addresses","canonical_anchor":"windows-device-namespace-paths-rejected-as-socket-addresses","heading":"Windows device-namespace paths rejected as socket addresses","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/windows-device-namespace-paths-rejected-as-socket-addresses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Windows device-namespace paths rejected as socket addresses\n\nWindows device-namespace paths are now rejected as message socket targets.\n\n**What**\n\nA `uds:` or `bridge:` message target starting with a `\\??\\`-style prefix is now rejected with the existing \"is not a local socket address\" error rather than being passed through to the named-pipe check.\n\n**Evidence**\n\n`is not a local socket address. Use an address from `\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}