安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
-Open Task Manager >> Right Click "steamwebhelper.exe" process >> Select "Open File Location"
- Kill steamwebhelper.exe with Task manager and Rename .exe to .bak
Simple to execute and reverse if needed..
I'm asking for legitimate help and instead of trying to offer any you would rather let corporate loyalty see it as an attack because nothing could possibly ever be wrong with anything so perfect as whoever makes what you buy.
When I cut the process to steamwebhelper I stop lagging.
Steamwebhelper is the problem.
I have made a clean install, reinstall, I have tried it on several different computers and a laptop and the problem persists through all of them. Based on this there is no possible way to say it is anything but steamwebhelper causing issue.
I am asking for a way to stop steamwebhelper from running while I play a game which I paid money for to play because it is impeding me from playing on multiple machines, two of which are running a completely clean install of both Linux and Windows 7.
On every machine steamwebhelper being killed has stopped framerate issues temporarily; after which they resumed in ten minutes or less.
There are currently ways to impede steamwebhelper itself, however they are inefficient.
Why would other people make these ways and seek them if it was not a problem for these people?
Why would you turn this into a discussion about defending something that is obviously a problem instead of trying to stay on the topic of resolving the issue?
Saying something that is an issue isn't an issue does not resolve it, and in fact impedes resolution.
If you do this, steam will say it is corrupted, restart, and update with a clean new install of steamwebhelper.
Might want to look up what the ad populum argument means. Because it's not what you think it means.
Occams' Razor would indicate that you're much more likely having a localized system issue, rather than the entier CEF back end being broken. That is not an ad populum argument.
Again if you dont' want help. Dont' ask.
Thereby working around the steam applications check that the webhelper executable is present, and preventing the "corrupt install" event.
Note: I think ZoneAlarm has a resident shield program that will block process execution as well (but the overhead of that software may defeat the point). Also, I've heard of some freeware called AnVir that is light weight should be able to auto terminate\block specific processes.
AnVir discussion w/ links: http://superuser.com/questions/69783/how-to-monitor-and-kill-a-process-automatically-on-windows-by-process-name
Yeah saying "Lol uninstall it haha it isn't even a real problem dumbo you're just lying obviously to discredit my perfect program" really helped, thanks a lot.
Thanks a whole ton, you must have really gone out of your way to dissect every single little problem I was having and fix it. You must have a whole essay planned on how to help people who have this problem in the future by telling them to shut up and deal with it.
You're a real humanitarian, you must be a member of the red cross or some other similar organization which goes around telling starving kids that they don't even need food to eat because stomachs don't exist.
"Everyone else isn't starving so what's your problem?"
In argumentation theory, an argumentum ad populum (Latin for "appeal to the people") is a fallacious argument that concludes a proposition is true because many or most people believe it. In other words, the basic idea of the argument is: "If many believe so, it is so."
This does basically what the killer.bat does which means I'm confronted with the same problem of it freezing up constantly while ending the process as it starts. Killing the process is something that's already easily done but steam is being real adamant about constantly starting it back up, and when the process gets killed everything seizes up while it's trying to restart it, so you can see the issue with having this done constantly.
I'll try ZoneAlarm and see if blocking it from starting at all helps.
Edit : ZoneAlarm and similar firewall blocking procedures doesn't help, it just causes one massive long freeze inbetween small breaks. I'm entirely sure this is steam trying to start up steamwebhelper at beyond-lightspeed which wouldn't even surprise me in the slightest. It's more likely to due with steam constantly trying to call steamwebhelper, which isn't starting as it's being blocked. If this is steam's response to steamwebhelper being blocked then there is no way to efficiently block it with a desirable outcome so I'll just have to wait until steam eventually fixes it by finding a better alternative; I'll probably be 50 by the time I can play TF2 again.
Thanks for trying to help Anime8ted.
It's best to not feed the Troll.
If you were providing help in the first place, then you would have a grounds to stop giving it. So far your replies have been that the issue is lilkely OP's setup alone, cuz everyone else's install is working fine.
And this may be the Case, OPs OS or Steam install may be jacked beyond all recognition, but OP's intentions from the start suggested that their goal was to implement a workaround to the issue, not investigate and remedy the underlying cause (whether it rest with their install\setup, or the Steam application itself).
Wel that sucks...Only other think I can think of is creating your own (empty) .exe with the same name, hope that steam doesn't try and validate the executable, and that it only tries to find the process loaded\running. And pull a switch between the two. So that the blank exe runs without utilizing resources and Steam is placated into thinking that the helper process is doing something. Though it is unlikely to work as I'm sure there is some kind of process "CrossTalk" and Steam is gonna prbly get upity when the helper process doesn't check in.
Also, did you try rightclicking steamwebkiller.bat and selecting delete? It sounds like this might solve your freezing issue you keep complaining about.
Steamwebhelper is part of the chromian framework that steam uses to show the pages in the client and the in-game browser. If they get killed, you lose that part of the client and it stops working.
There isn't any option to 'turn it off' as it's a part of the application.
How fast is your internet?
You shouldnt be able to play csgo, if this process would
If you're concerned, run a Malwarebytes' Anti-Malware[downloads.malwarebytes.org] -scan.