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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
rename old "steam.exe.old" to main and see if that help or run as admin onetime at steam.exe.
And is that really the only solution?
Problem here is why, and you can try rename steam backup file if such is made.
and other solution can be a forced try to run as administrator on steam.exe ( to see if that help. )
Most will not use such long explanation, in what to do. ( pc is know for this, sometimes as user you are need to take actions on things goes wrong, and sometimes other things cause issue with other things, and sometimes its user that did not do or know other app or things can cause the problem, its simple not just one thing, and thern you think over it, steam has 250 to 350 millions of user online per day, thats mean alot of user it work for.
Most will not start over in new system, but even that is a option, and none here will stop you, but i can also say most will not even suggest such anymore, try see it as last option then you have wait long enough, and thats your call then that is.
gl with it.
Go to your Steam installation folder(i.e. C:\Program Files\Steam) and delete everything except steam.exe and the steamapps folder.
Then run Steam.exe.
My guess is that it is a configuration error and by deleting and letting steam fully rebuild your installation like this it might work.
All this is assuming, of course, that you actually have a working internet connection and you are facing no other issues with browsers and other applications.
No problems with my wifi as far as I can tell.
[2023-01-11 14:52:21] Startup - updater built Mar 15 2022 17:15:38
[2023-01-11 14:52:21] Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults
[2023-01-11 14:52:21] Using the following download hosts for Public, Realm steamglobal
[2023-01-11 14:52:21] 1. http://media.steampowered.com, /client/, Realm 'steamglobal', weight was 1, source = 'baked in'
[2023-01-11 14:52:21] Verifying installation...
[2023-01-11 14:52:21] Unable to read and verify install manifest C:\Program Files (x86)\Steam\package\steam_client_win32.installed
[2023-01-11 14:52:21] Verification complete
[2023-01-11 14:52:21] Downloading update...
[2023-01-11 14:52:21] Checking for available updates...
[2023-01-11 14:52:21] Downloading manifest: http://media.steampowered.com/client/steam_client_win32
[2023-01-11 14:52:42] Download failed: http error 0 (media.steampowered.com/client/steam_client_win32)
[2023-01-11 14:52:42] DownloadManifest - exhausted list of download hosts
[2023-01-11 14:52:42] failed to load manifest from buffer.
[2023-01-11 14:52:42] Failed to load manifest
[2023-01-11 14:52:42] Error: Download failed: http error 0
[2023-01-11 14:52:42] Saving metrics to disk (C:\Program Files (x86)\Steam\package\steam_client_metrics.bin)
[2023-01-11 14:52:42] Error: Steam needs to be online to update. Please confirm your network connection and try again.
[2023-01-11 14:52:53] Shutdown
Purged the entire installation at that point, thinking it must be corrupted files or registry entries, went to do full reinstall. Same issue, same errors in my log as those posted above. Changing my connection's DNS servers to Cloudflare's servers for both ipv4 and ipv6, running ipconfig /flushdns, and trying again seems to work at times. It was enough to finally get the install done and get me back in. Steam mostly works okay at this point, though community stuff and many images are still broken or missing all over the place.
Try to do a tracert on media.steampowered.com and see what kind of nonsense you get back. I'm largely having problems when hitting Akamai CDN hops no matter the route taken, as well as some odd routing loops from Comcast when following one particular route. I think gathering info is the best we're going to get at this point, which will hopefully lead someplace more useful soon.