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
The fsx.cfg file is located in the user profile AppData location and as such I would expect a user running the application to be able to write to it without issue.
Have a look at the Microsoft sysinternals website, there you'll find a tool named Process Monitor which will log processes, registry and file accesses and various other items.
You can use the tool to find out what is accessing fsx.cfg and what is denying.
SysInternals website:
https://technet.microsoft.com/en-us/sysinternals/bb545021.aspx
Process Monitor:
https://technet.microsoft.com/en-us/sysinternals/processmonitor
Note that Process Monitor logs a lot of realtime data.
Cheers