Clearer errors for a Windows sandbox install failure and for cloud file sync never applying your uploads.
What's wrong with this entry?
The 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.
- 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. - 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.
- What turns cloud file sync on as a whole is not decided in this code path.
"install_ambient_failed", install_ambient_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.