How to Fix Steam Error Code -105: Easy Step-by-Step Guide

How to Fix Error code: -105 steam Step by Step
How to Fix Steam Error Code -105: Easy Step-by-Step Guide

If you have been trying to access your Steam library or the Steam Store only to be met with the dreaded "Error code: -105," you are certainly not alone.

This connection error is a common hurdle for many PC gamers, effectively cutting off access to your games, community features, and the marketplace.

Understanding how to fix error code: -105 steam step by step can save you hours of downtime and frustration.

Whether you are a casual player or a dedicated enthusiast, this guide will walk you through the most effective troubleshooting methods to get you back into your games quickly.

Understanding Steam Error Code -105

Before diving into the fixes, it is helpful to understand what causes this issue.

Essentially, Error code -105 indicates that your Steam client is unable to establish a secure connection to the Steam servers.

This can be caused by various factors, ranging from unstable internet connections and DNS misconfigurations to interference from third-party firewall software or corrupted cache files within the Steam client itself.

Because the source can vary, we recommend following these steps in order to isolate and eliminate the problem systematically.

Understanding Steam Error Code -105

Step 1: Check Your Internet Connection

The most common culprit behind a -105 error is a disruption in your internet connection.

Before making complex changes to your system, perform a basic sanity check.

Ensure that your router is powered on and that other devices on your network are browsing the web without issues.

If you are connected via Wi-Fi, try switching to a wired Ethernet connection to see if signal interference is the cause.

Simply restarting your router by unplugging it for 30 seconds and plugging it back in can often refresh your connection and resolve minor packet loss issues that trigger Steam errors.

Step 2: Flush Your DNS Cache

Step 1: Check Your Internet Connection

If your internet seems fine but Steam still reports error -105, your system might be holding onto outdated or corrupted DNS (Domain Name System) records. Flushing your DNS is a powerful way to force your computer to request fresh IP addresses for Steam’s servers. To do this, press the Windows key, type "cmd," and run it as an administrator. In the command prompt window, type ipconfig /flushdns and press Enter. Once you see the message confirming that the DNS Resolver Cache has been flushed, restart Steam and check if the error persists.

Step 3: Clear Steam Browser and Client Cache

Steam acts like a web browser for its store and community pages.

Like any browser, it stores cache files to speed up loading.

Occasionally, these files become corrupted, leading to connection errors.

To clear this, navigate to your Steam client's "Settings" menu.

Select the "Web Browser" tab and click the button labeled "Delete Web Browser Data." Additionally, you can navigate to the Steam installation folder on your hard drive, locate the "appcache" folder, and delete its contents.

Do not worry—this will not delete your installed games, but it will force Steam to rebuild its internal database.

Step 2: Flush Your DNS Cache

Step 4: Check Firewall and Antivirus Interference

Security software is essential, but sometimes it can be too aggressive, misinterpreting Steam's background processes as unauthorized network traffic.

If you use a third-party antivirus or a highly restrictive firewall, try temporarily disabling them to see if the error clears.

If Steam connects successfully after disabling these tools, you will need to add an exception (or whitelist) for the Steam executable in your security software’s settings.

This ensures your protection remains active while allowing Steam to communicate freely with its servers.

Step 5: Reset Winsock Settings

Step 3: Clear Steam Browser and Client Cache

If the previous methods fail, the issue might lie in your system's Winsock catalog, which handles how Windows applications access network services. A corrupted Winsock configuration can block Steam from reaching the internet. To reset this, open the Command Prompt as an administrator once again. Type netsh winsock reset and press Enter. You will be prompted to restart your computer to apply the changes. This is a common final step for many network-related errors and often resolves stubborn connection issues that are not fixed by simpler methods.

Conclusion

Encountering Steam Error code -105 is undoubtedly annoying, but it is rarely a permanent issue.

By following these step-by-step troubleshooting techniques—starting from verifying your internet connection, flushing DNS, clearing the cache, checking your firewall settings, and resetting Winsock—you can address the vast majority of causes.

Most users find success within the first three steps.

If you have exhausted all these options and still cannot connect, it is possible that Steam's own servers are experiencing an outage.

In such cases, checking a site like DownDetector is a wise final move before waiting for Valve to resolve the issue on their end.



Frequently Asked Questions (FAQ)

What does Steam Error -105 actually mean?

Error -105 is a network-related issue that signifies the Steam client cannot connect to the Steam servers, preventing access to the Store, Library, and Community features.

Will clearing my Steam cache delete my installed games?

No, clearing the Steam web browser cache or the appcache folder will not delete your installed games or save files.

It only removes temporary data that the client uses to load pages faster.

Is it safe to reset my Winsock settings?

Yes, resetting your Winsock settings is a standard Windows diagnostic procedure that restores your network settings to their default configuration, which is safe for most home users.

What if I still see Error -105 after trying all these steps?

If all local fixes fail, the issue might be on Steam's end.

Check the Steam Status page or social media to see if Valve is experiencing a widespread server outage.



Written by: Mia Robinson

Read also: 7 Effective Ways to Fix Dbd Error Code 130 Fast