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
Once I am done for the time being, I run another which renames them both back to normal. This is because if they are gone when you try to launch Steam, it will update and re-download them every time.
No spinning cursor, no problem. Only takes a second to run either batch file as well.
Or you are doing something silly like running a script that is automatically closing all the Steamwebhelper.exe processes, in which case anytime you try to do something on steam it will see that it has unexpectedly closed, run the reporter, and then open another webhelper (which is needs to do things).
Well in my case, I am not closing or ending the webhelper processes.
When I launch Steam, the errorreporter runs. When I click on a new item within the client, it runs again. For example, I just clicked VIEW FRIENDS LIST in the bottom right and it ran errorreporter and my Windows cursor spun for about five seconds, then it closed.
If I go into a game and use the overlay and open the web brower in game or view achievements or something different, it will run each time.
I haven't found a solution yet other than renaming the files while using Steam, and then renaming them back when I close it for the night. I've read that even a fresh install of Steam doesn't fix it, and also even a brand new machine with Steam newly installed and it still happens. No clue what to do here other than deal.
Some people were upset about the resource usage and did various things to block the processes or shut them down. Which would cause the reporter to run once Steam realized it had been lost.
You say that you've "read" that a fresh install of Steam doesn't fix it. But have you tried? You don't even have to uninstall/reinstall, you just need to delete everything except Steam.exe and the SteamApps folder (where your games are) and Steam downloads all the files and makes sure everything is OK.
There's also this:
https://support.steampowered.com/kb_article.php?ref=3134-TIAL-4638
Thanks for the reply, but I have tried the flushconfig refresh thing. Didn't fix it.
I may try deleting those files at some point, as that's the only other thing I can think to try. I have no problem with the webhelper processes, it just seems that, like you said, there's something wrong or it thinks there is and it's trying to "report" some "error" each time.
Dumb question, but should I install Chrome? I use Firefox and maybe Chrome installs some files that Steam is looking for since you said it's a modified Chrome browser. Just a thought.
I've tried to reinstall Steam and tried on 2 other PCs, it's the same on all of them.
EDIT: However, steamerrorreporter.exe is not "popping up every few seconds" like you describe it. I can only see steamerrorreporter.exe in my task manager for a few seconds before it disappears again.
Complete nonsense. Started about a month ago, when Valve allegedly 'fixed' some problems with the steamwebhelper process in one of their updates.
Ever since I also get the occasional BEX error on Steam shutdown, related to data execution prevention. As far as I've been able to tell, it's because when shutting down there's a race condition where Steam may be trying to access something from an already unloaded DLL.
If I had to hazard a guess, I'd say Valve managed to screw up the inter-process communication and it's causing a lot of grief for some people.
Kind of fighting symptoms there. steamerrorreporter is a proces that's spawned specifically to provide error / crash telemetry back to Valve.
Anyway; I figured out that updating the nVidia driver on my system fixed it. Presumably the hardware-accelerated rendering in the Webkit browser that is embedded into Steam was to blame...