Configure the WebView2 release channels
Explanation
This policy configures the release channel options for WebView2 applications. To configure these options, set the value to a comma-separated string of integers, which map to the `COREWEBVIEW2_RELEASE_CHANNELS` values from the corresponding WebView2 API. These values are: WebView2 Runtime (0), Beta (1), Dev (2), and Canary (3). By default, environment creation searches for channels from most to least stable, using the first channel found on the device. When `ReleaseChannels` is provided, environment creation will only search for the channels specified in the set. For example, the values "0,2" and "2,0" indicate that environment creation should only search for Dev channel and the WebView2 Runtime, using the order indicated by `ChannelSearchKind`. Environment creation attempts to interpret each integer and treats any invalid entry as the Stable channel. Set `ChannelSearchKind` to reverse the search order so environment creation searches for least stable build first. If both `BrowserExecutableFolder` and `ReleaseChannels` are provided, the `BrowserExecutableFolder` takes precedence, regardless of whether the channel of `BrowserExecutableFolder` is included in the `ReleaseChannels`.
To set the value for release channels, provide a Value name and Value pair. Set the value name to the Application User Model ID or the executable file name. You can use the "*" wildcard as value name to apply to all applications.
Example value:
Name: WebView2APISample.exe, Value: 0,1,2
Registry
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\WebView2HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge\WebView2- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Computer (HKLM)
Enable
# Enable: msedgewebview2/ReleaseChannels
$k = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2\ReleaseChannels'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Set value name to the Application User Model ID or the executable file name. You can use the "*" wildcard as value name to apply to all applications.
# Non-additive list: existing values of the key are cleared first
if (Test-Path -Path $k) { (Get-Item -Path $k).Property | ForEach-Object { Remove-ItemProperty -Path $k -Name ([WildcardPattern]::Escape($_)) -ErrorAction SilentlyContinue } }
$items = @{
'<name1>' = '<value1>'
'<name2>' = '<value2>'
} # Replace the values with your own
$items.GetEnumerator() | ForEach-Object { Set-ItemProperty -Path $k -Name $_.Key -Value $_.Value -Type String }Disable
# Disable: msedgewebview2/ReleaseChannels
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": msedgewebview2/ReleaseChannels
$k = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2\ReleaseChannels'
Remove-Item -Path $k -Recurse -Force -ErrorAction SilentlyContinueUser (HKCU)
Enable
Disable
Revert to "Not configured"
Options (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Set value name to the Application User Model ID or the executable file name. You can use the "*" wildcard as value name to apply to all applications.ReleaseChannelsDesc | List (table)list | Software\Policies\Microsoft\Edge\WebView2\ReleaseChannelsName = value pairs | REG_SZ (values under the key) |
Application
Microsoft Edge (+ Edge Update, WebView2) (Microsoft) — November 2026 templates
Official templates downloaded on November 12, 2026.