{"version":"2.1.221","anchor":"windows-sandbox-errors-carry-a-code-and-the-failing-subcomma","canonical_anchor":"windows-sandbox-errors-carry-a-code-and-the-failing-subcomma","heading":"Windows sandbox errors carry a code and the failing subcommand","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/windows-sandbox-errors-carry-a-code-and-the-failing-subcomma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Windows sandbox errors carry a code and the failing subcommand\n\nWindows sandbox failures now carry a specific error code, though one remediation hint was dropped.\n\n**What**\n\nWindows sandbox failures now raise a typed error instead of a bare Error, so callers can branch on the cause rather than parse a message.\n\n**Details**\n\n- The error class is WindowsSandboxError, carrying a machine-readable code plus the `srt-win` subcommand that failed.\n- Codes: `bin_shell_invalid`, `srt_win_nonzero`, `srt_win_bad_json`, `not_provisioned`, `argv_too_long`.\n- The argv-length message lost its trailing remediation sentence suggesting you shorten the command.\n- Windows only.\n\n**Evidence**\n\n`srt_win_bad_json`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}