Anavem
EnglishFrancais
Anavem
Languagefr
administrative templatesComputer ConfigurationNot configured

Enable Windows Sandbox

Enables isolated sandbox environment for testing untrusted applications. Valuable for MSPs testing patches and software before deployment.

10 May 20264 min —
Policy path
Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Sandbox
Supported on
Windows 10, Windows 11, Windows Server 2016 and later

Enables isolated sandbox environment for testing untrusted applications. Valuable for MSPs testing patches and software before deployment. Security baselines recommend setting it to 2.

Description

Enable Windows Sandbox is a Windows Group Policy setting located under Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Sandbox. It applies to the Computer Configuration branch and is classified as a Informational-level policy in the Windows Sandbox & Application Guard category.

Enables isolated sandbox environment for testing untrusted applications. Valuable for MSPs testing patches and software before deployment.

Microsoft sets the default value to Not configured while industry security baselines (CIS, NIST, DISA STIG) recommend 2.

Under the hood, this policy is enforced through the Windows registry at HKLM\Software\Policies\Microsoft\Windows\Sandbox using the value name AllowWindowsSandbox. Modifying the value directly through regedit.exe or PowerShell produces the same effect as configuring the GPO, but going through Group Policy is preferred so that the setting is centrally managed and survives reboots, image rebuilds, and policy refresh cycles.

In-depth explanation

This is primarily an operational or user-experience setting. It does not directly raise or lower the security posture, but it standardizes behavior across the fleet, which is important for predictable support, training, and troubleshooting in an MSP-managed environment.

The policy is grouped under Windows Sandbox & Application Guard, which means it is typically applied through a domain-wide GPO linked at the OU level. In a multi-tenant MSP context, scope it through WMI filters or security group filtering rather than linking at the domain root, so that you can roll out progressively (pilot OU → wider rings → all production).

The setting takes effect after the next Group Policy refresh (gpupdate /force for immediate testing, or by default within ~90 minutes for workstations and ~5 minutes on domain controllers). For computer-side policies a reboot may be required; for user-side policies, a sign-off/sign-on cycle is enough.

Use cases

  • Apply organization-wide hardening of windows sandbox & application guard on all domain-joined Windows endpoints.
  • Roll out a CIS Benchmark-aligned baseline targeting 'Enable Windows Sandbox' via a dedicated GPO.
  • Reduce attack surface for accounts that handle privileged credentials or sensitive data.
  • Standardize the configuration across multiple customer tenants for an MSP-managed fleet.

Security implications

This control is primarily about consistency and supportability rather than security. The main risk of leaving it unconfigured is divergence between machines, which makes troubleshooting and standardized imaging harder, especially across multiple customer tenants in an MSP context.

How to configure

  1. Open Group Policy Management Console (gpmc.msc) on a domain controller or a workstation with RSAT installed.
  2. Create or edit a GPO linked to the OU containing the target computer configurations. We recommend a dedicated baseline GPO (e.g. SEC – Windows Sandbox & Application Guard) instead of editing Default Domain Policy.
  3. Navigate to Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Sandbox.
  4. Open Enable Windows Sandbox and set it to 2.
  5. Click OK and close the editor.
  6. On the target endpoint, run gpupdate /force (or wait for the next refresh cycle), then verify with rsop.msc or gpresult /h report.html.

Direct registry path: HKLM\Software\Policies\Microsoft\Windows\Sandbox\AllowWindowsSandbox. You can apply the same change with PowerShell:

New-Item -Path 'HKLM\Software\Policies\Microsoft\Windows\Sandbox' -Force | Out-Null
Set-ItemProperty -Path 'HKLM\Software\Policies\Microsoft\Windows\Sandbox' -Name 'AllowWindowsSandbox' -Value <value> -Type DWord

Registry mapping

Registry pathHKLM\Software\Policies\Microsoft\Windows\Sandbox
Value nameAllowWindowsSandbox
Value typeREG_DWORD
Enabled value2
Disabled valueNot configured

Frequently asked questions

What does the Enable Windows Sandbox Group Policy do?
Enables isolated sandbox environment for testing untrusted applications. Valuable for MSPs testing patches and software before deployment.
Where do I find this setting in the GPO editor?
Open <code>gpmc.msc</code>, then navigate to <code>Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Sandbox</code> and look for <strong>Enable Windows Sandbox</strong>.
What is the Microsoft default value?
<code>Not configured</code> on a fresh Windows install. Domain-joined machines may inherit a different value if a baseline GPO is already in place.
What value do security baselines recommend?
<code>2</code> – aligned with CIS, NIST, and DISA STIG guidance for current Windows versions.
Can I configure this without a GPO?
Yes, by writing to <code>HKLM\Software\Policies\Microsoft\Windows\Sandbox\AllowWindowsSandbox</code> directly via <code>regedit</code>, PowerShell, or Intune. A GPO is preferred for centrally managed environments because it survives reimaging and is easier to audit.