Skip to content

Steam: Error Code 138 Fix – Store Page Not Loading

Interactive troubleshooting

Fix Progress

Try the steps in order. Open each step, follow the instructions, then mark the step that solved the problem.

0community fixes

What worked for other readers

Step 1
0%
Step 2
0%
Step 3
0%
Step 4
0%
Step 5
0%
Step 6
0%
Step 7
0%
Step 8
0%
Step 9
0%

Steam Error Code -138, often searched without the minus sign as Error Code 138, appears when the client cannot give its embedded Store page network access. Games already installed may still launch, while Store, Community, Workshop, profile, or Points Shop pages remain blank or display “Failed to load web page.” The fastest path is to identify whether the block sits inside Steam, in Windows security software, or on the current network.

Quick Fix

  1. Choose Steam > Exit, restart Windows, and reopen Steam.
  2. Open Steam > Settings > In Game > Delete Web Browser Data.
  3. Allow both steam.exe and the active steamwebhelper.exe through the firewall or antivirus application control.
  4. Disconnect any VPN and disable an unneeded manual proxy for one test.
  5. Run ipconfig /flushdns, then restart Steam.

What the Error Means

Steam Error Code -138 is a web-view networking failure associated with network access being denied. It points more directly to a firewall, security filter, proxy, network policy, or damaged local web session than to a corrupt game installation.

What Steam Error Code 138 Means

Steam’s Store is a web application displayed inside the desktop client. The client starts several steamwebhelper.exe processes to render Store and Community content. Error -138 is associated with Chromium’s ERR_NETWORK_ACCESS_DENIED condition. Chromium’s Windows networking code maps a socket access-denied result from Windows to that network error, including cases where Windows Firewall blocks a connection. [✅Source-1]

This distinction matters. Error -138 is not a normal “server not found” message, and it does not prove that Valve’s servers are offline. The request may be stopped before it leaves the computer. A stale firewall rule, antivirus web inspection, a VPN filter driver, a managed-network rule, or an invalid proxy can all produce the same visible Store failure.

Symptoms That Match Error 138

  • The Steam client opens, but the Store tab does not load.
  • Community, Workshop, profile, inventory, or Points Shop pages fail inside Steam.
  • Installed games may launch normally because the Library and game files do not need the same web request.
  • The Store works in Chrome, Edge, or Firefox but fails inside the Steam client.
  • The problem begins after a Steam update, Windows update, antivirus update, firewall change, VPN installation, or network-policy change.
  • Reloading may switch between a blank page and a “Failed to load web page” message.

Valve notes that a firewall can block Steam after a first installation or a client update, even when Steam connected correctly before the update. Valve also recommends checking background applications and security software during network troubleshooting. [✅Source-2]

Find Out Whether Steam, Windows, or the Network Is Blocking the Page

Do not begin by reinstalling games. A short comparison test can narrow the cause without changing the system.

Test ResultMost Likely AreaNext Action
Store works in a normal browser but not in SteamSteam web data, steamwebhelper.exe, firewall, or antivirus application controlClear Steam web browser data and rebuild app rules
Store fails in Steam and every browser on one computerWindows proxy, DNS, security suite, Hosts file, or network stackCheck proxy and filters, then refresh DNS
Store fails on every device using one routerRouter filtering, DNS service, ISP path, or managed-network policyRestart the router and test a different trusted network
Store works through a mobile hotspotOriginal network or routerInspect DNS, parental controls, firewall rules, and access policies
Store fails on two unrelated networks only on one PCLocal firewall, antivirus, VPN driver, or Steam clientReauthorize Steam and inspect local filters
Only one Store page failsPage-specific session, cookie, region, or temporary content issueDelete Steam web data and retry the page later

Run a Two-Minute Browser and Network Test

  1. Fully exit Steam. Closing the window may leave Steam running in the notification area, so use Steam > Exit.
  2. Open store.steampowered.com and steamcommunity.com in a normal browser.
  3. Test the same addresses on a phone using the same Wi-Fi.
  4. Turn off Wi-Fi on the phone and test once through mobile data.

If the external browser works on the same PC, the internet connection itself is available. That result moves steamwebhelper.exe, cached web data, and per-application security rules to the top of the list. If the phone also fails only on home Wi-Fi, Steam is less likely to be the local cause.

Recognize Managed-Network Restrictions

School, workplace, hotel, dormitory, library, and public networks may filter storefronts, gaming services, proxy traffic, or nonstandard ports. Do not attempt to bypass an organization’s policy. Test a permitted personal connection instead or ask the network administrator whether Steam web traffic is allowed.

Valve states that university and business networks and proxies may block ports Steam needs. For Store browsing, normal HTTP and HTTPS traffic uses remote TCP ports 80 and 443; other Steam functions use additional TCP and UDP ranges. [✅Source-3]

Repair Steam’s Embedded Store Session

Exit Every Steam Process Before Retesting

A normal window close does not always end Steam. Open Task Manager with Ctrl + Shift + Esc and check for steam.exe and steamwebhelper.exe. Use Steam’s Exit command first; end a remaining process only when the client has stopped responding.

Restarting Windows clears locked files, stale process state, and temporary networking state. Valve lists a computer restart as a basic Steam client troubleshooting step because it releases resources and resets other programs that may be interfering. [✅Source-4]

Delete Steam Web Browser Data

In the current desktop client, open Steam > Settings > In Game and use Delete Web Browser Data. This clears local browser cache and cookies used by Steam’s web views. It may sign the embedded pages out of some web sessions, but it does not delete installed games, saves, screenshots, or the account.

Use the right cache control. Delete Web Browser Data targets Store and Community web content. Clear Download Cache targets download and installation state. A download-cache reset may sign Steam out and is not the first choice when only the Store page is failing.

Check for a Steam Client Update

Open Steam > Check for Steam Client Updates when that command is available. After an update, restart the client completely. Security software may treat a replaced or updated executable as a new application, so a firewall rule that worked yesterday can become ineffective after the binary changes.

Allow Steam Through Firewall and Security Software

Rebuild the Windows Firewall App Rule

Open Windows Security > Firewall & network protection > Allow an app through firewall, then choose Change settings. Locate Steam and allow it on the network profile you are using. On a home network, that is normally Private. Avoid enabling Public access unless it is required and understood.

If the list contains duplicate Steam entries, entries pointing to an old drive, or rules created before Steam was moved, remove the stale entries and add the current steam.exe. The default path is often C:\Program Files (x86)\Steam\steam.exe, but a custom library or client installation can use another location.

Microsoft explains that allowing a specific app is safer than opening a port permanently because the app uses the needed ports only while required. [✅Source-5]

Do not turn off the firewall as a permanent fix. A brief test can identify the blocking layer, but protection should be restored immediately. Create a narrow rule for the official, digitally signed Steam executable instead of opening broad port ranges on a personal computer.

Check steamwebhelper.exe, Not Only steam.exe

The Store page is rendered by steamwebhelper.exe. Some security suites allow the main client while blocking the helper process that makes web requests. Because its folder can change with client updates, use Task Manager to find the active file:

  1. Open Steam and leave the failed Store tab visible.
  2. Open Task Manager and expand the Steam process group.
  3. Right-click a Steam Client WebHelper process.
  4. Select Open file location.
  5. Check the file’s digital signature and add only that official file to application-control rules when needed.

If a security product has separate controls for firewall, web shield, HTTPS scanning, behavior monitoring, or application control, the block may sit in any one of those modules.

Test Antivirus Web Inspection Carefully

Valve warns that antivirus software can affect both disk and network operations because it integrates deeply with the operating system. Valve also lists firewalls, security applications, VPN software, download accelerators, peer-to-peer tools, and other background programs as possible sources of Steam interference. [✅Source-6]

Pause one module at a time for a single Store test. If Steam begins working, turn the module back on and configure an app exception. This preserves protection and identifies the exact control that needs adjustment.

Likely Security Controls

  • Application firewall
  • HTTPS or TLS inspection
  • Web reputation filter
  • Behavior blocking
  • Parental-control filter

Safer Correction

  • Allow the signed executable
  • Remove stale duplicate rules
  • Update the security product
  • Limit the exception to Steam
  • Keep real-time protection active

Valve’s firewall guidance also notes that Steam may need to be reauthorized after a client update. [✅Source-7]

Check Proxy, VPN, DNS, and Filtering Settings

Turn Off an Unintended Manual Proxy

Open Settings > Network & internet > Proxy. Leave Automatically detect settings available unless the network requires another setup. Turn off Use a proxy server when it was enabled by mistake or belongs to software no longer used.

Do not remove a work or school proxy without permission. On a managed device, the setting may return through policy, and the correct fix belongs with the administrator.

Use a VPN Test to Diagnose, Not to Hide the Cause

Disconnect the VPN and retry Steam. VPN clients install network adapters and filter drivers that can affect only certain applications. If Error -138 disappears, update the VPN client, change its protocol, disable split-tunneling rules for Steam, or ask the VPN provider how to allow the client.

The opposite test is also useful: if Steam fails on the home connection but works on a trusted alternative network, the original router, DNS resolver, or ISP route deserves inspection. Avoid account purchases on unknown public Wi-Fi.

Flush the Windows DNS Client Cache

Open Terminal or Command Prompt as administrator and run:

ipconfig /flushdns

The command clears the DNS client resolver cache, including cached negative entries. Microsoft documents /flushdns as a DNS troubleshooting option. [✅Source-8]

Close and reopen Steam after the command. A DNS flush does not change the configured DNS provider and does not repair a firewall denial. It is useful when the Store domain recently resolved incorrectly or a local filter left a bad cached response.

Change DNS Only When the Comparison Test Supports It

Changing DNS is reasonable when Steam fails on one network, works through a mobile hotspot, and other signs point to name resolution or filtering. Record the current settings first. On a home PC using automatic configuration, return to Automatic (DHCP) if a forgotten manual DNS address is present.

Do not claim a public DNS service will always be faster or fix Error -138. The error is often an access-control problem, and a DNS change cannot override a local firewall rule.

Inspect the Hosts File for Steam Domains

Open Notepad as administrator and inspect:

C:\Windows\System32\drivers\etc\hosts

Look for lines containing steampowered.com, steamcommunity.com, or related Steam hostnames. Remove only entries you understand and did not intentionally create. Keep a backup before editing.

Microsoft notes that a modified Hosts file can override normal name resolution and cause website or network-resource access problems. [✅Source-9]

Reset Windows Networking Only After Targeted Checks Fail

Reset Winsock

Winsock is the Windows interface applications use for network communication. Security software, VPN clients, and damaged network providers can leave the Winsock catalog in an unusable state. Open an elevated Terminal or Command Prompt and run:

netsh winsock reset

Restart Windows afterward. Microsoft states that the reset returns the Winsock catalog to a clean state and removes custom layered service providers that can cause network problems. [✅Source-10]

Expected side effect: Software that installs network providers may need repair or reinstallation after a Winsock reset. This is why it belongs after firewall, proxy, and VPN checks rather than before them.

Reset TCP/IP When General Connectivity Is Also Unstable

Use a TCP/IP reset when browsers, launchers, or other applications also show network failures and the smaller fixes did not help:

netsh int ip reset resetlog.txt

Restart the computer. Microsoft explains that this reset rewrites TCP/IP and DHCP-related registry settings and has an effect similar to removing and reinstalling TCP/IP. Administrator rights are required. [✅Source-11]

Use the Windows Network Reset Screen Last

Open Settings > Network & internet > Advanced network settings > Network reset in Windows 11. Windows 10 places the control under Network & Internet > Status. Select Reset now only after saving network details and closing work.

Microsoft describes Network reset as a last step. It removes installed network adapters, reinstalls them after restart, and returns their settings to defaults. VPN clients, Hyper-V virtual switches, static IP settings, and custom DNS settings may need to be configured again. [✅Source-12]

Steam Ports and What Error 138 Usually Needs

A home user normally should not create manual inbound port-forwarding rules just to load the Store. Store pages rely mainly on standard outbound web traffic. Managed firewalls may need the official Steam port list.

TrafficPort or RangeRelevance
HTTPTCP remote port 80Standard web traffic and redirects
HTTPSTCP remote port 443Encrypted Store, account, and Community web traffic
Steam login and contentUDP and TCP remote ports 27015–27050Steam services beyond basic page rendering
Steam client and game trafficAdditional UDP ranges listed by ValveDownloads, game traffic, Remote Play, and related functions

Application allow rules are preferable on personal PCs. Broadly opening ports can expose more traffic than needed and may not fix a block aimed specifically at steamwebhelper.exe.

Repair or Reinstall Steam Without Deleting Installed Games

Back Up the Right Folders

Before reinstalling, fully exit Steam and copy these folders from the Steam installation directory to a safe location:

  • steamapps — installed game content and library metadata
  • userdata — account-specific local data, screenshots, and some configuration files

Cloud synchronization does not cover every game or every local file. Back up saves separately when a game stores them outside Steam’s folders.

Use Reinstallation as a Client Test

  1. Back up steamapps and userdata.
  2. Uninstall Steam through Windows Settings.
  3. Restart Windows.
  4. Install Steam from the official Steam website.
  5. Open the Store before restoring optional client files.
  6. Restore the backed-up folders and let Steam rediscover installed games.

If a clean client still shows Error -138 before old files are restored, reinstalling again is unlikely to help. Return to firewall, antivirus, proxy, VPN, and network tests.

Fixes That Often Waste Time or Create New Problems

Do Not Delete the Entire Steam Folder First

Error -138 concerns a web request. Removing game data can create a large redownload without correcting the security rule that denied access.

Do Not Permanently Disable Antivirus or Firewall Protection

A temporary test may identify the blocker. The lasting repair should be a narrow allow rule, a repaired security installation, or an updated filtering policy.

Do Not Open Every Steam Port on the Router

Port forwarding changes inbound routing and is rarely required for a Store page. Confirm the network type and use the official port list only when administering a controlled firewall.

Do Not Run Large Command Bundles Without Knowing Their Effects

Commands that release the IP address, reset TCP/IP, clear routes, reset Winsock, and change DNS all at once make the cause harder to identify. Apply one measured change, restart when required, and verify the result.

Common Questions About Steam Error Code 138

Is Steam Error Code 138 a server outage?

Not necessarily. Error -138 is associated with denied network access in the client’s web component. A server-side issue remains possible, but first compare the Store in an external browser, another device, and a separate trusted network.

Why do Steam games launch while the Store does not load?

Installed games can start from local files, while Store and Community pages depend on web requests made by Steam Client WebHelper. A rule can block the web helper without preventing local game launch.

Should steamwebhelper.exe be allowed through the firewall?

Yes, when it is the official digitally signed file launched from the Steam installation. Locate the active file through Task Manager rather than trusting an unknown copy found elsewhere.

Will clearing Steam web browser data delete games?

No. The control clears cached web files and cookies used by Steam’s embedded browser. It does not remove installed games or the Steam account.

Does clearing the download cache fix Error 138?

It can help when download state is also damaged, but it is not the closest match for a Store-only web access denial. Use Delete Web Browser Data first. Clearing the download cache may sign the client out.

Can a VPN cause Steam Error Code 138?

Yes. A VPN can add adapters, filtering drivers, proxy rules, or split-tunneling policies. Disconnect it for one test, then update or reconfigure it if Steam begins working.

Why did Error 138 start after a Steam update?

A client update can replace executable files or change their path. Firewall and antivirus rules may then treat Steam or Steam Client WebHelper as a different application and require authorization again.

What should be tried before reinstalling Steam?

Restart the client and Windows, delete Steam web browser data, rebuild firewall permissions, test antivirus web filtering, check proxy and VPN settings, flush DNS, and test another network. Reinstallation belongs near the end because it does not remove an external network block.

Can Error 138 be an account ban?

The error by itself does not indicate an account restriction. It describes a failed web request. Account notices should be checked through the official Steam Support area after normal Store access is restored.

Leave a Reply

Your email address will not be published. Required fields are marked *