Microsoft Edge built-in PDF reader powered by Adobe Acrobat enabled (deprecated)
Verified with Microsoft Edge 157.0.4341.60 — updated on October 22, 2026 Supported on: Microsoft Edge version 111, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge - Default Settings (users can override) User Configuration\Administrative Templates\Microsoft Edge - Default Settings (users can override) Registry
Software\Policies\Microsoft\Edge\Recommended Software\Policies\Microsoft\Edge\Recommended - Value name:
-
NewPDFReaderEnabledREG_DWORD - Enabled:
1- Disabled:
0
Description
DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release. Starting in Microsoft Edge version 156, this policy is deprecated as the built-in PDF reader experience has transitioned to the newer version. The policy will remain supported for a minimum of 6 major releases and is planned to become obsolete starting in Microsoft Edge version 162. Once obsolete, organizations will no longer be able to use this policy to opt out of the new PDF reader. Your organization should remove this policy before it becomes obsolete. The policy lets Microsoft Edge launch the new version of the built-in PDF reader that's powered by Adobe Acrobat's PDF rendering engine. 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 handling, and greater accessibility. If you enable this policy, Microsoft Edge will use the new Adobe Acrobat powered built-in PDF reader to open all PDF files. If you disable or don't configure this policy, Microsoft Edge will use the existing PDF reader to open all PDF files.
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: Microsoft Edge built-in PDF reader powered by Adobe Acrobat enabled (deprecated)
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 111, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\Recommended]
"NewPDFReaderEnabled"=dword:00000001 More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Microsoft Edge built-in PDF reader powered by Adobe Acrobat enabled (deprecated)
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 111, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\Recommended'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NewPDFReaderEnabled' -Value 1 -Type DWord 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: Microsoft Edge built-in PDF reader powered by Adobe Acrobat enabled (deprecated)
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 111, 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\Recommended' -Name 'NewPDFReaderEnabled' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Microsoft Edge built-in PDF reader powered by Adobe Acrobat enabled (deprecated)
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 111, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\Recommended'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NewPDFReaderEnabled' -Value 1 -Type DWord SCCM scripts
# Exported from gporais.com
# Policy: Microsoft Edge built-in PDF reader powered by Adobe Acrobat enabled (deprecated)
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 111, 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: Microsoft Edge built-in PDF reader powered by Adobe Acrobat enabled (deprecated)
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 111, 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\Recommended' -Name 'NewPDFReaderEnabled' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Microsoft Edge built-in PDF reader powered by Adobe Acrobat enabled (deprecated)
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 111, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\Recommended'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NewPDFReaderEnabled' -Value 1 -Type DWord Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.