[FIX] Address Incompatible with the Requested Protocol (10047 Error)
A “Connection Error: An address incompatible with the requested protocol was used (10047)” usually appears when you’re setting up network software or running a test, suddenly stopping what you’re doing. This error, also called WSAEAFNOSUPPORT, means that the software is trying to use a network address that doesn’t match the type of connection expected—for example, trying to use an IPv4 connection with an IPv6 address.

The most common reason for this error is when a program tries to use an IP version (like IPv6) that isn’t supported or turned on for your computer. This often happens if IPv6 is disabled, but a program still tries to use it. In some cases, having “::1” (which is the IPv6 version of localhost) in your hosts file while IPv6 is off can also cause this error.
In this article, we will discuss different ways to solve this error.
1. Perform a Winsock Reset
For most users, this error is linked to a temporary network problem caused by corrupted TCP or IP data. Resetting your network settings (Winsock Reset) often resolves these issues.
- Press Windows key + R to open the Run dialog box. Type cmd and then press Ctrl + Shift + Enter to open an elevated Command Prompt. If prompted by UAC (User Account Control), click Yes to allow.
Accessing the CMD prompt
- In the Command Prompt window, type or paste each of these commands in order, pressing Enter after each one:
nbtstat -R nbtstat -RR netsh int reset all netsh int ip reset netsh winsock reset
- Once all commands have finished running, close the Command Prompt.
- Restart your router, and if possible, unplug the power for at least one minute before plugging it back in. This helps clear any leftover cache.
- After your Internet is working again, try running the bandwidth test in uTorrent.
2. Whitelist uTorrent and Its Connection Port
If resetting Winsock didn’t work, your antivirus or firewall may be blocking uTorrent. Adding uTorrent (and its port) to your whitelist can fix this.
This process is a bit different depending on whether you’re using third-party security software or Windows built-in protection. Use the relevant guide below:
2.1. Whitelisting uTorrent and Port in Third-Party Antivirus
Exact steps will vary by software, so check your antivirus documentation or look up a specific guide. Generally, you’ll need two things:
- The location of uTorrent’s main program file (typically C:\Users\[YourName]\AppData\Roaming\uTorrent if you didn’t choose a custom folder).
- The port uTorrent uses for incoming connections.
To view hidden folders like AppData, open File Explorer, select the View tab, and check Hidden items.

To find uTorrent’s port:
- Open uTorrent, click Options at the top, then select Preferences.
Accessing the Preferences menu in uTorrent
- In Preferences, choose the Connections tab on the left. Note the Listening port being used.
Finding out the uTorrent Listening port for incoming connections
- With this info, follow your antivirus documentation to whitelist both uTorrent and its listening port.
2.2. Whitelisting uTorrent and Port in Windows Defender / Firewall
If you use Windows Defender and Windows Firewall, follow these steps:
- Press Windows key + R, type control firewall.cpl, and press Enter to open Windows Firewall.
Accessing the Windows Defender Firewall menu
- Click Allow an app or feature through Windows Defender Firewall.
Allowing an app or feature through Windows defender
- Click Change settings and confirm any prompts.
Changing the Settings first
- Click Allow another app, then click Browse and find uTorrent’s main folder and select utorrent.exe.
C:\Users\[YourName]\AppData\Roaming\uTorrent
- After adding it, ensure both Private and Public boxes are checked next to uTorrent in the app list, then click OK.
- Now, in uTorrent, open Options > Preferences, go to Connections, and write down the Listening port number—it’s needed for the next steps.
Finding out the uTorrent Listening port for incoming connections
- Return to the main Windows Firewall screen and click Advanced settings.
Accessing the Firewall rules menu
- Click Inbound Rules on the left, then choose New Rule.
Create new rules in Windows Firewall
- Select Port, then hit Next. Choose TCP, select Specific local ports, and enter your uTorrent port from earlier.
- Click Next, choose Allow the connection, click Next again, and follow prompts to finish creating the rule.
Enforcing the firewall rule
- Give this new rule a name, then click Finish to save.
- Restart your computer, then repeat the uTorrent bandwidth test.
3. Uninstall Any Conflicting 3rd-Party Security Software
Many users report that security suites like certain antivirus or firewall programs caused the An address incompatible with the requested protocol was used. (10047) error during the bandwidth test in uTorrent.
Some antivirus programs (like AVG and similar) may block these connections by default. If whitelisting doesn’t solve it, or you can’t find the right settings, try temporarily uninstalling the third-party software and using only Windows Defender.
- Press Windows key + R, type appwiz.cpl, and press Enter to open Programs and Features.
Opening the Programs and Features menu
- Find your antivirus or security program in the list, right-click it, and choose Uninstall.
Uninstalling the overprotective AV suite
- Follow any removal prompts and restart your PC when done.
- After your computer restarts, try running the bandwidth test in uTorrent again.
4. Disable IPv6 on Your Network Adapter
Some users have fixed this error by turning off IPv6 on their network adapter. You can always re-enable it later if you need it.
- Press Windows key + R, type ncpa.cpl, and press Enter to open Network Connections.
Accessing the Network Connections Menu
- Right-click your active network adapter and select Properties.
Accessing the Properties screen - Note: If asked by UAC (User Account Control), click Yes.
- In the Networking tab, scroll down and uncheck Internet Protocol Version 6 (TCP/IPv6).
Accessing the Internet Protocol Version 6
- Click OK to save, then try running uTorrent’s bandwidth test again.