Enable or Disable Windows Sandbox in Windows 10  

Thanks for your help

Wondering if anyone else is seeing an occasional issue where Sandbox doesn't surrender its memory when closed.

To be clear, it does this subtly. It's not as if the sandbox process (I forget its name at the moment) that takes the memory is stuck in memory. The process is gone, and there's nothing of a comparable size in its place. But the memory (or a large part of it) still isn't returned, as evidenced by knowing what overall memory load was before running Sandbox (Task Manager and other like programs show this information).

A reboot, AFAIK, is the only way to get it back, although now that I think about it, I'm not sure what would happen if I were to run Sandbox again before doing so. This is Insider, but it's a pretty weird problem.

On my Windows 10 Pro 64-Bit OS, version 1909 (OS Build 18363.592)...

Memory utilization:

• Idle: 1.8 GB
• Sanbox started: 3.8 GB
• Sanbox closed: 2.3 GB
• Sanbox started again: 4.3 GB
• Sandbox exit: 2.3 GB
• Reboot: 2.1 GB

There seems to be a 0.5 GB memory leftover for each times it started and closed for the Sandbox. You are correct, that rebooting clears the leftover memory.

This might be by "design" for faster restart of the Sandbox. I don't believe that this is a big issue; nowadays, most system have at least 8 GB memory. At least in my case anyway...

What I didn't like is that, running Sandbox requires admin access and nothing is saved. I'd love to use it for general browsing the web and have all of the cookies, ads, tracking, etc., deleted once the Sanbox closed. Oh well, that's why I run Linux Mint in the VM...

I just wanted to remind users that when I close sand box after downloading Norton, the name Norton was left in the Chrome download folder. If the sand box closing deletes all within it, there is something wrong to have that Norton file left over. I have never actually used Norton except that once in the sand box, so there is no other way it could have gotten there except to leak through the sand box. Until I hear otherwise, I shall be leery to use it depending upon security when it closes.

mbrown said:

Attachment 239313
I got this error when booting the first time. Any suggestions? Thanks.

almost a year later and im still getting that issue.

(I get the same results with hyperV off.)

https://i.imgur.com/CbJp1dE.png

LVTHER said:

almost a year later and im still getting that issue.

(I get the same results with hyperV off.)

https://i.imgur.com/CbJp1dE.png

So I went through the process to install this on w10 home, and I get the same issue. I had to enable intel virtualization in the bios, but thats the only thing I changed. Should I be changing something else? Am I missing a setting? No emergent need to mess with it, just wanted to play around and keep it in the back pocket for a rainy day.

Just in case someone has the same problem, in my Windows 10 Pro 20H2 build 19042.985 spanish version, Sandbox didn't even show up in Windows Features to activate. It was driving me nuts as I read someone saying that it only works in english W10 releases

Well, the Powershell activation did the trick, I could enable Sandbox and I have it running flawlessly (so far, I just opened it :) )