{"version":"2.1.307","anchor":"windows-sandbox-uninstall-command","canonical_anchor":"windows-sandbox-uninstall-command","heading":"New claude sandbox uninstall command removes the Windows sandbox","tier":"use","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/windows-sandbox-uninstall-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### New `claude sandbox uninstall` command removes the Windows sandbox\n\nOn native Windows, `claude sandbox uninstall` removes the sandbox account, group, stored password and network filters, then lists what remains\n\n**What**\n\nThe sandbox is a restricted environment Claude Code can run commands in. On native Windows, a new terminal command, `claude sandbox uninstall`, removes it from the PC. It removes:\n\n- The sandbox user account and its group.\n\n- The stored password for that account.\n\n- The network filters the sandbox installed.\n\nIt refuses to run while Claude Code processes are still running. Afterwards it lists permission entries left behind on files, and reports a status such as ok, partial, in_use, cancelled or not_installed. Windows may ask for administrator approval. With `--json` it prints one line of JSON with the status, a message, what was left behind and which filters were checked. To set the sandbox up again, run `\/sandbox install`.\n\nOn other platforms the command says: \"This command applies to native Windows only.\"\n\n**Why**\n\nWindows users now have a supported way to remove the sandbox completely, and can see exactly what it could not clean up.\n\n- Area: Sandbox\n- Names: `claude sandbox uninstall`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}