{"version":"2.1.234","anchor":"network-and-windows-device-paths-refused-in-more-places","canonical_anchor":"network-and-windows-device-paths-refused-in-more-places","heading":"Network and Windows device paths refused in more places","tier":"notice","area":"Path Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/network-and-windows-device-paths-refused-in-more-places","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Network and Windows device paths refused in more places\n\nWindows device paths and network automount roots are now refused in more places, like memory files and edits.\n\n**What**\n\nPaths in Windows NT object-namespace form (`\\??\\`, `GLOBALROOT`, `DosDevices`, `Device`) and network automount roots (`\/net\/<host>`, `\/Network\/`) are now rejected alongside UNC shares when loading memory files, applying edits, adopting a remote session's working directory, resuming a session home, and resolving a workflow script path.\n\n**Details**\n\n- The workflow error text was broadened to name all three shapes.\n\n**Evidence**\n\n`Network (UNC, NT-namespace, or automount) paths are not allowed for workflow scriptPath`\n\n- Area: Path Safety\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}