Problem with .config folder location

[elsamnyxillum]

Some users (verified only on windows 7 at this point) have reported a problem where they are unable to access their profiles without running mudlet with administrator privs. The .config folder, even when installed by a different user, seems to default to the original users profile i.e.:

Penny is the original user created on the computer. Alf and Ring are created after, if Ring installs mudlet, the .config folder will be in C:\Users\Penny.config forcing both Ring and Alf to run mudlet as an administrator in order to access their saved profiles.

Maybe an option to install mudlet for only the user installing the software would remedy this?

[SlySven]

Is this something that needs to/can be configured differently in the Windows Installer builder?

[elsamnyxillum]

There is currently no option on the windows installer. A lot of programs will let you either install for all users or for just one user. I am not 100% that adding the option to install for a single user would make any difference since I haven't tested it out, but in theory it should.

[SlySven]

I meant as a configuration option for the team member using the installer-builder to make the installer rather than the (end) user of the installer so built... 😉

[vadi2]

I've no idea about multi user setup on Windows. Will have a look at it.

…

On Sun, 2 Apr 2017 1:40 am Stephen Lyons, ***@***.***> wrote: I meant as a configuration option for the *team member* using the *installer-builder* to make the installer rather than the (end) *user* of the installer so built... 😉 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGxjHfeerypUYXZMOcksIdxGVj_pmrAks5rruBwgaJpZM4Mwobh> .

[SlySven]

It is a bit late for a response but since I am in the area I can observer that the Windows installers we make are for per-user installation and not intended for machine-wide installation (you should be able to install them without WUC(?) asking for Administrator rights)...

<aside>We do have the option in our CI/build code to specify to build a machine-wide type installer - and that would produce a .msi type installer that WOULD require administrator rights to install, instead of the setup.exe one that we currently provide.</aside>