You'll notice
Useful3 Signal3
Windows sandbox decisions now hinge on configured strict mode rather than a runtime toggle.
What's wrong with this entry?
Anonymous. No account, no email.
forbidUnsandboxedCommandsallowUnsandboxedCommands
What
On Windows, writing excluded-command settings and the check for whether a sandbox is required now both test whether strict sandbox mode is configured, meaning managed policy sets forbidUnsandboxedCommands or settings set allowUnsandboxedCommands to false. The old condition also folded in a runtime toggle for disabling unsandboxed commands, which no longer influences these two decisions.
Details
- A helper that combined the old runtime check with platform checks was deleted.
- Non-Windows platforms are unaffected.
Evidence
isStrictSandboxModeConfigured
Strings lifted out of the shipped bundle, so the claim above can be checked against them.