{"version":"2.1.236","anchor":"two-new-failure-messages-windows-sandbox-install-and-cloud-f","canonical_anchor":"two-new-failure-messages-windows-sandbox-install-and-cloud-f","heading":"Two new failure messages: Windows sandbox install and cloud file sync","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/two-new-failure-messages-windows-sandbox-install-and-cloud-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Two new failure messages: Windows sandbox install and cloud file sync\n\nClearer errors for a Windows sandbox install failure and for cloud file sync never applying your uploads.\n\n**What**\n\nThe Windows sandbox installer gains a distinct failure for exit code 17, and the cloud file-sync path gains a warning telling you that \"file sync may not be enabled for your account yet\" when the other side never applied files uploaded from this directory.\n\n**Details**\n\n- On Windows, the sandbox installer exiting with code 17 is now reported as `install_ambient_failed`, explaining that world-writable system directories could not be marked as denied to the sandbox user. Other platforms are unaffected.\n- The cloud warning fires when the paired cloud session has not picked up files sent from this directory, and adds that your changes may not reach the other side. A companion check decides which sync outcomes count as the other side having been reached.\n- What turns cloud file sync on as a whole is not decided in this code path.\n\n**Evidence**\n\n`\"install_ambient_failed\"`, `install_ambient_failed`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}