Sandbox is not working after Pro Update

Joris1 · 24 Jul 2020

Hi there,
To cut this short(because my english is not that good).Yesterday I found out that I really need Sandbox. So I searched how to get it ... In the end I noticed that my Windows Home edition is not able to get this and I tryed a bypass to get Sandbox on Home edition. I kept getting this error : "the connection to the sandbox was lost.error 0x80072746. an existing connection was forcibly closed by the remote host." So I bought Windows Pro and activated it. My problem now is, I keep getting this error. I think its beacause I bypassed it with a .bat fila in Home edition. Is there any way to "reset" the bypass. Its very important for me.

Thank you :)

dalchina · 24 Jul 2020

Hi, to enable Sandbox, please follow this very carefully, noting the prerequisites: it may work for you.

Prerequisites for using the feature

Windows 10 build 18305 or higher
AMD64 architecture (64-bit)
Virtualization capabilities enabled in BIOS
At least 4GB of RAM (8GB recommended)
At least 1 GB of free disk space (SSD recommended)
At least 2 CPU cores (4 cores with hyperthreading recommended)

Enable Windows Sandbox Feature in Windows 10 Home Edition

For Pro: see
Enable or Disable Windows Sandbox in Windows 10

I think its beacause I bypassed it with a .bat fila in Home edition.

I doubt anyone can guess what this means. What is the source of your bat file? Did you write it yourself?

Joris1 · 24 Jul 2020

Hi my System fulfils all conditions. I already enabled Sandbox and tryed with enalbled Hyper-V an deactivated Hyper-V. I activated Sandbox in Windows 10 Home with this file: YouTube and followed the Instructions of Enable Windows Sandbox Feature in Windows 10 Home Edition this tutorial. Then I tried everything recommended on the Internet in case of this error. As nothing worked, I just upgraded to Windows pro by license. But the error isnt gone, I think its because I activated Sanbox before in Windows Home. I dont know how to reset this or any other solution. I already tried all the things I found e.g. How to Fix All Error of Windows Sandbox Not Opening in Windows 10 - YouTube these. I dont know what to do.

dalchina · 24 Jul 2020

Hi, you might try this (free) sandbox- been around a long time:
https://www.softpedia.com/get/Tweak/...andboxie.shtml

Windows' sandbox implementation has a perhaps unexpected consequence:

When Windows Sandbox is enabled a read-only 8 GB PortableBaseLayer system partition without a drive letter is automatically created and should not be deleted. The PortableBaseLayer partition is automatically removed when Windows Sandbox is disabled.

I recall I wasn't impressed when I tried it.

Digital Life · 25 Jul 2020

I just read this Today

Microsoft working to fix Windows Sandbox failed to open Issues in Windows 10

Microsoft working to fix Windows Sandbox failed to open Issues in Windows 10Last updated on July 24, 2020
Today, Microsoft updated a help article to say users may receive any of the following error when they try to open Sandbox in Windows 10

“ERROR_VSMB_SAVED_STATE_FILE_NOT_FOUND (0xC0370400)”
“E_PATHNOTFOUND (0x80070003)”

Workaround: If you encounter above mentioned error, you need to restart your device to use Sandbox again without any issues, Microsoft says.

jimbo45 · 26 Jul 2020

Hi folks
I know there's all sorts of reasons for people to use Sandboxes (when they work) but I'd really currently look at the idea of using a full blown Virtual Machine - there's some free Virtualisation software out there -- on PRO you can use HYPER-V , Virtual Box or VMWare player -- the disadvantage is that you do need an extra Windows license (I really think Ms should allow some sort of laxity in the licensing process when people are using Virtual Machines at Home - or allow them to be used for example like test server editions for 180 or even 90 days).

As far as Ms's sandbox is concerned it's currently of really limited use since anything that needs a re-boot for instance some configuration changes or after installing some software the whole kybosh is gone !!! -- you can't re-boot an Ms Sandbox in "Persistent mode" which means after the reboot any changes are lost.

Difficult one --there might be some commercial sandbox systems out there -- but IMO if you are paying for a sandbox you might just as well use another copy (legitimate) of Windows instead. !!!

Cheers
jimbo