On screen: Failed to load web page (unknown error) — Error Code: -105
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
This is not a Steam platform code. It comes from the Chromium browser embedded in the Steam client, with the sign inverted: Steam's -105 is Chromium's ERR_NAME_NOT_RESOLVED.
Chromium's description: the host name could not be resolved. This is DNS — your machine could not turn Steam's address into a number.
Which means the rest of Steam is very likely working. Your library opens, your games launch, and a part of the client that happens to be a web browser cannot load a page.
Run nslookup store.steampowered.com. If it does not resolve, it is DNS and nothing about Steam. If it resolves and the client still will not load the page, the client's browser cache or an ad blocker is interfering.
Steam's client embeds a Chromium browser, and these numbered codes are Chromium's own network errors with the sign flipped. We verified each one against Chromium's error list rather than guessing. That is why the on-screen message is the same unhelpful line for all of them while the causes are completely different — and why most of them mean Steam is working fine. Valve publishes no article for this code. Worth knowing: Valve publishes no status page of its own. The link in their own support article now redirects to a sales chart. That gap is why we measure Steam ourselves, by probing its public endpoints every five minutes.
This is not a Steam platform code. It comes from the Chromium browser embedded in the Steam client, with the sign inverted: Steam's -105 is Chromium's ERR_NAME_NOT_RESOLVED.
This error is produced locally. It does not appear because the service is down, so the fixes below are worth working through in order.
Start with: Change DNS to 1.1.1.1 or 8.8.8.8. The direct fix for a resolution failure.