安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
Look in Task Manager (Ctrl + Shift + ESC) and first check to see if Steam is running any instances and if so End those Processes and Restart Steam.
If this is false, then proceed to Task Manager < Startup tab and check is Steam is in there and if so, make sure it has its Valve icon attached because if not, then the Startup app has broken registry keys - the icon will be blank instead of the proper Valve logo.
Also, run Steam as Administrator seems to be the more proper way to start the app/client.
If you are using an external storage solution (data drive) this could most likely be the issue as some users forget to assign those static drive letters and keep them on floating drive assignments which in turn will cause issues when launching games.
And then I have a huge list of things for another issue on another thread and if you want I can send it here but not until you say okay because it is for a different/specific issue, but could hold water.
Apart from running the Steam Client Setup Installation over the current Steam Client installation WITHOUT uninstalling Steam itself. Be aware that this solution will default all Steam Client settings but will leave all games intact.
Sometimes the paths can become broken...
The external drive solution is applicable when using external drives and also if you are using USB sticks or any other external hardware.
This will put your Steam Library on a floating drive letter which Steam might not see properly.
Therefore, the remedy is to assign the external drive to a letter to solve the issue as Steam will only look on that drive letter and not on the other floats.
It is not applicable if Steam does see the floating drive in which the library was first installed on (Floating Drive D takes initial precedence)
Match the external drive letter to what Steam Client says it should be and if it is true, then it shouldn't be that, but if false, that is the issue.
Maybe you should also run SFC (System File Checker) Scan Tool.
Proper Client RAM usage should be around 600MB - 900MB.
Have you run the SFC scan tool to check for system corruptions that can lead to software app launch failure?
Sometimes seemingly a simple remedy is to try to restart the PC but I am sure you tried this already.
Have you added any new software?
If so, you may want to rollback the driver.
It is key and only key to update the GPU when and only when it begins to cause issues.
If the GPU was not having issues prior to the update, you should never update the driver until issues appear.
I think it is not driver related, but could be.
Have you attempted to run the Steam Client Setup Installation over the current Steam Client version without uninstalling Steam?
This will "clean install" the most updated Steam Client replacing all files without affecting game libraries.
As stated before, all Steam Client settings will return to default positions.
There is also a troubleshooting method I personally used if you have more than one drive, preferably 2 or more to thus reinstall another Client, download a small game you know would crash on the original Steam Client and to test that Client to see if it launches said game.
Mind you, using this method of troubleshooting you will NOT want Steam on the same drive, nor the library(ies) that you use.
If you only have two drives, you can still attempt this method by manually creating a Steam Library Folder preferably something not named the same or similar - name it "Steam - Test" or something but you CANNOT have two Clients on the same drive, only libraries in this test.
This method helped me to reset my original Steam Client back to the default store from main library which was causing a Restarting Loop on Steam startup.
Then to remove the second Client, simply delete all its files as it will have no uninstaller to wit and using any Steam Uninstaller will remove both Clients.
If you do this test and it is clear (runs the game) you would need to switch over some folders but we will get to that later, if applicable throughout.
Personally, I would rather run the Setup Installation .exe over the current Steam version as this seems to fix most Client issues.