How to Configure Wi-Fi Preferred Band in Windows 11 Using PowerShell

Modern dual-band and tri-band wireless network interface cards (NICs) support multiple radio frequency bands, including 2.4 GHz, 5 GHz, and 6 GHz (Wi-Fi 6E/7). By default, wireless adapter drivers employ internal roaming algorithms to negotiate band selection based on Received Signal Strength Indication (RSSI) and channel utilisation. However, in enterprise environments or high-density deployments where 2.4 GHz saturation degrades throughput, system administrators often need to enforce or prioritise specific frequencies. In Windows 11, hardware driver properties can be audited and modified directly through the NetAdapter module in PowerShell.

Understanding Wi-Fi Driver Advanced Properties

Wireless driver parameters, including band steering preferences, are stored within driver-specific registry keys managed by the Network Driver Interface Specification (NDIS). In Windows 11, PowerShell provides access to these low-level adapter parameters through the Get-NetAdapterAdvancedProperty and Set-NetAdapterAdvancedProperty cmdlets. The exact property naming conventions depend on the hardware vendor (such as Intel, Realtek, Qualcomm, or MediaTek), but common property names include Preferred Band, Roaming Aggressiveness, and Wireless Mode.

When configured, the Preferred Band setting instructs the adapter firmware to prioritise connection handshakes on a preferred frequency whenever multiple Basic Service Set Identifiers (BSSIDs) broadcast the same Service Set Identifier (SSID) across different frequencies.

Auditing Wireless Adapter Capabilities in PowerShell

Before modifying driver configurations, you must identify the exact name of the active wireless network adapter and query its supported advanced property keywords. Launch PowerShell with elevated administrator privileges and retrieve the active Wi-Fi interface:

Get-NetAdapter -Physical | Where-Object { $_.MediaType -eq "Native 802.11" -or $_.InterfaceDescription -match "Wi-Fi|Wireless" } | Select-Object Name, InterfaceDescription, Status, LinkSpeed

Once you have identified the interface name (commonly Wi-Fi), query all exposed advanced properties to locate the property controlling band preference:

Get-NetAdapterAdvancedProperty -Name "Wi-Fi" | Where-Object { $_.DisplayName -match "Band" } | Select-Object DisplayName, DisplayValue, RegistryKeyword, RegistryValue, ValidDisplayValues

For Intel Wi-Fi adapters (such as the AX200, AX201, or AX210 series), the output will typically show:

• DisplayName: Preferred Band
• RegistryKeyword: RoamingPreferredBandType
• ValidDisplayValues: {1. No Preference, 2. Prefer 2.4GHz band, 3. Prefer 5GHz band} (or including 6GHz on newer drivers)

Configuring the Preferred Band via PowerShell

To prioritise higher-frequency spectrum with wider channel widths and lower interference, you can instruct the adapter to prefer the 5 GHz or 6 GHz bands. When setting advanced properties, use the exact string matching one of the values listed in ValidDisplayValues.

1. Prefer 5 GHz Band

To enforce a preference for 5 GHz connections over 2.4 GHz when both signals are detected:

Set-NetAdapterAdvancedProperty -Name "Wi-Fi" -DisplayName "Preferred Band" -DisplayValue "3. Prefer 5GHz band"

Executing this cmdlet triggers a brief NDIS driver re-initialisation, momentarily resetting the wireless connection while applying the new registry values.

2. Prefer 2.4 GHz Band

In environments where maximum physical range or wall penetration is necessary over raw bandwidth, you can revert the preference to 2.4 GHz:

Set-NetAdapterAdvancedProperty -Name "Wi-Fi" -DisplayName "Preferred Band" -DisplayValue "2. Prefer 2.4GHz band"

3. Clear Preference (Default Automatic Behaviour)

To allow the driver firmware to determine band roaming autonomously based on real-time signal calculations:

Set-NetAdapterAdvancedProperty -Name "Wi-Fi" -DisplayName "Preferred Band" -DisplayValue "1. No Preference"

Verifying the Active Frequency and Connection Details

After applying the configuration, confirm that the adapter has successfully negotiated the connection on the target frequency band using netsh:

netsh wlan show interfaces

Inspect the output fields to confirm operational parameters:

• Radio type: 802.11ax or 802.11ac
• Band: 5 GHz (or 6 GHz)
• Channel: Operating channel number (e.g., 36, 40, 149)
• Receive rate / Transmit rate (Mbps): Negotiated PHY data rate

Automating Band Preferences Across Enterprise Fleets

For fleet management via Microsoft Intune, SCCM, or Group Policy startup scripts, you can deploy a robust script that dynamically identifies any active Wi-Fi adapter regardless of hardware vendor and sets the preferred band without hardcoding interface names:

$wifiAdapter = Get-NetAdapter -Physical | Where-Object { $_.Status -eq "Up" -and ($_.MediaType -eq "Native 802.11" -or $_.InterfaceDescription -match "Wi-Fi|Wireless") } | Select-Object -First 1

if ($wifiAdapter) {
    $prop = Get-NetAdapterAdvancedProperty -Name $wifiAdapter.Name | Where-Object { $_.DisplayName -match "Preferred Band" }
    if ($prop) {
        $targetValue = $prop.ValidDisplayValues | Where-Object { $_ -match "5GHz|5 GHz" } | Select-Object -First 1
        if ($targetValue) {
            Set-NetAdapterAdvancedProperty -Name $wifiAdapter.Name -DisplayName $prop.DisplayName -DisplayValue $targetValue
            Write-Output "Successfully set $($wifiAdapter.Name) to $targetValue"
        }
    }
}

This automated approach ensures reliable migration to high-performance bands across heterogeneous hardware inventories while eliminating manual intervention in endpoint network profiles.