安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
winget install --id Valve.Steam --exact
Works since years and has way more options than the scripting winget from Windows.
All you need is a copy of a Steam.exe (even if it is old) and put into its own folder (for example c:\steam) and run it via right click > run as admin.
chocolatey uses powershell which is way too complicated for some. winget is able to be used by the good old ms-dos style command prompt. and as for scripting it, it is as simple as writing a few commands into a .bat or .cmd file. batch files are about as simple as you can get when it comes to scripting.
its pretty ez to put a steam.exe backup on a simple flash drive for new installs
plus all my new builds i keep all my games on 1 hdd so the fresh windows install on ssd does not affect steam as soon as windows is installed steam is rdy to go on a fresh install
either get hdd that has all your games that you just plop in new machines
or just simply copy steam.exe to flash drive for new installs
same thing really, simple and ez
I also keep a folder of all downloaded apps in case I want an older version installed for testing.
And Steam already installs properly the way I have it set up.