Clean Out Notifications
Verified with Microsoft FSLogix — updated on July 10, 2026
Supported on: v2105 or later
Path in the GPO console
Computer Configuration\Administrative Templates\FS Logix\Profile Containers Description
NOTE: Once this policy is Enabled or Disabled, setting it back to Not Configured has NO EFFECT. This setting cleans out stale entries created by the Windows Push Notification Platform (WPN) and Windows Notification Facility (WFN) which under some conditions leads to slow sign-ins. Only enable this setting if directed by a Microsoft Support Engineer. Registry Entry: HKLM\SOFTWARE\FSLogix\Profiles\CleanOutNotifications Type: DWORD Values: 0 = Disabled, 1 = Enabled
Registry
HKLM
Software\FSLogix\Profiles 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: Clean Out Notifications
; State: Enabled
; Supported on: v2105 or later
[HKEY_LOCAL_MACHINE\Software\FSLogix\Profiles]
"CleanOutNotifications"=dword:00000000More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Clean Out Notifications
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\FSLogix\Profiles'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'CleanOutNotifications' -Value 0 -Type DWordIntune 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: Clean Out Notifications
# State: Enabled
# Supported on: v2105 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\FSLogix\Profiles' -Name 'CleanOutNotifications' -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: Clean Out Notifications
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\FSLogix\Profiles'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'CleanOutNotifications' -Value 0 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: Clean Out Notifications
# State: Enabled
# Supported on: v2105 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: Clean Out Notifications
# State: Enabled
# Supported on: v2105 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\FSLogix\Profiles' -Name 'CleanOutNotifications' -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: Clean Out Notifications
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\FSLogix\Profiles'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'CleanOutNotifications' -Value 0 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.