安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
21 
举报此帖
Why, or how did you decide that this magic rune change would have any effect? How did you come to this magical parameter change?
Found this workaround here: https://www.reddit.com/r/steamsupport/comments/1fihhuf/steam_only_turns_on_with_the_option_with_browser/
It turns out the command is basically disabling the Steam Client's Chromium Embedded Framework (CEF), in which the PC will just skip interfacing with the "Sandbox environment" and directly interacting with the website of Steam's Store page.
Also, when you put this command the first time and reenable it (make sure you kill the Steam processes via the Task Manager), make sure the first thing you see is the update window shows you will need to let Steam update itself with a rather large file, then after it installs, the issue will solve by itself(at least in my case).
Then, go to Steam > Settings > Downloads and select Clear Download Cache. Steam should close, and you can remove the command from the icon's properties before opening it again, since CEF is a security feature of not letting online malicious content get into your PC via the Steam Client.
Thanks, feels like I should bookmark this, and maybe even automate it.
I usually just kill the processes, and reboot if that does not work. And am now tempted to write a watch-dogger script, because their launch watchdog is clearly miserably failing. And all these tips are helpful, because security needs to remain central. I will have to find a way to automate the cache clearing, because often I just wait about 10 minutes, and then steam does finally start on it's own. I want to first tail all the logs to build a picture of what is going on though, and this it a good clue, cheers WeyonEleven.
Can't say I have. Steam hasn't bugged up in the past 10 years for me. I'm sure this is the the same for the vast majority because otherwise we'd be seeing a lot of topics on the matter.
Steam has over 37 million active at peak and if just 0.1% of them decided to post about it we'd be swarming in topics.
Steam have got pretty reliable stats on this, so they know it's probably close to the 0.1% mark. I'm not disputing that, or I hope I'm not, because it's my day job to understand software quality, and that's a job where I know that defects are under-reported often by as much as 90%. Anecdotally if a thing crashes and does not loose your work or your 5 hours of progress in a game, it does not get reported. People have a pretty high pain threshold, and it's around the 15 minutes of work or wasted time mark. So a word document autosave or a web app state save every minute is very safe for example. I have this theory about busses when I visit a city for the first time. If the first ever timetabled bus does not run, it's a fluke, if it happens again the same week while on holiday, you can be pretty sure that it happens at least a few times a week. My experience on Windows will not match experiences on Linux, nor on variations of hardware that people have, which throws a variable in. But I've rebuild my computer 4 times at least since I have been here, and my last 2 builds re-installed the OS at least twice.
And that means that either I am unlucky and am trying to always catch that one scheduled bus in Manchester that always gets cancelled, or, Manc. busses do in fact, often enough get cancelled. It's just my experience, it's not universal, it's anecdotal, but it's my experience.