Windows sandbox install failures now report the real cause, and the timeout message correctly says two minutes.
What's wrong with this entry?
Windows sandbox install failures are classified from typed error codes rather than by matching stderr text, and the reported timeout is longer.
- Codes matched are install_timeout and install_config_conflict.
- The timeout message now says 2 minutes instead of 60 seconds.
- Windows-only, on the
/sandbox installpath.
The install timed out after 2 minutes
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
Headless plugin install refreshes the plugin cache in the background
Both mention install
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox