Force Onlooker Detection Action
Verified with Windows 11 25H2 — updated on July 30, 2026
Supported on: At least Windows 11 Version 24H2
Path in the GPO console
Computer Configuration\Administrative Templates\Windows Components\Human Presence Description
Determines whether the Onlooker Detection action is forced by the MDM policy. The user will not be able to change this setting and the toggle in the UI will be greyed out.
Registry
HKLM
Software\Policies\Microsoft\HumanPresence Value name: ForceOnlookerDetectionAction
MDM / Intune (CSP)
./Device/Vendor/MSFT/Policy/Config/HumanPresence/ForceOnlookerDetectionAction Microsoft Learn documentation Mapping data: Microsoft Learn (CC BY 4.0)
CSP values
-
3- ForcedDimAndNotify. -
2- ForcedNotify. -
0 (Default)- DefaultToUserChoice.
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: Force Onlooker Detection Action
; State: Enabled
; Supported on: At least Windows 11 Version 24H2
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\HumanPresence]
"ForceOnlookerDetectionAction"=dword:00000001
"ForceOnlookerDetectionAction"=dword:00000000 More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Force Onlooker Detection Action
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
$path = 'HKLM:\Software\Policies\Microsoft\HumanPresence'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ForceOnlookerDetectionAction' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'ForceOnlookerDetectionAction' -Value 0 -Type DWord Intune XML
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/HumanPresence/ForceOnlookerDetectionAction
Data type: String
Value:
<enabled/>
<data id="ForceOnlookerDetectionActionDropdown" value="0"/> Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Force Onlooker Detection Action
# 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\HumanPresence' -Name 'ForceOnlookerDetectionAction' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\HumanPresence' -Name 'ForceOnlookerDetectionAction' -Expected 0 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Force Onlooker Detection Action
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
$path = 'HKLM:\Software\Policies\Microsoft\HumanPresence'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ForceOnlookerDetectionAction' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'ForceOnlookerDetectionAction' -Value 0 -Type DWord SCCM scripts
# Exported from gporais.com
# Policy: Force Onlooker Detection Action
# 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: Force Onlooker Detection Action
# 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\HumanPresence' -Name 'ForceOnlookerDetectionAction' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\HumanPresence' -Name 'ForceOnlookerDetectionAction' -Expected 0 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Force Onlooker Detection Action
# State: Enabled
# Supported on: At least Windows 11 Version 24H2
$path = 'HKLM:\Software\Policies\Microsoft\HumanPresence'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ForceOnlookerDetectionAction' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'ForceOnlookerDetectionAction' -Value 0 -Type DWord Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.