Windows strict sandbox refusals now explain that an exclusion needs an available permission prompt to apply.
What's wrong with this entry?
On Windows in strict sandbox mode, a refused command used to give one message regardless of cause. There are now two: the existing one for an exclusion that matched only part of the command, and a new one explaining that an exclusion only exempts a command when a permission prompt could approve running it unsandboxed, and no such prompt is available here.
- Both paths still refuse the command with the
windows_policy_refusaloutcome. - Applies only on Windows, with sandboxing enabled in settings, the platform in the enabled list, and strict sandbox mode configured.
exclusions only exempt a command where a permission prompt can approve the unsandboxed run, and none is available here
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