@uveso said in FAF CLIENT ALWAYS AS ADMIN:
The problem here was the fact that many users had access permission errors inside the FAForever folder.
Mostly because they tried to start the FAF client as Admin to solve other problems they had.
But running as admin will write pref and config files with admin rights.
If you now run the client as normal windows user you no longer can change these files and you will get
permission errors in java.
To prevent users from starting the client as admin when they are normal user is the reason for this nag windows.
But when your system only has a single user with admin rights then this message makes no sense.
i can't run the client as normal user and will never get those permission errors...
So for us, this window is just annoying and has no meaning with our window configuration.
The client should look into the windows accounts and only display this message in case there are
admin and user accounts present.
And it should not display it on windows with just 1 user.
Dont agree at all. If you use windows with UAC like every other person, you should never run into this problem (unless there is a bug), and disabling UAC is just a REALLY bad idea in general and not at all recommended, even by windows itself.
Its impossible to check every way in which people misconfigure their system. The client should not need to support all of them, and in my book disabling UAC is a misconfiguration.