Windows sandbox failures now carry a reason code, though the message you see is unchanged.
What's wrong with this entry?
Bare error throws in the Windows sandbox helper were replaced with a dedicated WindowsSandboxError carrying a machine-readable code, and for srt-win calls the subcommand as well.
- Codes include
acl_grant_failed,srt_win_not_found,srt_win_timeout,srt_win_nonzero,spawn_failed,bin_shell_invalid,srt_win_bad_json,wfp_verify_bind_failed,wfp_verify_unparseableandacl_stamp_failed. None of these appear in 2.1.220. - Message text is unchanged, so what a user sees is the same; only the structure carried alongside it is new.
- Separately, the helper that rewrites raw sandbox-runtime install advice into Claude Code advice now returns the message untouched when the platform is not Windows.
bin_shell_invalid, acl_grant_failed
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.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window