Set Up Windows Sandbox on Windows 10/11 to Test Apps Safely (No VM Setup)

Set Up Windows Sandbox on Windows 10/11 to Test Apps Safely (No VM Setup)​

Prerequisites (What You Need)​

1. A supported Windows edition
   • Windows 10/11 Pro, Enterprise, or Education: Supported
   • Windows 10/11 Home: Not supported (Windows Sandbox feature isn’t available)
2. Windows version notes
   • Windows Sandbox is available on Windows 10 version 1903 and later, and on Windows 11 (supported editions).
   • To check your version: Settings → System → About (look for Windows specifications).
3. Hardware virtualization support enabled
   • Your CPU must support virtualization (Intel VT-x / AMD-V), and it should be enabled in BIOS/UEFI.
   • You don’t need to install Hyper-V manually, but Sandbox uses Windows’ virtualization platform.
4. Admin access
   • Enabling Windows features typically requires administrator privileges.

Note: Windows Sandbox is not meant to permanently store files. Anything inside Sandbox is deleted when you close it—by design.

Click to expand...

Step-by-Step: Enable Windows Sandbox​

1) Confirm Virtualization Is Enabled in Windows​

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Go to the Performance tab.
3. Click CPU.
4. Look for Virtualization: Enabled on the right side.

• If it says Enabled, continue.
• If it says Disabled, you’ll likely need to enable virtualization in BIOS/UEFI (see Troubleshooting).

2) Turn On the Windows Sandbox Feature​

1. Press Windows + R, type:
   optionalfeatures
   and press Enter.
2. In Windows Features, scroll down and check:
   • Windows Sandbox
3. Click OK.
4. Windows will apply changes—then prompt you to Restart. Restart your PC.

Tip: While you’re here, you may also see features like Hyper-V and Virtual Machine Platform. You typically don’t need to enable them manually just to use Sandbox; Windows will enable the required components automatically.

Click to expand...

Step-by-Step: Launch and Use Windows Sandbox​

3) Start Windows Sandbox​

1. Open the Start Menu.
2. Type Windows Sandbox.
3. Click Windows Sandbox to launch it.

Warning: Sandbox runs isolated, but don’t treat it as a license to ignore basic safety. Still avoid entering sensitive passwords into unknown apps and keep your host system secure.

Click to expand...

4) Copy an Installer (or File) into Sandbox​

1. On your main PC (host), locate the installer or file you want to test.
2. Right-click → Copy (or press Ctrl + C).
3. Click inside the Sandbox window.
4. Paste it (press Ctrl + V) onto the Sandbox desktop or into a folder.

Note: For security and simplicity, Windows Sandbox allows clipboard and basic integration by default. It’s convenient, but remember: if you download something malicious in Sandbox and run it, it can still try to access network resources while Sandbox is open. Isolation helps protect the host OS, but it doesn’t make malware “harmless.”

Click to expand...

5) Test the App Safely​

1. Double-click the installer or executable in Sandbox.
2. Use the software as needed to evaluate:
   • Does it install extra “bundled” programs?
   • Does it behave suspiciously?
   • Does it run and function as expected?
3. If you want to monitor changes, you can open tools like:
   • Task Manager
   • Event Viewer
   • Settings
   • Windows Security (limited usefulness for deep malware analysis, but fine for quick checks)

6) Save Anything You Want to Keep (Before Closing)​

1. In Sandbox, select the file → Copy (Ctrl + C).
2. Switch to your host desktop.
3. Paste it into a folder on your real PC.

Tip: Create a dedicated folder on your host, e.g. C:\Sandbox Transfers, so you always know what came from Sandbox and can scan it with Windows Security.

Click to expand...

7) Close Sandbox (Resets Everything)​

1. Click the X in the top-right corner of the Sandbox window.
2. Confirm you want to close it.

Optional (Intermediate): Use a Sandbox Configuration File (.wsb)​

8) Create a Basic .WSB File​

1. Open Notepad on your host PC.
2. Paste this example configuration:

<Configuration> <MappedFolders> <MappedFolder> <HostFolder>C:\Sandbox Transfers</HostFolder> <SandboxFolder>C:\Users\WDAGUtilityAccount\Desktop\Transfers</SandboxFolder> <ReadOnly>true</ReadOnly> </MappedFolder> </MappedFolders>
</Configuration>

1. Save the file as:
   Sandbox-Test.wsb
   (Make sure it’s not saved as .txt.
2. Double-click the .wsb file to launch Sandbox with that setup.

• Maps C:\Sandbox Transfers from your host into Sandbox.
• Sets it to ReadOnly, which is safer—Sandbox can read files, but can’t modify the host folder.

Warning: Be cautious with mapped folders, especially if ReadOnly is set to false. A malicious process in Sandbox could modify files in a writable mapped folder.

Click to expand...

Tips and Troubleshooting​

Sandbox option is missing from Windows Features​

• You’re likely on Windows Home, which doesn’t include Sandbox.
• Fix: Upgrade to Pro (or use alternative tools like a VM, or application sandboxing solutions).

“Virtualization is disabled” or Sandbox fails to start​

1. Reboot and enter BIOS/UEFI (common keys: Del, F2, F10, Esc).
2. Enable one of these (varies by vendor):
   • Intel Virtualization Technology (VT-x)
   • AMD-V / SVM Mode
3. Save changes and boot back into Windows.

Conflicts with other virtualization software​

• If your other VMs suddenly run slowly after enabling Sandbox, check whether they’re running under Hyper-V compatibility mode.
• Some setups require adjusting Windows features (Hyper-V / Virtual Machine Platform) or VM settings.

Performance tips​

• Close heavy apps on the host before launching Sandbox.
• Ensure you have enough RAM (8 GB+ recommended for a smooth experience).

Best practice for testing unknown installers​

• Prefer testing offline installers in Sandbox when possible.
• If you must download inside Sandbox, copy the URL into Sandbox and download there rather than downloading on the host first.

Conclusion​

• Windows Sandbox provides a disposable, isolated Windows session for testing apps.
• It’s available on Windows 10/11 Pro, Enterprise, and Education (not Home).
• Everything resets on close, making cleanup effortless.
• Optional .wsb files can streamline repeat testing and improve safety with read-only mapped folders.