I have encountered many posts with users having problems opening or updating steam, that their steam client is stuck at the updating/connectiong to x user screen, hangs and then crashes.

Now their is a simple fix to this problems which does not involve DELETING 'CLIENTREGISTRY.BLOB'. I repeat it does not involve deleting the frigging file. Not every user has lots of bandwidth and all it does is force you to update steam over an over again but sometimes to no avail.

Here's what you do...
1.) install a small software tcpview from the Internet. (if you need help Even with that, well then good luck using the Internet in the future)
2.) Run steam and tcpview.exe
3.) There will be list of processes in the tcpview window, locate steam (just click on any process and type s - t - e - a - m, Voila magic, their is the steam process)
4.) Now check the process protocol, it's the adjacent column, for UDP or TCP.
5.) Right Click on the process with TCP protocol and click 'CLOSE CONNECTION'
6.) In case their are no recieved bytes in the column to the extreme right after few seconds, repeat Step 5 again. You might have to do this couple of times to get it right.

What tcpview's close connection basically does is terminates the connection with the current IP and reconnects you to another IP of steam server, which solves the problem of Ill connection.

In case you see only see the process with UDP protocol, dont panic, turn off steam and open it again till you start seeing the TC Protocol process.

Hope this will help many user, it's also helpful if Steam is stuck at x% of updating.

1 decade ago

Comment has been collapsed.

Closed 1 decade ago by crazyseeder.