Windows Sandbox Not Starting? Fix the Common Causes

If Windows Sandbox will not start, first check that your Windows edition supports it, the Windows Sandbox feature is enabled, and hardware virtualization is turned on. Then restart Windows and try launching the default Sandbox before troubleshooting custom settings or repairing system files.

What Windows Sandbox needs to run

Windows Sandbox is a temporary Windows desktop that runs separately from your usual desktop. It is useful for opening an untrusted file, testing an application, or checking a website without keeping the session’s changes after you close it. Because it relies on Windows virtualization components, it will not run on every PC or Windows edition.

Check these basics before changing advanced settings:

Supported edition: Windows Sandbox is available in Windows 10 and Windows 11 Pro, Enterprise, and Education editions. It is not included in Home editions.
Supported Windows version: On Windows 10, Sandbox was introduced with version 1903. Install current updates for your supported Windows release; an old build can lack required components or fixes.
Hardware virtualization: The processor and firmware must support virtualization, and virtualization must be enabled in UEFI or BIOS.
System resources: Microsoft’s baseline requirements include at least 4 GB of memory, 1 GB of free disk space, and two processor cores. More memory and CPU capacity help when the host is busy.

To check the edition, open Settings > System > About and look under Windows specifications, or run winver. If the computer has Windows Home, enabling a feature or changing firmware settings will not add the officially supported Sandbox feature. Use a supported edition or consider another isolation option.

Confirm the Windows Sandbox feature is enabled

The feature may be available but not installed. Open the Start menu, search for Turn Windows features on or off, and select the matching Control Panel result. Find Windows Sandbox, select its checkbox, choose OK, and restart if Windows asks. After the restart, search for Windows Sandbox in Start and launch it.

If the checkbox is already selected, do not assume the installation is healthy. You can clear it, restart, select it again, and restart once more. This reinstalls the optional component without deleting your normal personal files. Close applications and save work before restarting.

On editions that support the feature, an administrator can also enable it from an elevated Command Prompt with:

DISM /Online /Enable-Feature /FeatureName:Containers-DisposableClientVM /All

Open Command Prompt as administrator before running the command. Let DISM finish, then restart Windows. If DISM reports that the feature name is unknown or unavailable, recheck the Windows edition and build rather than repeatedly running the command. The command cannot make an unsupported edition eligible.

Check virtualization in Windows and UEFI

Open Task Manager with Ctrl+Shift+Esc, select Performance > CPU, and look for the Virtualization entry. If it says Disabled, restart the PC and open its UEFI or BIOS setup. The key varies by manufacturer; common keys include F2, Delete, and Esc, but consult the computer maker’s instructions.

Look for a processor virtualization setting. It may be called Intel Virtualization Technology, Intel VT-x, AMD-V, or SVM Mode. Enable it, save the firmware settings, and boot Windows again. Menu names and locations differ, and changing unrelated firmware options can cause problems, so avoid changing settings you do not recognize.

Task Manager reporting virtualization as enabled is a useful check, but it does not prove that every Windows component is working. If Sandbox still fails, verify that the PC meets the processor and memory requirements and continue through the Windows feature checks. Some PCs managed by an employer or school have firmware settings locked by policy; contact the administrator rather than trying to bypass those controls.

Restart the hypervisor safely

Windows Sandbox uses Microsoft’s virtualization platform. On some PCs, its startup can be affected if Windows is configured not to launch the hypervisor at boot. This can happen after troubleshooting virtualization or using boot-configuration utilities. It is not a reason to turn off security features or remove unrelated software as a first step.

If you are comfortable using an elevated Command Prompt, inspect the boot setting with bcdedit. If you find that hypervisorlaunchtype is explicitly set to Off, you can set it to Auto with:

bcdedit /set hypervisorlaunchtype auto

Restart Windows after changing the setting. This changes how the Windows hypervisor starts, and may affect other virtualization software or configurations. Do not change boot settings on a managed PC without permission, and do not run the command blindly if you are unsure what another virtualization tool requires. Windows Sandbox is not fixed by disabling the hypervisor it depends on.

Test with the default Sandbox before custom settings

A custom Windows Sandbox configuration file can change networking, mapped folders, logon commands, or other startup behavior. If you double-click a .wsb file and the window never appears, test the basic app from the Start menu. If the default Sandbox opens, the problem is more likely in the configuration file than in the Windows feature itself.

For a clean test, create a new plain-text file, save it with a .wsb extension, and leave its contents at the basic configuration—or simply launch Sandbox from Start without opening a file. Check that a file intended to be test.wsb was not accidentally saved as test.wsb.txt; File Explorer’s file-extension display can help reveal this. Add custom settings back one at a time so you can identify which change causes the failure.

Mapped folders deserve particular attention. A path that no longer exists, an invalid XML value, or a command that depends on a missing file can interfere with a configured session. Also remember that a mapped host folder exposes some of its contents to the isolated environment. Share only what the task needs, and use read-only access when the Sandbox does not need to alter host files.

Install updates and check for system component problems

If edition, feature, and virtualization checks look correct, install available Windows updates and restart. Sandbox depends on Windows components, and an incomplete update or damaged component store can prevent an optional feature from installing or starting. On a work-managed computer, update timing may be controlled by your organization.

If Windows Features or DISM reports an error, note the complete message and any error code before trying repairs. On a personal PC, you can run these commands in an elevated Command Prompt, one at a time:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM checks and repairs the Windows component store; System File Checker then checks protected system files. Both can take time. Follow any repair message with a restart, and try enabling Sandbox again. These tools are not a guaranteed fix for an unsupported edition, disabled firmware virtualization, or an invalid configuration file.

If the issue began immediately after an update or a driver change, note that timing, but avoid deleting system folders or downloading replacement system files from unofficial sites. If the error persists, the exact Windows version and complete error text are more useful to support staff than a vague report that Sandbox “does nothing.”

What to do when it still will not start

Work from the simplest checks to the more disruptive ones. After each change, try launching the default Sandbox so you can tell whether the change helped. A practical order is:

Confirm Windows edition and version in Settings or with winver.
Check that Windows Sandbox is selected in Windows Features, then restart.
Check Task Manager for virtualization status and enable it in firmware if needed.
Test the default Sandbox rather than a custom .wsb file.
Install updates, record any error, and use DISM and SFC if Windows reports component problems.

If Windows does not list Windows Sandbox at all, edition or build compatibility is a leading possibility. If the feature installs but startup fails, virtualization settings, boot configuration, or a damaged component are more relevant. This distinction helps avoid spending time on firmware changes when the edition itself does not support Sandbox.

For an organization-managed PC, ask IT for help if virtualization is locked, the feature is controlled by policy, or the error appears after a managed update. Provide the Windows edition and version, the exact error, whether the default Sandbox also fails, and the steps already tried.

Security and alternatives

Sandbox is disposable: when you close it, its software, files, and session changes are discarded. That makes it convenient for short tests, but it is not a substitute for antivirus, careful browsing, backups, or a properly managed virtual machine. Its temporary nature also means it is a poor place to keep work you need later; move only files you trust and intend to retain.

If Sandbox is unavailable on Windows Home or unsuitable for the task, alternatives include a full virtual machine in compatible virtualization software, a separate test PC, or a cloud-hosted test environment. These options have different setup, licensing, performance, and security trade-offs. A virtual machine can preserve a disk between sessions, for example, but that persistence means unwanted changes may remain unless you revert a snapshot or reset it. Choose based on whether you need disposable testing, persistent development, or stronger separation from the host.

Frequently Asked Questions

Why is Windows Sandbox missing from Windows Features?

First check that the PC runs a supported Pro, Enterprise, or Education edition and a compatible Windows build. Windows Sandbox is not included in Windows Home. If the edition is supported but the feature is still missing, install Windows updates and check with your administrator if the device is managed.

Does Windows Sandbox work on Windows Home?

Windows Sandbox is not an officially available feature in Windows Home. Enabling virtualization in firmware does not change the Windows edition. Use a supported Windows edition or choose another isolation method that fits your needs and licensing.

Why does Sandbox open and then close?

Possible causes include an invalid custom configuration, a Windows component problem, or virtualization and hypervisor settings. Try launching Sandbox directly from Start with no custom file. If that works, inspect the .wsb file; if it does not, check the feature installation and Windows error details.

Do I need to enable Hyper-V separately?

Windows Sandbox relies on Windows virtualization components, but the supported Windows Features interface can install the dependencies when you enable Sandbox. Start by enabling Windows Sandbox itself rather than changing several virtualization features at once. Avoid turning off the hypervisor, which Sandbox needs.

Will files remain in Windows Sandbox after I close it?

No. The session is designed to be temporary, and its changes are discarded when the Sandbox closes. Copy out anything you need to keep before closing it, and be deliberate about mapped folders because they provide access to selected files on the host.

Sources: general know-how. Menus and buttons can differ slightly by version. Spotted something out of date? Tell us.