Understanding Steam Error Code 118
Steam Error Code 118 manifests as a “Connection Timeout” message and indicates that the Steam client cannot establish a TCP handshake with Steam’s backend servers within the allotted time. Unlike DNS failures (Error 118-0), this error specifically signals that network routes exist but packets are being dropped at the transport layer, typically due to ISP-level packet inspection, incorrectly configured MTU sizes, or Steam’s CDNs being routed through a degraded BGP path.
Common Triggers on Windows 11/10
Windows 11’s integration with Xbox Game Pass and associated network services sometimes introduces overlapping TCP connections on ports Steam requires. Additionally, Windows 11’s Quality of Service (QoS) packet scheduler may deprioritize Steam’s outbound connections when gaming traffic is detected. ISP-level throttling during peak hours can also selectively timeout Steam’s CDN requests while allowing web browsing to function normally.
Fixes
1. Use Steam’s Built-In Network Debug Tool
Open Steam → Settings → Interface → Steam beta participation → Change to opt into the beta branch (which often contains network diagnostic updates). Then go to Steam → Settings → Network and run the Connection Diagnostic. Steam will test connectivity to its CDN nodes and report the specific failure point.
2. Adjust Windows QoS Settings
Press Win+R, type gpedit.msc, navigate to Computer Configuration → Windows Settings → QoS Packet Scheduler. Ensure no restrictive policies are active. Alternatively, open Device Manager → Network Adapters → [Your Adapter] → Advanced → QoS and disable any packet scheduling if available.
3. Set Steam to Use HTTP/1.1 Protocol
Steam defaults to HTTP/2 which can timeout on certain ISP routing paths. Navigate to Steam → Settings → Interface, scroll to the bottom, and check Enable HTTP/1.1 fallback. This forces Steam to use HTTP/1.1 which has wider compatibility with legacy routing infrastructure.
4. Change Steam Download Region
Open Steam → Settings → Downloads → Download Region. Switch to a different region (e.g., from US West to US East or a nearby country). Steam may be using a CDN with a degraded route to your location; switching forces DNS to resolve new CDN endpoints with potentially cleaner paths.
5. Flush DNS and Reset TCP/IP Stack
Open Command Prompt as Administrator:
netsh int ip reset && netsh winsock reset && ipconfig /flushdns && ipconfig /registerdns
Restart the computer. This clears stale BGP route cache entries and re-establishes the TCP/IP stack, resolving cases where Steam’s server IPs have changed but cached routes still point to decommissioned infrastructure.
6. Whitelist Steam in Windows Defender
Open Windows Security → Firewall & network protection → Allow an app through the firewall → Change settings. Add steam.exe and steamservice.exe from the Steam installation directory with Private and Public access.
Deep Diagnostic
Run netstat -an