Sandbox: a virtual Windows
Updated
Sandbox runs a separate Windows environment with its own display and applications. Manual VM use is Free; guest scenario automation, PingLess and a custom VM proxy require PRO.
MultiBox · Sandbox
Several machines, each kept
Create machines, start and stop them, save one and resume it later exactly where you left off.
- Save and resume
- Arrange windows
- Own disk per VM
Create and open a VM
- Open Sandbox and create a VM with the wizard. Supply the Windows image and components requested by the app.
- Choose resources, shared folders, clipboard, sound and networking for the task. Leave memory available to the host.
- Start the VM and wait for its display to connect, then open the target application inside the guest.
- Use the configured capture/release and fullscreen shortcuts. Change them in the workspace settings.
Image and resource setup
- Current Sandbox needs 64-bit Windows 10 version 2004 (build 19041) or newer, or Windows 11 on an Intel/AMD PC. Enable virtualization in BIOS/UEFI and the Windows VM components. The app checks available capabilities; the Home or Pro edition name alone is insufficient.
- If the base image is not ready, the wizard requests a Windows 11 Pro ISO and an installation folder. Choose a drive with at least 25 GiB free for the base image; it need not be the system drive.
- Each VM folder can be separate from the base image. Maximum disk capacity is 64–2048 GiB, defaulting to 80 GiB. The file grows as it fills, but monitor actual free disk space.
- Resolution can be automatic, a preset up to 3840×2160 or custom: width 1024–3840 and height 768–2160. An explicit guest resolution is not limited by the host monitor.
- GPU acceleration depends on Windows capabilities and the driver. Investigate an unavailable-feature message before treating a black display as a scenario error.
- Shared folders have selected access modes; the clipboard transfers text. Use configured shared folders for files and check write permissions.
Display, saved state and input
- Guest resolution and viewer size are separate. Viewer scaling does not change guest coordinates.
- Choose automatic, preset or custom resolution. Applying it may require full shutdown/start instead of saved-state resume.
- Saving memory state differs from shutting down. Resumed applications retain their previous state; verify that the scenario expects it.
- Configure or hide fullscreen controls and the FPS overlay. Release a captured guest mouse with the assigned shortcut first.
Connect a scenario — PRO
- Start the VM manually, then add Set SandBox to the scenario.
- Choose the VM and optionally a guest window in the Inspector. With no window selected, the target is the guest desktop.
- Pass the guest target to capture, detection, OCR, mouse and keyboard nodes. Keep all related actions on that target.
- Handle the failure branch: a stopped VM or closed window is not a successful connection. The node does not start VMs.
Multi-target mode can iterate windows in one VM, multiple VM desktops or a mixed list. Connect to guest processes through Memory Viewer; host-managed browser automation uses the Browser workspace. These targets are not interchangeable.