Hacker News Reader

As someone noted, running `restart` in the sandbox sounds like it results in Windows preserving the sandbox.

The sandbox persists through a restart (to allow for the installation of software that requires a reboot) but never persists after Windows Sandbox is closed.

That’s the big distinction from Hyper-V or other virtualization products; otherwise, it’s just a Hyper-V VM with a prebaked Windows image and fewer options.

Not completely, it uses the Krypton microVM part of Hyper-V that is used for WSL2, Application Guard, and nothing else. I wish I could arbitrarily run Windows microVMs outside of sandbox.

That's not how I'd interpret it, it makes sense that if you restart the sandbox from inside the sandbox it doesn't get destroyed, but it doesn't seem to change anything else. If you shutdown the sandbox from outside it would still be destroyed.

It’s enough to install software that needs restarts, but not for use cases where you need the sandbox across host reboots.

Reply on news.ycombinator.com