How to Configure TCP ACK Frequency (TcpAckFrequency) in Windows 11 Using PowerShell

In standard TCP networking, RFC 1122 specifies a Delayed Acknowledgement (Delayed ACK) mechanism designed to minimize network congestion and packet overhead. Rather than sending a dedicated acknowledgement packet for every single incoming TCP segment, the operating system waits to bundle the ACK onto outgoing data or delays the response until a second packet arrives or an internal timer expires (typically up to 200 milliseconds). While this reduces packet flooding during bulk file downloads, it introduces artificial lag into interactive, low-latency applications—such as competitive online gaming, real-time financial trading platforms, and remote desktop protocols. In Windows 11, PowerShell allows administrators to tune the TcpAckFrequency parameter across specific network interfaces to enforce immediate packet acknowledgements.

Understanding TcpAckFrequency and Delayed ACKs

The TcpAckFrequency registry parameter specifies how many unacknowledged TCP packets the Windows TCP/IP stack will receive on a designated network interface before generating an immediate ACK packet:

  • TcpAckFrequency = 2 (Default): Windows waits until 2 full packets arrive before sending an ACK. If only one packet is received (common in turn-based gaming or tick-by-tick financial updates), Windows delays acknowledging it until the TCP delayed ACK timeout timer expires.
  • TcpAckFrequency = 1: Disables delayed ACKs completely on that interface. Every single incoming TCP packet triggers an immediate, zero-delay acknowledgement response back to the transmitting server.
  • TcpAckFrequency = 3+: Increases the threshold before ACKs are sent, suited only for highly constrained, high-congestion satellite links.

When paired with tuning the Initial Congestion Window (InitCwnd) and TCP keepalive parameters, configuring TcpAckFrequency = 1 eliminates 100 to 200 ms ping spikes caused by unacknowledged solitary packets.

Launching Elevated PowerShell in Windows 11

Modifying kernel TCP/IP network interface bindings requires administrative rights:

  1. Right-click the Start button on the taskbar or press Windows Key + X.
  2. Select Terminal (Admin) or PowerShell (Admin).
  3. Click Yes when prompted by the User Account Control (UAC) security prompt.

Identifying the Target Network Interface GUID

Unlike global TCP parameters that apply system-wide, TcpAckFrequency is configured per network adapter using its unique interface Globally Unique Identifier (GUID). To correlate your physical network adapter with its registry GUID, run:

Get-NetAdapter | Select-Object Name, InterfaceDescription, InterfaceGuid, Status

Locate your primary connection (such as Ethernet or Wi-Fi) and note its InterfaceGuid (for example, {3B2A1C0D-4E5F-6789-0123-456789ABCDEF}).

Configuring TcpAckFrequency with PowerShell

To set TcpAckFrequency to 1 on your primary active network interface automatically without manually copying GUIDs, execute the following script block:

$Adapter = Get-NetAdapter -Physical | Where-Object { $_.Status -eq "Up" } | Select-Object -First 1
$RegPath = "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\$($Adapter.InterfaceGuid)"

New-ItemProperty -Path $RegPath -Name "TcpAckFrequency" -Value 1 -PropertyType DWord -Force

PowerShell creates or updates the TcpAckFrequency DWORD value under the specific interface key, immediately instructing the Windows kernel to acknowledge every packet without delay.

Pairing with TCP No Delay (Nagling Suppression)

To achieve the lowest possible latency for interactive applications, delayed ACK suppression is frequently paired with disabling Nagle’s algorithm (which buffers outgoing small packets):

New-ItemProperty -Path $RegPath -Name "TCPNoDelay" -Value 1 -PropertyType DWord -Force

Setting both TcpAckFrequency = 1 and TCPNoDelay = 1 eliminates both sending and receiving buffering delays across the connection.

Verifying the Active Configuration and Monitoring Sockets

To verify that the custom values are correctly saved to the registry:

Get-ItemProperty -Path $RegPath | Select-Object TcpAckFrequency, TCPNoDelay

To confirm that connections are active and operating normally, audit socket health using PowerShell cmdlets like Get-NetTCPConnection.

While changes generally apply to newly established TCP sessions immediately, restarting the network adapter (or rebooting your Windows 11 PC) guarantees that all running network sockets reinitialize with immediate ACK frequency enabled.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.