Enable or Disable Windows Sandbox in Windows 10  

Is there any way to not delete the sandbox contents upon closing it? Or at least save stuff to a folder that's shared with the host?

This might just be the first useful feature to me since 1709, which I'm still running.

Kari said:

Only option I know is to use Hyper-V virtual machines. I run Sandbox in Windows 10 on a Hyper-V VM, and save a Standard Checkpoint of that VM when I want to save Sandbox state.

Restoring / applying that checkpoint, Sandbox is where I left it.

There is no way to save state of Sandbox when you close it.

Kari

Thanks for the answer!

I guess, for now, I'll keep going with a mix of Sandboxie and full VMs as needed. Hopefully Windows Sandbox matures by the next release and implements persistence.

i hope they fix it mine don't even work

Kari said:

Just to be sure you understand the difference, Sandboxie is a third party application which lets you run applications in isolated mode. Sandbox is a native Windows 10 feature, which runs a full Windows 10 OS in a virtual container.

Sandboxie and Windows Sandbox are two totally different things, in fact they couldn't be more different.

Yes, I understand. They're 2 very different approaches to tackle a same problem: running untrusted software without the complexity/overhead of running a full fat VM with a separate OS.

I read that Window Sandbox does some fancy things to reuse (link to) system files, while still providing isolation, but to be honest, it's not how it's implemented that matters. It's the end result.

In practical terms:
Sandboxie will let applications view (but not modify) my entire system by default, whereas Windows Sandbox will not (better isolation by default).
With Sandboxie I need to make sure the containers can't access any files/folders I don't want to, or access the internet. On the other hand, it is (can be) persistent and I can also give it direct access to certain host folders, which seems to be impossible with Windows Sandbox.
I can't comment on resource utilization of Windows Sandbox as I haven't tried it, but I'm curious to see what's the overhead.

Do let me know if I got something wrong!

Kari said:

Nothing to fix. Windows Sandbox works exactly as it is designed to work.

Microsoft acknowledged a couple of weeks ago that Windows Sandbox doesn't start for many: Windows Sandbox may fail to start with error code “0x80070002”

Feedback Hub shows thousands of reports with about 25 different error codes that people see: Windows Sandbox won't launch

NMI said:

Microsoft acknowledged a couple of weeks ago that Windows Sandbox doesn't start for many: Windows Sandbox may fail to start with error code “0x80070002”

Feedback Hub shows thousands of reports with about 25 different error codes that people see: Windows Sandbox won't launch

yeah i seen that mine has no error visible but it does show some in event viewer can we say a feature not well tested hmm maybe.

even my BIOS is virtualization capabilities enabled