"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?