How to Configure Network Adapter Speed and Duplex in Windows 11 Using PowerShell

In enterprise local area networks and high-performance server environments, physical Ethernet interfaces rely on IEEE auto-negotiation protocols to establish optimal link speed and duplex modes with upstream switch ports. In ideal configurations, modern network adapters automatically negotiate to the maximum supported speed—such as 1.0 Gbps Full Duplex, 2.5 Gbps, 5 Gbps, or 10 Gbps Full Duplex. However, cabling defects, faulty switch port firmware, energy-saving power transitions, or aggressive green Ethernet algorithms can trigger negotiation failures. These failures often cause the network interface to silently fall back to 100 Mbps or 10 Mbps Half-Duplex, leading to severe packet collisions, high latency, and dramatic bandwidth degradation. Using the NetAdapter PowerShell module, system administrators can inspect current link negotiation states, audit supported driver capabilities, and configure the Speed & Duplex advanced property in Windows 11.

Understanding Ethernet Auto-Negotiation and Duplex Modes

Ethernet physical link negotiation establishes physical layer signaling parameters between the network interface card (NIC) and the physical switch port. Key technical principles include:

  • Auto-Negotiation Protocol: Defined in IEEE 802.3u and 802.3ab standards, auto-negotiation uses Fast Link Pulses (FLP) to advertise capabilities and select the highest common denominator for transmission speed and duplexity.
  • Duplex Mismatch Hazards: A duplex mismatch occurs when one end of the physical link is forced to Full Duplex while the partner remains set to Auto-Negotiation. The auto-negotiating end fails to detect duplexity and defaults to Half-Duplex. While the link shows physical connectivity, bidirectional transmission causes massive late collisions, frame check sequence (FCS) errors, and severe packet loss.
  • Gigabit and 10GbE Specifications: The IEEE 802.3ab standard strictly requires auto-negotiation for 1000BASE-T (Gigabit Ethernet) operation to exchange clock synchronization parameters (Master/Slave clock resolution). Forcing 1.0 Gbps without negotiation can prevent link establishment on enterprise switches.
  • Hardware Property Abstraction: In Windows, link speed and duplex settings reside within the network adapter’s registry-backed advanced driver properties, queried and modified through the standardized *SpeedDuplex registry keyword.

Inspecting Active Link Speed and Duplex Status

Managing network adapter driver parameters requires an elevated administrative PowerShell prompt.

Open PowerShell as Administrator and inspect the current operational link speed across all network adapters:

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

The LinkSpeed property reveals active physical throughput (e.g. 1 Gbps, 100 Mbps, or 10 Gbps). If a Gigabit adapter connected to a Gigabit switch displays 100 Mbps, negotiation degradation has occurred.

To inspect the specific driver configuration value assigned to the Speed & Duplex advanced property:

Get-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex"

Review the output fields:

Name                      DisplayName                    DisplayValue                   RegistryKeyword RegistryValue
----                      -----------                    ------------                   --------------- -------------
Ethernet                  Speed & Duplex                 Auto Negotiation               *SpeedDuplex    {0}

Auditing Supported Speed & Duplex Options

Different network adapter hardware and vendor drivers support different link options. Query the valid display values supported by your specific hardware:

(Get-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex").ValidDisplayValues

A typical high-performance Intel or Realtek network adapter reports an array of supported options:

Auto Negotiation
10 Mbps Half Duplex
10 Mbps Full Duplex
100 Mbps Half Duplex
100 Mbps Full Duplex
1.0 Gbps Full Duplex
2.5 Gbps Full Duplex
10 Gbps Full Duplex

Always verify the exact string syntax reported by ValidDisplayValues before modifying configuration properties to avoid syntax rejection errors.

Configuring Speed & Duplex Using Set-NetAdapterAdvancedProperty

Use the Set-NetAdapterAdvancedProperty cmdlet to modify physical link parameters. Applying changes resets the network interface momentarily, causing brief network disconnection lasting 2 to 5 seconds.

To force an adapter to operate strictly at 1.0 Gbps Full Duplex (for example, to prevent intermittent downshifts to 100 Mbps on aging patch cables):

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex" -DisplayValue "1.0 Gbps Full Duplex"

To force high-speed 10 Gbps operation on a server storage adapter:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex" -DisplayValue "10 Gbps Full Duplex"

Confirm that the driver committed the updated setting:

Get-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex" | Select-Object DisplayName, DisplayValue, RegistryValue

Verify that the physical link re-established successfully at the intended throughput:

Start-Sleep -Seconds 3
Get-NetAdapter -Name "Ethernet" | Select-Object Name, Status, LinkSpeed

Restoring Auto-Negotiation Default Settings

In the vast majority of enterprise infrastructures, best practice requires maintaining Auto-Negotiation on both the host and the switch port. If testing is complete or if forced settings fail to establish link connectivity, restore the standard default.

Re-enable Auto Negotiation:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex" -DisplayValue "Auto Negotiation"

Alternatively, reset all advanced properties of the network adapter to factory driver defaults using Reset-NetAdapterAdvancedProperty:

Reset-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Speed & Duplex"

Troubleshooting Link Negotiation and Cable Faults

When physical interfaces fail to negotiate full link speed despite setting Auto Negotiation, investigate these common physical layer issues:

  1. Cable Pinout and Continuity Damage: Fast Ethernet (100BASE-TX) requires only two wire pairs (pins 1, 2, 3, and 6), whereas Gigabit Ethernet (1000BASE-T) strictly requires all four pairs (all 8 pins). If a Cat5e or Cat6 cable suffers a broken strand on pins 4, 5, 7, or 8, the adapter will seamlessly downshift to 100 Mbps without warning. Replace the patch cable or test with a physical cable tester.
  2. Switch Port Configuration Mismatches: If the managed switch port is hardcoded to speed 1000 and duplex full while the client is on auto-negotiation, verify whether IEEE clock synchronization fails. Both the switch port and the Windows host must share identical negotiation policies.
  3. Energy Efficient Ethernet (EEE) Interference: Certain green switches reduce link speed during periods of low activity. If link downshifting occurs intermittently during idle periods, inspect and disable Energy Efficient Ethernet on the network adapter:
    Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "Energy Efficient Ethernet" -DisplayValue "Disabled"

By auditing and configuring Speed & Duplex with PowerShell, system administrators resolve physical link bottlenecks, eliminate duplex mismatches, and maintain peak network throughput on Windows 11 workstations and servers.

Get the best tech tips delivered straight to your inbox.

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