Understanding Network Metrics
Windows uses a routing table to determine how data packets are sent across different networks. Each network interface card (NIC), whether it is built into the motherboard or plugged in via USB, is assigned a "metric." This is essentially a cost associated with using that path. The lower the number, the more preferred the route is. When both adapters are active and connected to the same SSID, Windows will almost always choose the internal Wi-Fi because its default metric is typically much lower than that of a generic USB dongle.
This automatic selection happens regardless of physical quality. A high-gain antenna USB adapter might offer superior signal strength and throughput, but if its metric is higher than the internal chip's, Windows will ignore the better hardware in favor of the default setting. To solve this, we need to intervene in the network configuration settings to flip this preference.
Method 1: Adjusting Interface Metric via Settings
The most reliable way to change this behavior is through the advanced properties of the network adapter itself. You do not need third-party software for this; Windows provides the necessary tools in the Control Panel.
- Press
Win + Rto open the Run dialog. - Type
ncpa.cpland press Enter. This opens the Network Connections window directly. - Locate your Internal Wi-Fi Adapter. Right-click it and select Properties.
- In the list of items, find Internet Protocol Version 4 (TCP/IPv4). Select it and click Properties again.
- Click the Advanced button at the bottom right.
- Uncheck the box labeled Automatic metric.
- Enter a value of 50 in the "Interface metric" field. Click OK on all open windows to save.
Now, repeat these steps for your External USB Wi-Fi Adapter. When you reach the Advanced TCP/IP settings, ensure Automatic metric is unchecked and set the value to 10. Because 10 is lower than 50, Windows will now prefer the external adapter for all internet-bound traffic while keeping the internal one available as a fallback.
If you want to ensure total separation, you can also disable the internal adapter entirely in the Device Manager, but adjusting metrics allows both to remain active for troubleshooting purposes. For users who frequently swap between internal and external hardware, seeing how others manage similar hardware conflicts can be helpful. See our guide on Forcing Win-10 Laptop to Connect Internal Wi-Fi Adapter Instead of USB Dongle for the reverse scenario.
Method 2: Using Command Prompt
For those who prefer command-line efficiency or are managing remote machines, PowerShell or CMD offers a faster route. Open Command Prompt as Administrator and use the netsh utility.
netsh interface ipv4 show interfaces
This command lists all interfaces along with their current metrics. Identify the index number or name of your external adapter. Then, run the following command to set its metric explicitly:
netsh interface ipv4 set interface "Your External Adapter Name" metric=10
Replace "Your External Adapter Name" with the exact name shown in the previous output, including spaces if present. Do the same for the internal adapter, setting it to a higher number like 50 or 100. This method is particularly useful if the GUI options are grayed out due to group policy restrictions.
Troubleshooting Connection Issues
Sometimes, changing the metric does not immediately switch the active connection. If you still find yourself connected to the internal adapter after making these changes, you may need to renew your IP address or restart the network service. Open a command prompt and type ipconfig /release followed by ipconfig /renew. This forces Windows to re-evaluate the routing table and establish a new session using the newly prioritized interface.
Another common issue is driver conflicts. Ensure that both adapters have the latest drivers installed from the manufacturer’s website. Outdated drivers can sometimes cause the OS to misidentify the capabilities of the USB dongle, leading to incorrect automatic metric calculations. If you experience intermittent drops, check the power management settings for the USB controller to ensure it is not putting the dongle to sleep too aggressively.
Additionally, verify that both adapters are not fighting for the same frequency band in a congested environment. While the metric dictates preference, physical interference can still degrade performance. Using the external adapter’s high-gain antenna helps mitigate this, but ensuring the internal radio is turned off when not needed can reduce electromagnetic interference within the laptop chassis.
For more complex networking scenarios involving specific protocol issues, refer to Windows 10 Ignores Manually Set Network Metric to understand why certain configurations might fail to apply correctly.
Frequently Asked Questions
Will this break my internet connection?
No, adjusting the metric only changes the priority order; it does not disable connectivity. If the external adapter loses signal, Windows will automatically fall back to the internal adapter because it remains active with a higher metric.
Can I set the metric to zero?
While technically possible, setting a metric to zero is not recommended. It can cause routing anomalies where the system struggles to distinguish between multiple low-cost paths. Values between 1 and 20 are standard for primary interfaces.
Why does my USB adapter keep disconnecting?
This is often a power management issue rather than a metric problem. Check the Power Management tab in Device Manager for the USB root hub and ensure "Allow the computer to turn off this device" is unchecked.
Does this affect local network sharing?
Local file transfers and printer sharing rely on the same network interface used for internet access. Prioritizing the external adapter means all LAN traffic will flow through it, which may improve speeds if the external adapter supports higher bandwidth standards.
What if I have multiple USB Wi-Fi adapters?
You must assign unique metrics to each. If two adapters have the same metric, Windows may load-balance or randomly pick one, leading to unstable connections. Always ensure one has a strictly lower value than the other.