Windows Sandbox: How to Use It

Windows Sandbox gives you a clean, disposable Windows environment for testing risky files or software without affecting your main system. You open it, do what you need, and close it—everything inside is permanently deleted. This guide covers the requirements, step-by-step enabling, and daily use.

What You’ll Need

• Windows 10 Pro, Enterprise, or Education (build 18305 or later) or Windows 11 Pro/Enterprise/Education. Home editions do not include Sandbox.
• 64-bit CPU with virtualization enabled (VT-x/AMD-V) and SLAT (Second Level Address Translation).
• At least 4 GB of RAM (8 GB recommended) and at least 1 GB of free disk space.
• Administrator access to your PC to enable the feature.

Step-by-Step

1. Check your Windows edition. Press Win + R, type winver, and press Enter. Confirm you are on Pro, Enterprise, or Education. If you’re on Home, you’ll need to upgrade or use a third-party alternative.
2. Enable virtualization in BIOS/UEFI if needed. Restart your PC, enter the BIOS/UEFI (usually by pressing Del, F2, or F12 during boot), and look for a setting like “Intel Virtualization Technology” or “SVM Mode” (AMD). Enable it, save, and exit. If you’re unsure, check your motherboard or laptop manual.
3. Turn on Windows Sandbox via Windows Features. Open the Start menu, type “Windows Features”, and click “Turn Windows features on or off”. Scroll down, check the box next to “Windows Sandbox”, click OK, and restart when prompted.
4. Launch Windows Sandbox. After restart, click the Start button, type “Windows Sandbox”, and click the app. It will open a fresh desktop window—this is your isolated environment.
5. Copy files into the sandbox. To test a file, copy it from your host and paste it into the sandbox window (Ctrl+C, then Ctrl+V). You can also drag and drop, but clipboard is more reliable. The file is now inside the sandbox only.
6. Run your test. Inside the sandbox, double-click the file or install software as you normally would. Everything stays within the sandbox—your host system cannot be affected.
7. Close the sandbox. When done, simply close the window like any app. A prompt asks if you want to discard the sandbox—click OK. All files, settings, and software inside are permanently erased.

Common Mistakes

• Using Windows Home edition. Sandbox is not available on Home. Check your edition before trying to enable it.
• Forgetting to enable virtualization. Even if Windows Features is on, Sandbox won’t start without VT-x/AMD-V active in BIOS.
• Copying files via drag-and-drop only. Dragging sometimes fails or copies a shortcut. Use clipboard copy/paste for reliability.
• Expecting persistence. Anything you save inside the sandbox is lost when you close it. If you need to keep something, copy it out before closing.
• Running Sandbox with low RAM. It needs at least 4 GB free; with less, it may be extremely slow or fail to start.

Tips

• Use the clipboard to move text and small files—it’s the most reliable method.
• You can run multiple sandbox instances at once, but each uses extra RAM and CPU.
• If you need network access inside the sandbox, it’s enabled by default. To disable it, you can edit the sandbox configuration file (advanced users only).
• For testing untrusted software, consider also using a dedicated virtual machine (like Hyper-V or VirtualBox) for more control.
• Sandbox is great for testing browser downloads, opening suspicious email attachments, or trying new apps without cluttering your main system.

Troubleshooting

• “Windows Sandbox failed to start” error. This usually means virtualization is off or not available. Reboot into BIOS and enable VT-x/AMD-V. If it’s already on, run systeminfo in Command Prompt and check the “Hyper-V Requirements” section—if it says “A hypervisor has been detected”, you may need to disable Hyper-V or Core Isolation in Windows Security.
• Sandbox opens but is blank or freezes. Close it, restart your PC, and try again. If it persists, ensure you have enough free RAM (close other apps). Also check that your graphics drivers are up to date.
• Can’t find “Windows Sandbox” in Windows Features. Your Windows edition doesn’t support it, or the feature is hidden because virtualization is off. Confirm your edition and BIOS settings first.
• Copy/paste not working. Try using the right-click menu instead of keyboard shortcuts. If that fails, use drag-and-drop or create a shared folder via the sandbox configuration file.
• Sandbox is very slow. Close other programs, reduce the number of running sandbox instances, and ensure your PC meets the recommended 8 GB RAM. Also, check that your CPU supports SLAT.

Frequently Asked Questions

Is Windows Sandbox free?

Yes, it’s a built-in feature of Windows Pro, Enterprise, and Education. No extra purchase is needed.

Can I use Windows Sandbox on Windows Home?

No, it’s not available on Home editions. You can either upgrade to Pro or use a free tool like VirtualBox.

Does Windows Sandbox protect against all malware?

It isolates the sandbox from your host, so most malware can’t escape. However, advanced malware could potentially exploit virtualization vulnerabilities. It’s not a substitute for a good antivirus.

Can I save files from the sandbox?

Yes, copy them out before closing. Once closed, everything inside is gone.

How much RAM does Windows Sandbox need?

At least 4 GB total on your PC, but 8 GB or more is recommended for smooth performance.

Can I run Windows Sandbox alongside other virtual machines?

Yes, but it may conflict with Hyper-V if both are active. You may need to disable Hyper-V temporarily to use Sandbox.

Related

• Fix Critical Structure Corruption BSOD in Windows 10
• Fix Error 0xc0000135: 5 Working Solutions
• Windows 10 Install Error 0xc1900101 0x20004 Fix