Disable the Windows firewall once this error occurs
by Henderson Jayden Harper
Passionate about technology, Crypto, software, Windows, and everything computer-related, he spends most of his time developing new skills and learning more about the tech world. He also enjoys… read more
Updated on
- Running into the Winsock error 10054 indicates the connection has been reset by peer, or it has been closed by the remote host.
- It can occur due to poor network connection and firewall interference.
- Disabling Windows Defender Firewall on your PC will stop it from accessing and impeding your connections.
Winsock error 10054 can appear with a message saying Connection reset by peer, or An existing connection was forcibly closed by the remote host. It means the target host closed the connection unexpectedly. Hence, we’ll explain why it happened and how to fix it.
Also, you may be interested in our guide about fixing socket error 10060 connection timed out on Windows PC.
What causes the Winsock error 10054?
Some factors that can cause the error are:
- Closing the connection midway – Just as the error message says, Windows 10054 can occur when you abruptly close or shut down the session while the computer tries to connect with a server.
- Internet connection issues -If there is network congestion between the peer servers or the network is not stable, it can cause the connection to reset or be closed forcibly. Also, it can disable the server connections when connected to a proxy server.
- Firewall interference with the connection – The activities of Windows Defender Firewall or other antivirus software may impede the connection between the servers. It checks every connection that goes in and out of the PC and can cause a delay in the process.
- Outdated network driver – When the network drivers on your computer are outdated, they can affect your network performance. Also, it can cause incorrect assembling of the TCP/IP transport packets.
Depending on the circumstances of occurrence, these causes may vary on different computers. However, you can resolve the error by following the fixes in this article.
How can I fix the Winsock error 10054?
Observe the following preliminary checks before trying any advanced troubleshooting steps:
- Restart the computer – It will refresh the system and is the quickest way to fix temporary issues affecting the computer.
- Fix network-related issues – Power cycling the modem or router and updating the router firmware can resolve network issues.
- Add Winsock to Firewall’s exception list – This will ensure that the Windows Defender Firewall will not flag anything related to Winsock as a threat or disrupt its activities.
If you can resolve the Winsock error, proceed with the solutions below:
1. Disable Windows Firewall
- Press Windows + R key to open the Run dialog box, type control, then press Enter to open the Control Panel.
- Click on the Windows Defender Firewall option.
- Click the Turn Windows Defender Firewall on or off option.
- Go to the Private and Public network settings, then click the radio buttons for the option to Turn off Windows Defender Firewall (not recommended).
- Restart your PC.
Disabling the Windows Defender Firewall resolves any interference it’s causing your computer from connecting to the peer server.
You can read about how to disable Windows Defender if you encounter issues with it.
2. Update the network driver
- Press Windows + R keys to prompt the Run window, type devmgmt.msc, and click OK.
- Expand the Network adapters, right-click on the driver, then click Update driver from the drop-down.
- Select the Search automatically for drivers option and wait till the update finishes.
- Restart your PC and check if the error persists.
Updating the network driver will fix bugs and install the latest features to improve your computer driver performance. Check other steps for updating drivers on Windows 11 if you have any issues.
Sometimes, malfunctioning drivers can cause multiple system errors. If this happens to your PC, you may need to update or reinstall certain drivers entirely. As the process is not quite straightforward, we recommend using a reliable driver updater for the job.
Here’s how to do it:
- Download and install Outbyte Driver Updater.
- Launch the software.
- Wait for the app to detect all faulty drivers.
- Now, it will show you all the malfunctioning drivers listed to select the ones to Update or Ignore.
- Click on Update & Apply Selected to download and install the newest versions.
- Restart your PC to ensure the applied changes.
Outbyte Driver Updater
Secure your Windows PC with Outbyte from various errors caused by problematic drivers.
Disclaimer: this program needs to be upgraded from the free version in order to perform some specific actions.
3. Reset TCP/IP Stack
- Left-click the Start button, type Command Prompt, and click the Run as administrator option.
- Click Yes on the User Account Control (UAC) prompt.
- Type the following in the command bar and press Enter:
netsh int ip reset c:\resetlog.txtipconfig /releaseipconfig /renewipconfig /flushdns
- Restart your computer.
Resetting the TCP/IP will restore its default settings and fix any configuration issues causing the winsock error 10054. Check our guide on how to fix Command Prompt not working on your PC.
Further, do not hesitate to check how to resolve the network connections’ unexpected error on Windows 11.
Also, we have a detailed explanation of the causes and ways to fix the requested address is not valid in its context error on the PC.
Symptoms
Consider the following scenario:
-
You have a computer that is running Windows 7 or Windows Server 2008 R2.
-
A Transport Driver Interface (TDI) filter driver is installed on the computer. For example, a TDI filter driver is installed when you install McAfee VirusScan.
-
An application opens a TCP listening port to receive connections.
In this scenario, the application may receive the following error message:
WSAECONNRESET (10054) Connection reset by peer.
A existing connection was forcibly closed by the remote host.
This issue occurs because the TCP/IP driver does not close an incomplete TCP connection. Instead, the TCP/IP driver sends a notification that the TCP/IP driver is ready to receive data when the incomplete TCP connection is created. Therefore, the application receives an instance of the 10054 error that indicates that a connection is reset when the application receives data from the connection.
Resolution
To resolve this issue, install this hotfix.
Note This hotfix temporarily resolves this issue for application vendors before they migrate their implementation to Windows Filtering Platform (WFP). These application vendors use the TDI filter driver or the TDI extension driver (TDX) on a computer that is running Windows 7 or Windows Server 2008 R2.
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.
Registry information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in WindowsTo enable the hotfix in this package, follow these steps:
-
In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters
-
If you are running a 32-bit operating system, perform the following step:
Right-click the Parameters registry subkey, point to New, and then click DWORD Value.If you are running a 64-bit operating system, perform the following step:
Right-click the Parameters registry subkey, point to New, and then click DWORD (32-bit) Value.
-
Rename the new registry entry to TdxPrematureConnectIndDisabled and set the value to 1.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Tdx.sys |
6.1.7600.20796 |
74,752 |
09-Sep-2010 |
02:19 |
x86 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Tdx.sys |
6.1.7600.20796 |
101,376 |
09-Sep-2010 |
02:52 |
x64 |
For all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Tdx.sys |
6.1.7600.20796 |
236,032 |
09-Sep-2010 |
01:47 |
IA-64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about WFP, visit the following Microsoft website:
General information about WFPFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
|
File name |
Package_1_for_kb981344~31bf3856ad364e35~x86~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,820 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_2_for_kb981344~31bf3856ad364e35~x86~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,825 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_3_for_kb981344~31bf3856ad364e35~x86~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,805 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_for_kb981344_rtm~31bf3856ad364e35~x86~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
2,421 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
X86_bfb7f2e54887b839240a44ae0de89137_31bf3856ad364e35_6.1.7600.20796_none_3f3df7432361a4c5.manifest |
|
File version |
Not Applicable |
|
File size |
702 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
X86_microsoft-windows-tdi-over-tcpip_31bf3856ad364e35_6.1.7600.20796_none_ea93f14a568e0aaf.manifest |
|
File version |
Not Applicable |
|
File size |
2,924 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
04:58 |
|
Platform |
Not Applicable |
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
Amd64_8e30a6e4951f89c20ce3f8a1c04b9f2a_31bf3856ad364e35_6.1.7600.20796_none_8d28eb4c99ddf2d4.manifest |
|
File version |
Not Applicable |
|
File size |
706 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Amd64_microsoft-windows-tdi-over-tcpip_31bf3856ad364e35_6.1.7600.20796_none_46b28cce0eeb7be5.manifest |
|
File version |
Not Applicable |
|
File size |
2,926 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
06:11 |
|
Platform |
Not Applicable |
|
File name |
Package_1_for_kb981344~31bf3856ad364e35~amd64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,830 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_2_for_kb981344~31bf3856ad364e35~amd64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
2,057 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_3_for_kb981344~31bf3856ad364e35~amd64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,815 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_for_kb981344_rtm~31bf3856ad364e35~amd64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
2,659 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
|
File name |
Ia64_0bb425f9d3502a4be9efc4af61147428_31bf3856ad364e35_6.1.7600.20796_none_09467879be47b542.manifest |
|
File version |
Not Applicable |
|
File size |
704 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Ia64_microsoft-windows-tdi-over-tcpip_31bf3856ad364e35_6.1.7600.20796_none_ea959540568c13ab.manifest |
|
File version |
Not Applicable |
|
File size |
2,925 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
05:48 |
|
Platform |
Not Applicable |
|
File name |
Package_1_for_kb981344~31bf3856ad364e35~ia64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
2,051 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
|
File name |
Package_for_kb981344_rtm~31bf3856ad364e35~ia64~~6.1.2.0.mum |
|
File version |
Not Applicable |
|
File size |
1,683 |
|
Date (UTC) |
09-Sep-2010 |
|
Time (UTC) |
18:48 |
|
Platform |
Not Applicable |
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
Socket errors are one of the most common problems that can occur when using a computer. The socket error 10054 is caused by an existing connection that is forcibly closed by the remote. The error could be solved by restarting your router, checking if the address of the computer or host is correct, scanning for malware and lastly trying to connect through a different port.
Table of Contents
This is an error that occurred when attempting to connect with the server. The primary reason for this issue is due to a software or network problem. Error 10054 might also be caused by accidentally shutting down or disconnecting a program while the computer is attempting to establish contact with a server.
There might be a problem with your Internet connection or a proxy server shutting down server connections. The firewall might be malfunctioning and causing the connection to break, as it does with all concerns.
How to Fix Socket Error 10054
Restart Your Router or DNS
When you are connecting to a new network, it is best to restart your router. If the computer is able to make a direct connection with the internet, then the problem lies somewhere else and not with your network.
You can follow these steps to clear DNS cache:
- Click Windows Start and type Command Prompt.
- Right-click the Command prompt and select Run as Administrator.
- In the Command Prompt, type netsh winsock reset and press Enter key.
- Type netsh int ip reset and press Enter key.
- Type ipconfig /release and press Enter key.
- Type ipconfig /renew and press Enter key.
- Type ipconfig /flushdns and press Enter key.
Check if The Address of Your Computer or Host Is Correct
The default gateway address should be different from the IP address assigned by DHCP (Dynamic Host Configuration Protocol). When there’s no difference in these values, it shows that something might be wrong with the settings in all programs that are related to the internet like firewalls.
You can check this by typing in “ipconfig /all” on Command Prompt (which will show your IP address and default gateway).
Scan for Malware
When you suspect that malware might be causing the issue, then it’s time to scan again with an antivirus if necessary. Sometimes, even after restarting your computer and router, malware can still cause problems as they are installed on a deeper level into the system.
It is best to scan for Malware at least twice to make sure that any remaining traces of malicious programs have been detected. If the problem persists even after removing them from your computer, then you may need a deeper analysis or a complete reformatting of your machine.
Reboot Your Computer
It doesn’t matter whether you want to call it a “warm reboot” or a “cold boot”, but rebooting your computer is a basic step in troubleshooting any problems that could affect your PC performance.
Check Your Settings In All Programs That Are Related to the Internet (Like Firewalls)
If you don’t have enough knowledge about networking, then it’s best to consult with a network specialist when dealing with internet-related problems. Or if you still think that you can handle it on your own, then make sure to check and change all of your settings in every program related to the internet.
For instance, anything related to Skype or Firefox should be disabled especially if you suspect that these programs might cause this issue.
Try Connecting Through a Different Port
If nothing seems out of order regarding your router and hardware settings but socket error 10054 keeps on occurring, then it is best to try connecting through a different port.
These errors usually mean that there’s a problem with the connection settings where it creates a faulty connection between two programs for a specific port number. This means that you have to configure your network so that outgoing connections use other ports instead of the default one.
Отключите брандмауэр Windows после возникновения этой ошибки
- Ошибка Winsock 10054 указывает, что соединение было сброшено узлом или закрыто удаленным хостом.
- Это может произойти из-за плохого сетевого подключения и помех брандмауэра.
- Отключение брандмауэра Защитника Windows на вашем ПК предотвратит его доступ к вашим соединениям и препятствование им.
ИксУСТАНОВИТЕ, НАЖИМАЯ НА СКАЧАТЬ ФАЙЛ
- Скачать инструмент восстановления ПК Restoro который поставляется с запатентованными технологиями (патент доступен здесь).
- Нажмите Начать сканирование чтобы найти проблемы Windows, которые могут вызывать проблемы с ПК.
- Нажмите Починить все для устранения проблем, влияющих на безопасность и производительность вашего компьютера.
- Restoro был скачан пользователем 0 читателей в этом месяце.
Ошибка Winsock 10054 может появиться с сообщением о том, что Соединение сброшено узлом, или существующее соединение было принудительно закрыто удаленным хостом.. Это означает, что целевой хост неожиданно закрыл соединение. Поэтому мы объясним, почему это произошло и как это исправить.
Также вас может заинтересовать наше руководство по исправлению ошибка сокета 10060 время ожидания соединения истекло на ПК с Windows.
Что вызывает ошибку Winsock 10054?
Некоторые факторы, которые могут вызвать ошибку:
- Закрытие соединения на полпути — Как говорится в сообщении об ошибке, Windows 10054 может возникнуть, когда вы резко закрываете или завершаете сеанс, когда компьютер пытается подключиться к серверу.
- Проблемы с подключением к Интернету -Если есть перегрузка сети между одноранговыми серверами или сеть нестабильна, это может привести к сбросу или принудительному закрытию соединения. Кроме того, он может отключать соединения с сервером при подключении к прокси-серверу.
- Вмешательство брандмауэра в соединение – Действия брандмауэра Защитника Windows или другого антивирусного программного обеспечения могут препятствовать соединению между серверами. Он проверяет каждое соединение, которое входит и выходит из ПК, и может вызвать задержку в процессе.
- Устаревший сетевой драйвер – Когда сетевые драйверы на вашем компьютере устарели, они могут повлиять на производительность вашей сети. Кроме того, это может привести к неправильной сборке транспортных пакетов TCP/IP.
В зависимости от обстоятельств возникновения эти причины могут различаться на разных компьютерах. Однако вы можете устранить ошибку, выполнив действия, описанные в этой статье.
Как исправить ошибку Winsock 10054?
Соблюдайте следующие предварительные проверки, прежде чем предпринимать какие-либо дополнительные шаги по устранению неполадок:
- Перезагрузите компьютер — Это обновит систему и является самым быстрым способом исправить временные проблемы, влияющие на компьютер.
- Устранение проблем, связанных с сетью – Выключите и снова включите модем или маршрутизатор и обновление прошивки роутера может решить проблемы с сетью.
- Добавьте Winsock в список исключений брандмауэра – Это гарантирует, что брандмауэр Защитника Windows не пометит ничего, связанное с Winsock, как угрозу и не нарушит его работу.
Если вы можете устранить ошибку Winsock, выполните следующие действия:
1. Отключить брандмауэр Windows
- Нажимать Окна + р ключ, чтобы открыть Бегать диалоговое окно, введите контроль, затем нажмите Входить открыть Панель управления.
- Нажать на Брандмауэр Защитника Windows вариант.
- Нажмите на Включение или отключение брандмауэра Защитника Windows вариант.
- Перейти к Настройки частной и общедоступной сети, затем щелкните переключатели для параметра Отключите брандмауэр Защитника Windows (не рекомендуется).
- Перезагрузите компьютер.
Некоторые проблемы с ПК трудно решить, особенно когда речь идет об отсутствующих или поврежденных системных файлах и репозиториях вашей Windows.
Обязательно используйте специальный инструмент, например Защитить, который просканирует и заменит ваши поврежденные файлы их свежими версиями из своего репозитория.
Отключение брандмауэра Защитника Windows устраняет любые помехи, из-за которых ваш компьютер не может подключиться к одноранговому серверу.
Вы можете прочитать о том, как отключить Защитник Windows если у вас возникнут проблемы с ним.
- Что такое Scrobj.dll и как его исправить, если он отсутствует
- Bcryptprimitives.dll: что это такое и как исправить ошибки
- 0x800f0841 Ошибка Центра обновления Windows: как ее исправить
- 0x800704f1 Ошибка Центра обновления Windows: как ее исправить
- Invalid_mdl_range BSOD: 4 способа исправить это
2. Обновите сетевой драйвер
- Нажимать Окна + р клавиши для подсказки Бегать окно, тип devmgmt.msc, и нажмите ХОРОШО.
- Развернуть Сетевые адаптеры, щелкните правой кнопкой мыши драйвер, затем щелкните Обновить драйвер из раскрывающегося списка.
- Выберите Автоматический поиск драйверов вариант и дождитесь окончания обновления.
- Перезагрузите компьютер и проверьте, сохраняется ли ошибка.
Обновление сетевого драйвера исправит ошибки и установит новейшие функции для повышения производительности драйвера вашего компьютера. Проверьте другие шаги для обновление драйверов на виндовс 11 если у вас есть какие-либо проблемы.
Различные ошибки являются следствием неправильной работы драйвера. В этом случае вам может потребоваться полностью обновить или переустановить этот конкретный компонент. Поскольку этот процесс не является простым для завершения, мы рекомендуем использовать для этой работы автоматизированный инструмент. Вот как это сделать:
- Скачайте и установите DriverFix.
- Запустите приложение.
- Подождите, пока программа обнаружит все неисправные драйверы.
- Теперь вам будет представлен список всех драйверов, у которых есть проблемы, и вам просто нужно выбрать те, которые вы хотели исправить.
- Подождите, пока DriverFix загрузит и установит новейшие драйверы.
- Перезапуск ваш компьютер, чтобы изменения вступили в силу.
DriverFix
Защитите свою Windows от любых ошибок, вызванных поврежденными драйверами, установив и используя DriverFix уже сегодня!
Бесплатная пробная версияПосетите вебсайт
Отказ от ответственности: эта программа должна быть обновлена с бесплатной версии, чтобы выполнять некоторые определенные действия.
3. Сбросить стек TCP/IP
- Щелкните левой кнопкой мыши Начинать кнопка, тип Командная строкаи щелкните значок Запустить от имени администратора вариант.
- Нажмите Да на Контроль учетных записей пользователей (UAC) быстрый.
- Введите следующее в командной строке и нажмите Входить:
netsh int ip reset c:\resetlog.txtipconfig/выпускipconfig/обновитьipconfig /flushdns
- Перезагрузите компьютер.
Сброс TCP/IP восстановит его настройки по умолчанию и устранит все проблемы с конфигурацией, вызывающие ошибку winsock 10054. Ознакомьтесь с нашим руководством о том, как исправить Командная строка не работает на вашем ПК.
Кроме того, не стесняйтесь проверить, как решить непредвиденная ошибка сетевых подключений в Windows 11.
Также у нас есть подробное объяснение причин и способов устранения запрошенный адрес недействителен в своем контексте ошибка на ПК.
Все еще испытываете проблемы?
СПОНСОР
Если приведенные выше рекомендации не помогли решить вашу проблему, на вашем компьютере могут возникнуть более серьезные проблемы с Windows. Мы предлагаем выбрать комплексное решение, такое как Защитить для эффективного решения проблем. После установки просто нажмите кнопку Посмотреть и исправить кнопку, а затем нажмите Начать ремонт.
Windows error 10054: Connection reset by peer.
An existing connection was forcibly closed by the remote host.
Got this error message and looking for a fix?
This Windows error 10054 occurs when the connection is reset by the peer application.
It happens usually due to an incorrect firewall configuration.
At Bobcares, we often get requests to fix windows errors, as a part of our Server Management Services
Today, let’s see how our Support Engineers fix the Windows error 10054 for our customers.
5 Symptoms of Windows error 10054
Basically, the error indicates that the remote host closed the connection unexpectedly. So we cannot do anything on the program except to accept that the connection lost.
Let’s discuss the symptoms of this windows error.
- When running the same script, the PC frequently crashes with Error 10054.
- System displays “Windows Error Code 10054”.
- Windows is slow to react to mouse or keyboard input.
- The system periodically “freezes” for a few seconds at a time.
- “Error 10054” appears and crashes the active program window.
Causes of Windows Error 10054?
We just saw the 5 Symptoms of windows error 10054.
Let’s check the main causes of this Error 10054.
- Infection with a virus or malware that has infected Windows system files.
- Another program maliciously or mistakenly deleted Windows-related files.
- Corrupt update/download and incomplete Windows software installation.
- Corruption in the Windows registry.
- Firewall restrictions.
The typical error shows up as :
How we fix the Windows Error 10054?
Let’s see how our Support Engineers fix this error for our customers.
1. Firewall and router configuration
One of the main reasons for this windows error is an incorrect configuration of firewall and router. So we recommend that the customers test the firewall and that the routers configured properly.
If any unwanted settings are existing on the customers’ system, we ask them to uninstall it or reinstall it again.
2. Disable peer-to-peer functionality.
On certain systems, the problem occurs when connected via a peer-to-peer connection.
To disable this functionality, we do like this:
- We open the Windows Update.
- Then after, we click or tap Advanced options
- And then click or tap Choose how updates are delivered.
- On this screen, we choose to toggle the slider to Off to completely disable P2P.
This fixes the error.
3. Clean Out System Junk (Temporary Files and Folders).
If the system accumulates junk files, it can also cause Windows to respond slowly or show a 10054 error.
So cleaning up these temporary files usually solve the 10054 error. We use the utility cleanmgr on the Windows servers to perform this task.
4. Install All Available Windows Updates.
Sometimes resolving your Runtime Errors problems help to resolve the windows error.
To check for the windows updates.
- We first, Click >> Start button.
- Then we type >> update into the search box and hit ENTER
- Then after the Windows Update dialog box will appear.
- If updates are available, we click >> Install Updates button.
5. Conduct a Full Malware Scan of Your PC
At times, there is a chance that the 10054 error could be related to a malware infection on the PC.
These malicious intruders can destroy, corrupt, or even delete files associated with runtime errors.
So we help our customers to run a full malware scan on their PC to resolve the windows error.
6. Perform a Clean Installation of Windows
This is the last option in trying to resolve the Error 10054.
Reinstalling Windows will erase everything from your hard drive, allowing you to start again with a fresh system. However, this method requires the proper backup of data. A clean install of Windows will also quickly clean out any and all “junk” that has accumulated over the normal usage of your computer.
This fixes the customer’s windows error.
[Need more assistance in windows error 10054? We’ll fix it for you.]
Conclusion
In short, the windows error 10054 occurs when the connection is reset by the peer application. It usually due to an incorrect firewall configuration. Today we saw how our Support Engineers fix this error for our customers.