{"version":"2.1.307","anchor":"windows-sandbox-preflight-reports-a-disabled-or-missing-seco","canonical_anchor":"windows-sandbox-preflight-reports-a-disabled-or-missing-seco","heading":"Windows: the sandbox now reports when Secondary Logon is off or missing","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/windows-sandbox-preflight-reports-a-disabled-or-missing-seco","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Windows: the sandbox now reports when Secondary Logon is off or missing\n\nOn Windows, Claude Code now tells you when the sandbox can't start because the Secondary Logon service is disabled or missing\n\n**What**\n\nThe sandbox is a restricted environment that limits what commands run by Claude can touch. On Windows, when the sandbox is turned on, Claude Code now checks whether it can start. If the Windows Secondary Logon service (seclogon) is disabled or missing, it reports that the sandbox is turned on but can't start because of that service.\n\nThe report includes the fix. For a disabled service, an administrator must set its startup type to Manual.\n\n**Why**\n\nOn Windows you now get a clear reason and a fix when the sandbox can't start, instead of having it fail without saying why.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}