Alle diskussioner > Steam-fora > Help and Tips > Trådoplysninger
spyderDFX 23. mar. kl. 14:30
Steam encountered an unexpected error during startup (0x3000)
Hi. So, after some March update, I'm getting this error on startup.

I can rollback to an older version using those steps https://test1.login.steam.hlxgame.cc/discussions/forum/1/592891465952144378/#c592891465952179735
and the older version works fine.
But I'm afraid that using this older version can cause some issues with games.

Steam\logs\webhelper.txt says:
SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket error
SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: websocket error
SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: failed to reach open state
SP Shared JS Context-'SharedJSCo': WARNING: https://steamloopback.host/library.js:2: connect attempt failed: 2 - failed to reach open state

I added Steam Client WebHelper to firewall exceptions, I tried to reset net interfaces via "netsh int ip reset" command - nothing helped
< >
Viser 1-9 af 9 kommentarer
Jan Jommeke 29. mar. kl. 4:04 
Same
#1
spyderDFX 31. mar. kl. 5:50 
I managed to get rid of this error by allowing absolutely ALL connections for steam and webhelper processes. Not sure if this is expected behavior. Steam supposed to work with OutgoingOnly
#2
FastSlowGrey 7. apr. kl. 18:18 
Oprindeligt skrevet af spyderDFX:
I managed to get rid of this error by allowing absolutely ALL connections for steam and webhelper processes. Not sure if this is expected behavior. Steam supposed to work with OutgoingOnly

Hi, which specific settings did you end up changing?
#3
gls1 9. apr. kl. 10:39 
I also had the 0x3000 error. For me, for unknown reasons (possibly a program not cleaning up after itself?) the system was set up to use a local proxy. Settings -> Network and Internet -> Proxy -> turn off manual proxy.
#4
Ragnar Ironhide 7. maj kl. 19:04 
Well, ChatGPT fixed this issue for me real fast. Go to your steam folder->steamapps then delete the entire shadercache folder then run steam.
#5
savexu 16. aug. kl. 23:21 
Oprindeligt skrevet af gls1:
I also had the 0x3000 error. For me, for unknown reasons (possibly a program not cleaning up after itself?) the system was set up to use a local proxy. Settings -> Network and Internet -> Proxy -> turn off manual proxy.
This helped me, it was all due to proxies from Fiddler
#6
Not a Human 19. aug. kl. 16:19 
If you've encountered this issue, this solution should help (it worked for me).

First, clear the entire shadercache and appcache folders in the main Steam directory. Then, check if you're using custom DNS servers or a proxy—if so, temporarily disable them. For example, I use AdGuard for Windows, and once I disabled it, Steam started working properly and was no longer blocked at startup.

I hope this helps someone! <3
#7
joojeene 30. sep. kl. 22:33 
Deleting everything under appcache helped me
#8
Yupnitski 10. dec. kl. 12:36 
Hi!
Got this same error today.
I tried few of the solutions posted on the webs, but nothing did the trick (clean re-install or suspending steam.exe when steamwebhelper is booting).
It seemed my VPN app somehow suddenly started blocking steamwebhelper. Made an exception in the VPN for steamwebhelper and it worked! I had done the same for steam.exe before, so it might be a contributing factor, but not the only solution for this error.
#9
< >
Viser 1-9 af 9 kommentarer
Per side: 1530 50

Alle diskussioner > Steam-fora > Help and Tips > Trådoplysninger
Dato opslået: 23. mar. kl. 14:30
Indlæg: 9
Start en ny diskussion

Diskussionsregler og retningslinjer