{"version":"2.1.281","anchor":"windows-coninconout-names-rejected-as-path-segments-and-w","canonical_anchor":"windows-coninconout-names-rejected-as-path-segments-and-w","heading":"Windows CONIN$\/CONOUT$ names rejected as path segments and working names","tier":"notice","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/windows-coninconout-names-rejected-as-path-segments-and-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Windows CONIN$\/CONOUT$ names rejected as path segments and working names\n\nCONIN$ and CONOUT$ are now rejected as parts of file paths and as working names, ignoring case, extension and trailing spaces\n\n**Unclear.** The finding does not say what a working name is used for.\n\n**What**\n\n`CONIN$` and `CONOUT$` are special names on Windows that refer to the console rather than to files. They are now rejected in two places:\n\n- As a part of a file path, alongside the other names already treated as unsafe on Windows.\n\n- As a working name, where they fail with `WORKING_NAME_NOT_PLAIN`.\n\nThe match ignores upper or lower case, any file extension and trailing spaces, so `conout$.txt` is caught too.\n\n**Why**\n\nA folder or file with one of these names does not behave like an ordinary file on Windows, so these names are now stopped before they are used.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}