{"version":"2.1.307","anchor":"windows-sandbox-install-waits-for-the-sandbox-user-to-sign","canonical_anchor":"windows-sandbox-install-waits-for-the-sandbox-user-to-sign","heading":"Windows sandbox set-up now confirms the sandbox user can sign in","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/windows-sandbox-install-waits-for-the-sandbox-user-to-sign","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Windows sandbox set-up now confirms the sandbox user can sign in\n\nOn Windows, `\/sandbox install` waits up to 150 seconds for the sandbox user to sign in and reports logon problems\n\n**What**\n\nOn Windows, `\/sandbox install` sets up the sandbox, a restricted environment Claude Code runs commands in, under its own Windows user. Set-up now does more:\n\n- It detects when the Windows secondary logon service, which lets programs run as another user, cannot be used, and reports a partial result saying \"Set-up changed nothing\" and to run it again once this is fixed.\n\n- After a successful install, it starts the sandbox user for the first time and waits up to 150 seconds.\n\n- It then adds a note saying whether Windows signed the user in, timed out, did not start it, or ran out of time. If sign-in fails, Claude Code tries again the next time it starts the sandbox.\n\nRunning `\/sandbox uninstall` inside a session is now refused. It tells you to close every Claude Code session and run `claude sandbox uninstall` in a terminal. The old hint pointing to `npx @anthropic-ai\/sandbox-runtime windows-uninstall` is gone.\n\n**Why**\n\nWindows users learn during set-up when the sandbox will not work, and why, instead of finding out later.\n\n- Area: Sandbox\n- Names: `\/sandbox install`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}