You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steam client version (build number or date): Jun 4 2020
Distribution (e.g. Ubuntu): Debian unstable
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
Please describe your issue in as much detail as possible:
Steam client is updating itself in background even when I playing online games, in a slow Internet connection.
Now do the math and you will see that Steam if fcking up my online plays.
It seems that there is nowhere to disable the client auto-update.
It seems that there is nowhere to say "if I am playing, please DON'T update"
And right after I quit my online game (because steam if creating such massive lags while it's auto-updating), it finishes the update and asks me to restart the client.
If it's smart enough to say that I should restart my client only after I quit my game, it should also be smart to only update when I am not playing.
Steps for reproducing this issue:
Play any online game
Be lucky enough to have a client auto-update with a slow network link
The text was updated successfully, but these errors were encountered:
Your system information
Please describe your issue in as much detail as possible:
Steam client is updating itself in background even when I playing online games, in a slow Internet connection.
Now do the math and you will see that Steam if fcking up my online plays.
It seems that there is nowhere to disable the client auto-update.
It seems that there is nowhere to say "if I am playing, please DON'T update"
And right after I quit my online game (because steam if creating such massive lags while it's auto-updating), it finishes the update and asks me to restart the client.
If it's smart enough to say that I should restart my client only after I quit my game, it should also be smart to only update when I am not playing.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: