For example, the technical blog refers to the Windows Containers technology, but in the official documentation, the creation and management of Windows Containers is done using the Docker utility for Windows, which isn’t used in Windows Sandbox. While it combines two widely documented technologies (Windows Containers and Hyper-V), we are still missing on how it all works together. Lack of documentation on its internal technicalities, both official and community-based.We decided to dig deeper into this technology for several reasons. The guest disk and filesystem are created dynamically, and are implemented using files in the host filesystem.įigure 1 – Dynamically generated image (from Microsoft official documentation). One of the interesting features is of particular importance, and we will elaborate on it here. On the other hand, the sandbox contains several features which allow sharing resources with the host machine to reduce CPU and memory consumption. The resulting sandbox presents the best of both worlds: on the one hand, the sandbox is based on Hyper-V technology, which means it inherits Hyper-V’s strict virtualization security. Judging by the accompanying technical blog post, we can say that Microsoft achieved a major technical milestone.

The deployment is based on Windows Containers technology.

You can configure networking, vGPU, mapped folders, an automated script to run at user login, and many other options. Configurable through a configuration file that has a dedicated format (WSB format).Pristine and disposable – Starts clean on each run and has no persistent state.Integrated part of Windows 10 (Pro/Enterprise).This sandbox has some useful specifications:

Two years ago, Microsoft released a new feature as a part of the Insiders build 18305 – Windows Sandbox.

Install windows sandbox