Enable built-in PDF reader powered by Adobe Acrobat for WebView2
Verified with Microsoft Edge 152.0.4191.53 — updated on July 10, 2026
Supported on: Microsoft Edge version 116, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge WebView2 User Configuration\Administrative Templates\Microsoft Edge WebView2 Description
This policy configures WebView2 applications to launch the new version of the PDF reader that's powered by Adobe Acrobat's PDF reader. The new PDF reader ensures that there's no loss of functionality and delivers an enhanced PDF experience. This experience includes richer rendering, improved performance, strong security for PDF file handling, and greater accessibility. If this policy is specified for an application, it is possible that it may impact other related applications as well. The policy is applied to all WebView2s sharing the same WebView2 user data folder. These WebView2s could potentially belong to multiple applications if those applications, which are likely from the same product family, are designed to share the same user data folder. Use a name-value pair to enable the new PDF reader for the application. Set the 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. Set the Value to true to enable the new reader or set it to false to use the existing one. If you enable this policy for the specified WebView2 applications, they will use the new Adobe Acrobat powered PDF reader to open all PDF files. If you disable the policy for the specified WebView2 applications or don't configure it, they will use the existing PDF reader to open all PDF files. Example value: {"name": "app1.exe", "value": true} {"name": "app_id_for_app2", "value": true} {"name": "*", "value": false}
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: Enable built-in PDF reader powered by Adobe Acrobat for WebView2
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 116, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\WebView2\NewPDFReaderWebView2List]
; List values: enter one value per line in the builder UI. More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Enable built-in PDF reader powered by Adobe Acrobat for WebView2
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 116, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2\NewPDFReaderWebView2List'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI. Intune 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: Enable built-in PDF reader powered by Adobe Acrobat for WebView2
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 116, 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
}
# HKLM:\Software\Policies\Microsoft\Edge\WebView2\NewPDFReaderWebView2List: List values: enter one value per line in the builder UI.
# No testable registry values are available for this state.
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Enable built-in PDF reader powered by Adobe Acrobat for WebView2
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 116, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2\NewPDFReaderWebView2List'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI. SCCM scripts
# Exported from gporais.com
# Policy: Enable built-in PDF reader powered by Adobe Acrobat for WebView2
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 116, 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: Enable built-in PDF reader powered by Adobe Acrobat for WebView2
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 116, 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
}
# HKLM:\Software\Policies\Microsoft\Edge\WebView2\NewPDFReaderWebView2List: List values: enter one value per line in the builder UI.
# No testable registry values are available for this state.
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Enable built-in PDF reader powered by Adobe Acrobat for WebView2
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 116, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\WebView2\NewPDFReaderWebView2List'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI. Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.