Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
The .NET framework that is in the Steam directory would not install on a 64 bit machine. I downloaded the latest .NET 4.5 from Microsoft but it still wouldn't work. That's when I realized that perhaps it was the reduced privileges of the guest account that might be causing the problem. Logging in as administrator solved it, and the game started up normally. I tried running the executable from the Steam directory as administrator but it didn't work. I actually had to log off the guest account and log in as administrator on my PC for it to work. I'm not sure what's happening here.
I still haven't played it yet, since I was so happy to get passed this startup bug that I wanted to share. The game must be trying to access some part of the drive that it shouldn't have access to, and the windows guest mode is really strict about that. This is not the first program that I've had this problem with, but it isn't very common. It would be nice not to have to log in as administrator every time I want to play this game.