Running FSUIPC & permissions

[wogapat]

FSUIPC v7.2.10v  Windows 11 Version 21H2

I first noticed this issue when my key & button assignments wouldn't save. I have a registered version of FSUIPC.

I looked through the forums and found references to the .ini and .log files, created when FSUIPC runs. I checked the installation directory and those files don't exist. I ran a search of my system. They definitely don't exist.

After a little testing, I've managed to narrow it down to FSUIPC needing to be run as an administrator. When I run the .exe as an adminstrator the .ini and .log files are created. When I run MSFS, and start-up FSUIPC from the .xml, FSUIPC does not create the .ini and .log files. Hence why my assignments are not saving.

Here is what I've tried:

1 - Setting the 'run as administrator' in the compatibility settings of the .exe properties. - FSUIPC fails to start with MSFS

2 - Creating a .manifest file to try and force it. - FSUIPC starts with MSFS but the manifest is ignored.

3 - Changing the security properties of the FSUIPC directory to give 'write' rights - I get all sorts of security permissions errors and the .log and .ini file are still not created.

I appreciate this is more a system issue than an actual problem with FSUIPC but I can't seem to get around it. Any suggestions, please?

Edited September 22, 2021 by wogapat
Spellings and grammar

[Pete Dowson]

4 hours ago, wogapat said:

I appreciate this is more a system issue than an actual problem with FSUIPC but I can't seem to get around it. Any suggestions, please?

It does sound very much like you chose an installation path for FSUIPC which is protected by Windows, like somewhere in Program Files. You could try reinstalling to a more accessible folder, created perhaps directly under a drive name, like C:\FSUIPC7.

Note that if FSUIPC is run "as administrator" then every FSUIPC client program also needs that status (and vice versa). Programs at differrent privilege levels cannot communicate via shared memory which is the way the FSUIPC interface works.

Pete

 

[wogapat]

Thanks. I'm not sure how that path ended up protected. One for me to try and figure out. Worked out last night that running the FSUIPC MSFS shortcut as admin seemed to pull it all together. At least now the .ini file exists and can be read. I'll stick to doing that, for now, until I can figure out what windows is doing. I have a standalone m.2 drive for MSFS. FSUIPC is installed in top-level directory there which shouldn't be protected like that. Now the .ini exists, and is being read even when I start up normally, I could just leave it and not get logs. I've had a few add-on crashes, though, which I think the .log file may help me narrow down. Thanks for your reply.

[John Dowson]

13 minutes ago, wogapat said:

Worked out last night that running the FSUIPC MSFS shortcut as admin seemed to pull it all together.

Yes, doing that would run MSFS as admin which would then run FSUIPC7 as admin.

14 minutes ago, wogapat said:

I have a standalone m.2 drive for MSFS. FSUIPC is installed in top-level directory there which shouldn't be protected like that. Now the .ini exists, and is being read even when I start up normally, I could just leave it and not get logs.

It does sound like permissions issues, and it is strange if this is on a non-C drive. Maybe try  moving it to another location/drive to see if you get the same issue.
Not a good idea to run FSUIPC if it can't create the logs, as this means that it also can't update your .ini, so no assignments can be saved.

I see you are also using Windows 11. Be aware that I haven't tried/tested FSUIPC on windows 11 yet. 

[wogapat]

9 hours ago, John Dowson said:

I see you are also using Windows 11. Be aware that I haven't tried/tested FSUIPC on windows

Thanks. No problems so far.

9 hours ago, John Dowson said:

Maybe try  moving it to another location/drive to see if you get the same issue

Just re-installed (again) to a clean location and the problem seems to be corrected. The program is no longer in an admin protected directory and happily creating the .ini and .log file from the MSFS .xml start-up.

Thanks for your help. I really appreciate you taking the time.