Steam client no longer loads after latest update

[ThreeSon]

Windows 10 LTSC 21H2

After applying the latest big update that dropped today, now my Steam client won't start and no game can be played. Trying to launch a game directly from a desktop shortcut doesn't work either. The Steam client window appears, but is all black and gives a (not responding) error in the title bar.

I tried "resetting" the Steam installation by deleting everything in the Steam directory except steam.exe and the steamapps folder. After that, the Steam client will load once, on the next attempt. However after exiting Steam, it will not boot again.

EDIT: Although the client will load on the first attempt after clearing out the Steam directory, the Library window can't be used - nothing in the window is clickable.

[ProXicT.]

Same issue here. I'm on linux, launching Steam via wine and the problem seems to be that Steam switched to SDL3 from SDL2, but gldriverquery.exe still tries to load SDL2.dll, which is no longer shipped with Steam.

[bSun Gyarados]

I have the same issue only difference is that any library page (home, collection, download) will show up and "shifts" off the screen and can not be interacted with. going into big picture makes the main menu do the same. every other page works just fine. Windows 10

EDIT: after try to interact with my runaway library i figured out a few things. first off it only moves to the bottom of the screen as long as my mouse is over it. next off i can interact with it. i was able to click on a update for a game. not i still cant play anything due to the fact the screen moves way to fast to even have a chance to hit play.

[UN0W3N]

Same issue here, Steam Client is "not responding" after the latest update from today. Windows 10.

[PhrostB]

same here. steam dead yo..

[Captain Arctica]

+1

[Captain Arctica]

deleted appcache folder
restarted the computer
everything worked

[luckz]

Sounds a lot like https://steamcommunity.com/groups/SteamClientBeta/discussions/0/3710433479212267804/ and/or https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3710433479209089860/ from the end of last year.
(Coincidentally my friend also has a broken hardware survey on this new version.)

[ThreeSon]

Originally posted by Captain Arctica:

deleted appcache folder
restarted the computer
everything worked

This seemed to work for me for a couple of attempts, but then on the third try launching the Steam client, I ran into the same problem - all black client window and it just hangs there. After that I have to repeat the whole process to get Steam to launch again.

[Lulu Rainsong]

LTSC clients aren't supported, you'll have to reinstall Windows 10 using offline media.

[UN0W3N]

Originally posted by Shizune Hakamichi:

LTSC clients aren't supported, you'll have to reinstall Windows 10 using offline media.

I call BS on that, been using Enterprise for as long as I've used Steam as well.

[TS2]

Originally posted by ProXicT.:

Same issue here. I'm on linux, launching Steam via wine and the problem seems to be that Steam switched to SDL3 from SDL2, but gldriverquery.exe still tries to load SDL2.dll, which is no longer shipped with Steam.

Steam Client Beta 01/31/2023 user here. Searching for the SDL .dlls turned up ones for both SDL3 and SDL2 for some reason. Seems the migration may have only been partial in nature, and unfinished.

Thanks to SDL2 retention, the Steam client still loads for me, but I will check to confirm whether this is the direct source of breakage later.

[Seb]

Same issue

[TS2]

Originally posted by TS2:

Originally posted by ProXicT.:

Same issue here. I'm on linux, launching Steam via wine and the problem seems to be that Steam switched to SDL3 from SDL2, but gldriverquery.exe still tries to load SDL2.dll, which is no longer shipped with Steam.

Steam Client Beta 01/31/2023 user here. Searching for the SDL .dlls turned up ones for both SDL3 and SDL2 for some reason. Seems the migration may have only been partial in nature, and unfinished.

Thanks to SDL2 retention, the Steam client still loads for me, but I will check to confirm whether this is the direct source of breakage later.

Sadly, even after reverting to the Stable build version, I cannot replicate this. Something must be affecting those whom are solely updating from the December Stable build to the January one; not those on the Beta build that reverted to it or were otherwise using it.

[TS2]

Okay, I managed to find something in Steam/logs/sitelicense_log.txt and content_log.txt that may point to the cause of this.

[2023-02-02 08:26:37] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (0.0.0.0:0 / 0.0.0.0:0, host: edge.steam-dns.top.comcast.net): Failed to get manifest request Code for depot 229004 manifest 5220958916987797232 - No Connection (3) - continuing without it
[2023-02-02 08:26:37] HTTPS (CDN,64) - edge.steam-dns.top.comcast.net ([2001:558:fe2e:82::2]:443 / [2001:558:fe2e:82::2]:443, host: edge.steam-dns.top.comcast.net): edge.steam-dns.top.comcast.net/depot/229004/manifest/5220958916987797232/5 - received 401 (Unauthorized) HTTP response
[2023-02-02 08:26:37] HTTPS (CDN,64) - edge.steam-dns.top.comcast.net ([2001:558:fe2e:82::2]:443 / [2001:558:fe2e:82::2]:443, host: edge.steam-dns.top.comcast.net): Received 401 (Unauthorized) HTTP response for depot 229004
[2023-02-02 08:26:37] HTTPS (CDN,64) - edge.steam-dns.top.comcast.net ([2001:558:fe2e:82::2]:443 / [2001:558:fe2e:82::2]:443, host: edge.steam-dns.top.comcast.net): Closing connection
[2023-02-02 08:26:37] Created download interface of type 'CDN' (2) to host f3b7q2p3.ssl.hwcdn.net (f3b7q2p3.ssl.hwcdn.net)
[2023-02-02 08:26:37] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (0.0.0.0:0 / 0.0.0.0:0, host: edge.steam-dns.top.comcast.net): AuthenticateDepotID (229004) - Success!
[2023-02-02 08:26:57] HTTP (CDN,64) - edge.steam-dns.top.comcast.net (0.0.0.0:0 / 0.0.0.0:0, host: edge.steam-dns.top.comcast.net): Failed to get manifest request Code for depot 229004 manifest 5220958916987797232 - No Connection (3) - continuing without it
[2023-02-02 08:26:57] HTTPS (CDN,64) - edge.steam-dns.top.comcast.net ([2001:558:fe2e:84::2]:443 / [2001:558:fe2e:84::2]:443, host: edge.steam-dns.top.comcast.net): edge.steam-dns.top.comcast.net/depot/229004/manifest/5220958916987797232/5 - received 502 (Bad Gateway) HTTP response
[2023-02-02 08:26:57] HTTPS (CDN,64) - edge.steam-dns.top.comcast.net ([2001:558:fe2e:84::2]:443 / [2001:558:fe2e:84::2]:443, host: edge.steam-dns.top.comcast.net): Closing connection
[2023-02-02 08:26:58] HTTP (CDN,35) - google2.cdn.steampipe.steamcontent.com (0.0.0.0:0 / 0.0.0.0:0, host: google2.cdn.steampipe.steamcontent.com): AuthenticateDepotID (229004) - Success!


It seems that the Stable Steam client is failing to phone home to the Steam server backend for even simple things such as clearing the download cache and reinstalling Steamworks Common Redistributables.

[UN0W3N]

When will this get fixed? Deleting the appcache folder didn't help one bit, not even restarting. I can no longer use the Steam client. First time this happens to me in 8 years of Steam membership.

How long can it take for Valve to realize they screwed up the update from last night, bleeding February and rollback the previous version or whatever?