Make Print Screen key yieldable
Verified with Windows 11 25H2 — updated on September 15, 2026 Supported on: At least Windows 11 Version 24H2
Shipped in a Windows update: not in the official ADMX package (Administrative Templates (.admx) for Windows 11 Oct 2025 Update), present no later than KB5124008 (build 26200.9445).
Path in the GPO console
Computer Configuration\Administrative Templates\Windows Components\File Explorer Registry
Software\Policies\Microsoft\Windows\Explorer - Value name:
-
MakePrintScreenKeyYieldableREG_DWORD - Enabled:
1- Disabled:
0
Description
This policy setting determines whether the Print Screen key can be yielded to other applications. If you enable this policy setting, the print Screen key can be intercepted by applications, allowing them to override the default screenshot functionality. If you disable this policy setting, the print Screen key will retain its legacy behavior for taking screenshots and cannot be intercepted by applications. If this policy is not configured, the print Screen key can be intercepted by applications, allowing them to override the default screenshot functionality, same as the enabled behaviour. Note: This setting may require a system restart to take effect.
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. ⓘ
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Make Print Screen key yieldable
; State: Enabled
; Supported on: At least Windows 11 Version 24H2
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Explorer]
"MakePrintScreenKeyYieldable"=dword:00000001 More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Make Print Screen key yieldable
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
$path = 'HKLM:\Software\Policies\Microsoft\Windows\Explorer'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'MakePrintScreenKeyYieldable' -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: Make Print Screen key yieldable
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
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\Windows\Explorer' -Name 'MakePrintScreenKeyYieldable' -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: Make Print Screen key yieldable
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
$path = 'HKLM:\Software\Policies\Microsoft\Windows\Explorer'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'MakePrintScreenKeyYieldable' -Value 1 -Type DWord SCCM scripts
# Exported from gporais.com
# Policy: Make Print Screen key yieldable
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
# 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: Make Print Screen key yieldable
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
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\Windows\Explorer' -Name 'MakePrintScreenKeyYieldable' -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: Make Print Screen key yieldable
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
$path = 'HKLM:\Software\Policies\Microsoft\Windows\Explorer'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'MakePrintScreenKeyYieldable' -Value 1 -Type DWord Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.