Steam won't open on Windows 11

[BuG]

As per title. Ever since a combination of either Windows update or Steam, I cannot open Steam at all.

I can see the process in the task manager but no windows nothing. No error messages. I uninstalled/reinstalled a dozen times, tried everything I could find on the troubleshooting guides etc but no luck. Support could not help.

Wondering if anyone has any magic idea or if there is a way to enable some "forced" logging so that I could maybe get an idea what is going on and why it won't open?

Any help is appreciated (I just do not want to reinstall my machine just for that... :()

Thanks!

[PikaMug]

Originally posted by Iceira:

But you will never get a word from valve, dual card issue hase been there sense 20 years ago, we other see it at intel onboard with Nvidia card so long ago, nothing has change this, other then user now think valve will still fix this today.

It's likely we never get an official solution, but not impossible. How long people have been using dual cards for is irrelevant—reports of this particular issue started after the Steam client update.

Originally posted by REDACTED:

Also had this issue, have rolled back to 23H2 to fix it. Tried so many things, all the command line args, reinstalling Steam and all cache clears, tried three drivers (incl 551.86), network/netsock commands, disabling various Windows 11 features in 24H2, anti-virus exemption. Nothing would get the Steam Web Helper to load.

Did you use the Go back feature, or a System Restore point? If it's the latter, then you likely just reverted to an older version of Steam client.

Originally posted by Dettlaff:

In my case, reverting to version 23H2 did not solve the issue, and none of the suggestions from the forum thread worked.

Description of my PC (Laptop):

RAM: 16 GB DDR5
Video Memory: 8 GB
RAM Speed: 4800 MHz
Graphics Card: Nvidia GeForce RTX 4060
Processor : AMD Ryzen 7 7735H 4.7 GHz
SSD Capacity: 2 x 500 GB"

https://imgur.com/a/steam-wont-open-on-windows-11-even-after-reverting-to-version-23h2-rnY0reV

Ryzen 7 7735H features integrated graphics. Have you tried to temporarily disable the GeForce RTX 4060 and then open Steam? Easiest way to do this on a laptop should be through Device Manager.

[Iceira]

PikaMug you keep going, becuase i and other dont care if you install a old GPU card thats even worse then onboard even, not a steam issue and game devs.

i bet other are start to be tired of you use onboard crap office card , and you cant admit whatever plugincard assue its a 3D is better, again steam dont care what card you have.

i do not work for steam, but many have learn go ahead use a office card, not a steam issue and if you cant even start the games not a steam issue.

this is what many learn over the years have game requirements if you have surplus not a game devs issue or lesser.


you need to let it go i will start to report you for false information, i doubt steam will give a clue , its more yes they can see we are effect by it, but not a steam problem

and we are back at your lack of undrstanding in product support, steam did not tell you buy that pc or gpu cards. ( this is what we other have learn over many years with IT and gaming. ) you dont think i have not make mistake as gamers sure i do, you know what happend then you get education and work with IT , you get a reality check. all is Brand Support, gl go in the wrong place , and complain, you get head bite off, problem is you never seen this i bet , because we have to talk nicly here and all the company we work for., and see what that has help.

i'm tell you again and for the last time FIX your DUAL card issue, end of Debat.

next chat with you will be with a steam moderator.

problem is you never learn old pc core rules 1 gpu card, things you dont have learn from the past. ( its still standing as back to basic then things go wrong. ) its the old faulth finding that help us even over 20 years ago.

[PikaMug]

Originally posted by Iceira:

PikaMug you keep going, becuase i and other dont care if you install a old GPU card thats even worse then onboard even, not a steam issue and game devs.

i bet other are start to be tired of you use onboard crap office card , and you cant admit whatever plugincard assue its a 3D is better, again steam dont care what card you have.

i do not work for steam, but many have learn go ahead use a office card, not a steam issue and if you cant even start the games not a steam issue.

this is what many learn over the years have game requirements if you have surplus not a game devs issue or lesser.


you need to let it go i will start to report you for false information, i doubt steam will give a clue , its more yes they can see we are effect by it, but not a steam problem

and we are back at your lack of undrstanding in product support, steam did not tell you buy that pc or gpu cards. ( this is what we other have learn over many years with IT and gaming. ) you dont think i have not make mistake as gamers sure i do, you know what happend then you get education and work with IT , you get a reality check. all is Brand Support, gl go in the wrong place , and complain, you get head bite off, problem is you never seen this i bet , because we have to talk nicly here and all the company we work for., and see what that has help.

i'm tell you again and for the last time FIX your DUAL card issue, end of Debat.

next chat with you will be with a steam moderator.

problem is you never learn old pc core rules 1 gpu card, things you dont have learn from the past. ( its still standing as back to bacis then things go wrong. ) its the old faulth finding that help us even over 20 years ago.

Yes, I intend to keep helping others with this issue by keeping the facts straight, as I hope you would do, as well. What do old GPU cards have do with this? The problem is multiple cards; their age doesn't appear to matter?

Statistically, the best solution we've found thus far is disabling one of the graphics options. I would never recommend using an office card for gaming, but you must realize that not everyone can afford the latest hardware. Whichever card they have to disable, it doesn't take much processing power to open the Steam client. Once it's open to the point of launching games, the user can re-enable their other card if need be.

I can see you're frustrated. I'm not happy with this workaround, either, but it's all we've got at the moment. However, please do not threaten me with false reports; that in itself is punishable under Rules and Guidelines for Steam.

[[REDACTED]]

Originally posted by Iceira:

PikaMug you keep going, becuase i and other dont care if you install a old GPU card thats even worse then onboard even, not a steam issue and game devs.

i bet other are start to be tired of you use onboard crap office card , and you cant admit whatever plugincard assue its a 3D is better, again steam dont care what card you have.

i do not work for steam, but many have learn go ahead use a office card, not a steam issue and if you cant even start the games not a steam issue.

this is what many learn over the years have game requirements if you have surplus not a game devs issue or lesser.


you need to let it go i will start to report you for false information, i doubt steam will give a clue , its more yes they can see we are effect by it, but not a steam problem

and we are back at your lack of undrstanding in product support, steam did not tell you buy that pc or gpu cards. ( this is what we other have learn over many years with IT and gaming. ) you dont think i have not make mistake as gamers sure i do, you know what happend then you get education and work with IT , you get a reality check. all is Brand Support, gl go in the wrong place , and complain, you get head bite off, problem is you never seen this i bet , because we have to talk nicly here and all the company we work for., and see what that has help.

i'm tell you again and for the last time FIX your DUAL card issue, end of Debat.

next chat with you will be with a steam moderator.

problem is you never learn old pc core rules 1 gpu card, things you dont have learn from the past. ( its still standing as back to bacis then things go wrong. ) its the old faulth finding that help us even over 20 years ago.

What are you on about. I have a RTX 4090 and i9 13900k and have this exact issue. And it only appears when you update to 24H2. Disappears when you revert back, reappears when you update back to 24H2 across 3 drivers. Occurs with or without the iGPU enabled in BIOS. I also work in IT if that for you helps clarify that this is a real issue.

[Kaizoku]

Originally posted by BuG:

Appreciate the suggestion but I have already used DDU several times to re-install the drivers and no differences. I do not think it is a graphic drivers issues at this point

I'm also seeing this error in another log file:

[2024-06-11 23:20:41] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket error
[2024-06-11 23:20:41] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket unexpectedly closed

[1970-01-01 01:00:00] Client version: no bootstrapper found


not sure what they mean..

I am getting this as well. It has to do with 24h2 and Websocket's event. Cloudflare's wrap proxy doesn't work on this version. It seems like something was changed in the way Websocks works.

"[2024-06-25 02:48:46] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket unexpectedly closed
[2024-06-25 02:48:46] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket unexpectedly closed
[2024-06-25 02:48:46] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket error
[2024-06-25 02:48:46] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket error
[2024-06-25 02:48:47] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: failed to reach open state
[2024-06-25 02:48:47] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: connect attempt failed: 2 - failed to reach open state

[1211/193504.292:INFO:CONSOLE(2)] "TypeError: Cannot read property 'CompositionStateStore' of null", source: https://steamloopback.host/156.js (2)
[1211/193504.293:INFO:CONSOLE(2)] "Uncaught (in promise) TypeError: Cannot read property 'CompositionStateStore' of null", source: https://steamloopback.host/libraryroot.js (2)
[1211/193554.649:ERROR:network_service_instance_impl.cc(264)] Network service crashed, restarting service.
[1211/205817.826:INFO:crash_reporting.cc(248)] Crash reporting enabled for process: browser
[1211/205818.653:INFO:crash_reporting.cc(248)] Crash reporting enabled for process: utility
[1211/210018.644:INFO:crash_reporting.cc(248)] Crash reporting enabled for process: gpu-process
[1211/210755.911:WARNING:dns_config_service_win.cc(700)] Failed to read DnsConfig.
[1211/210755.915:WARNING:dns_config_service_win.cc(700)] Failed to read DnsConfig.
[1211/213818.834:WARNING:dns_config_service_win.cc(700)] Failed to read DnsConfig.
[1211/213818.834:WARNING:dns_config_service_win.cc(700)] Failed to read DnsConfig.


You can check Steam/Logs webhelper log.
"

[Iceira]

Originally posted by REDACTED:

Originally posted by Iceira:

PikaMug you keep going, becuase i and other dont care if you install a old GPU card thats even worse then onboard even, not a steam issue and game devs.

i bet other are start to be tired of you use onboard crap office card , and you cant admit whatever plugincard assue its a 3D is better, again steam dont care what card you have.

i do not work for steam, but many have learn go ahead use a office card, not a steam issue and if you cant even start the games not a steam issue.

this is what many learn over the years have game requirements if you have surplus not a game devs issue or lesser.


you need to let it go i will start to report you for false information, i doubt steam will give a clue , its more yes they can see we are effect by it, but not a steam problem

and we are back at your lack of undrstanding in product support, steam did not tell you buy that pc or gpu cards. ( this is what we other have learn over many years with IT and gaming. ) you dont think i have not make mistake as gamers sure i do, you know what happend then you get education and work with IT , you get a reality check. all is Brand Support, gl go in the wrong place , and complain, you get head bite off, problem is you never seen this i bet , because we have to talk nicly here and all the company we work for., and see what that has help.

i'm tell you again and for the last time FIX your DUAL card issue, end of Debat.

next chat with you will be with a steam moderator.

problem is you never learn old pc core rules 1 gpu card, things you dont have learn from the past. ( its still standing as back to bacis then things go wrong. ) its the old faulth finding that help us even over 20 years ago.

What are you on about. I have a RTX 4090 and i9 13900k and have this exact issue. And it only appears when you update to 24H2. Disappears when you revert back, reappears when you update back to 24H2 across 3 drivers. Occurs with or without the iGPU enabled in BIOS. I also work in IT if that for you helps clarify that this is a real issue.

Because you do not get it, MS do not fix other Brands driver issue, or gpu choise. and they dont care if you rollback, another MS choise, or you wont be allowed to do it.

and soon watchout for hot fixes i doubt you even notice then is been done, because most steam user do not notice anything here.

so what rock do you live under, a few user with the issue and now you think you have a point here no you dont.

i said it again look more like a backsit moderator. you was not here then OP made post and was in troube date BuG 12 Jun @ 8:14pm where was you back then, nowhere, to little and to late to join and did not read anything here.

[Iceira]

And you forget how many win11 user steam has, so it cant be a win11 update issue alone. and this is why steam want all suggestion in all subject , problem is dont mean we can solve it here as users. and steam can then it work for so many others.

[[REDACTED]]

Originally posted by Iceira:

And you forget how many win11 user steam has, so it cant be a win11 update issue alone. and this is why steam want all suggestion in all subject , problem is dont mean we can solve it here as users. and steam can then it work for so many others.

Obviously we should lodge it directly with Steam support as individual users sk they can collect data, identify patterns and pass it to the team that can fix the issue. That I agree. Just seems your gatekeeping the issues existence, even if it’s 5%, 10%, 2% of 24H2 users that’s going to be an avalanche on general release, better to make notice of it now than let it fester until that day.

[[REDACTED]]

Originally posted by Kaizoku:

Originally posted by BuG:

Appreciate the suggestion but I have already used DDU several times to re-install the drivers and no differences. I do not think it is a graphic drivers issues at this point

I'm also seeing this error in another log file:

[2024-06-11 23:20:41] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket error
[2024-06-11 23:20:41] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket unexpectedly closed

[1970-01-01 01:00:00] Client version: no bootstrapper found


not sure what they mean..

I am getting this as well. It has to do with 24h2 and Websocket's event. Cloudflare's wrap proxy doesn't work on this version. It seems like something was changed in the way Websocks works.

"[2024-06-25 02:48:46] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket unexpectedly closed
[2024-06-25 02:48:46] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket unexpectedly closed
[2024-06-25 02:48:46] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket error
[2024-06-25 02:48:46] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket error
[2024-06-25 02:48:47] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: failed to reach open state
[2024-06-25 02:48:47] SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: connect attempt failed: 2 - failed to reach open state

[1211/193504.292:INFO:CONSOLE(2)] "TypeError: Cannot read property 'CompositionStateStore' of null", source: https://steamloopback.host/156.js (2)
[1211/193504.293:INFO:CONSOLE(2)] "Uncaught (in promise) TypeError: Cannot read property 'CompositionStateStore' of null", source: https://steamloopback.host/libraryroot.js (2)
[1211/193554.649:ERROR:network_service_instance_impl.cc(264)] Network service crashed, restarting service.
[1211/205817.826:INFO:crash_reporting.cc(248)] Crash reporting enabled for process: browser
[1211/205818.653:INFO:crash_reporting.cc(248)] Crash reporting enabled for process: utility
[1211/210018.644:INFO:crash_reporting.cc(248)] Crash reporting enabled for process: gpu-process
[1211/210755.911:WARNING:dns_config_service_win.cc(700)] Failed to read DnsConfig.
[1211/210755.915:WARNING:dns_config_service_win.cc(700)] Failed to read DnsConfig.
[1211/213818.834:WARNING:dns_config_service_win.cc(700)] Failed to read DnsConfig.
[1211/213818.834:WARNING:dns_config_service_win.cc(700)] Failed to read DnsConfig.


You can check Steam/Logs webhelper log.
"

Maybe the -tcp launch argument could help here

[Shauck]

I'm not sure if this is the case for everyone, but I noticed I couldn't open steam after switching to BBR2 congestion provider on W11 24h2. Switching it back to CTCP or CUBIC fixed the issue for me. The command below is used to switch your congestion provider.

 netsh int tcp set supplemental Internet CongestionProvider=ctcp 

[RPG Gamer Man]

This is why i do not update to the newest drivers for graphics cards. They tend to be more buggy lately.

Also, i am on windows 11 atm,. the most updated version of it, and i do not have the most updated graphics driver. My money is that a graphics driver is causing this issue. In fact, nvidia has done this in the past with faulty graphics drivers on windows. Just google it and you will see someone talking about it.

[KyuKyu]

Folks, try netsh int tcp set supplemental internet congestionprovider=ctcp in admin terminal - helped me

[Fryderyk Huang]

Originally posted by KyuKyu:

Folks, try netsh int tcp set supplemental internet congestionprovider=ctcp in admin terminal - helped me

Hell no, that actually works!

[Hazza]

Originally posted by Shauck:

I'm not sure if this is the case for everyone, but I noticed I couldn't open steam after switching to BBR2 congestion provider on W11 24h2. Switching it back to CTCP or CUBIC fixed the issue for me. The command below is used to switch your congestion provider.

 netsh int tcp set supplemental Internet CongestionProvider=ctcp 

OMFG THANK YOU

[Stitch]

Originally posted by Shauck:

I'm not sure if this is the case for everyone, but I noticed I couldn't open steam after switching to BBR2 congestion provider on W11 24h2. Switching it back to CTCP or CUBIC fixed the issue for me. The command below is used to switch your congestion provider.

 netsh int tcp set supplemental Internet CongestionProvider=ctcp 

oh wow I tried everything but this actually did it!! thank you