How to Configure Hardware Checksum Offload on Network Adapters in Windows 11 Using PowerShell

In modern high-throughput networking environments, computing and verifying checksums for every incoming and outgoing packet consumes substantial host CPU cycles. Every IPv4 packet contains a header checksum, while TCP and UDP packets across both IPv4 and IPv6 protocols contain data checksums designed to detect transmission corruption. When network adapters handle multi-gigabit connections, transferring checksum calculations from the operating system kernel to the physical network interface card (NIC) hardware engine significantly lowers CPU utilisation and minimises packet processing latency.

Windows 11 includes full native support for hardware checksum offloading, managed via the NetAdapter module in PowerShell. By querying and tuning hardware checksum offload settings directly through PowerShell, systems administrators and network engineers can verify that hardware acceleration is active, resolve packet drop issues caused by outdated firmware, and optimise networking performance on physical workstations and Hyper-V hosts.

Understanding Hardware Checksum Offloading

When hardware checksum offloading is disabled, the Windows TCP/IP networking stack (tcpip.sys) must calculate the checksum for every transmitted packet before handing it to the NIC driver. On the receiving end, the CPU must compute and verify the checksum of every incoming packet against the header value before passing the payload to user-space applications. At link speeds of 1 Gbps, 2.5 Gbps, 10 Gbps, or higher, this continuous computation creates measurable CPU overhead and increases cache thrashing.

When hardware checksum offload is enabled, the Windows networking stack sets specific transmit descriptors indicating that the hardware should calculate and insert the checksum on egress. Similarly, on packet ingress, the NIC hardware calculates the checksum as the frame streams into its internal buffer and passes a pass/fail flag to the operating system driver. Checksum offloading operates across several distinct protocol layers:

  • IPv4 Checksum Offload: Calculates the 16-bit one’s complement sum of the IPv4 packet header.
  • TCP Checksum Offload (IPv4 and IPv6): Computes checksums covering the pseudo-header, TCP header, and segment payload.
  • UDP Checksum Offload (IPv4 and IPv6): Computes checksums covering the pseudo-header, UDP header, and datagram payload.

Auditing Active Checksum Offload Capabilities

To audit the current hardware checksum configuration on Windows 11, open an elevated PowerShell console and query your network interfaces using Get-NetAdapterChecksumOffload:

# Inspect checksum offload settings for all network adapters
Get-NetAdapterChecksumOffload

To inspect a specific physical adapter with detailed properties, target the interface by name:

# Retrieve detailed checksum offload properties for Ethernet
Get-NetAdapterChecksumOffload -Name "Ethernet" | Format-List *

The output presents the current operational status for each supported offload category:

Name                   : Ethernet
InterfaceDescription  : Intel(R) Ethernet Connection I219-LM
IpIPv4                 : RxTxEnabled
TcpIPv4                : RxTxEnabled
TcpIPv6                : RxTxEnabled
UdpIPv4                : RxTxEnabled
UdpIPv6                : RxTxEnabled

Values indicate the active operational state: RxTxEnabled (active for both receiving and transmitting), RxEnabled (receive only), TxEnabled (transmit only), or Disabled.

Enabling Hardware Checksum Offload Across All Protocols

If an adapter has checksum offloading disabled or partially configured after a driver update, you can enable hardware offloading across all protocols using Set-NetAdapterChecksumOffload:

# Enable full hardware checksum offloading for IPv4 and IPv6
Set-NetAdapterChecksumOffload -Name "Ethernet" `
    -IpIPv4 Enabled `
    -TcpIPv4 Enabled `
    -TcpIPv6 Enabled `
    -UdpIPv4 Enabled `
    -UdpIPv6 Enabled

To suppress interactive confirmation prompts in automated scripts, append the -Confirm:$false parameter:

# Apply configuration non-interactively
Set-NetAdapterChecksumOffload -Name "Ethernet" -IpIPv4 Enabled -TcpIPv4 Enabled -TcpIPv6 Enabled -UdpIPv4 Enabled -UdpIPv6 Enabled -Confirm:$false

Configuring Asymmetric Offload for Troubleshooting

In certain enterprise scenarios—such as when diagnosing packet corruption introduced by faulty network switch ASICs, buggy NIC firmware, or virtual appliance bridges—you may need to configure asymmetric offloading (for example, enabling transmit offload while verifying receive checksums in the kernel) or disable specific protocols.

To configure transmit-only offload for TCP and UDP over IPv4:

# Enable transmit-only checksum offload
Set-NetAdapterChecksumOffload -Name "Ethernet" `
    -IpIPv4 TxEnabled `
    -TcpIPv4 TxEnabled `
    -UdpIPv4 TxEnabled

To selectively disable UDP checksum offload while keeping TCP and IPv4 offload active (useful when debugging multicast streaming or voice protocols):

# Disable UDP checksum offload while maintaining TCP offload
Set-NetAdapterChecksumOffload -Name "Ethernet" `
    -UdpIPv4 Disabled `
    -UdpIPv6 Disabled

Disabling Checksum Offload for Packet Capture and Forensics

When running network packet capture tools such as Wireshark, Microsoft Message Analyzer, or pktmon, hardware checksum offloading often causes captured outbound packets to appear corrupted with invalid checksums. This happens because the packet capture driver captures the frame before it reaches the physical NIC hardware where the checksum is actually calculated.

To temporarily disable all hardware checksum offloading for troubleshooting and packet inspection:

# Disable all checksum offloading on the target adapter
Set-NetAdapterChecksumOffload -Name "Ethernet" `
    -IpIPv4 Disabled `
    -TcpIPv4 Disabled `
    -TcpIPv6 Disabled `
    -UdpIPv4 Disabled `
    -UdpIPv6 Disabled

Once packet analysis is complete, restore full offload functionality using the configuration commands shown previously.

Auditing Advanced Driver Registry Properties

In addition to standard PowerShell cmdlets, network card vendors (such as Intel, Realtek, and Broadcom) expose proprietary advanced driver properties in the Windows Registry. You can inspect and verify these properties using Get-NetAdapterAdvancedProperty:

# Inspect vendor-specific checksum offload driver properties
Get-NetAdapterAdvancedProperty -Name "Ethernet" | Where-Object { $_.DisplayName -like "*Checksum*" }

The output displays the underlying driver registry keys and their active values:

Name      DisplayName                    DisplayValue    RegistryKeyword
----      -----------                    ------------    ---------------
Ethernet  IPv4 Checksum Offload          Rx & Tx Enabled *IPChecksumOffloadIPv4
Ethernet  TCP Checksum Offload (IPv4)    Rx & Tx Enabled *TCPChecksumOffloadIPv4
Ethernet  TCP Checksum Offload (IPv6)    Rx & Tx Enabled *TCPChecksumOffloadIPv6
Ethernet  UDP Checksum Offload (IPv4)    Rx & Tx Enabled *UDPChecksumOffloadIPv4
Ethernet  UDP Checksum Offload (IPv6)    Rx & Tx Enabled *UDPChecksumOffloadIPv6

If vendor utilities modify driver settings outside of standard Windows interfaces, Get-NetAdapterChecksumOffload and Get-NetAdapterAdvancedProperty provide complete visibility to ensure hardware network acceleration operates at maximum efficiency.

Get the best tech tips delivered straight to your inbox.

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