{"version":"2.1.221","anchor":"sandbox-install-error-classification-by-code-and-a-longer-ti","canonical_anchor":"sandbox-install-error-classification-by-code-and-a-longer-ti","heading":"\/sandbox install error classification by code, and a longer timeout","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/sandbox-install-error-classification-by-code-and-a-longer-ti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### \/sandbox install error classification by code, and a longer timeout\n\nWindows sandbox install failures now report the real cause, and the timeout message correctly says two minutes.\n\n**What**\n\nWindows sandbox install failures are classified from typed error codes rather than by matching stderr text, and the reported timeout is longer.\n\n**Details**\n\n- Codes matched are install_timeout and install_config_conflict.\n- The timeout message now says 2 minutes instead of 60 seconds.\n- Windows-only, on the `\/sandbox install` path.\n\n**Evidence**\n\n`The install timed out after 2 minutes`\n\n- Area: Sandbox\n- Names: `\/sandbox install`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}