FAF CLIENT ALWAYS AS ADMIN
-
I built that window. I would have built an check box sure, BUT I do the check and the warning before ever starting the acctual client programm. Because I wanna avoid doing any operations as an admin. So I can not call any other functionally than I code explitically for that functionallity... and as @Askaholic said just change your system to not run programms with privilidges... it is BAD
-
Well @Azmodeu we are writting a dummy value in the registry
so however your system is configured u are doing something wrong. Because this window only pops up if we are able to write/read from the registry -
Should this function falsebly return that you are an admin I am more than welcome to change it
-
Seems like cals what we are using is deprecated
-
So I take back what I said:
We are not writing registry even tho I think that would also be a way to determine if one has privileges.
We are using cacls.exe to read the permissions of a file we should not be able to read...
https://docs.microsoft.com/de-de/windows-server/administration/windows-commands/cacls
-
If you open Task Manager under details you can click on the table header and select columns(on right click). You can add a column showing you if a process is elevated(Herraufgestuft in German, my windows is in German).
if the client shows as not elevated but shows the warning. We can have you guys type in a commands in a terminal(cmd) and check what commands work better to determine if you are admin.
-
what it should look like -
Heraufgestuft = Elevated
-
Btw if you are not using windows 10 that might be the reason... but I am not sure if I would change it for ppl that are not using a OS with support.
-
@axel12 said in FAF CLIENT ALWAYS AS ADMIN:
Btw if you are not using windows 10 that might be the reason... but I am not sure if I would change it for ppl that are not using a OS with support.
So you are deciding how i have to use my PC ?
This is at least interesting if not outrageous.I stop arguing here since it looks like it depends on your opinion not on support for users.
-
I think it is more that it would be a burden from the development standpoint to try and figure out how to implement detection for a depreciated OS
-
Ehm I offer my help
I don't have to capabilities to decide -
You miss understood me. I offer to fix it if it should be the case that anybody is using windows 10 and the check is broken.
-
Im not with the error anymore after doing some things to run without admin mode.
Even without error i got to task manager and faf is not on admin mode but it istill creates folder on ProgramData and recreates a mydocuments there where i need to put the mod/maps or it wont show on my launcher.
Im feed up with this i dont need help anymore since my problem was not being able to create a lobby with my mods/maps to play a private games with friends, if i select the mods inside the game everyone was kicked saying they dont have the mods(even when everyone had).
This was caused by this ProgramData folder where i need to put the mods/maps on instead of the real C:\Users\xxx\Documents\etc.
-
Yes this is the case in FAF because Anti Virus often gets mad at the client for editing documents folder so the default now is to use programmdata. Because we had a million complains where client was not able to read/write the folder. There is a setting to turn it back if you want to. Also in the menu you can click open mod folder and it will open the currently set one.
Further you could upload the maps/mods then FAF will take care of installing them.
You can of course suggest other solutions but as far was I am aware there is not much other choices. Writing stuff to documents folder in win 10 is sub optimal as I far as I am aware.
-
A symlink could be discussed but then I think you would load them twice I guess tho
Unsure if that works -
Shows you mod folder
Can be turned off to use the documents folder again...
-
Often times Documents folder that the client found was out of sync with the game. But is less hassle if the default is programmdata
-
Thanks didint know of that Vault Fallback Setting i turned it off and the client is looking at my original maps/mods locations so i dont need duplicates on ProgramData(My C is a small SSD only with windows and programs and is almost full).
-
@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
[13]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.