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.

1. When running the same script, the PC frequently crashes with Error 10054.
2. System displays “Windows Error Code 10054”.
3. Windows is slow to react to mouse or keyboard input.
4. The system periodically “freezes” for a few seconds at a time.
5. “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.

1. Infection with a virus or malware that has infected Windows system files.
2. Another program maliciously or mistakenly deleted Windows-related files.
3. Corrupt update/download and incomplete Windows software installation.
4. Corruption in the Windows registry.
5. 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:

1.  We open the Windows Update.
2. Then after, we click or tap Advanced options
3. And then click or tap Choose how updates are delivered.
4. 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.

1. We first, Click >> Start button.
2. Then we type >> update into the search box and hit ENTER
3. Then after the Windows Update dialog box will appear.
4. 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.