{"version":"2.1.234","anchor":"windows-sandbox-decisions-keyed-on-configured-strict-mode","canonical_anchor":"windows-sandbox-decisions-keyed-on-configured-strict-mode","heading":"Windows sandbox decisions keyed on configured strict mode","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/windows-sandbox-decisions-keyed-on-configured-strict-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Windows sandbox decisions keyed on configured strict mode\n\nWindows sandbox decisions now hinge on configured strict mode rather than a runtime toggle.\n\n**What**\n\nOn 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.\n\n**Details**\n\n- A helper that combined the old runtime check with platform checks was deleted.\n- Non-Windows platforms are unaffected.\n\n**Evidence**\n\n`isStrictSandboxModeConfigured`\n\n- Area: Windows\n- Names: `forbidUnsandboxedCommands`, `allowUnsandboxedCommands`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}