Windows Sandbox Won't Start (0x80070002)? How to Fix
—
If Windows Sandbox won't start, the cause is almost never a Windows bug — it's one of four things: you're on Windows Home (Sandbox isn't included at all), virtualization is switched off in your BIOS, the Hyper-V-related Windows features aren't enabled, or another virtualization tool is holding the CPU's virtualization extensions before Sandbox can get to them. The counterintuitive part: most people assume Sandbox is broken because it used to work and suddenly stopped. In the majority of those cases, nothing actually broke — a Windows update quietly reset an optional feature back off, and re-enabling it is the entire fix.
Jake's shop keeps a Sandbox open most mornings — he uses it to open attachments customers hand him on a USB stick before he'll let them near his real machine. When it stopped opening on a Tuesday, he lost twenty minutes convinced he'd broken something. He hadn't. A cumulative update the night before had quietly turned the feature off again.
That's the pattern worth knowing before you touch anything: Windows Sandbox is not a standalone app. It's a thin, disposable desktop sitting on top of the same virtualization engine that runs Hyper-V. When it fails, you're almost always diagnosing that underlying engine, not Sandbox itself.
The one question that sorts most cases in ten seconds
Before any troubleshooting: open Settings, go to System > About, and look at "Edition." Everything downstream depends on the answer.
🙋♂️ Jake's Reality Check
"I bought this laptop three months ago and it doesn't have Sandbox in the Windows Features list at all. Is it broken already?"
No — it's Home edition. Windows Sandbox simply isn't shipped on Home, on Windows 10 or Windows 11. It won't appear in the features list, in search, or anywhere else, no matter how new or powerful the machine is.
If your edition says Pro, Enterprise, or Education and Sandbox still won't start, keep reading — the fix is almost always in the two sections below, not a reinstall.
Fixing it on Windows 11
Step 1 — turn on the three features it depends on
Press Win + R — this is the Run box, a small "type a command, hit Enter" window that's faster than clicking through menus once you know it exists. Type optionalfeatures and press Enter. In the list, tick all three of: Windows Sandbox, Virtual Machine Platform, and Hyper-V (or Hyper-V Platform, if that's the only Hyper-V line your edition shows). Click OK and restart when prompted — this feature genuinely needs the restart to take effect, it isn't a formality.
Step 2 — the same thing, via PowerShell, if the checkboxes won't stick
Some machines let you tick the boxes and they just uncheck themselves after restart. If that happens, open PowerShell as Administrator (right-click Start, then use "Show more options" if you're on the classic right-click menu, and choose Windows Terminal (Admin) or PowerShell (Admin)) and run:
Enable-WindowsOptionalFeature -Online -FeatureName "Containers-DisposableClientVM" -All
This is the same feature the checkbox controls, just addressed by its internal name. It's more reliable on machines where the graphical toggle silently fails, and it's the same command a Group Policy or Intune-managed business rollout uses under the hood.
Step 3 — confirm virtualization is actually on
Open Task Manager (right-click the taskbar or Ctrl+Shift+Esc), go to the Performance tab, click CPU, and look at the bottom right. If "Virtualization" says Disabled, the fix isn't in Windows at all — it's in your BIOS/UEFI. The fastest way in is from inside Windows itself: Settings > System > Recovery > Advanced startup > Restart now, then Troubleshoot > Advanced options > UEFI Firmware Settings. Once you're in the BIOS, look for a setting called Intel VT-x, AMD-V, or sometimes just "Virtualization Technology," turn it on, save, and let it boot back into Windows.
✅ Why this is the one to use
Do the checkbox-based feature toggle before anything more drastic. It's the same fix that solves the vast majority of "Sandbox suddenly stopped working" cases, it's fully reversible, and it doesn't touch anything else on your system. Save the BIOS trip for when Task Manager actually confirms virtualization is off — don't go hunting in the BIOS on a hunch.
Fixing it on Windows 10
The core fix is identical to Windows 11 — same Windows Sandbox, Virtual Machine Platform, and Hyper-V checkboxes in optionalfeatures, same PowerShell command if they won't stick, same virtualization check in Task Manager. Two things are genuinely different, and worth knowing before you go looking in the wrong place.
Getting to the BIOS is a different menu path
On Windows 10 the same restart-into-firmware option lives under Settings > Update & Security > Recovery > Advanced startup, not System > Recovery. It's the same destination — Windows reboots you straight into the UEFI firmware settings screen — just filed under the old Update & Security section that Windows 11 later broke apart and moved.
Windows 10 is out of free security updates
Windows 10 reached the end of free security updates on October 14, 2025. Sandbox itself still works exactly the same way if you're enrolled in Consumer ESU or running an LTSC build, but if a Sandbox failure on Windows 10 turns out to be feature-store corruption rather than a simple toggle, you're troubleshooting an OS branch that isn't getting the monthly servicing fixes it used to get unless you're enrolled — worth knowing before you sink an evening into DISM repairs on a machine that might be a better candidate for retirement.
⚠️ What this actually breaks
Consumer ESU enrollment requires a Microsoft account, not a local account, and needs Windows 10 22H2 specifically. If you're on an older Windows 10 feature update and hit a Sandbox problem tied to component-store corruption, you may need to update to 22H2 before ESU enrollment — and therefore before you're back on a servicing branch — is even possible.
When the easy fix doesn't work
"The feature failed to install"
This is different from Sandbox simply not being enabled — it means Windows tried to turn the feature on and couldn't, usually because a piece of the underlying component store is missing or damaged. Turning the feature off, restarting, and turning it back on clears a surprising number of these. If it doesn't, an elevated Command Prompt running DISM /Online /Cleanup-Image /RestoreHealth repairs the component store itself, followed by sfc /scannow to catch anything DISM's repair pass missed.
You also run VirtualBox or VMware
Sandbox and older-style VirtualBox/VMware both want first claim on the CPU's virtualization extensions, and only one hypervisor can hold them at a time. Modern VirtualBox and VMware Workstation both have a Hyper-V compatibility mode that lets them run alongside Hyper-V-based tools like Sandbox — check your version's settings for it. Older versions genuinely can't coexist; you'll need to fully uninstall the older tool, not just close it, since a running background service can still be holding the extensions.
🕐 What changed since we first covered this fix
- Then: this article originally covered a single language-related install bug (error 0x80070002) that affected Windows 10, version 1903, when the OS language was changed mid-update.
- Now: that specific bug was resolved by Microsoft in a servicing update years ago, and version 1903 itself is long out of support. The Sandbox failures people search for today are almost entirely edition, BIOS, and feature-toggle issues instead.
- What that means for you: if you landed here from an old bookmark about the 1903 error, you can stop worrying about it — it isn't the cause of a modern Sandbox failure.
Black screen, freeze, or crash right after opening
Ethan's take on this one is blunt: "Nine times out of ten, people blame Sandbox for what's actually a graphics driver problem." Sandbox shares your GPU with the host by default, and an outdated or flaky driver on the host machine shows up as a black or frozen Sandbox window. Update your graphics driver first. If that doesn't help, you can stop Sandbox from sharing the GPU at all by launching it with a small configuration file (a plain text file saved with a .wsb extension) containing <vGPU>Disable</vGPU> inside a <Configuration> block, then double-clicking that file instead of the Start menu shortcut.
You're on a laptop with a hybrid or business antivirus suite
Some endpoint-security products used in small businesses manage Hyper-V's virtualization-based security settings themselves and can silently block Sandbox from claiming the resources it needs. If you manage the antivirus policy yourself, check for a "virtualization-based security" or "hypervisor protection" setting and confirm it's set to allow, not block, other Hyper-V-based features. If it's a managed business device, this is one to hand to IT rather than fight alone — you likely don't have the permissions to change it either way. Jake ran into this exact conflict once he moved his shop's own machines onto a proper business-grade antivirus package instead of a free consumer one; one setting change in the console fixed it, and he hasn't had to touch it since.
You're on a VM, remote desktop session, or work-issued cloud PC
Windows Sandbox needs nested virtualization to run inside another virtual machine, which most consumer and even a lot of business virtualization platforms don't expose by default. If your "PC" is actually a VM, a Cloud PC, or a remote desktop session, Sandbox failing isn't a configuration mistake on your end — it may genuinely be unsupported on that platform, and no amount of toggling features will fix it.
Your CPU is simply too old
If the BIOS doesn't have a virtualization option at all, rather than one that's switched off, the CPU itself may predate the instruction sets Windows 11 now requires. Windows 11's 24H2 update and later hard-require the CPU instructions POPCNT and SSE4.2, which rules out pre-2009-era processors outright, unsupported-install tricks or not. Jake sees this a few times a year: a customer's older laptop simply can't offer what Sandbox needs, and at that point the honest answer isn't another registry tweak — it's that the machine has aged out, and a Windows 11-capable replacement is the actual fix.
Common Sandbox error codes at a glance
| Error code | What it usually means | Where to look |
|---|---|---|
| 0x80370102 | CPU virtualization extensions aren't reachable | BIOS/UEFI virtualization setting, or another hypervisor holding it |
| 0x8007042B | The feature install itself failed | Toggle the feature off/on; if that fails, run DISM RestoreHealth |
| 0x80004005 | Unspecified — usually a virtualization conflict | Close/uninstall other VM software; recheck BIOS setting |
| 0x80070002 | The historical 1903 language-switch bug — long resolved | Not relevant on any currently supported build |
When to use something other than Windows Sandbox
Sandbox isn't the right tool for every isolation job, and it's worth knowing when to stop fighting it and reach for something else instead.
| Tool | Works on Home? | Use it when |
|---|---|---|
| Windows Sandbox | No | A quick, one-off look at a file or installer with no setup and no leftover trace |
| Sandboxie-Plus | Yes | Isolating one specific app on your real Windows install, on Home edition, without a full separate desktop |
| A Hyper-V or VirtualBox VM | VirtualBox: yes | You need the environment to persist between sessions, or need a different OS entirely |
✅ Why this is the one to use
For the "let me check this one file before I trust it" job Sandbox is built for, don't bother with a third-party tool at all — Sandbox needs no separate download, no license, and nothing to configure. Reach for Sandboxie-Plus only if you're stuck on Home edition, and reach for a real VM only when you actually need something to survive a restart.
The thing you'll want thirty seconds after it finally opens
Once Sandbox is open, the next question people hit almost immediately is "how do I get a file from my real PC into it." Simplest route: copy the file on your host, then paste it inside the Sandbox window — clipboard sharing works by default. Drag-and-drop works too, straight from a File Explorer window on the host into the Sandbox desktop. Neither needs any setup, and neither leaves anything behind once you close the window — which is the whole point.
Jake's version of this is simpler than a config file: he keeps a shortcut to Sandbox pinned to his taskbar, and any USB stick a customer hands him gets opened there first, every time, no exceptions. "It's not that I don't trust people," he says. "It's that I can't tell which ones I shouldn't."
🙋♂️ Jake's Reality Check
"If I install something inside Sandbox to test it, can I just close it and reopen the same Sandbox with that program still there?"
No. Every single time you close Windows Sandbox, everything inside it — installed programs, files, changes — is gone. The next time you open it, it's a fresh copy again. That's not a limitation to work around; it's the entire security model.
Ethan disagrees with the workaround some forums suggest — editing the .wsb file to point at a persistent virtual disk to fake permanence. "At that point you've built yourself a worse VM than just using Hyper-V Manager properly," he says. "Sandbox earns its keep by throwing everything away. The moment you fight that, use a real virtual machine instead."
Setting it up once so you don't repeat the clicks
If you open Sandbox for the same kind of task regularly — Jake's case is "check this download before it touches a customer's data" — a .wsb file saves the repeat setup. It's a plain text file, saved with a .wsb extension instead of .txt, and Windows treats double-clicking it exactly like opening the Sandbox app, but with your settings already applied. A minimal one that maps in a downloads folder and disables the GPU share looks like this:
<Configuration>
<MappedFolders>
<MappedFolder>
<HostFolder>C:\Users\Jake\Downloads\ToCheck</HostFolder>
<ReadOnly>true</ReadOnly>
</MappedFolder>
</MappedFolders>
<vGPU>Disable</vGPU>
</Configuration>
Save that as, for example, CheckDownloads.wsb, and every double-click opens a fresh Sandbox with that folder already mapped in — read-only, so nothing inside Sandbox can write back to your real files. Keep a few different .wsb files for different jobs (one for checking downloads, one for testing an installer with a startup command) rather than editing the same one each time; they're small enough that a handful sitting in one folder costs nothing.
Frequently asked
Why does Windows Sandbox fail to start?
Most often it's one of four things, in this order of likelihood: Home edition (Sandbox isn't included), virtualization off in the BIOS, the Hyper-V-related features not enabled, or another virtualization tool holding the CPU's extensions.
Does Windows Sandbox work on Windows 10 Home or Windows 11 Home?
No, on either version. It isn't included on Home at all, and there's no setting, download, or workaround that adds it — the edition itself needs to be Pro, Enterprise, or Education.
What does error 0x80370102 mean?
The CPU's virtualization extensions aren't reachable. Check Task Manager's Performance tab for whether virtualization shows Enabled, and if not, turn it on in your BIOS/UEFI.
Can I run Windows Sandbox and VirtualBox or VMware at the same time?
Only if your version of VirtualBox or VMware has Hyper-V compatibility mode turned on. Older setups can't share the CPU's virtualization extensions and one of the two will fail to start.
Do I need to enable Hyper-V to use Windows Sandbox?
Yes — Sandbox runs on the same virtualization platform as Hyper-V, so Virtual Machine Platform and Hyper-V need to be enabled alongside the Windows Sandbox feature itself.
Why does it say the feature failed to install?
Usually a corrupted or missing piece of the Windows component store. Toggle the feature off and back on first; if that doesn't clear it, run a DISM RestoreHealth repair.
Is it safe to turn off Memory Integrity to fix Windows Sandbox?
It can resolve a conflict, but it disables a real security protection, so treat it as a last resort and switch it back on once you've confirmed it isn't permanently needed off.
Why does Sandbox open to a black screen or freeze?
Almost always a graphics driver issue on the host, not a Sandbox bug. Update the host's GPU driver, or disable vGPU sharing in a .wsb configuration file if updating the driver doesn't help.
Can I install software permanently inside Windows Sandbox?
No — everything is wiped the moment you close it, on purpose. If you need something to persist, that's a job for a real virtual machine, not Sandbox.
Does Windows Sandbox need internet access to run?
No, it starts without one. By default it shares your host's network connection, so anything installed inside it can reach the internet the same way your main PC does.
Why did Windows Sandbox stop working after an update?
Feature updates occasionally reset optional Windows features, including the ones Sandbox needs. Recheck Windows Features and re-enable Windows Sandbox, Virtual Machine Platform, and Hyper-V if any got switched off.
Is Windows Sandbox the same as Hyper-V or a virtual machine?
No — it uses Hyper-V's engine underneath, but it isn't something you configure like a VM. It's a ready-made, disposable Windows desktop that resets completely every time you close it.
What's the difference between Windows Sandbox and Sandboxie?
Sandboxie isolates one app on your real, live Windows install by intercepting its file and registry access. Windows Sandbox boots an entirely separate, disposable copy of Windows instead — heavier, but stronger isolation, and the only one of the two that works without a third-party download.
Can I automate opening a specific setup in Windows Sandbox every time?
Yes, with a .wsb configuration file — a small text file specifying which folders to map in and how to launch. Save different ones for different jobs and double-click the one you need instead of configuring Sandbox by hand each time.
Revision note. Originally published June 26, 2019, covering a specific error tied to the Windows 10 May 2019 Update. Rewritten August 20, 2026, for Windows 11 and Windows 10, since the original bug was resolved by Microsoft in a servicing update long ago and version 1903 itself is long out of support — this update covers the reasons Sandbox actually fails to start today instead. If you're here at midnight with a customer's USB stick and a Sandbox window that won't open, hang in there — it's almost always a five-minute fix, not a reinstall.