Код ошибки 138 steam

Steam is a digital distribution platform where digital versions of PC games are installed quickly, instead of going to a store and purchasing the video game. Steam is used by gamers all over the globe, but sometimes gamers will experience steam error code 118 or 138. The error messages you see are:

Steam Error Code 118, Unable to connect to server, Server may be offline or you may not be connected to the internet

Steam Error Code 138, Failed to load web page (Unknown error)

What is Steam error code 118?

Steam error code 118 indicates that users are not communicating with Valve’s storefront, or they’re not giving access for Valve’s servers to reach them. Restaring your router is the first thing you should try.

What does Steam error code 138 mean?

Steam error code 138 means that the web page has failed to load or cannot load the server, so users cannot access the Steams server; Steam is a gaming platform that needs a strong internet connection.

To fix steam 118  or 138, follow the solutions below.

1. Enable Steam through Firewall
2. Restart the router
3. Disable all third-party applications
4. Scan computers for viruses

1] Enable Steam through Firewall

The reason behind error code 118 is that the Windows Firewall may be blocking the software from being in contact with the Steam servers due to the function of the Windows Defender Firewall to block potentially harmful software from your computer automatically, even though it’s not always the case.

Follow the steps below to allow Steam through Windows  Firewall.

Type Windows Defender Firewall in the search bar and press enter.

You will see an open panel displaying Windows Defender Firewall; click on it.

The Windows Defender Firewall window will pop up.

Click the Allow an app or feature through Windows Defender Firewall option on the left pane.

Click on the Change settings option.

Now scroll down the list and check both Private and Public options for the Steam client.

Click on Apply option and check if the problem continues.

If the issue persists, follow the other solution below.

2] Restart the router

If the internet speed is slow, Steam might have issues connecting to its servers or database. Resetting your router can improve the connection speed.

Follow the steps below to reset the router.

The first step is to unplug the cord from the router.

Wait for five minutes, and then plug the cord back in.

Wait until the internet access is granted and then launch Steam

3] Disable all third-party applications

Press the Win + R keys together to open the Run dialog box.

Type in the Run dialog box msconfig and press the enter key.

A System Configuration window will open, click on the Services tab and uncheck the Hide all Microsoft Services option.

Click on the Disable all option and then click on the Startup tab.

Click on the option Open Task Manager.

A Task Manager window will open.

Click on a listed application.

Click on the Disable button at the bottom right of the window to disable it from starting automatically at startup.

Repeat the process to disable all applications on the list.

Restart your computer and run only the Steam client.

Check if the issue goes away; If it does, you can start to enable one at a time until the problem returns; in this way, you can easily isolate the issue to a single service or application and disable it permanently.

If the issue continues, try the other solution below.

4] Scan computers for viruses

If a virus or malware is on your computer, it can prevent the Steam client from functioning correctly and cause issues while connecting to the server. The solution for fixing this issue is to scan the computer for viruses.

We hope this tutorial helps you fix the Steam errors.

Related: Steam is having trouble connecting to Steam servers.

Error Code -137 and Error Code -138 are the most common errors that occur due to failure to load the web page. Many users nowadays claimed that they are having issues with the Steam overlay browser as some of the pages are not getting processed. But this is not the issue from the browser side. You might be getting Error Code -137 and Error Code -138, which generally pop up with unknown errors, which caused by server issues.

You might get a solution for resolving Error Code -137 and Error Code -138, which failed to load the web page (unknown error) from here. Go through various reasons mentioned below to identify the cause of failure and then proceed to the particular solution for resolving the issue. Here are some of the reliable solutions discussed below on the page.

Also Read

Fix: Steam Game Won’t Download or Start Issue in Windows 11

How to Clear Steam Download Cache To Make Your Game Run Faster

Fix: Steam VR Headset Not Detected Error

Reasons for getting Code -137 and Error Code -138:

There might be some issues with the web page which restrict the page from loading. Some of the major causes identified for Code -137 and Error Code -138 are:

Network Inconsistency:

This is the primary reason for not getting into any web page. You might check for your internet connection to get rid of the issue sometimes. You might have a stable and robust network connection if you want not to get Code -137 and Error Code -138 while visiting any web page.

Application glitch:

The second most common reason for getting Code -137 and Error Code -138 while loading the page is an application error. You might have some issues with Steam Client. The solution and scan procedure get mentioned in this article.

Steam server:

This will be a reason for Code -137 and Error Code -138 if the server is preventing users from accessing community features. It may get the solution from the user end, but sometimes you need to go for technical support.

Steam Cache:

Corrupted cached data can also cause Code -137 and Error Code -138. Deleting the browser’s cache will help you to get rid of these unwanted temporary files. The cache is not generally the big issue to go through the solution. It is not a general cause also for getting Code -137 and Error Code -138.

Steam Service permissions:

Another reason for having Error Code -137 and Error Code -138 while loading a web page, might be Steam Service permission. Possibly your Steam service does not have the authority to access the Webpage. You have to verify your services by approaching the digital signature or another verification method.

Blocking third-party apps:

You Steam connection might affect by third-party applications. These applications might restrict you from accessing the community feature of any web page. The major problem occurs due to the antivirus firewall.

First, you need to check the status of the issue that if you can solve it by the user’s end, or it requires technical support. For checking the status of error, you might check internet connectivity on the very first hand. Your network connection should be stable if you do not want to stick in any loading error for the Webpage. You may also check the status of the Steam client to properly going for the solution. Here is how you can proceed with some of the answers:

Using Big Picture Mode:

This method will not fix the root cause, but you may get access to the Webpage if you use a big picture mode. Some of the users claimed to get their Error Code -137 and Error Code -138 issue resolved by applying big picture mode on the Steam library. Here are the steps to get into big picture mode:

• Click ‘Windows key + S’ and search for Steam Client
• Open ‘Steam Client’ and access it in administrator mode.
• Then open the Steam client window
• You click on big window icon on the top-right corner of the Steam client window
• This process might provide you temporary access to the page. For troubleshooting the leading cause, you may need to follow the below-mentioned procedure.

Uninstalling/Blocking third-party applications:

The primary cause behind getting Error Code -137 and Error Code -138 is a third-party firewall. You need to allow access from the third-party firewall. An overprotective firewall restricts the communication for Steam due to false positives.

• There are two ways to get into the solution for this. One is to provide the whitelisting for Steam, and another is to uninstall the third-party apps. To whitelist the Steam, you need to give full access to “Gameoverlayui.exe” located in the root folder, and “SteamWebHelper.exe” located in the Steam bin.
• If this doesn’t affect the problem, then you might proceed to uninstall the third-party apps. Here is how you can uninstall the third-party applications:
• Press ‘Windows key + R’ to open the ‘Run’ dialogue box
• Type ‘appwiz.cpl’ and hit ‘Enter’
• Programs and Features menu will get open
• Inside the Programs and Features menu, scroll down the list of installed apps and locate the third-party applications you are using
• Right-click the app and click to ‘Uninstall.’
• Take a quick restart and look into your problem
• It might get a solution now. If the issue is still there, then you need to uninstall or restrict your antivirus services.

Uninstalling Antivirus:

Uninstalling the antivirus program might be a solution for resolving Error Code -137 and Error Code -138 issues. You may also restrict the firewall. You can uninstall the antivirus by following these steps:

Advertisement

• Press ‘Windows key + R’ to open the ‘run’ dialogue box
• Type ‘appwiz.cpl’ and hit ‘Enter’
• Programs and Features menu will get open
• Find your antivirus program here
• Right-click the app and click to ‘Uninstall.’
• Restart to get the issue resolved.

Clearing Browser Cache:

Browser’s caches are another reason for having Error Code -137 and Error Code -138 on the Webpage. You might be able to fix the issue by accessing your Steam Web Browser settings and deleting the Browser Cache and Cookies. You may clear the cache by following these simple steps mentioned below:

• Open Steam and sign-in to your account
• Click on Steam from the dashboard
• Go to ‘Settings’
• Inside the ‘Settings’ menu, select ‘Web Browser’ button on the left side
• Click on ‘Delete Browser Cache’ which you will see on the right panel
• Press ‘Ok’ to start the process
• Click on ‘Delete All Browser Cookies’ once after the cache removal
• Press ‘Ok’ and let the process complete
• Restart your Steam client after the processing
• See if the issue has removed from the page.

Allow SteamService.exe permissions:

When Windows is unable to recognize the Steam client signatures, then the standard error which occurs is the failure of the web page. You might see Error Code -137 and Error Code -138 if you are having this issue. For the solution, you may correct permissions to StreamService.exe by forcing Windows to acknowledge the digital signature. Here is how to proceed with the method:

• Press ‘Windows key + S’ and search for ‘File Explorer’
• Open ‘File Explorer’ and move to the location of your Steam directory.
• On the root directory, access the ‘bin’ folder
• Find ‘steamservice.exe’ and right-click it.
• Choose ‘Properties’ from the context
• You can Select the ‘Digital Signatures’ tab
• Then select ‘Value’ and click on the ‘Details’ box
• Select the ‘General’ tab and click on ‘View Certificate.’
• Click on ‘Install Certificate’ and click ‘Next’ to continue.
• Follow the instruction on the screen and let the system find certificates automatically
• Finally, click ‘Finish’ to complete the process
• Restart Steam and see if the issue gets a solution.

The mentioned procedure might help you to get the appropriate solution for the Error Code -137 and error code -138, failure to load Webpage. Take each step very carefully and also include the backup of all the necessary files as some of the actions may lead to losing data sometimes. You might also connect to the internet for the whole procedure.

If you stuck into some of the issues due to internet connectivity, then you may proceed to change the DNS settings of your system. Internet service providers assign DNS (domain name servers) and dynamic IP. This reason may also cause Error Code -137 and Error code -138. Set alternate DNS server with the values: 8.8.8.8 and 8.8.4.4 and enjoy the optimized solution for the cause of getting Error Code -137 and Error code -138, failure to load a Webpage. If you have any queries or feedback, please write down the comment in the comment box. For more updates like this, check out our iPhone Tips and Tricks, PC tips and tricks, Android Tips and Tricks and other sections.

• How To Recover Steam Account Lost Password?
• How to Fix Steam Error Codes -7 or -130 [Failed to Load Web Page (unknown error)]
• After Ark Update: The Game is Not Launching in Steam or any other platform
• How to Verify Game Cache and Missing Files on Steam in Your PC
• How to Optimize Steam’s Download Speeds in Windows 10
• How to Fix Pending Transaction Steam Error Message?

Some Windows users are reporting that they get the Error Code: -137 or Error Code: -138 every time they attempt to load a page through the Steam overlay browser. The error message accompanying the error code is ‘Failed to load web page (unknown error)’.

Here’s a list of potential scenarios that might spawn this error:

Before trying any of the potential fixes below, do some research to confirm that the issue is not beyond your control. It’s possible that Steam is currently dealing with a server issue that prevents its users from accessing community features. One way to verify this is by checking the current status at SteamStat.us.

Using Big Picture Mode

If you’re using for a quick workaround that will allow you to play games from your Steam library, consider using Big Picture Mode. This will not fix the root cause of the issue, but a lot of affected users have confirmed that this workaround is effective in circumventing the ‘Failed to load web page (unknown error)’ issue.

To enter Big Picture Mode, simply click on its icon – Top-right corner of the Steam client window.

Once you are inside Big Picture mode, repeat the action that was previously causing the error and see if the issue is now resolved.

If it works, you’ve just managed to circumvent the issue. But keep in mind that this is merely a workaround and it doesn’t resolve the root cause of the issue. If you’re looking to find and fix the problem properly, troubleshoot with the next methods below.

Whitelisting Steam or Uninstalling 3rd party firewall (if applicable)

As it turns out, the majority of users that were encountering -137 and -138 error codes when trying to use the overlay browser from within Steam have confirmed that the issue was being caused by an overprotective firewall that ended up blocking communications going out of Steam due to a false positive.

If this scenario is applicable, you should take a look at your firewall settings and whitelist the Steam application and the ports that are being used by this application. However, keep in mind that the exact steps of doing so will be different from firewall to firewall.

With this in mind, open your 3rd party firewall solution and see if you can whitelist Steam. Additionally, if your Firewall works with a permission system, give full access to Gameoverlayui.exe – Located in the root folder where Steam was installed.

Next, repeat the same thing with SteamWebHelper.exe – Located in Steam/bin.

IMPORTANT: If the problem is being caused by a 3rd party firewall tool, disabling it will NOT fix the issue. The same security rules will still remain in place and the ports will still be blocked from communicating even if the responsible app is turned off.

If whitelisting is not an option in your case, the only way to go is to simply uninstall the 3rd party firewall entirely. Here’s a quick step by step guide with how to do this:

1. Press Windows key + R to open up a Run dialog. Next, type ‘appwiz.cpl’ and press Enter to open up the Programs and Features menu.
2. Once you’re inside the Programs and Features menu, scroll down through the list of installed applications and locate the 3rd party firewall solution that you are actively using. After you manage to locate it, right-click on it and choose Uninstall from the newly appeared context menu.
3. Inside the uninstallation screen, follow the on-screen prompts to complete the uninstallation. Next, reboot your computer at the end of this procedure.
   Note: If you want to ensure that you’re not leaving behind any leftover files that might still cause the same behavior, follow this article (here) to remove any remnant files that might still enforce security restrictions on Steam.

In case this method wasn’t applicable, move down to the next potential fix below.

Clearing the Steam’s Web Browser Cache

Another potential culprit that might be contributing to the apparition of the  -137 or -138 error codes in Steam is bad temporary cached data. As confirmed by some users, you might be able to fix the issue by accessing your Steam Web Browser settings and deleting the Browser Cache and Cookies.

This is especially effective in those situations where the problem is only occurring when you attempt to use the overlay browser that Steam offers.

If this scenario is applicable, follow the instructions below to clear the web browser cache in Steam:

1. Open Steam and sign-in with the same account that you’re encountering issues with.
2. From the main dashboard, click on Steam (from the ribbon bar at the top), then click on Settings from the newly appeared context menu.
3. Once you’re inside the Settings menu, select Web Browser from the vertical menu on the left.
4. Next, move to the right section, click on Delete Browser Cache and then confirm by clicking Ok to initiate the procedure.
5. After the web browser cache has been cleared, click on Delete All Browser Cookies and repeat the procedure again.
6. Once the operation is complete, restart your steam client and see if the issue is resolved at the next system startup.

In case this operation didn’t fix the issue and you’re still encountering the same Error Code: -137, move down to the next potential fix below.

Giving Permissions to SteamService.exe

As it turns out, this issue can also occur due to an inconsistency caused by the fact that Windows is unable to recognize the signature of the Steam client – it will treat the application as one from an Unknown publisher even though Steam is signed by Valve.

If this scenario is applicable, you can end up giving every permission needed to SteamService.exe by opening the Properties screen and showing and installing the certificate from the Digital Signature tab. By forcing Windows to retrieve certificate data manually, you should end up eliminating the Error Code: -137 or Error Code: -138 completely.

Here’s a quick guide on giving the correct permissions to StreamService.exe by forcing Windows to acknowledge the digital signature of the main executable involved in this operation:

1. Open File Explorer and navigate to the location of your Steam directory. Once you get to the root directory, access the bin folder in order to reach steamservice.exe.
2. Once you are inside the correct location, right-click on steamservice.exe and choose Properties from the newly appeared context menu.
3. Inside the Properties screen, select the Digital Signatures tab, select Value from the Signature list section, then click on the Details box.
4. At the Digital Signature Details screen, select the General tab and click on View Certificate.
5. Next, click on Install Certificate from the Certificate menu (General Tab).
6. At the first Certificate Windows Wizard menu, select Local Machine under Store Location and click Next to continue.
7. Next, select the toggle associated with Automatically select the certificate store based on the type of certificate and click Next to continue.
8. At the final prompt, click Finish to complete the installation of the Valve certificate
9. After the operation is complete, restart steam and see if the issue is resolved.

In case you’re still encountering the Error Code: -137 or Error Code: -138 despite ensuring that the Valve digital certificate is installed, move down to the next potential fix below.

Enabling Beta Participation

In case you only get the Error Code: -138 when trying to access the Store and the Community tab in Steam, but you can access your Steam’s Library, you might be able to fix the issue swiftly by enlisting in Beta Participation.

There is no official explanation on why this is effective, but a lot of affected users have confirmed that this quick fix finally allowed them to get rid of the annoying error message.

If this scenario is applicable to your current situation, here’s a quick step by step guide that will show you how to enable Beta Participation in your Steam Client:

1. Open Steam and use the ribbon bar at the top to click on Stream and then on Settings (from the context menu).
2. Inside the Settings menu, select the Accounts tab from the menu on the right, then move to the right section and click the Change button associated with Beta Participation.
3. From the Beta Participation screen, use the drop-down menu to select Steam Beta Update, then click Ok to save the changes.
4. Wait until the installation is complete, then restart your Steam client once the operation is complete.
5. Attempt to access the Store or the Community tabs in Steam to see if the problem has been fixed.

If the same issue is still occurring, move down to the next potential fix below.

Changing the Default DNS Settings

In case you’re using an ISP (Internet Service Provider) that assigns automatic DNS (domain name servers) and dynamic IPs, it’s possible that you are seeing the Error Code: -138 / -137 due to a network inconsistency.

If this scenario is applicable, you should be able to get the issue resolved by moving away from the default DNS switchboard to Google’s Public DNS. A lot of affected users have confirmed that this operation was the only thing that allowed them to fix the issue.

However, keep in mind that in order to do this, you will need to do some modifications from your Network Connections window (in your Windows GUI settings). Here are some step by step instructions that will show you how to do this:

1. Open up a Run dialog box by pressing Windows key + R. Next, type ‘ncpa.cpl’ and press Enter to open up the Network Connections window.
2. Once you’re inside the Network Connections menu, select the connection that you want to configure with Google Public DNS.
   Note: If you’re using a wireless network, right-click on Wi-Fi (Wireless Network Connection) and choose Properties from the context menu. If you’re using a wired connection, right-click on Ethernet (Local Area Connection)
3. When you get to the Wi-Fi/Ethernet Properties screen, select the Networking tab and click on the Settings button under This connection uses the following items. 
4. Next, select Internet Protocol Version 4 (TCP/IPv4) and click on the Properties menu.
5. Inside the Internet Protocol Version 4 (TCP/IPv4) settings, select the General tab and check the toggle associated with Use the following DNS server address and replace the Preferred DNS server and Alternate DNS server with the following values:

   8.8.8.8
   8.8.4.4

6. Save the changes, then repeat steps 3 and 4 all over again with Internet Protocol Version 6 (TCP / IPv6). But when you do this, use the values below for Preferred DNS server and Alternate DNS server respectively:

   2001:4860:4860::8888
   2001:4860:4860::8844

7. Once the change has been enforced, restart your network connection and open Steam again to see if the problem has been resolved.
8. 

   In case you’re still encountering the same error message, move down to the final potential fix below.

Refreshing the Network Adapter

If you get this far and none of the potential fixes above have helped, it’s very likely that you’re dealing with some type of network inconsistency. One final thing that you can try is to reset the network adapter to the default configuration – This procedure is also known as winsock reset or coms reinstall.

In the event that an inconsistent network adapter is causing the Failed to Load Web Page in Steam, follow the instructions below to refresh your network adapter:

Note: The instructions below should work regardless of the Windows version that you’re currently using.

1. Open up a Run dialog box by pressing Windows key + R. Next, type ‘cmd’ and press Ctrl + Shift + Enter to open up an elevated Command Prompt terminal. When you see the User Account Control prompt, click Yes to grant Admin Access.
2. Once you’re inside the elevated CMD prompt, type the following command and press Enter to refresh the network adapter:

   netsh winsock reset

3. After the command is successfully processed, restart your computer and see if the problem is fixed at the next computer startup.

When you open steam on your windows 11 or 10 computer and you are getting an error code on steam 118 or 138 and cant connect to steam or can’t open steam on windows computer, then you can easily fix this issue on your own. So, let’s see in detail below.

Steam Error 118 Means it means that your are unable to connect to the server or steam server is offline and you might check with your internet connection first and the error code 138 failed to load webpage unknown error on steam.

Fix Steam error code 118 or 138 on Windows 11 or 10

Below methods will help you fix steam error code 118/138 on windows 11 computer and get up and running without any issues on your steam.

Unplug Power Cable

Step 1: Unplug your windows power cable connected to wall socket and completely disconnect it from power source.

Step 2: Now ,wait for 10 to 20 seconds and then plug back power cable and turn on your windows computer.

Once you unplug and plug back power cables then your issue will be resolved and steam will connect to internet without any issues.

Reset Modem or Router

Step 1: Unplug power cable of router and all power cables connected to your computer.

Step 2: wait for 30 seconds and connect router or modem cables and plug back router and turn it on.

Step 3: Now, wait for your windows computer to turn on and connect your windows computer to the internet.

Now, go ahead and open steam on windows 11 computer and your issue of steam error code 118 or 138 will be fixed successfully.

Also Read:

1) How to stop steam from opening on startup on Windows 11 or 10

2) How to Change Steam Location or Country on Steam Profile

3) How to Fix Steam Preparing to Launch on Windows 11 or 10 Computer

4) How to Fix Battle Net Error BLZBNTAGT00000BB8

5) How to Fix Twitch Error 1000 When Playing A Video or Video Download Was cancelled

Check Whether Steam server is Up or Not

Step 1: Open Google chrome browser and go to https://steamstat.us/ 

Step 2: Check with stream status and if there is any downtime of steam server then wait for sometimes and then check.

Step 3: Once steam server is up then your issue of error code 118 or 138 will be resolved as there is an issue with steam server.

Windows Firewall

Step 1: Click on Windows search and type in windows firewall

Step 2: Open windows Defender firewall settings

Step 3: On left side options -> click on Allow an app or features through windows Defender firewall.

Step 4: Click on Change Settings

Step 5: Scroll down and select Steam and check private and public check box next to steam.

Step 6: Click on Ok and Save changes and restart your windows computer.

Once you restart your windows computer then your issue of steam error 118 or 138 issue on your windows 11 or 10 computer will be resolved successfully.

Reset Network Settings

Step 1: Open windows settings on your computer.

Step 2: On left side menu -> click on Network and Internet

Step 3: Scroll down on right side and click on Advanced network settings

Step 4: Under More Settings -> Click on Reset Network Settings

Step 5: Click on Reset and confirm reset network settings and wait for your windows 11 or 10 computer to completely reset network settings.

Once you reset your network settings, then you need to connect your windows computer to wifi and then go ahead and open steam and your issue of steam error code 118 or 138 or steam not connecting issue will be resolved successfully.

Steam Error Code Failed to Load Web Page

When you are trying to open steam on your windows computer and you are getting an error code that fails to load webpage then this is an issue of wifi internet or firewall blocking steam and you need to reset modem or router and reset network settings to fix steam error failed to load webpage.

FAQ