How to Configure Jumbo Frames on Network Adapters in Windows 11 Using PowerShell

Standard Ethernet networks operate with a maximum transmission unit (MTU) of 1,500 bytes per frame. While standard frames are sufficient for general internet browsing and office productivity, high-throughput environments—such as Network Attached Storage (NAS) transfers, iSCSI storage area networks, Hyper-V virtualisation clusters, and 10 GbE / 25 GbE local backbones—experience substantial CPU overhead processing millions of small packets. Jumbo Frames allow Ethernet frames to carry payloads up to 9,000 or 9,014 bytes, drastically reducing packet counts, interrupt moderation frequency, and CPU packet inspection load. In Windows 11, hardware NIC driver properties can be audited and configured directly via PowerShell.

Understanding Jumbo Frames vs TCP/IP MTU

A common point of confusion is the distinction between the hardware driver setting and the operating system’s IP interface MTU:

• Physical Hardware Layer (Jumbo Packet): Governed by the Network Interface Card (NIC) driver, this setting instructs the physical transceiver and MAC controller to accept and transmit frames larger than 1,518 bytes (including Ethernet headers). Common values include 4088 Bytes, 9014 Bytes, or Disabled.
• TCP/IP Layer (IP Interface MTU): Configured via Set-NetIPInterface, this specifies the maximum IP packet size allowed over the interface. The IP MTU cannot safely exceed the hardware frame threshold without causing packet fragmentation or silent drops.

Network Prerequisite: Jumbo Frames must be enabled end-to-end across every hop on the local network path—including the Windows client, network switches, and target storage servers. If an intermediate switch does not support jumbo frames, packets will be dropped.

Auditing Jumbo Frame Support in PowerShell

Open an elevated PowerShell console as Administrator and identify your active physical network adapters:

Get-NetAdapter -Physical | Select-Object Name, InterfaceDescription, Status, LinkSpeed

Query the advanced driver properties of the target Ethernet adapter to inspect Jumbo Frame capability:

Get-NetAdapterAdvancedProperty -Name "Ethernet" | Where-Object { $_.DisplayName -match "Jumbo" -or $_.RegistryKeyword -match "Jumbo" } | Select-Object DisplayName, DisplayValue, RegistryKeyword, RegistryValue, ValidDisplayValues

For Intel, Realtek, or Marvell network controllers, the output typically indicates:

• DisplayName: Jumbo Packet (or Jumbo Frame)
• RegistryKeyword: *JumboPacket
• ValidDisplayValues: {Disabled, 4088 Bytes, 9014 Bytes} (or numeric packet sizes)

Configuring Jumbo Frames on Network Adapters

To enable Jumbo Frames, assign a supported frame size using the Set-NetAdapterAdvancedProperty cmdlet.

1. Enable 9,014-Byte Jumbo Frames (Recommended for 10GbE / NAS)

To enable the standard 9K frame size for high-speed local data transfers:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Jumbo Packet" -DisplayValue "9014 Bytes"

Note: Applying this setting will momentarily reset the network interface as the driver reloads the NDIS stack.

2. Enable 4,088-Byte Jumbo Frames

If intermediate network equipment or virtual switches only support moderate MTU expansion (4K frames):

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Jumbo Packet" -DisplayValue "4088 Bytes"

3. Disable Jumbo Frames (Revert to Standard 1500 MTU)

To revert to default 1,500-byte Ethernet framing:

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

Aligning the IP Interface MTU

Once the physical driver supports oversized frames, ensure the Windows TCP/IP interface MTU is updated to take advantage of the expanded payload size:

# Check current IP MTU
Get-NetIPInterface -InterfaceAlias "Ethernet" -AddressFamily IPv4 | Select-Object InterfaceAlias, NlMtu

# Set IPv4 MTU to 9000 bytes
Set-NetIPInterface -InterfaceAlias "Ethernet" -AddressFamily IPv4 -NlMtu 9000

# Set IPv6 MTU to 9000 bytes
Set-NetIPInterface -InterfaceAlias "Ethernet" -AddressFamily IPv6 -NlMtu 9000

Verifying End-to-End Jumbo Frame Delivery

To verify that oversized packets traverse the network without fragmentation, use ping.exe with the Don’t Fragment flag (-f) and a buffer size representing the IP payload (9000 – 28 bytes for IP and ICMP headers = 8972 bytes):

ping -f -l 8972 192.168.1.50

If jumbo frames are configured correctly on both ends and across all intermediate switches, the target will reply successfully. If you receive “Packet needs to be fragmented but DF set”, inspect switch port MTU settings along the network path.

By leveraging PowerShell to configure hardware Jumbo Frame parameters, systems administrators ensure optimal throughput and minimal CPU utilisation across demanding high-bandwidth Windows 11 workloads.