安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
Thx for the tip. It solved my issues :)
My issue was the cryptographic service, and, assuming, Chromium's interaction with it.
I was able to fix the issue by running the service as a local system account vs a network account.
Local accounts have higher privileges than a network account.
To do this, open the task manager, go to the services tab, click open services, scroll down to "Cryptographic Services", right click, properties, log on tab, click local system account, and restart the service.
One side effect of this has been that launching some things from "Run" makes UAC flip out, I can launch cmd from Run, but launching services.msc results is a bright red box saying NOPE!!!
I have UAC on the lowest setting, so that's not it.
I'll reply to this post if I find any other unintended side effects, but for now both Chrome and Steam work as intended.
Crypto Services then becomes omnipotent and prevents you from doing anything management related.
On the other hand steam seems to work correctly now...
If you've done it, or want to try the flip on -> flip off:
To change back:
Services -> Crypto Services -> Properties -> log on tab -> click "this account" -> browse -> in the enter name box type "Network Service" without the quotes -> check names -> it should refresh -> ok -> clear out the password dots in both fields -> ok -> restart service -> restart pc and everything should be fine now.
But on a fresh Windows install both Chrome and Steam went haywire with the Crypto Service. After changing how the service runs, and then changing it back, Steam is fine, but Chrome no longer works.
I tried all the ipconfig tricks, netbios, DNS service change, MAC filtering is not enabled, and Google support is recommending the change above or a registry edit and the registry edit just resets itself on reboot. Even run as admin doesn't make a difference.
The problem is pervasive enough that I think MS made a change that Chrome doesn't like.
Meh, Steam works, I don't use Chrome, and I've ranted long enough.
This worked very well and quickly. Thanks for the info.
For unrelated reasons I had to do a fresh install of windows, with the new Steam install everything worked.
The Chrome problem was a red herring and related to Chrome's interaction with the Crypto Service. Again, it worked correctly after reinstall.
Reality is we all may have, or had, buggy Windows installs. Maybe try rolling back and re-updating?
https://techisours.com/how-to-fix-steam-error-code-105/