Control communication with the Experimentation and Configuration Service
Verified with Microsoft Edge 152.0.4191.53 — updated on July 10, 2026
Supported on: Microsoft Edge version 97, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge WebView2 User Configuration\Administrative Templates\Microsoft Edge WebView2 Description
The Experimentation and Configuration Service is used to deploy Experimentation and Configuration payloads to the client. Experimentation payload consists of a list of early-in-development features that Microsoft is enabling for testing and feedback. Configuration payload consists of a list of recommended settings that Microsoft wants to deploy to optimize the user experience. Configuration payload may also contain a list of actions to take on certain domains for compatibility reasons. For example, the browser may override the User Agent string on a website if that website is broken. Each of these actions is intended to be temporary while Microsoft tries to resolve the issue with the site owner. If you set this policy to 'FullMode', the full payload is downloaded from the Experimentation and Configuration Service. This includes both the experimentation and configuration payloads. If you set this policy to 'ConfigurationsOnlyMode', only the configuration payload is downloaded. If you set this policy to 'RestrictedMode', the communication with the Experimentation and Configuration Service is stopped completely. Microsoft doesn't recommend this setting. If you don't configure this policy on a managed device, the behavior on Beta and Stable channels is the same as the 'ConfigurationsOnlyMode'. On Canary and Dev channels, the behavior is the same as 'FullMode'. If you don't configure this policy on an unmanaged device, the behavior is the same as the 'FullMode'. Policy options mapping: * FullMode (2) = Retrieve configurations and experiments * ConfigurationsOnlyMode (1) = Retrieve configurations only * RestrictedMode (0) = Disable communication with the Experimentation and Configuration Service Use the preceding information when configuring this policy.
Registry
Software\Policies\Microsoft\Edge\WebView2 Software\Policies\Microsoft\Edge\WebView2 Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
Applying both scopes creates an ambiguous configuration (computer takes precedence over user). Only do this intentionally.
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Control communication with the Experimentation and Configuration Service
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 97, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\WebView2]
"ExperimentationAndConfigurationServiceControl"=dword:00000002More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Control communication with the Experimentation and Configuration Service
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 97, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ExperimentationAndConfigurationServiceControl' -Value 2 -Type DWordIntune XML
No direct Policy CSP / OMA-URI mapping for this policy. Use the Intune Remediation tab, or ingest the ADMX in Intune.Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Control communication with the Experimentation and Configuration Service
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 97, Windows 7 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Edge\WebView2' -Name 'ExperimentationAndConfigurationServiceControl' -Expected 2 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Control communication with the Experimentation and Configuration Service
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 97, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ExperimentationAndConfigurationServiceControl' -Value 2 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: Control communication with the Experimentation and Configuration Service
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 97, Windows 7 or later
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: Control communication with the Experimentation and Configuration Service
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 97, Windows 7 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Edge\WebView2' -Name 'ExperimentationAndConfigurationServiceControl' -Expected 2 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Control communication with the Experimentation and Configuration Service
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 97, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ExperimentationAndConfigurationServiceControl' -Value 2 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.