Some Windows users are trying to run a speed exam on their Internet connection, but every online tool that they try to use will end up displaying the 'Socket Error' bulletin. In well-nigh cases, this effect is reported to occur with  SpeedTest.

Socket Error On SpeedTest

Equally it turns out, one of the virtually common instances that will produce the Socket Erroris an outbound rule (Connected Devices Platform – Wi-Fi Direct Transport (TCP-Out)) belonging to Windows Firewall. If it'due south disabled, you AV might non allow connections with speed test utilities. In this case, y'all can resolve the problem by enabling the outbound rule from the Advanced settings of the Windows Firewall.

But if you're using a tertiary party AV or Firewall, you might need to whitelist the domain of the SpeedTest tool that yous're using in gild to allow the test to complete. Additionally, you should await to disable the real-time protection or uninstall the 3rd political party suite birthday.

However, cloud solutions like Onedrive or Google Drive are also reported to trigger the 'Socket Error'. If this scenario is applicable, disable the real-time syncing feature of your cloud solution and see if the issue is resolved.

If all else fails, y'all should consider using a dissimilar speed testing tool that is more permissive with your Net connexion.

Method 1: Enabling Connected Device Platform dominion in Windows Firewall

As information technology turns out, the 'socket mistake' when running an Cyberspace speed examination with your browser can be caused past your firewall – even if you're using the congenital-in firewall (Windows Firewall). This scenario is nigh encountered on a Wi-Fi connectedness.

According to some affected users, this detail consequence can occur due to an Outbound rule called 'Connected Devices Platform – Wi-Fi Straight Transport (TCP-Out)'.

Some afflicted users have managed to fix the issue by accessing the Advanced Security suites of Windows Firewall and enabling the problematic outbound rule. But continue in listen that the outbound rule that needs to be enabled will be different if you're encountering the issue with an ethernet connection.

Here's a quick step by footstep guide that will allow y'all to access the Advanced congenital-in Firewall settings and enabling the correct outbound dominion:

  1. Press Windows key + R to open upwards a Run dialog box. Side by side, type 'firewall.cpl' within the text box and press Enter to open up the Windows Firewall settings window.
  2. Once you're inside the Windows Defender Firewall settings, click on the Advanced settings menu from the left-hand side carte du jour bar.
  3. Later on you lot manage to land inside the Windows Defender Firewall and Avant-garde Security, click on Outbound Rules from the card on the left.
  4. With the Outbound Rules menu selected, motility down to the right-hand department and scroll down through the listing of available Outbound Rules and locate 'Connected Devices Platform – Wi-Fi Direct Transport (TCP-OUT)'. Once you meet it, double-click on it.
    Note: If you're encountering the outcome with an ethernet connection, access the Continued Devices Platform (TCP-Out)outbound rule instead.
  5. Inside the Properties screen of the outbound rule that you desire to change, select the General tab from the menu at the pinnacle, then ensure that the box associated with Enabled is checked.
  6. Click on Apply to save the changes, then close every window and restart your computer.
  7. In one case the side by side startup is complete, echo the speed test once over again and run into if the issue is now resolved.
    Enabling the problematic outbound dominion

In example the aforementioned 'Socket Mistake' is even so occurring, motion downward to the adjacent potential set up below.

Method 2: Pause OneDrive or Drive Syncing (if applicable)

If you're using OneDrive or the desktop version of Google Bulldoze as the primary cloud solution, go on in listen that these 2 can be huge Internet bandwidth hoggers if you're they are actively syncing files while you are trying to run a speed test.

Several affected users have reported that they got this error consistently until they realized that their cloud solution (Onedrive or Google drive) was uploading files in the background, effectively taking up all the available bandwidth.

If this scenario is applicable, you can ready this outcome by pausing the syncing sequence of Ondrive or Google Drive – depending on the tool that y'all're using.

Since we don't discriminate, we created two separate guides that will help you lot disable active syncing regardless of the deject awarding that you're using.

Pausing Active Syncing on OneDrive

  1. Right-click on the taskbar icon associated with OneDrive (an icon resembling a deject).
  2. Next, from the OneDrive context menu, click on More, select Pause Syncing and select ii Hours from the list of available options.
    Pausing Syncing on OneDrive

    Annotation: Two hours is more than enough to complete the speed test – no need to finish the active syncing feature indefinitely.

  3. Once the OneDrive syncing feature is disabled, repeat the speed exam and meet if the 'Socket Fault' has been resolved.

Pausing Agile Syncing on Google Drive

  1. Go to your taskbar and look for the icon associated with Google Drive.
  2. If y'all come across that the utility is actively syncing files, click on the action push button (superlative-right corner) and click on Pause from the newly appeared cotext menu.
    Pausing Google Drive Sync
  3. Now that the active syncing is disabled, repeat the speed examination and come across if the problem is resolved.
  4. In one case the performance is completed, render to the aforementioned Google Drive menu and click on Resume to reestablish real-time syncing.

In case you've already done this with no success or this scenario was not applicable, move down to the next potential set below.

Method 3: Whitelist Speedtest domain (if using 3rd party AV)

Every bit it turns out, there are some overprotective suites that will simply flag the speed test equally a suspicious activity – which will end up triggering the 'Socket Fault'. Avast Antivirus, Kaspersky and Comodo AV are commonly signaled out for blocking communications between computer and Speedtest server.

If this scenario is applicable, yous should be able to resolve the issue by whitelisting the domain in social club to allow the speed test to run. But continue in mind that this operation will exist different depending on the AV suite that you're using.

In Avast, yous can constitute a whitelisting rule by going to Settings > Full general > Exclusions > URL. Once you get at that place, simply paste 'https://www.speedtest.net/' and save the modifications.

White-listing the Speed test domain in third party AV settings

Notation: Keep in heed that these steps volition be different depending beyond multiple 3rd party suites.

Additionally, you can merely disable the real-fourth dimension protection while you perform the speed test. In nigh cases, you tin do this directly from the taskbar carte du jour. Simply right-click on the icon associated with your AV and look for an option that will disable the existent-time protection.

Right Click Avast Icon From System Tray To Disable Avast Temporarily

In instance the same trouble is persisting and you lot're using a third party security suite, move down to the side by side potential fix below.

Method 4: Uninstalling 3rd political party suite (forth with remnant files)

If the method above didn't resolve the issue simply yous are using a 3rd party suite that yous suspect might exist causing this problem, the only mode to examination the theory out is to uninstall the third party suite and ensure that you're not leaving behind whatsoever leftover files that might withal cause the aforementioned type of behavior.

In example you doubtable that a false positive triggered by your 3rd party AV is causing the consequence, here's a quick step-past-step guide on uninstalling the 3rd party suite or firewall and ensuring that you're non leaving behind any remnant files that might nevertheless produce the fault:

  1. Press Windows key + R to open up a Run dialog box. Next, type 'appwiz.cpl' and press Enter to open upwards the Programs and Features card.
    Type appwiz.cpl and Press Enter to Open Installed Programs List
  2. Once y'all manage to get inside the Programs and Features menu, ringlet down through the list of installed applications. Practise so until you locate the 3rd party A/5 or firewall that you doubtable might exist causing the event.
  3. When you see it, correct-click on information technology and cull Uninstall from the newly appeared context menu.
    Uninstalling Avast Firewall
  4. Inside the uninstallation magician, follow the on-screen prompts to complete the process of uninstalling the 3rd party AV app.
  5. Once the uninstallation is complete, restart your estimator and follow this article (here) once the side by side startup is complete in gild to ensure that you likewise remove any leftover files that might still produce this type of behavior.
  6. Run the speed test once more and encounter if the issue is still resolved.

In instance the aforementioned problem is still occurring, motility down to the next potential prepare below.

Method 5: Using a Unlike Testing Tool

If none of the methods below have allowed y'all to ready the 'Socket Error' and perform a SpeedTest, it's time to consider the alternatives. Keep in mind that SpeedTest.net is not the only reliable tools that volition allow you to test your Internet connection.

We've created a listing with 5 Alternatives that y'all can utilize in case Speedtest.Net is consistently showing the same error message:

  • Fast.com
  • Xfinity Speed Test
  • Internet Health Examination
  • Cox Internet Speed Test
  • SpeedOf.Me

Experience free to use any of the alternatives featured above. They are but as reliable as the most pop option (SpeedTest.Net) and will most likely non trigger the same 'Socket Error'.