Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
- Switch to Steam beta via settings, but if already in it opt out instead.
- Restart modem and/or router by unplugging it power, then plug it back in after a minute. If it works then means modem and/or router has issue, and just needed a restart.
- Redownload Steam client, head to where you install Steam, go into folder, delete everything except for "Steamapp" folder, and "Steam.exe" file, once done run Steam.exe see if issue resolved.
- If using VPN/proxy, may cause issues you're having.
- If using custom DNS service depending which one may cause issues.
- If using 3rd party software to manage apps behavior, incoming, and out going traffic, or even 3rd party anti virus affecting apps doing dumb deep scans, ensure that not causing issue.
- If using custom firewall, pi hole, or etc, and blocking thing could affect things, might want to look into that.
- Flushing your network might fix things, open command promt as admin, and give this a try, then restart PC and test, do things in order.
netsh winsock reset
netsh int ip reset
If not working still try these in order, then restart PC, and test.
ipconfig /release
ipconfig /flushdns
ipconfig /renew
Done, done and done sadly.
Ive been looking into it for a while now. But one thing you are right about here, and that is changing between beta and current version. That helps usaly from time to time. I think that says more about the issue. We should not face issues like this, to make it work as it should. Its more like a work around at this point. Then why should it help to change between em current and beta? That points even more towards a client issue.
Ive been troubleshooting computers since 1999 as work. So i usaly get around to find the issue. But this one, is starting to enoy me. Due i cant find any issues in network or the computers. Im pending between 4 computers due work. different computers have the same problem.
First i started to suspect the hoste computer. Then i did a clean os. Did not work. Then i bought a new computer home, due it needed an upgrade. Same problem. Then the internet provider was upgrading the network in july, due a policy they have, to change equipment every 4 years. Changed router and modem plus the decoder on the tv. So the problem was still there. 3 other computers, are on 3 different networks. Then still have the same issue. Meaning its not possible that its the computer or the network. Then it all points to the client.
Now i have not been able to fix the issue for 2 hours. I changed to beta. did not work. changed back 2 more times in current and beta. So i figured, let`s put it back to current build again.. then look at the pc home.. changed to current for 3th time, and its working again out of the blue. So frustraiting.
But it did not change that its a cursor problem yet. Still of by 2 cm off, and flickers. Also checked that it matches my resolution at home.
If you hearing a loud dunking sound.. Its just me hitting my head in the keyboard
Could try posting here if wanted.
https://steamcommunity.com/groups/SteamClientBeta/discussions/
Could try another remote play software like parsec, moonlight, or sunshine.