{"version":"2.1.281","anchor":"helper-path-validation-rejects-windows-prefix","canonical_anchor":"helper-path-validation-rejects-windows-prefix","heading":"Helper path validation rejects Windows \\??\\ prefix","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/helper-path-validation-rejects-windows-prefix","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Helper path validation rejects Windows `\\??\\` prefix\n\nThe helper path check now rejects Windows paths that start with the `\\??\\` prefix\n\n**Unclear.** The finding does not say which setting supplies the helper path.\n\n**What**\n\nClaude Code checks that the path to a helper program is a safe, ordinary local path. That check now also rejects paths that start with the Windows `\\??\\` prefix (written as `\/??\/` with forward slashes). The error message now spells out every rule. The path must be a local absolute path (Windows: `C:\/...` or `C:\\...`) and must not:\n\n- use `~`, `..`, UNC paths or the `\\??\\` prefix\n\n- contain `\"`, `%`, carriage return, line feed or NUL characters\n\n- end with a dot or a space\n\n**Why**\n\nA helper path starting with `\\??\\` is now refused. If you set one up, the error message tells you which rules the path has to follow."}