Understanding Interface Metrics
Windows uses an internal value called the interface metric to determine which network adapter handles traffic when multiple connections are active. The system automatically selects the path with the lowest metric value. By default, Ethernet typically has a lower metric than Wi-Fi because it offers higher bandwidth and stability. However, if you find that your device prefers Wi-Fi even when plugged in, you can manually correct this behavior.
The metric is not directly visible in the standard settings menu. You must access the advanced properties of the network adapter through the legacy Control Panel or PowerShell. Adjusting this number allows you to explicitly tell the operating system which connection to trust first. This is particularly useful for users who switch between desktop setups and laptop mobility frequently.
Method 1: Using Network Connections
This method provides a graphical way to change settings without using command-line tools. It is accessible to most users and does not require administrative scripts.
- Open Network Connections: Press
Win + R, typencpa.cpl, and press Enter. This opens the classic Network Connections window where all adapters are listed. - Access Properties: Right-click on your Ethernet adapter (usually labeled "Ethernet" or "Local Area Connection") and select Properties.
- Select Internet Protocol Version 4: In the list of items, find Internet Protocol Version 4 (TCP/IPv4). Click it once to highlight it, then click the Properties button at the bottom.
- Advanced Settings: In the IPv4 Properties window, click the Advanced... button located in the bottom right corner.
- Change Metric: Uncheck the box that says Automatic metric. In the text field below, enter a low number such as
10. Lower numbers indicate higher priority. Keep the Wi-Fi metric at its default (usually25or higher) to ensure Ethernet wins. - Confirm Changes: Click OK on the Advanced window, then OK again on the IPv4 Properties window, and close the adapter properties. Your changes take effect immediately.
If you need to reverse this process, simply return to these steps and re-check Automatic metric. Windows will then recalculate the optimal path based on current link speeds.
Method 2: Using PowerShell
For users who prefer automation or need to script this change across multiple machines, PowerShell offers a precise way to set metrics. This method is faster once you know the correct commands.
# List all network adapters and their current metrics
Get-NetAdapter | Select-Object Name, InterfaceDescription, Metric
# Set the metric for the Ethernet adapter to 10
Set-NetIPInterface -InterfaceAlias "Ethernet" -Metric 10
Replace "Ethernet" with the exact name shown in the first command if your adapter is named differently, such as "Ethernet 2" or "LAN". To verify the change, run the first command again. The output should show the updated metric value. This approach is also helpful if you want to automate the restoration of automatic metrics after a reboot.
Troubleshooting Connectivity Issues
After changing metrics, some users may experience temporary connectivity drops or conflicts with other network services. If you encounter issues, consider the following related fixes.
If your Wi-Fi fails to connect in the morning or intermittently, check for driver updates or power management settings that might be turning off the adapter. For more details on resolving wireless failures, see Windows 11 Laptop Failing to Connect to Wireless Network in the Morning.
Another common issue involves network resets occurring unexpectedly. If your adapter keeps resetting, you may need to disable the automatic reset feature in Windows. Learn how to prevent this here: Disable reset network adapter: Loss of connectivity in Windows 10/11.
Why Prioritize Ethernet?
Prioritizing Ethernet reduces jitter and packet loss, which is critical for online gaming and video conferencing. Wi-Fi signals are subject to interference from walls, other devices, and distance from the router. A wired connection provides a consistent pipe to your internet service provider. Even if Wi-Fi shows a higher speed in benchmarks, the stability of Ethernet often results in better real-world performance for latency-sensitive applications.
Additionally, some applications bind to specific interfaces. By ensuring Ethernet is the primary route, you avoid scenarios where a slow Wi-Fi connection throttles downloads while the Ethernet port sits idle. This optimization is especially relevant if you use VPNs or remote desktop tools that rely on stable TCP connections.
Frequently Asked Questions
Does changing the metric affect my internet speed?
No, changing the interface metric does not increase your maximum bandwidth. It only dictates which adapter Windows chooses to send data through first. Your actual speed is determined by your ISP plan and the hardware capabilities of the selected adapter.
How do I reset the metric to automatic?
To revert to automatic selection, go back to the Advanced settings in the IPv4 properties of your adapter. Simply check the box next to Automatic metric and click OK. Windows will then assign values based on the link speed of each connection.
Will this setting survive a Windows update?
In most cases, manual metric settings persist through minor updates and feature upgrades. However, major version upgrades or driver reinstallations may reset custom configurations. It is advisable to verify your settings after significant system changes.
Can I set different metrics for IPv6?
Yes, you can configure metrics separately for IPv6. Repeat the steps for IPv4 but select Internet Protocol Version 6 (TCP/IPv6) instead. Ensure both protocols have consistent priorities if you want predictable routing behavior for all traffic types.
What happens if both adapters have the same metric?
If two adapters share the same metric, Windows may load-balance traffic or choose one arbitrarily based on internal heuristics. This can lead to inconsistent performance. It is best practice to keep distinct metric values to ensure deterministic routing decisions.