You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
WindowsArea: what it touches
Bug FixesKind: in v2.1.221,
Bug FixesSection of the release
What
A sandbox failure caused by launching from a mapped network drive now explains itself and names the drive, instead of surfacing as a generic sandbox failure.
Details
triggered by sandbox exit code 16 together with a structured mapped_drive_cwd error from the sandbox runtime
fires a sandbox_exec telemetry event at the point windows_mapped_drive_cwd
Windows sandbox execution path only
Evidence
mapped drives don't exist for the sandbox account. Use a workspace on a local drive.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
