NTFS parallel flush threshold
Verified with Windows 11 25H2 — updated on July 10, 2026
Supported on: At least Windows Server 2016, Windows 10
Path in the GPO console
Computer Configuration\Administrative Templates\System\File System\NTFS Description
When flushing modified file data from memory, NTFS chooses to use one or more threads based on how many files are currently open. This setting gives control over the open file threshold used to trigger parallel flush.
Registry
HKLM
System\CurrentControlSet\Policies 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: NTFS parallel flush threshold
; State: Enabled
; Supported on: At least Windows Server 2016, Windows 10
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Policies]
"NtfsParallelFlushThreshold"=dword:000003e8More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: NTFS parallel flush threshold
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
$path = 'HKLM:\System\CurrentControlSet\Policies'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NtfsParallelFlushThreshold' -Value 1000 -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: NTFS parallel flush threshold
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
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:\System\CurrentControlSet\Policies' -Name 'NtfsParallelFlushThreshold' -Expected 1000 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: NTFS parallel flush threshold
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
$path = 'HKLM:\System\CurrentControlSet\Policies'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NtfsParallelFlushThreshold' -Value 1000 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: NTFS parallel flush threshold
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
# 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: NTFS parallel flush threshold
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
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:\System\CurrentControlSet\Policies' -Name 'NtfsParallelFlushThreshold' -Expected 1000 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: NTFS parallel flush threshold
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
$path = 'HKLM:\System\CurrentControlSet\Policies'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'NtfsParallelFlushThreshold' -Value 1000 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.