Launcher.exe automatically launches in admin mode

[White-Gandalf]

"Launcher.exe" on my windows 10 home (with activated software restriction policies and restricted, but adapted for the game access rights) automatically tries to start "KSP_x64.exe" in admin mode.

When staring "KSP_x64.exe" manually under the normal user account, it launches perfectly fine and finds all settings and save games.

Maybe the launcher should not take access restrictions that seriously?

Or has it something to do with it testing all eventually needed folders for write access? (I didn't go into adding custom stuff (mods/addons) so far.)

Is there some explanation available what folders are needed having write access?

[Jas0n]

In my experience, I've had problems with mods loading when it doesn't run in admin mode. but i don't know if that's still a problem.

[severedsolo]

On 26/05/2017 at 0:14 AM, Jas0n said:

In my experience, I've had problems with mods loading when it doesn't run in admin mode. but i don't know if that's still a problem.

That should not be the case. A mod is just a plugin for KSP, it should inherit all the permissions that KSP does (and therefore should not be trying to write anywhere outside the KSP directory). If a mod is trying to access a restricted area, it is being naughty and should be reported as a bug.

In laymans terms: A mod by itself doesn't actually do anything, it just instructs Unity (and therefore KSP) to execute it's code. If KSP could write to that location, so could the mod.

You really should not be running KSP (or any application really) in elevated mode, there is no need.

I've just tested my own Launcher.exe and it has no issues with launching with non-elevated permissions.

 

[Gordon Fecyk]

I'm assuming you're using the download from the KSP Store and not from Steam, GOG or other distributor.

If you're running launcher.exe in an area normally read-only to non-admins, you'll get a UAC prompt when it tries to write anything. KSP needs read/write permissions in its installation folder to save game states, write log files, and such. Just grant it Modify access to BUILTIN\Users, and that'll work. Here's a command line: Save this as a batch file in your KSP folder, launch it, and answer any UAC prompt that comes up:

icacls ".\" /grant Users:(OI)(CI)M

What this does is grant the BUILTIN\Users local group Modify access to the current folder; the folder the script is launched in. "M" = Modify, "(OI)" = Object Inherit (all items in the folder get these permissions), "(CI)" = Container Inherit (All folders in this folder get these permissions).

This will also let you add any add-ons to the GameData folder without needing UAC prompts.

I suggest "Modify" instead of "Full Control" because KSP does not need to change permissions for anything inside the folder it runs in.