Steam: Error Code 118 Fix – Store and Community Loading

Steam Error Code 118 appears when the client cannot load web content from the Store, Community, profile pages, news panels, or other browser-based sections. The message often states that the server may be offline or the computer may not be connected to the internet. The connection can still be partly functional: installed games may launch, friends may appear online, and downloads may continue while Store and Community remain unavailable.

Valve’s network troubleshooting material notes that proxies and restricted networks can block ports needed by Steam. The client uses ordinary web traffic as well as Steam-specific traffic, so a network may permit one function and block another. [✅Source-1]

Symptoms That Point to Error Code 118

Error Code 118 usually affects content drawn from Steam’s web services rather than every part of the desktop client. The exact pattern helps narrow the fault before any reset is attempted.

What the Error Does Not Prove

• It does not prove that the entire Steam platform is offline.
• It does not prove that the account is suspended or restricted.
• It does not normally indicate damaged game files.
• It does not mean Windows has lost all internet connectivity.
• It does not automatically require Steam reinstallation.

Why Steam Store and Community Stop Loading

Steam Client WebHelper Is Stuck

The modern Steam interface relies on separate Steam Client WebHelper processes for browser-based panels. A stalled process can leave the Library partly usable while Store, Community, profile, and news content fail. Valve’s support page for an unresponsive Steamwebhelper advises restarting Steam as the first response. [✅Source-2]

Repeated WebHelper crashes can also come from damaged cache data, security software injection, GPU rendering trouble, or a broken client update. Error 118 alone does not identify which one occurred, so test the browser and network before changing Steam files.

DNS Cannot Resolve a Steam Hostname Correctly

DNS converts names such as store.steampowered.com into IP addresses. A stale local record, an unavailable DNS server, or filtering DNS can prevent Steam from locating the destination even while already-open services continue to work.

Windows provides ipconfig /flushdns to clear the local resolver cache. Microsoft also recommends checking proxy settings and DNS reachability when a computer is connected to Wi-Fi but web access is not working correctly. [✅Source-3]

A VPN, Proxy, or Filter Changes the Route

A VPN sends Steam traffic through another exit location. A proxy may inspect or forward web requests. DNS filters, parental controls, ad blockers, and security gateways can block a Steam hostname or a content delivery address. These tools may affect the Store and Community without stopping game launches.

Do not permanently remove a required company or school proxy. Test on an unrestricted personal connection instead, or ask the network administrator whether Steam web domains and required ports are permitted.

The Firewall Allows Steam Incompletely

Steam is updated regularly, and executable paths or signatures may be re-evaluated by a firewall or security suite. An old allow rule can stop matching, or one Steam component may be permitted while steamwebhelper.exe is blocked.

Valve advises giving Steam executables permission for TCP and UDP communication when firewall software asks. [✅Source-4]

The Network Blocks Required Traffic

Steam’s official port list includes TCP 80 for HTTP, TCP 443 for HTTPS, and TCP and UDP 27015–27050 for login and content-related operation. Other functions use additional ranges, including UDP 27000–27250 for game traffic and UDP 4380. [✅Source-5]

Error 118 on Store and Community is especially connected to web access over ports 80 and 443. Opening every Steam port on a home router is usually unnecessary for a normal outbound client. On managed networks, only the administrator should change gateway rules.

The Hosts File Overrides Normal DNS

The Windows Hosts file can force a hostname to a chosen address before normal DNS lookup. Old blocking entries for Steam domains can therefore direct requests to an invalid address or the local computer.

Microsoft states that a modified Hosts file can override normal name resolution and cause website connectivity problems. The usual path is C:\Windows\System32\drivers\etc\hosts. [✅Source-6]

Steam or a Regional Route Is Temporarily Unavailable

When the same failure appears on several devices and several networks, a local Windows repair becomes less likely to help. The issue may involve Steam’s web service, a content delivery route, or regional provider routing. Wait briefly and retest before changing system settings, especially when the error began suddenly without any local change.

Repair Steps in the Right Order

1. Separate a Steam Client Fault from a Network Fault

1. Exit Steam.
2. Open store.steampowered.com in a normal browser.
3. Open steamcommunity.com.
4. Repeat the test in a private browsing window.
5. If possible, repeat it on another device using the same network.

2. Close Every Steam Process

Closing the main window may leave Steam running in the notification area. Use Steam > Exit. Then open Task Manager and check for steam.exe and steamwebhelper.exe. End remaining Steam processes only after games and downloads have stopped.

Start Steam normally. Avoid running several repair changes at once; one change at a time makes the cause visible.

3. Restart the Router Correctly

Disconnect the router or combined modem-router from power for about 30 seconds. Reconnect it and wait until the internet indicator returns to its normal state. This clears temporary routing and DNS-forwarder state without erasing the router configuration.

4. Remove Unneeded Proxy and VPN Routing

Disable a Manual Windows Proxy

1. Open Settings.
2. Select Network & internet.
3. Select Proxy.
4. Keep Automatically detect settings enabled.
5. Turn off Use a proxy server only when no administrator requires it.

Test Without a VPN

Disconnect the VPN, fully restart Steam, and test Store and Community. If the error disappears, change the VPN server or protocol, or exclude Steam from the tunnel if the VPN supports split tunneling. Do not use an unknown free proxy as a repair method.

5. Flush DNS and Renew the Address

First try the smallest DNS repair:

1. Exit Steam.
2. Search for Command Prompt.
3. Select Run as administrator.
4. Run ipconfig /flushdns.
5. Start Steam and test again.

If the computer also has wider connection trouble, run these commands in the listed order:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart Windows after the Winsock and TCP/IP reset. The release command temporarily removes the current DHCP address, so do not run it during a remote session unless another connection method is available.

6. Test DNS Resolution Directly

Open Command Prompt and run:

nslookup store.steampowered.com
nslookup steamcommunity.com

A normal result shows one or more resolved addresses. A timeout, server failure, or repeated inability to resolve both names points toward the configured DNS server or a network filter.

To compare with another resolver, temporarily set DNS through the Windows network adapter settings. Use only a known provider, record the original setting, and return to Automatic (DHCP) if the test makes no difference.

7. Review Firewall Access Without Opening Broad Ports

1. Open Windows Security.
2. Select Firewall & network protection.
3. Select Allow an app through firewall.
4. Select Change settings.
5. Confirm that Steam is allowed for the active network profile.
6. If Steam is missing, use Allow another app and select the installed Steam executable.

Microsoft notes that allowing a known application is safer than leaving a port permanently open. A port rule remains available until it is removed, while an allowed application uses its required access when running. [✅Source-7]

8. Rebuild the Steam HTML Cache

Use this step when web pages work in a normal browser but fail inside Steam.

1. Exit Steam and end any remaining steamwebhelper.exe processes.
2. Press Windows+R.
3. Enter %LOCALAPPDATA%\Steam.
4. If htmlcache exists, rename it to htmlcache.old.
5. Start Steam and allow the client to rebuild the folder.

Renaming is safer than immediate deletion because it leaves a copy available during testing. Once Steam has worked normally for several sessions, the old folder can be removed.

9. Clear the Steam Download Cache

This cache is mainly connected to downloads and local Steam configuration, so it sits later in the order for Error 118. It may still help when the client began failing after an interrupted update or when several client functions behave incorrectly.

1. Open Steam > Settings.
2. Select Downloads.
3. Select Clear Download Cache.
4. Sign in again if Steam requests account credentials.

Valve states that the command is available under the Downloads settings page. [✅Source-8]

10. Inspect the Windows Hosts File

Open Notepad as administrator, then open:

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

Look for lines containing steampowered.com, steamcommunity.com, steamstatic.com, or other Steam-related names. A line that maps one of these names to 127.0.0.1, 0.0.0.0, or an unfamiliar fixed address can block access.

Remove only entries you understand or restore the default Hosts file using Microsoft’s documented process. Save a backup before editing. Corporate devices may intentionally use custom entries.

11. Check Security Filters and Parental Controls

Web protection modules can inspect HTTPS traffic, filter categories, or block individual domains. Check antivirus web shields, family safety tools, router parental controls, DNS filtering services, and browser-level filtering software.

Prefer a temporary test rather than uninstalling protection. Disable one web-filtering module for a few minutes, restart Steam, test, and enable the module again. If that identifies the cause, add only the official Steam executable or domain exception required by that product.

12. Update or Repair the Steam Client

Open the Steam menu and check for a client update. If the interface cannot reach the update control, exit Steam, download the current installer from Steam’s official site, and run it over the existing installation. Keep the steamapps and userdata folders intact.

A full uninstall should remain the final local step. An incorrect uninstall method can remove installed game data, and reinstalling cannot repair a router, DNS, proxy, or provider route.

Advanced Checks for Persistent Error 118

Compare IPv4 and IPv6 Behavior

Run these commands:

ping -4 store.steampowered.com
ping -6 store.steampowered.com

Some Steam hosts may not answer ping, so packet loss alone is not proof of failure. The useful detail is whether name resolution returns an IPv4 or IPv6 address and whether the problem changes when another network is used. Do not disable IPv6 permanently based only on Error 118.

Trace the Route

tracert store.steampowered.com
tracert steamcommunity.com

A trace may stop because routers ignore diagnostic packets, yet a repeated failure near the first hop can still point toward the local router or provider. A failure much later in the path may reflect upstream routing. Compare the trace with a phone hotspot before drawing a conclusion.

Test HTTPS Outside Steam

PowerShell can test whether the web endpoint answers:

Test-NetConnection store.steampowered.com -Port 443
Test-NetConnection steamcommunity.com -Port 443

TcpTestSucceeded: True means a TCP connection to port 443 was established. It does not verify the entire web page, account session, certificate chain, or Steam client rendering process. A false result on one network and a true result on another strongly points toward the first network path.

Check the System Clock

HTTPS depends on certificate validity periods. Open Settings > Time & language > Date & time, enable automatic time and time zone when appropriate, then select Sync now. This is more relevant when browsers show certificate warnings alongside Steam failures.

Use a Clean Boot Only After Simpler Tests

A clean boot can reveal a third-party service that injects into web traffic or Steam processes. It is an advanced isolation step, not a routine fix. Record disabled services, keep Microsoft services enabled, and restore normal startup after testing.

What to Record Before Contacting Support

• The full Error Code 118 message and when it first appeared.
• Whether Store and Community work in a normal browser.
• Whether the problem follows the computer to another network.
• Whether another device fails on the same network.
• Results from nslookup and Test-NetConnection.
• VPN, proxy, DNS filter, antivirus web shield, and firewall products in use.
• The Steam client version and Windows version.

Fixes That Usually Waste Time

Verifying Every Game File

Error 118 affects Steam web content, not one game’s installed files. File verification is relevant when a game crashes, misses assets, or cannot start. It is not a direct repair for Store and Community loading.

Forwarding Every Steam Port on a Home Router

Outbound web access normally does not require broad manual port forwarding. Opening unnecessary inbound rules adds exposure and can hide the real issue. Start with the application firewall rule and the specific network policy.

Deleting the Entire Steam Folder

This can remove installed games, screenshots, local configuration, and account-related local data. Test browser access, DNS, proxy, firewall, WebHelper, and cache before considering reinstallation.

Changing Several Network Settings at Once

Simultaneous changes make verification impossible. Change one item, restart the relevant component, test Store and Community, and record the result. Small steps expose the cause faster.

Common Questions About Steam Error Code 118