How to Configure Network Adapter Packet Coalescing in Windows 11 Using PowerShell

In modern enterprise offices, homelabs, and dense campus local area networks (LANs), network switches and connected devices constantly broadcast background traffic. Common broadcast and multicast sources include Address Resolution Protocol (ARP) queries, IPv6 Neighbor Discovery (ND) solicitations, NetBIOS announcements, mDNS discovery packets, and SSDP UPnP beacons. On standard desktop and laptop network adapters, every received packet triggers a hardware interrupt, forcing the CPU to wake from low-power sleep states (C-states) to process the packet in memory.

When hundreds of random broadcast packets arrive every second, the host processor suffers constant context switching and interrupt processing overhead, resulting in elevated idle power draw, reduced battery endurance on mobile workstations, and increased latency jitter. To mitigate this, Windows 11 supports Packet Coalescing (including NDIS D0 Packet Coalescing). By configuring network adapters to buffer and batch non-critical broadcast and multicast packets inside the network interface card (NIC) hardware before generating a single batch interrupt, Windows allows CPU cores to remain in deep energy-saving states longer. This guide demonstrates how to audit, configure, and verify packet coalescing in Windows 11 using PowerShell.

Architecture of Hardware Packet Coalescing in NDIS

The Network Driver Interface Specification (NDIS 6.30 and later) in Windows coordinates hardware-assisted packet coalescing directly with compliant Ethernet and Wi-Fi network interface cards:

  • Hardware Filtering: The NIC hardware inspects incoming frame headers against operating system defined filter rules (targeting broadcast, multicast, or non-urgent unicast packets).
  • Coalescing Buffer: Packets matching the filter criteria are held in on-adapter hardware memory buffers rather than immediately firing an interrupt line.
  • Batch Interrupt Dispatch: The NIC holds packets until either the hardware coalescing buffer reaches a defined byte threshold or a programmable expiration timer (typically 10 to 30 milliseconds) elapses. Once triggered, the adapter issues a single consolidated hardware interrupt, allowing the OS networking stack to process all queued packets in one batch.
  • Urgent Traffic Bypass: Latency-sensitive unicast TCP/UDP traffic and time-critical packets bypass the coalescing buffer immediately, ensuring real-time gaming, VoIP, and database connections experience zero latency degradation.

Auditing Network Adapter Packet Coalescing Support via PowerShell

Packet coalescing is exposed as an advanced driver property on modern gigabit and multi-gigabit network adapters (such as Intel I225/I226, Realtek 2.5GbE/10GbE, and Marvell AQtion adapters).

Launch an elevated PowerShell console as Administrator and query the advanced properties of all active physical network adapters:

# Query advanced properties matching packet coalescing
Get-NetAdapterAdvancedProperty | Where-Object { 
    $_.DisplayName -like "*Coalescing*" -or $_.RegistryKeyword -like "*PacketCoalescing*" 
} | Select-Object InterfaceDescription, DisplayName, DisplayValue, RegistryKeyword

To inspect all advanced properties available on a specific network adapter (e.g. Ethernet):

Get-NetAdapterAdvancedProperty -Name "Ethernet" | Format-Table DisplayName, DisplayValue, RegistryValue -AutoSize

If the adapter driver supports hardware packet coalescing, the DisplayName column displays Packet Coalescing with an active value of Enabled or Disabled.

Enabling Packet Coalescing via PowerShell

To enable Packet Coalescing on your primary physical network interface, use the Set-NetAdapterAdvancedProperty cmdlet.

To enable the property on an adapter named “Ethernet”:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Packet Coalescing" -DisplayValue "Enabled"

If your vendor driver uses the direct registry keyword rather than the localized display name, you can set it via registry keyword:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -RegistryKeyword "*PacketCoalescing" -RegistryValue "1"

To apply packet coalescing across all physical wired and wireless network adapters simultaneously:

Get-NetAdapter -Physical | ForEach-Object {
    $Adapter = $_
    $Prop = Get-NetAdapterAdvancedProperty -Name $Adapter.Name | Where-Object { $_.DisplayName -like "*Packet Coalescing*" }
    if ($Prop) {
        Write-Host "Enabling Packet Coalescing on $($Adapter.Name)..."
        Set-NetAdapterAdvancedProperty -Name $Adapter.Name -DisplayName $Prop.DisplayName -DisplayValue "Enabled"
    }
}

Note: Modifying advanced driver properties briefly reinitializes the network adapter link (typically a 1 to 2-second link renegotiation).

Configuring D0 Packet Coalescing in the Windows Networking Stack

In addition to per-adapter hardware properties, Windows 11 manages D0 Packet Coalescing at the operating system networking stack layer. This feature enables Windows to instruct compatible NICs to coalesce random broadcast packets while the system is operating in the active working power state (D0).

To verify the global TCP/IP offload and coalescing settings in PowerShell:

Get-NetOffloadGlobalSetting | Select-Object ReceiveSegmentCoalescing, ReceiveSideScaling, NetworkDirect

To ensure system-wide packet coalescing and receive offloads are active:

Set-NetOffloadGlobalSetting -ReceiveSegmentCoalescing Enabled

Verifying Power Savings and Interrupt Reduction

After enabling Packet Coalescing, verify that the configuration successfully reduces CPU interrupt rates and allows deeper processor sleep states.

To monitor hardware interrupt rates per second using Windows Performance Counters:

Get-Counter "\Processor Information(_Total)\Interrupts/sec" -Continuous -SampleInterval 2

Compare the interrupt frequency on a noisy network before and after enabling Packet Coalescing. On enterprise subnets with frequent broadcast traffic, Packet Coalescing typically reduces idle interrupt rates by 40% to 70%.

To audit CPU C-state residency (confirming that CPU cores spend more time in low-power idle states such as C6 or C7):

Get-Counter "\Processor Information(_Total)\% C3 Time", "\Processor Information(_Total)\% C2 Time" -SampleInterval 2 -MaxSamples 5

Troubleshooting and Disabling for Latency-Critical Workloads

While Packet Coalescing is highly recommended for general desktop workloads, office environments, and laptops to maximize battery life, high-frequency financial trading or competitive LAN gaming rigs may prefer zero packet buffering.

To disable Packet Coalescing and revert the adapter to immediate per-packet interrupt generation:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Packet Coalescing" -DisplayValue "Disabled"

Verify that the setting reverted cleanly:

(Get-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Packet Coalescing").DisplayValue

Get the best tech tips delivered straight to your inbox.

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