{"version":"2.1.232","anchor":"policy-helper-executable-paths-must-be-in-normalized-form","canonical_anchor":"policy-helper-executable-paths-must-be-in-normalized-form","heading":"Policy helper executable paths must be in normalized form","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/policy-helper-executable-paths-must-be-in-normalized-form","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Policy helper executable paths must be in normalized form\n\nPolicy helper paths must be fully normalized, and Windows needs a drive or UNC path.\n\n**What**\n\nThe managed-settings policy helper path check now rejects `.` and `..` segments, doubled or trailing separators, and on Windows requires a drive-qualified or UNC path with no device-namespace prefix. This is on top of the existing absolute-path and `.exe` checks, and failures return `code: \"bad_path\"`.\n\n**Details**\n\n- The check also moved inside the runner, so it applies at the point the helper is invoked.\n\n**Evidence**\n\n`path must be in normalized form (no \".\" or \"..\" segments, no doubled or trailing separators)`\n\n- Area: Managed Settings\n- Names: `policyHelpers`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}