{"version":"2.1.234","anchor":"windows-policy-helpers-can-be-powershell-scripts","canonical_anchor":"windows-policy-helpers-can-be-powershell-scripts","heading":"Windows policy helpers can be PowerShell scripts","tier":"use","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/windows-policy-helpers-can-be-powershell-scripts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Windows policy helpers can be PowerShell scripts\n\nOn Windows your permission policy helper can now be a .ps1 PowerShell script, with wildcard characters rejected.\n\n**What**\n\nThe external helper that answers permission policy questions can now be a `.ps1` file on Windows, not just an `.exe`. A `.ps1` path containing `[`, `]`, a backtick, `*` or `?` is rejected, because PowerShell would treat those as wildcard syntax and resolve the path to something else.\n\n**Evidence**\n\n`path must end in .exe or .ps1 on Windows`\n\n- Area: Windows\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}