The topic I stopped downloading VirtualBox after discovering Windows 11’s built-in sandbox is currently the subject of lively discussion — readers and analysts are keeping a close eye on developments.
This is taking place in a dynamic environment: companies’ decisions and competitors’ reactions can quickly change the picture.
If you ask anyone how to safely test a sketchy executable or PowerShell script, the answer will usually involve downloading VirtualBox, VMware, or another similar virtualization suite, followed by finding a Windows ISO, and then spending an evening installing a whole OS within their OS. It’s the standard advice, and for a lot of people, that’s more friction than they’ll ever bother with. Suffice it to say, the executable or the script will likely go straight to the Recycle Bin.
What many don’t realize is that Windows 11 already ships with a disposable virtual machine built-in to the platform. It launches in seconds, needs no bulky ISOs, wipes itself completely the moment it is closed, and requires nothing besides knowing the name of the utility. It’s called Windows Sandbox, it has been around for years now, and recent updates have only made it better. Here’s why you don’t need a third-party virtualization tool if you’re on Windows 11 Pro, Enterprise or Education edition.
There is plenty of third-party software out there, but some tools and apps are exclusive to Windows 11.

Windows Sandbox is a light, disposable version of Windows that runs in an isolated window on your desktop. You can think of it as a temporary desktop environment that runs whenever you need it to, and then vanishes when you close the session. Since every single session starts fresh, it’s just as though you installed Windows inside a machine for the first time in a virtual environment, and nothing you do inside it impacts your main PC.
It’s built on the same Hyper-V virtualization technologies that powers full virtual machines, using hardware-level isolation to keep whatever happens inside the Sandbox sealed away from your real OS. Unlike a traditional virtual machine, though, you require no configuration, no disk images, and, of course, no dealing with Microsoft’s nudges to sign in or install any of their bloatware AI features. The reason for this is that it borrows from your existing Windows installation to spin itself up instantly. Currently, Windows Sandbox is available for all Windows 11 Pro, Enterprise, and Education variants.
If you’re trying to run Windows Sandbox for the first time, you’d have to enable the toggles it relies on, which is important to mention since your OS never will. If you try to run it from Start, you will likely see an error dialogue that says, “The connection to the Windows Sandbox environment was lost” alongside an unhelpful error code that won’t point you anywhere useful.
To get it up and running, you need to satisfy a few simple pre-requisites. First, you’ll want to look for “Windows Features” on Search, tick a few boxes you see on the new window, including “Windows Sandbox” (obviously), “Hyper-V”, “Virtual Machine Platform” and then “Windows Hypervisor Platform”. Once all of that is done, you’re ready to roll after a quick restart. This part is worth mentioning, since I’ve noticed that, even if you’ve used the Sandbox before, sometimes after an update, these boxes tend to get unchecked for reasons I cannot reliably explain. It’s best to take a second look in that regard.
After it’s enabled, Windows Sandbox will appear on your Start menu. If you click it and wait a couple of seconds, you’ll be greeted with a Windows desktop with the default wallpaper and a few icons opened up in a new window. It’s really simple, and if you were to compare how long it would’ve taken you to get to the same screeen by downloading a hypervisor, obtaining a multi-gigabyte Windows image, creating a virtual disk and sitting through a full OS installation, the appeal would become rather obvious.

Enable Windows Sandbox and test questionable software risk-free in a disposable virtual machine.
Windows Sandbox has always been simple, but that itself was its own ceiling. It did one thing well, but it offered almost no control over configuration, which is why most power users would still gravitate towards third-party VM tools. A lot has changed on that front recently, for the better.
Microsoft has now added a settings interface and expanded what you can configure, including sharing your microphone or webcam into the sandbox, hardening the connection with a protected-client mode, and perhaps most importantly, adjusting how much of system memory is allocated to it. All of this behavior is configured through a plain-text file saved with a .wsb extension, but you’d have to create and save them manually to a location of your choice.
If you know what you want and what you’re doing, it can be quite convenient. A few lines let you disable networking entirely for testing a shady script you found on GitHub, map a specific folder from your actual PC as “read-only” so a suspicious executable can’t touch anything else, or run a command automatically when the Sandbox pops open. I often use it by cutting off internet access and sharing only my Downloads folder in read-only mode, which gives me a quarantine zone to inspect a questionable file with no path back to my actual system.
Recently, I’ve gotten a lot into vibe-coding and generating system-level scripts with Claude Code. When it comes to running them (before I fully trust them), Windows Sandbox has become the natural other half of that workflow. It’s also where those one-star GitHub scripts find a home to run as well, which might just wreck my OS or open a gaping hole in my security if I ran them on the real thing. For any tinkerer, it’s a habit worth building, mostly because the setup cost is effectively zero in terms of the time taken to get it running.
Windows 11 is the most popular desktop operating system in the world by market share. An installation of the Windows 11 Pro, Enterprise or Education edition will include a license key, along with several additional features like Hyper-V and Windows Sandbox support.