The sandbox employs the strict virtualization security of Hyper-V and also contains features that enable resource sharing with your host machine. Once you initiate the sandbox, it launches a Windows 10 VM. WSB, which you can use to configure a wide range of options, including mapped folders, vGPU, networking and an automated script that can run at user login.

The sandbox provides a dedicated configuration file format, called.

Windows Sandbox starts clean on each run and does not have a persistent state. Behind the scenes, Windows Containers uses Hyper-V, but you do not control Hyper-V or directly work with VMs. It is based on Windows Containers technology, and supports use cases like troubleshooting, demos or isolation of untrusted or malicious software. Windows Sandbox is built into Windows 10 (Pro/Enterprise). It also enables you to provide different people, services and groups access to different resources and systems. Hyper-V can help you prevent crashes from affecting other workloads. Hyper-V enables you to run multiple VMs simultaneously, on the same hardware. Instead of running a single operating system on physical hardware, you can use Hyper-V and run each VM inside its own isolated space. You can use Hyper-V to create and run a virtual machine (VM), a virtual computer running its own operating system and applications. Microsoft Hyper-V offers hardware virtualization. In this article I’ll discuss how to perform sandboxing in a Windows environment using Hyper-V, Windows Containers, and the Windows Sandbox environment built into Windows 10. Read this post for an excellent background to sandboxing technology. It involves granting each application, process, or user its own isolated environment. Sandboxing is a technique commonly used in security, software development, and IT resource provisioning.

Windows 10 sandbox vm