{"version":"2.1.221","anchor":"clear-error-when-the-windows-sandbox-runs-from-a-mapped-netw","canonical_anchor":"clear-error-when-the-windows-sandbox-runs-from-a-mapped-netw","heading":"Clear error when the Windows sandbox runs from a mapped network drive","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/clear-error-when-the-windows-sandbox-runs-from-a-mapped-netw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Clear error when the Windows sandbox runs from a mapped network drive\n\nOn Windows, launching from a mapped network drive now tells you that's the problem and names the drive.\n\n**What**\n\nA 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.\n\n**Details**\n\n- triggered by sandbox exit code 16 together with a structured `mapped_drive_cwd` error from the sandbox runtime\n- fires a `sandbox_exec` telemetry event at the point `windows_mapped_drive_cwd`\n- Windows sandbox execution path only\n\n**Evidence**\n\n`mapped drives don't exist for the sandbox account. Use a workspace on a local drive.`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}