Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
In any case, I'm not sure which part(s) of this were strictly necessary, but this is what I did between when it didn't work, and did work:
1) Went into Steam's preferences and opted out of the beta (goodbye, Steam Broadcasting :P). This triggered a restart of the Steam client.
2) When Steam finished restarting and came back up, I exited it manually and pulled up the Task Manager to make sure "steamservice.exe" exited gracefully on its own (it did).
3) Ran "Command Prompt" as Administrator (right-click on your shortcut), cd to Steam's binary directory (in my case, X:\programs\steam\bin) and ran a repair with this command:
4) Restarted the operating system. My gut feeling is that this was unnecessary, but, I figured what the heck...if I'm doing all this, might as well.
After that, when I launched Steam and TPP, I still got the "Completing installation" window but it went through to completion and eventually launched the game.
Yeah, no problem; I picked up the "steamservice.exe /repair" idea from another post on these forums ("these" meaning Steam's...was for a different game, one of the Call of Duty ones actually IIRC) but it didn't initially work for me (presumably due to the Steam beta). See, Call of Duty can be useful!
It may be worth noting that -- despite the fact that I'm up and running now -- the service repair operation did not resolve the issue while I was still opted in to the Steam client beta. Obviously it's not outside the realm of possibility that that's simply due to some other, as of yet undiscovered reason, but...you guys may want to consider booting up your own instance of a Steam client, opted in to the current beta, and see if you get the same issue. *shrug*
I tried to enter Steam's binary directory and it didn't work, (C:\Program Files(x86)\Steam\bin).
also when I entered the Steam service repair it didnt work either.
Well, the gist is that you need to get to your "bin" directory. As far as I know, it should just be a subdirectory of your main Steam installation directory, wherever that is. I don't know if it's required that you be in that directory when you run the rebuild, but I figured better safe than sorry which is why I did so, and ran the command with ".\" prepended to it. That's why you have to be in that directory for the command (as I showed it) to work.
When you run it, it'll sit there with no output for a while (mine took over half an hour...I have a large library, although I'm not sure if that matters) and then eventually print "rebuild successful" or something along those lines.
Nope...my troubleshooting was a mixture of general Web searching and throwing spaghetti at the wall until something stuck.