Some Windows users are trying to run a speed test on their Net connectedness, only every online tool that they endeavor to use volition end up displaying the 'Socket Error' bulletin. In virtually cases, this issue is reported to occur with  SpeedTest.

Socket Error On SpeedTest

Every bit it turns out, one of the near mutual instances that volition produce the Socket Faultis an outbound rule (Connected Devices Platform – Wi-Fi Straight Transport (TCP-Out)) belonging to Windows Firewall. If information technology's disabled, you AV might not allow connections with speed examination utilities. In this case, you can resolve the problem past enabling the outbound rule from the Advanced settings of the Windows Firewall.

Simply if you're using a tertiary party AV or Firewall, you might need to whitelist the domain of the SpeedTest tool that you're using in order to allow the test to complete. Additionally, you should look to disable the real-fourth dimension protection or uninstall the third party suite altogether.

However, cloud solutions like Onedrive or Google Bulldoze are also reported to trigger the 'Socket Fault'. If this scenario is applicable, disable the real-time syncing characteristic of your deject solution and see if the result is resolved.

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

Method one: Enabling Continued Device Platform rule in Windows Firewall

Every bit it turns out, the 'socket error' when running an Internet speed examination with your browser can be caused by your firewall – even if you're using the built-in firewall (Windows Firewall). This scenario is virtually encountered on a Wi-Fi connection.

According to some affected users, this item issue can occur due to an Outbound rule called 'Connected Devices Platform – Wi-Fi Directly Send (TCP-Out)'.

Some affected 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 mind that the outbound rule that needs to be enabled will be dissimilar if you're encountering the issue with an ethernet connection.

Hither'due south a quick step past step guide that will allow you to access the Advanced built-in Firewall settings and enabling the correct outbound rule:

  1. Press Windows fundamental + R to open up upward a Run dialog box. Next, blazon 'firewall.cpl' within the text box and press Enter to open up upwards the Windows Firewall settings window.
  2. Once you're within the Windows Defender Firewall settings, click on the Advanced settings carte du jour from the left-hand side menu bar.
  3. After you manage to country inside the Windows Defender Firewall and Advanced Security, click on Outbound Rules from the carte du jour on the left.
  4. With the Outbound Rules bill of fare selected, motility downward to the right-hand section and scroll down through the listing of available Outbound Rules and locate 'Connected Devices Platform – Wi-Fi Direct Transport (TCP-OUT)'. Once yous see it, double-click on it.
    Note: If you're encountering the upshot with an ethernet connection, access the Connected Devices Platform (TCP-Out)outbound dominion instead.
  5. Inside the Properties screen of the outbound rule that you want to alter, select the Full general tab from the bill of fare at the top, and then ensure that the box associated with Enabled is checked.
  6. Click on Utilize to save the changes, and then close every window and restart your computer.
  7. One time the adjacent startup is complete, repeat the speed test over again and encounter if the outcome is now resolved.
    Enabling the problematic outbound rule

In example the same 'Socket Error' is still occurring, movement downward to the next potential gear up below.

Method two: Pause OneDrive or Drive Syncing (if applicative)

If yous're using OneDrive or the desktop version of Google Drive as the primary cloud solution, continue in mind that these two can be huge Internet bandwidth hoggers if you're they are actively syncing files while you lot 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 bulldoze) was uploading files in the groundwork, effectively taking up all the available bandwidth.

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

Since we don't discriminate, we created two separate guides that will assistance yous disable active syncing regardless of the cloud application 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 2 Hours from the list of available options.
    Pausing Syncing on OneDrive

    Note: Two hours is more than than enough to complete the speed test – no demand to stop the active syncing feature indefinitely.

  3. Once the OneDrive syncing feature is disabled, echo the speed test and come across if the 'Socket Error' has been resolved.

Pausing Active Syncing on Google Drive

  1. Become to your taskbar and look for the icon associated with Google Drive.
  2. If you see that the utility is actively syncing files, click on the activeness button (top-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 see if the trouble is resolved.
  4. Once the operation is completed, render to the same Google Drive bill of fare and click on Resume to reestablish real-time syncing.

In example yous've already done this with no success or this scenario was non applicable, move down to the adjacent potential gear up below.

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

Every bit it turns out, there are some overprotective suites that will simply flag the speed test equally a suspicious activity – which volition terminate up triggering the 'Socket Error'. 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 order to allow the speed test to run. Merely keep in heed that this operation volition exist dissimilar depending on the AV suite that you're using.

In Avast, you lot tin can institute a whitelisting rule by going to Settings > General > Exclusions > URL. Once you lot get there, merely paste 'https://world wide web.speedtest.internet/' and save the modifications.

White-listing the Speed exam domain in 3rd party AV settings

Notation: Keep in listen that these steps will be different depending across multiple 3rd political party suites.

Additionally, y'all can simply disable the real-time protection while you perform the speed test. In most cases, you can practise this directly from the taskbar menu. Simply right-click on the icon associated with your AV and look for an selection that will disable the real-time protection.

Right Click Avast Icon From Organization Tray To Disable Avast Temporarily

In case the aforementioned problem is persisting and y'all're using a third party security suite, move downwardly to the side by side potential fix beneath.

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

If the method above didn't resolve the outcome simply you are using a tertiary party suite that y'all suspect might be causing this problem, the only way to test the theory out is to uninstall the 3rd party suite and ensure that you're not leaving backside any leftover files that might nevertheless cause the same type of behavior.

In case you suspect that a false positive triggered by your 3rd party AV is causing the result, hither's a quick step-by-step guide on uninstalling the 3rd political party suite or firewall and ensuring that you're not leaving behind any remnant files that might still produce the error:

  1. Press Windows cardinal + R to open upward a Run dialog box. Side by side, type 'appwiz.cpl' and printing Enter to open up the Programs and Features menu.
    Blazon appwiz.cpl and Press Enter to Open Installed Programs List
  2. In one case you manage to get within the Programs and Features bill of fare, scroll downwardly through the listing of installed applications. Do and then until you locate the 3rd party A/V or firewall that you doubtable might exist causing the effect.
  3. When you see it, right-click on it and choose Uninstall from the newly appeared context menu.
    Uninstalling Avast Firewall
  4. Inside the uninstallation sorcerer, follow the on-screen prompts to complete the process of uninstalling the third party AV app.
  5. Once the uninstallation is complete, restart your figurer and follow this article (here) once the adjacent startup is complete in club to ensure that yous as well remove whatsoever leftover files that might still produce this blazon of behavior.
  6. Run the speed test over again and encounter if the issue is notwithstanding resolved.

In example the same problem is withal occurring, move down to the next potential gear up below.

Method 5: Using a Different Testing Tool

If none of the methods beneath have allowed you to fix the 'Socket Error' and perform a SpeedTest, it's fourth dimension to consider the alternatives. Keep in mind that SpeedTest.net is not the but reliable tools that volition allow yous to examination your Internet connection.

We've created a list with 5 Alternatives that you can use in case Speedtest.Cyberspace is consistently showing the same error message:

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

Experience free to utilize any of the alternatives featured above. They are just as reliable as the most popular option (SpeedTest.Internet) and will most likely not trigger the aforementioned 'Socket Error'.