Some Windows 10 users are encountering the Connection error: An address incompatible with the request protocol was used. (10047) error whenever they attempt to run a bandwidth test inside uTorrent.
After investigating this particular issue thoroughly, it turns out that there are several different common culprits that are known to cause this particular behavior on Windows 10. Here’s a list of the most common occurrences:
- Network inconsistency – As it turns out, you might find out that this particular issue will occur due to bad TCP or IP data that is being perpetuated and ends up affecting the stability of your internet connection. In this case, you can fix the issue by performing a Winsock reset procedure from an elevated Command Prompt window.
- Bandwidth test is blocked by Firewall – Under certain circumstances, affected users have found out that the bandwidth scan was actually being interrupted by the Firewall solution that was active on that network. In this case, depending on if you’re using a 3rd party firewall or the native equivalent, you can fix the issue by establishing a whitelisting rule that will accept both the main executable and the port that is used for incoming connections.
- 3rd party conflict – A 3rd party antivirus or another 3rd party utility might also be responsible for interfering with the uTorrent scan. In case you are unable to establish a whitelist rule for it in order to prevent the conflict, the only way to fix the issue is to uninstall the 3rd party program completely.
- Inconsistency with the IPv6 on the active Network Adapter – In certain cases, the bandwidth scan might be interrupted by inconsistency with the Internet Protocol version that is actively being used. Several affected users have managed to fix the issue by disabling IPv6 before repeating the bandwidth test.
Now that you know every potential culprit that might be responsible for this issue, here’s a list of confirmed fixes that other affected users have successfully used to get rid of the issue and complete the bandwidth test inside uTorrent:
Method 1: Performing a Winsock Reset
In the majority of documented cases, this particular issue is related to some type of network inconsistency that’s either facilitated by bad TCP or IP data that ends up affecting the stability of your Internet connection.
Some users that were also dealing with this kind of issue have reported that they were finally able to avoid the Connection error: An address incompatible with the request protocol was used. (10047) error and complete the bandwidth test by performing a Winsock reset procedure.
This operation will successfully allow you to recover your PC from the vast majority of socket errors that might arise after the download of an unknown file or after a malicious script has made its way on your computer.
If this scenario is applicable, you should be able to fix the issue by following the instructions below to perform a Winsock reset procedure via an elevated CMD prompt:
- Press Windows key + R to open up a Run dialog box. Once you’re inside the text box. type ‘cmd’ and press Ctrl + Shift + Enter to open up an elevated Command Prompt. When you are prompted by the UAC (User Account Control), click Yes to grant admin access.
- Inside the elevated Command Prompt, type or paste the following commands in order and press Enter after each one to effectively reset every TCP and IP data that might be causing the Connection error: An address incompatible with the request protocol was used. (10047) error:
nbtstat -R nbtstat -RR netsh int reset all netsh int ip reset netsh winsock reset
- Once you are certain that every command is processed successfully, you can go ahead and close the elevated Command Prompt.
- At this point, you should also consider restarting your router and physically disconnecting the power cable for 1 minute or more in order to allow the power capacitors enough time to discharge.
- Finally, reconnect the power cable of your router and wait until Internet access is re-established before trying to run the bandwidth test in uTorrent once again.
If the end result is the same and you are still getting interrupted by the Connection error: An address incompatible with the request protocol was used. (10047) error, move down to the next potential fix below.
Method 2: Whitelist the Executable + Port used for Incoming Connections
If a Winsock Reset procedure didn’t work in your case, you have to think about the fact that the security suite that is active on your Windows 10 computer might be actively blocking the incoming connections that uTorrent is managing.
If this scenario is applicable, you should be able to prevent the issue from occurring again by accessing your AV settings and whitelisting the executable + the port that is being used by your current installation.
In this case, the instructions for doing so will be different depending on if you’re using a 3rd party security suite or the integrated solution (Windows Defender + Windows Firewall)
Because of this, we’ve put together 2 separate guides, so follow the one applicable to your particular scenario:
A. Whitelisting uTorrent Executable + Incoming Connection Port on 3rd party security suite
In this case, we can’t provide you with a definitive guide on doing this because the steps of whitelisting will be different from security tool to security tool.
You will need to read the official documentation supplied by the developer of the 3rd party Antivirus tool that you’re using or search online for specific tutorials that will show you how to do this.
However, there are some common steps that you need to take prior to establishing these whitelisting rules.
First, you need to determine where you previously installed your uTorrent suite. If you haven’t installed it in a custom location, you will find the main executable of uTorrent inside C:\Users\madro\AppData\Roaming\uTorrent.
Note: However, unless you have hidden folders enabled by default, you will not be able to access the AppData folder because it will not be visible. In this case, you will need to access the View Menu of File Explorer and check the box associate with Hidden Items.
Once you know the default location of the main executable of Utorrent, the next step is to figure out which port is currently used by the peer-to-peer client for your incoming connection. Here’s a short step-by-step guide that will show you how to do this:
- Open uTorrent, click on Options from the ribbon menu at the top, then click on Preferences from the context menu that just appeared.
- Once you’re inside the Preferences menu, click on the Connections tab from the menu on the left, then move over to the right-hand side and take note of the Listening port that is actively being used for incoming connections.
Now that you know both the location of uTorrent and the incoming connection port, you can access the Advanced / Expert settings of your 3rd party antivirus and effectively whitelist every component that might be causing the bandwidth error.
B. Whitelisting uTorrent Executable + Incoming Connection Port on Windows Defender / Windows Firewall
If you are using Windows Defender + Windows Firewall as the default antivirus suite, you will need to go through 2 separate processes in order to successfully whitelist the main executable of uTorrent and ensure that the port used for incoming connections is not blocked.
To make matters easier for you, we’ve put together a series of step-by-step instructions that will walk you through the entire process:
- Press Windows key + R to open up a Run dialog box. Next, type ‘control. firewall.cpl‘ inside the text box and press Enter to open up the Windows Firewall menu.
- Once you are inside the main Windows Defender Firewall menu, click on Allow an app or feature through Windows Defender Firewall from the menu on the left.
- Once you are inside the Allowed Apps menu, go ahead and click on the Change settings button, then hit Yes when asked by the User Account Control prompt.
- Once you see that the list became fully editable, go directly under it and click on Allow another app, then click on Browser and navigate to the location where the game is installed.
- Next, navigate to the location where you installed uTorrent and whitelist the main utorrent.exe executable. If you didn’t install it in a custom location, you’ll be able to find it here:
- Once you have successfully managed to find and add the correct executable to the Allowed apps, go ahead and find it inside the list and ensure that both checkboxes associated with Private and Public are checked before clicking Ok to save the changes.
- Open uTorrent, click on Options from the ribbon menu at the top, then click on Preferences from the context menu that just appeared.
- Once you’re inside the Preferences menu, click on the Connections tab from the menu on the left, then move over to the right-hand side and take note of the Listening port that is actively being used for incoming connections. Take note of this port as we will use it a little later.
- Once the executable of uTorrent is successfully whitelisted, you need to focus on whitelisting the incoming connections promptly. To do this, you can close the current window and follow step 1 again to return to the initial firewall menu.
- After you manage to return to the first firewall menu, click on Advanced settings from the menu on the left. When prompted by the UAC (User Account Control), click Yes to grant admin access.
- Once you land inside the Advanced Settings of your Firewall menu, click on Inbound Rules from the menu on the left-hand side, then click on New Rule.
- Next, you should see a New Inbound Rule wizard, then choose Port when asked for the Rule Type, then click on Next once again. When you get to the next screen, choose TCP and select Specific Local ports toggle, then paste the port you have obtained at step 9.
- Follow the on-screen instructions to create the rule that will prevent this port from ever being blocked, then hit Next to arrive inside the Action Prompt menu. Once you’re there, click on Allow the connection and click on Next once again.
- Finally, establish a name for the rule you have just established, then click on Finish to save the changes.
- Restart your computer and wait for the next startup to complete before repeating the bandwidth test inside uTorrent and seeing if the issue is now resolved.
In case the same problem is still occurring, move down to the next potential fix below.
Method 3: Uninstall 3rd-party Culprit
There are a lot of user reports reporting that in their case, a 3rd party Antivirus or firewall suite was being responsible for triggering the An address incompatible with the request protocol was used. (10047) error when performing a bandwidth test inside uTorrent.
As it turns out, there are a handful of Antivirus suites that will actively block peer-to-peer connections unless you specifically tell them not to. AVG is among the most popular ones, but there are others that will cause this issue.
If you were unable to whitelist uTorrent + the incoming connection port (or you’re not planning to), the only viable fix at this point is to uninstall the problematic 3rd party suite and allow Windows Defender to kick in.
If you plan on going this route, follow the instructions below to uninstall the 3rd party AV suite via the Programs and Files menu:
- Press Windows key + R to open up a Run dialog box. Next, type ‘appwiz.cpl’ and press Enter to open up the Programs and Features menu.
- Once you’re inside the Programs and Files menu, scroll down through the list of installed applications and locate the 3rd party antivirus suite that you suspect is responsible for this particular error.
- Next, right-click on it and choose Uninstall from the context menu that just appeared.
- From the uninstallation menu, follow the on-screen prompts to complete the uninstallation process, then restart your computer and wait for the next startup to complete.
- Once your computer boots back up, repeat the action that was previously causing the Connection error: An address incompatible with the request protocol was used. (10047) error and see if the issue is now fixed.
If you’re still encountering the same error message, move down to the next potential fix below.
Method 4: Disabling IPv6 on Network Adapter
According to some affected users that were encountering this issue on Windows 10, this issue was resolved after they have disabled the IPv6 on the network adapter. They were successfully able to run the bandwidth test inside uTorrent once they’ve made some changes to the Internet Protocol Version.
In case you are not reliant on IPv6, you should consider effectively disable IPV6 – At least temporarily, until you complete the bandwidth test.
If you’re looking for step by step instructions on how to do this, follow the instructions below:
- Press Windows key + R to open up a Run dialog box. Next, type ‘ncpa.cpl’ inside the text box, then press Enter to open up the Network Connections menu.
- Once you’re inside the Network Connections menu, right-click on the network adapter that you’re currently actively using and click on Properties from the context menu that just appeared.
Note: When you’re prompted by the UAC (User Account Control), click Yes to grant admin access.
- Inside the Properties screen of your Network adapter, access the Networking tab, scroll down through the list of items used and uncheck the box associated with Internet Protocol Version 6 (TCP / IPv6).
- Click Ok to save the changes, then get back to uTorrent and repeat the bandwidth test and see if the Connection error: An address incompatible with the request protocol was used. (10047) error is now fixed.