On Windows your permission policy helper can now be a .ps1 PowerShell script, with wildcard characters rejected.
What's wrong with this entry?
The 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.
path must end in .exe or .ps1 on Windows
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Windows sandbox runtime now installs machine-wide
Both mention window
-
v2.1.239
PowerShell path checks distinguish a timeout from an error
Both mention window
-
v2.1.239
Windows pipe names no longer mangled by locale-specific lowercasing
Both mention window