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
My ram usage is minimal, less that 1GB but steam takes multiple minutes to login and games are unable to launch until I end all of the webhelper tasks in task manager. The webhelper is directly causing the issue so to everyone saying just restart steam needs to humble themselves for a minute and listen. If I launch steam from any location, multiple minutes pass before the logging in to xxxx steam account dialog box pops up. My games freeze as they are launching and the only fix is to end all of the client webhelper tasks in task manager. Of course, if I end 1 then 5 more appear. I can make hundreds of copies of the webhelper (they use very little RAM overall but spike RAM and CPU usage ramdomly) by ending the bottom webhelper task. Until I manage to spam end task fast enough to kill all webhelper tasks, my games freeze and do not launch. Once I’ve killed them all the games and steam client run fine.
Set Steam settings up so that the Client loads directly to Library upon launch. Set the settings regarding Library to enable low performance mode and enable low bandwidth mode. These both help the Library portion run smoother and not be a cpu and ram hog.
Have OS and game clients on an SSD. The games can go onto a secondary HDD if needed.
So as said above, library as start view and doing the settings for low features of library is a good idea.
I still laugh at this because you're the one bloody jabbing passive-aggressive insults at everyone for no apparent reason. Your tone always seems salty like you're working yourself up-- it's an anomaly to me.
I came here for help, and got none here. I will not bother reading through the paragraphs of "its not that hard" and "you're behind" and "get a better pc idiot". So if any of you have already answered to this, I apologize in advance:
I felt a bit of a performance boost when I set Steam's launch options in the properties: "C:\Program Files (x86)\Steam\Steam.exe" -console -no-browser
Makes the client finnicky and only half functional, but it's worth the try.
Hope it helps
The solution for me was to reinstall Steam.
First I moved my games and user data folders (\SteamApps\ + \Userdata\) outside the Steam folder on the same disk, (or they will be gone!), then shut down Steam very quickly after Windows restart, before finally uninstalling Steam in control panel -> Uninstall a program, and downloading and reinstalling Steam again. Last was to move back the games and user data folders I saved previously.
After this, things worked fine again. There are only a handful of Steamwebhelper.exe running now.
Well if you stop using Steam as a Web browser and also restart Steam or your PC every once in a while that won't happen.
There is zero need to uninstall Steam. You can wipe all the old files from the folder very easily and then run Steam.exe with run as admin option to repair it.
No. I will not allow Valva to dictate what can or cannot be done on my PC. Forcing me to restart their bloatware multiple times a day so that it doesn't slowly devour more and more RAM like some vile monster out of the abyss that is Valva's soul.
And Yes, I have plenty of RAM, and NO it's doesn't really make a difference on my PC, other than the fact that it's MY PC!
NOT VALVA's!
For those who for some obscure reason have a deep seated fear of not being able to uninstall a game after hacking out the web helpers, shift deleting the folder also works.
If they wrote a decent application they wouldn't have to divide it up into multiple processes to stop it falling on it's face.
I can understand that in a full web browser that has to serve content from multiple different providers, but Valve is only serving it's own content. Is their own content so unstable it makes their own client application crash? To the point that they have to protect themselves from themselves?