How to Audit and Inspect Network Adapter Statistics in Windows 11 Using PowerShell

In enterprise Windows workstation and server management, diagnosing network bottlenecks, packet loss, and physical cable degradation requires comprehensive visibility into network interface performance. When users experience slow file transfers, frequent VPN drops, or video conferencing jitter, network administrators often inspect top-level interface status indicators in Windows Settings. However, simple “Connected” status flags fail to reveal low-level driver anomalies such as discarded frames, buffer overflows, cyclic redundancy check (CRC) errors, or multicast broadcast storms.

Windows 11 includes the Get-NetAdapterStatistics PowerShell cmdlet within the native NetAdapter module. This tool interfaces directly with the Network Driver Interface Specification (NDIS) layer, exposing real-time hardware counters for transmitted and received bytes, packet discards, and low-level driver error tallies. System administrators and network engineers can track interface health, monitor bandwidth consumption, and detect hardware degradation programmatically. This guide shows how to audit and inspect network adapter traffic statistics in Windows 11 using PowerShell.

Querying Basic Interface Statistics

The Get-NetAdapterStatistics cmdlet queries active NDIS hardware and miniport driver statistics across all physical and virtual network adapters.

Listing Statistics Across All Adapters

  1. Right-click the Start button on Windows 11 and select Terminal (Admin) or PowerShell (Admin).
  2. Run the following command:
Get-NetAdapterStatistics

Windows outputs a summary table listing key throughput and discard counters:

Name           ReceivedBytes ReceivedUnicastPackets OutboundBytes OutboundUnicastPackets
----           ------------- ---------------------- ------------- ----------------------
Ethernet          4512098412                3841029    1240985120                1920512
Wi-Fi              120459102                  98410      45120981                  38120
vEthernet (WSL)    891240192                 781204     341098210                 312045

Filtering by Specific Network Adapter

To inspect a single network interface (such as your primary physical Ethernet adapter), pass the interface name to the -Name parameter:

Get-NetAdapterStatistics -Name "Ethernet"

Auditing Packet Discards and Hardware Errors

While byte counters indicate total data throughput, discard and error counters are critical for diagnosing faulty network cables, overloaded switch ports, or misconfigured MTU frame sizes.

Inspecting Complete Error and Discard Properties

Retrieve all diagnostic error properties using Select-Object *:

Get-NetAdapterStatistics -Name "Ethernet" | Select-Object Name, ReceivedBytes, OutboundBytes, ReceivedDiscardedPackets, OutboundDiscardedPackets, ReceivedPacketErrors, OutboundPacketErrors | Format-List

Interpreting Diagnostic Error Counters

  • ReceivedDiscardedPackets: Packets successfully received by the physical network adapter hardware but dropped before delivery to upper-layer protocol drivers. High counts typically point to host buffer exhaustion, excessive interrupt moderation delays, or severe system CPU throttling.
  • OutboundDiscardedPackets: Packets passed to the network adapter driver for transmission that were discarded due to local interface queue congestion or lack of transmission ring buffers.
  • ReceivedPacketErrors: Inbound frames that arrived damaged or corrupted. Consistent increments indicate physical Layer 1 issues—such as damaged Ethernet patch cables, electromagnetic interference, or faulty switch transceivers.
  • OutboundPacketErrors: Outbound transmission failures generated by hardware faults or driver initialization timeouts.

Monitoring Real-Time Bandwidth and Transfer Speeds

Because Get-NetAdapterStatistics reports cumulative counters since the adapter last initialised, calculating current bandwidth consumption requires sampling byte counters over a fixed time interval.

Real-Time Throughput Monitor Script

Execute the following PowerShell snippet to measure real-time download and upload speeds in megabits per second ($\text{Mbps}$):

$AdapterName = "Ethernet"

while ($true) {
    $stat1 = Get-NetAdapterStatistics -Name $AdapterName
    Start-Sleep -Seconds 1
    $stat2 = Get-NetAdapterStatistics -Name $AdapterName

    $rxMbps = [math]::Round((($stat2.ReceivedBytes - $stat1.ReceivedBytes) * 8) / 1MB, 2)
    $txMbps = [math]::Round((($stat2.OutboundBytes - $stat1.OutboundBytes) * 8) / 1MB, 2)

    Clear-Host
    Write-Host "Real-Time Throughput for [$AdapterName]:" -ForegroundColor Cyan
    Write-Host "  Download: $rxMbps Mbps" -ForegroundColor Green
    Write-Host "  Upload:   $txMbps Mbps" -ForegroundColor Yellow
}

Press Ctrl+C to terminate the monitoring loop.

Auditing Broadcast and Multicast Traffic Proportions

Excessive non-unicast broadcast packets consume host CPU resources due to constant network interrupt processing. Audit the proportion of broadcast vs unicast traffic across your network adapters:

Get-NetAdapterStatistics | Select-Object Name, ReceivedUnicastPackets, ReceivedMulticastPackets, ReceivedBroadcastPackets | Format-Table -AutoSize

If ReceivedBroadcastPackets approaches or exceeds ReceivedUnicastPackets, your local subnet is experiencing heavy broadcast traffic or network loops.

Resetting Interface Counters and Troubleshooting

  • Resetting Counters: Cumulative NDIS counters maintained by Get-NetAdapterStatistics cannot be cleared arbitrarily without resetting the network adapter session. To reset counters to zero for clean baseline performance testing, restart the interface:
Restart-NetAdapter -Name "Ethernet"
  • Elevated Permissions: While querying basic statistics is accessible in non-elevated sessions, resetting adapters or correlating statistics with low-level packet trace sessions requires an elevated PowerShell console.
  • Virtual Switch Telemetry: In Hyper-V and WSL2 virtualized configurations, virtual adapters report statistics independent of physical host hardware. Inspect both physical NICs and virtual endpoints to isolate virtual switch routing overhead.

Get the best tech tips delivered straight to your inbox.

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