How to Configure Receive Segment Coalescing on Network Adapters in Windows 11 Using PowerShell

Modern high-speed network interfaces operating at 10GbE, 25GbE, 40GbE, or higher bandwidths process millions of incoming network packets per second. When a network adapter receives high volumes of TCP datagrams, transferring each individual small segment into the operating system network stack triggers constant hardware interrupts and excessive CPU context switching, saturating processor cores with packet-processing overhead. To alleviate this bottleneck, modern network interface cards (NICs) support Receive Segment Coalescing (RSC). RSC hardware logic aggregates multiple contiguous TCP segments from the same connection into a single consolidated, larger segment before passing it up to the Windows TCP/IP stack. Using the NetAdapter PowerShell module, system administrators and performance engineers can inspect, enable, disable, and tune Receive Segment Coalescing across physical and virtual network adapters in Windows 11.

Understanding Receive Segment Coalescing Architecture

Receive Segment Coalescing operates as a hardware and kernel offload mechanism designed to minimize packet per-segment processing overhead. Key architectural aspects include:

• In-NIC Packet Consolidation: When contiguous TCP segments arrive, the NIC hardware merges their payloads into a single memory buffer and constructs a single updated TCP/IP header, updating sequence numbers and checksums.
• Interrupt and CPU Reduction: Instead of generating ten discrete hardware interrupts and memory allocations for ten 1500-byte packets, the NIC presents a single 15,000-byte coalesced segment, drastically reducing CPU cycles per byte transferred.
• IPv4 and IPv6 Support: Modern NIC drivers support discrete RSC offloading for both IPv4 and IPv6 protocols, which can be toggled independently.
• Virtual Receive Segment Coalescing (vRSC): In virtualized environments, Hyper-V virtual switches and virtual machine network adapters can coalesce segments inside the software vSwitch before delivering them to guest operating systems.
• Latency vs Throughput Trade-offs: While RSC maximizes bulk data transfer throughput for file transfers, database backups, and video ingestion, slight buffering delays can occasionally introduce latency jitter in highly time-sensitive financial trading or competitive online gaming workloads.

Inspecting Current RSC Capabilities and Configuration

Managing network adapter hardware offloads requires an elevated PowerShell session with local administrative privileges.

Open PowerShell as Administrator and inspect the current RSC configuration across all network interfaces:

Get-NetAdapterRsc

The command outputs a structured table detailing operational status:

Name                   IPv4OperationalState IPv4FailureReason IPv6OperationalState IPv6FailureReason
----                   -------------------- ----------------- -------------------- -----------------
Ethernet               True                 None              True                 None
vEthernet (Default)    False                NotSupported      False                NotSupported
Wi-Fi                  False                Disabled          False                Disabled

To inspect detailed adapter metrics, including whether hardware support is active:

Get-NetAdapterRsc -Name "Ethernet" | Format-List *

The IPv4FailureReason and IPv6FailureReason properties reveal whether inactive RSC states stem from driver limitations, administrator policy disables, or unsupported miniport features.

Enabling Receive Segment Coalescing Using Enable-NetAdapterRsc

If high-speed network adapters have RSC disabled or if performance testing requires re-enabling offloads, use the Enable-NetAdapterRsc cmdlet.

To enable RSC for both IPv4 and IPv6 on a specific network adapter:

Enable-NetAdapterRsc -Name "Ethernet"

To selectively enable RSC exclusively for IPv4 while leaving IPv6 disabled:

Enable-NetAdapterRsc -Name "Ethernet" -IPv4

To selectively enable RSC exclusively for IPv6 traffic:

Enable-NetAdapterRsc -Name "Ethernet" -IPv6

Verify that the operational state transitions to True:

Get-NetAdapterRsc -Name "Ethernet" | Select-Object Name, IPv4OperationalState, IPv6OperationalState

Disabling Receive Segment Coalescing for Low-Latency Workloads

In low-latency environments—such as audio streaming, competitive multiplayer gaming, or real-time telemetry streaming—disabling packet coalescing ensures that packets are delivered to user space immediately upon physical arrival without waiting for buffer aggregation.

To disable RSC globally on the target network interface:

Disable-NetAdapterRsc -Name "Ethernet"

To disable RSC only for IPv4 or IPv6:

Disable-NetAdapterRsc -Name "Ethernet" -IPv4
Disable-NetAdapterRsc -Name "Ethernet" -IPv6

Confirm that the operational state reports False:

Get-NetAdapterRsc -Name "Ethernet"

Auditing Packet Statistics and Offload Performance

To measure the tangible impact of RSC on incoming network streams, inspect driver offload statistics and TCP performance counters.

Query adapter-specific hardware statistics using Get-NetAdapterStatistics:

Get-NetAdapterStatistics -Name "Ethernet" | Format-List ReceivedBytes, ReceivedPackets, DiscardedPacketsReceived

In Windows Performance Monitor (perfmon.exe), add the TCPv4 and TCPv6 performance counters under Segments Received/sec and monitor total processor utilization under high network load:

Get-Counter "\TCPv4\Segments Received/sec", "\Processor(_Total)\% Processor Time" -Continuous -SampleInterval 2

With RSC enabled during sustained 10GbE throughput benchmarks, you will observe substantially lower CPU percentage usage for equivalent gigabit transfer volumes.

Troubleshooting RSC Driver Incompatibilities

When tuning Receive Segment Coalescing, evaluate these operational considerations:

1. VPN and Virtual Switch Interaction: When third-party VPN clients, packet inspection filters (such as Wireshark Npcap), or legacy virtual switches bind to a network adapter, Windows automatically disables hardware RSC to ensure raw packets can be inspected individually.
2. RSC in Hyper-V Virtual Machines: In guest virtual machines running Windows 11 under Hyper-V, vRSC must be supported by the host’s virtual switch. Ensure the host virtual switch has software RSC enabled:

   Get-VMSwitch | Select-Object Name, EnableSoftwareRsc

3. Driver Updates: If IPv4FailureReason reports DriverDisabled or InitializationFailed, verify that vendor device drivers (such as Intel PROSet or Mellanox WinOF-2) are updated to the latest certified WHQL versions.

By configuring Receive Segment Coalescing using Enable-NetAdapterRsc in PowerShell, Windows administrators optimize processor efficiency and eliminate packet-processing bottlenecks across modern enterprise network adapters.