When you start tinkering with unfamiliar software, strange scripts sent to you via chat, or attachments you don't fully trust, having a isolated environment where none of that can break your Windows It's practically mandatory. In security, this is called sandboxing. It means creating a kind of controlled environment where you can run tests without fear of crashing the system or leaking sensitive data.
The good thing is that in many cases you can mount this protection in a way that manual and without installing third-party programstaking advantage of what Windows already offers (such as the Windows Sandboxor even by using sandbox environments that rely on operating system primitives in macOS, Linux, or WSL2. And when you need to go a step further, you have tools like Sandboxie Plus that give you fine control over what each application can do.
What exactly is sandboxing and why might you be interested in using it?
In simple terms, a sandbox is a security mechanism that separates the execution of programs So that, even if something goes wrong or is malicious, the damage remains confined within that environment and doesn't reach the main system or your personal data. This isolation can affect the CPU, memory, disk, network, and even input devices.
One of the most common uses of the sandbox is the running unreliable applicationsThese include installers downloaded from dubious websites, suspicious email attachments, or binaries received via messaging. By keeping them in an isolated environment, their access to resources such as storage, network, host system inspection, or reading input devices is greatly restricted. limited or directly blockeddepending on how you configure the protection.
A classic example of a sandbox is the complete virtual machinesThese emulators emulate an entire computer and load a guest operating system completely separate from the host. The guest system does not run natively, but rather through the emulator or hypervisor. It can only access the host's physical resources through this intermediate layer.
However, virtual machines are not the only type of sandbox that exists. Modern browsers like Chrome, Chromium or Edge They use multiple layers of process isolation so that a compromised tab doesn't drag down the rest of the system. Similarly, some modern development tools offer their own internal sandbox for running code agents, scripts, and terminal commands with very restricted permissions.
In the Windows ecosystem, in addition to virtual machines, you have options such as Windows Sandbox and advanced solutions like Sandboxie Plus. Solutions that create a separate operating environment for your programs. And if you look at other systems, projects like native sandbox development agents use system primitives (Seatbelt on macOS, seccomp or Landlock on Linux, bubblewrap, etc.) to reinforce that isolation.
Windows Sandbox (WSB): The sandbox built into Windows 10 and 11
Microsoft included a feature in Windows 10 and Windows 11 called Windows Sandbox (Windows Sandbox, WSB), designed so that any user can have a ready-to-use "mini virtual machine" without much hassle. It is based on hypervisor virtualization (Hyper-V) and sets up a lightweight, temporary, and completely separate desktop environment of the main system.
Within that isolated space you can install and run programs with complete peace of mind. Everything that happens in there stays in thereWhen you close the sandbox window, the installed software, created files, and even the system state are erased, as if it never existed. Every time you start it, you get a new and clean instance, similar to a fresh Windows installation.
Host applications are not automatically shared with the sandbox. If you need something inside, you'll have to... install it explicitly within the isolated environmentOr map folders following the syntax of .wsb files, where you can even mark paths in read-only mode and disable the network to add an extra layer of security.
From a technical point of view, WSB behaves like a disposable virtual machineHowever, it's much lighter than a conventional VM. It leverages files from the host operating system, uses a separate, stripped-down kernel, and employs optimizations to reduce memory consumption and speed up boot times. This way, you can have it up and running in a matter of seconds.
Key features of Windows Sandbox
One of the clearest advantages of WSB is that it is part of the professional editions of WindowsTherefore, you don't need to install a third-party hypervisor or a full virtualization solution to have a reasonably robust sandbox. Everything is already in the system, ready to be activated from the optional features.
This isolated space is completely disposable and pristineEach launch is equivalent to booting a fresh Windows installation. Nothing is saved when you close the window, which greatly simplifies software testing and prevents the accumulation of program remnants or unusual configurations over time.
In terms of security, Windows Sandbox is based on the hardware virtualization to isolate the kernelIt uses Microsoft's hypervisor to run a separate kernel that strictly isolates the sandbox from the main system. This greatly reduces the attack surface if the executable you're testing contains malware, exploits, or unexpected behavior.
In terms of performance, WSB is designed to be fast and efficientIt makes use of the virtual GPU, an integrated kernel scheduler, and intelligent memory management, resulting in low boot times and lower resource consumption than a full virtual machine with its own independent operating system.
Being included in Windows 10 Pro, Enterprise and Education, as well as in Windows 11 Pro and Enterprise, You don't need external VHDs or additional licensesThe system uses a reduced image of Windows itself, approximately 100 MB, to run the environment, simplifying maintenance and reducing additional downloads.
Editing, licensing, and hardware requirements for using WSB
Windows Sandbox is not available in all versions of the system. To activate it, you need a compatible edition of WindowsWindows 10 Pro, Enterprise, or Education (including Pro Education/SE), or Windows 11 Pro and Enterprise, are supported. Windows Home is excluded for now, as Microsoft does not offer official WSB support for that version.
Regarding licensing, the rights to use the isolated space are included in the Windows licenses geared towards professional and educational environmentsThis would include Windows Pro and Pro Education/SE, Windows Enterprise E3 and E5, and the A3 and A5 educational licenses. Full details about licensing can be found in the general Windows licensing documentation.
From a hardware perspective, the system needs a CPU with virtualization capabilities (in AMD64 or modern ARM64 architecture in the case of Windows 11), at least 4 GB of RAM (8 GB is recommended for extra capacity), 1 GB of free disk space (ideally on SSD) and a minimum of two CPU cores, with four with hyper-threading being desirable for smoother performance.
It is essential that the virtualization is enabled in the BIOS/UEFI of the physical equipment. If you are inside a virtual machine, you will also need to enable nested virtualization and, in some cases, update the VM to add that functionality, using PowerShell commands to expose the virtualization extensions and update the machine version; if you are interested in setting up a more complex environment, you can see a guide on Windows 11 as a test lab host.
If the Windows Sandbox checkbox doesn't appear when you try to activate the feature, it's very likely that the system has determined that Your equipment does not meet one or more of the requirementsIn that case, you need to check both the installed Windows version and the BIOS settings and available hardware.
How to activate and start Windows Sandbox step by step
Once you've confirmed that your edition and hardware meet the requirements, the first step is turn on virtualization options in the BIOS or UEFI. You'll usually need to look for settings like Intel VT-x, AMD-V, or similar and enable them. This is a crucial step, because without it, Windows can't use Hyper-V or the container and sandbox features.
With virtualization complete, follow these steps:
- Open Windows.
- Go to Control Panel.
- Open the Programs folder.
- Access Programs and Features.
- Select Turn Windows features on or off.
There you'll find a list of optional components; check the Windows Sandbox box and accept. The system will download and configure what's needed and then prompt you to restart.
If you prefer, you can enable the feature from PowerShell run as administratorThis is done with a command that activates the Containers-DisposableClientVM functionality, which manages this temporary desktop environment. This method is particularly convenient if you automate deployment or work with configuration scripts for multiple machines.
After restarting, simply open the Start menu and search for “Windows Sandbox” To launch the tool for the first time, you'll see a window with a minimalist Windows desktop: from there you can copy files, install programs, and run tests, knowing that when you close it, the entire environment will disappear.
For advanced users, there is the possibility of create .wsb configuration files These features allow you to customize the sandbox's behavior: enabling or disabling the network, mapping host folders to read-only or read/write mode, running scripts at startup, and more. With this configuration, you can design highly refined environments tailored to each use case, for example, a sandbox for malware analysis without an internet connection and with a read-only sample folder.
Try out advanced WSB features with the Windows Insider program
If you want to stay up to date with the latest improvements Microsoft is introducing to sandboxing, you can join the Windows Insider ProgramBy doing so, you'll gain access to preview builds of Windows that often include changes and new WSB options before they're released to the general public.
Within this program you can choose different update channels in Windows settings.
- Development channel. It provides the latest features, at the cost of reduced stability.
- Beta ChannelMore balanced. It's usually the best option for advanced users who want to try new things without too many surprises.
- Preview Channel. It focuses on Key fixes and features in the next stable versionjust before its final release. It's a good way to validate that the new sandboxing capabilities behave as expected without exposing yourself to overly radical changes.
However, keep in mind that using Insider builds implies accepting a certain degree of risk and instabilityIt is recommended to do this on test equipment or in environments where a system failure does not pose a serious production problem.
Sandboxing on macOS, Linux, and Windows beyond WSB
Although the focus here is on Windows Sandbox and manual sandboxing, it's worth taking a look at how Isolation is implemented in other systemsbecause many ideas are applicable when you think about designing your own security and testing strategy.
On macOS, for example, there are several options: App Sandbox (aimed at apps from the Mac App Store), containers, virtual machines, and a sandbox profiling system called seat beltaccessible via sandbox-exec. Although Seatbelt was declared obsolete years ago, it is still used by critical third-party applications like Chrome, precisely because of the granularity with which it allows defining permissions.
With Seatbelt you can dynamically generate a policy profile that restricts calls to the system and reads/writes to specific paths. Typically, the tool or code agent builds this profile in real time based on the user's configuration and rules similar to an .ignore command, very specifically blocking what can and cannot be accessed.
In Linux, the kernel offers powerful primitives such as seccomp and LandlockThese features allow blocking dangerous syscalls and applying access restrictions to file systems. Many sandbox solutions combine these capabilities with an overlay file system to present the process with a filtered view of the disk, where "ignored" files are replaced with protected copies that the isolated process cannot read or modify.
In the Windows world, when you need to run general-purpose development tools with Linux-like isolation, one strategy is Use WSL2 and launch it within a Linux sandbox. (for example, with bubblewrap) instead of trying to recreate all the primitives on top of native Windows itself, which has historically been more oriented towards application isolation than flexible containers for development.
Code agents and sandboxing: fewer interruptions and more security
Modern code agents benefit greatly from sandboxing. Without it, every bash command they want to run needs to be sandboxed. your manual approvalThis leads to a flood of permission requests and the risk of fatigue (you end up accepting almost without looking).
By placing these agents within a well-defined, isolated environment, they can be allowed to work with much more autonomy provided they don't try to go outside the established boundaries. Only when they need something outside the sandbox is a permission request triggered.
In practice, this means that the officers stop around a 40% fewer times This is because when everything requires one-by-one approval, it saves time and reduces interruptions. For the model to know how to behave, the sandbox constraints must be clearly defined in the shell tool.
Furthermore, many implementations refine the experience by displaying in the terminal tool's results a Explicit explanation of what restriction caused the failureAnd, in some cases, a suggestion to escalate the situation. This way, the agent learns to decide when they can continue retrying on their own and when they should request an escalation.
All these mechanisms rely on operating system primitives: Seatbelt in macOS, bubblewrap in Linux, and WSL2, or combinations of seccomp, namespaces, and network proxies. The result is an environment where the attack surface against prompt injections, malicious dependencies, or compromised scripts is reduced, since even if the agent makes a mistake, Their actions are confined within the sandbox.
Sandboxie Plus: Granular application isolation in Windows
Beyond Microsoft's built-in sandbox, there is a well-known solution in Windows called Sandboxie plusThis is an evolution of the classic Sandboxie, which creates an isolated operating environment for running and installing programs without permanently modifying the local system. Unlike WSB, it's not a complete mini-installation of Windows, but rather a virtualization layer at the process and file system level.
Sandboxie was born back in 2004 as a tool for enclose Internet Explorer and minimize the impact of their vulnerabilities. Over time, it expanded to other browsers and any untrusted application. Today, under the GPLv3 license, both the classic and Plus versions share a security foundation. The difference is that the latter has a Modern interface based on Qt and a series of extras that make it more comfortable and powerful.
Among the most interesting features of Sandboxie Plus is the snapshot managerThis allows us to take a picture of any "sandbox" and restore it later, a maintenance mode to install or uninstall the service and driver when needed, and a portable mode that extracts all the files to a directory to take it anywhere without traditional installation.
It also offers additional interface options for block access to specific Windows componentsFor example, the clipboard or the print queue. And also more fine-tuning to restrict internet access, control what can be launched from Start > Run, and a global hotkey to kill all processes within an isolated box in case of emergency.
In addition, it includes a sandbox firewall based on the Windows Filter Platform (WFP)This allows each device to be treated as if it had its own network rules. All of this is supported by predefined restriction templates so that even less experienced users have a reasonably secure environment from the outset, with the ability to adjust and strengthen these restrictions as needed.
Getting Started with Sandboxie Plus
When you install Sandboxie Plus, the program creates a default isolation environment called “DefaultBox”From the context menu, you can access the sandbox options and modify its behavior. For example, you can decide which paths it can write to, which applications are automatically launched inside, what network restrictions to apply, and so on.
What's truly interesting, however, is creating your own separate environments for different use casesFrom the Sandbox menu, you can choose "Create new Sandbox." Then give it a descriptive name and finally select an initial configuration such as "Hardened" to increase protection and accept.
Running an application inside a sandbox is as simple as right-click on the boxPlace the cursor on “Run” and choose “Run a program.” You can manually enter the path to the executable or use the Browse button to locate it. Once you select and confirm, that program will start within the isolated environment, inheriting all the defined restrictions.
Another convenient way to use it is to resort to Sandboxie Plus integrated start menuFrom the same "Run" menu, you can choose "Run from Start Menu" and select applications installed on your system that you want to run under the protection of the sandbox, without having to search for their executable manually.
In short, manual sandboxing without additional software and using tools integrated into the system, reinforced when necessary with solutions like Sandboxie Plus or well-configured Linux/macOS environments, allows you to have very clear layers of defense against dubious software, human error, and increasingly automated code agentsTaking advantage of these isolated environments to browse, test, debug, and run sensitive programs is a practical way to reduce risks, without sacrificing experimentation or working comfortably.
