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
Alright, see ya, then.
Seriously, just run Steam as an admin and let the installs go through.
I have done that numerous times, it didn't change a thing. If it had I wouldn't have spent all that time scouring the Web or even bothered posting a message here asking for help. It's not like I haven't given the install numerous occasions to "go through", even as an admin, which was confirmed by inspecting the Security privileges of the process in Process Explorer. Steam is currently running as an admin but I still see the first time setup every single time. Editing the vdf file is useless, it gets rewritten every single time the Play button is clicked.
Why would a game need elevated privileges to run? Especially when not installed in Program Files but on a secondary drive? I know some people feel comfortable running everything as admin, or disabling UAC, or whatever. I just don't. I didn't want to turn this into a UAC disabling debate or flamewar, hence the last sentence of my opening post.
Here's what I did to find the cause of the problem and fix it (note that I'm a software engineer). I launched a command line and manually executed the command that the install script is supposed to execute, namely the command relative to the VC redistributable. I followed all the steps, even setting the INSTALLDIR environment variable in the command line window. I copied and pasted the fragments of the command and ended up with:
%INSTALLDIR%\\support\\vcredist_x86\\vcredist_x86.exe /q /norestart
When executed from a command line window as a normal user, the UAC prompt showed up again. On Yes, the program proceeded for a second or two and nothing happens. The errorlevel variable then had a value of 5, which means (because the value is not 0) that a problem occurred.
When executed from a command line window run as an administrator, the UAC prompt did not appear. But a fraction of second into the execution, I got an error window informing me that a newer version of Microsoft Visual C++ 2010 Redistributable had been detected on the system and... asking me to fix that problem ^^
I checked and I had version 10.0.40219 of that package. After uninstalling it, the command listed above proceeded further than previously since this time, I got to the License window. Therefore, I canceled it so that the Steam first time setup wouldn't be hindered.
As one could expect in the light of all this, the first time setup happened again, for the very last time (Steam was running as admin). Subsequent launches whether as admin or as a normal user never showed the First time setup window again. Problem solved. The version that came with Ace Combat turns out to be 10.0.30319.
Disabling UAC or running Steam (or any non-system program) as an admin might seem like a solution, but it doesn't bring an understanding of what is really going on. It's only sweeping the dirt under the rug.
I hope all of this helps someone someday.
Anyway, I'm glad it all worked out OK for you.
literally nothing is working. im on windows 10 btw
didint worked.
i should mention im having the problem with dota altho that dosent changes anything.
it just so happen the thread was here
Dude seriously, thats a general issue that isint game specific, who the **** cares where i post it