I got FSUIPC to start automatically again

[SWhite]

Neither of the two auto-start apps I had were auto-starting anymore, I'm not sure when they stopped but I think it is since SU9. I don't always require the two apps. 

After much mucking around and as a last resort, I decided to move FSUIPC and LogiMicrosoftFlightSimulator from their original locations that they'd been in for many months (FSUIPC was in a folder on my Desktop and LogiMicrosoftFlightSimulator was in its default install path in C:\Program Files) to my archive disk. Once I updated the paths in exe.xml, both apps loaded properly. FSUIPC wasn't minimized like it used to. But it worked at least! 

There were two changes necessary to get the original paths to work. I had to do both.

1. The EXEs must *not* be set to run as "Administrator". Both of mine were. This is required whether I run MSFS as Administrator or not.

2. The folders have to have the "Users" group and be given the standard "Read" and "Read and Execute" permissions.

If you don't know how to set permissions, maybe try moving the folders of the necessary app folders to "C:\ProgramData". That's not great, but easier.

Good luck 🙂

[John Dowson]

31 minutes ago, SWhite said:

maybe try moving the folders of the necessary app folders to "C:\ProgramData". That's not great, but easier.

Do not install FSUIPC in a windows protected folder such as under ProgramData, Program Files or Documents. Installing FSUIPC in such folders invariably creates issues.

35 minutes ago, SWhite said:

I think it is since SU9

I have just updated to SU9 (v1.25.7.0) so I don't think that this can be an issue - unless it was present in the beta and has now been fixed.

Thanks for the info though - quite a few people are experiencing this issue, and it may help them...

John

[SWhite]

16 hours ago, John Dowson said:

Thanks for the info though - quite a few people are experiencing this issue, and it may help them...

ProgramData was the only one on my system that had the same security permissions as my other drives which is why I listed it. But yeah, it is hidden by default. I'd be surprised if the Documents folder was an issue though. It is for all our editable user data after all! 

I am 100% able to reproduce the issue with each settings change so each of those things so it is most definitely my causes. Of course, that there may be other other constraints my machine doesn't trip that others might. The wonderful world of PCs eh.

I tried the SU9 beta 3 days before release but it was causing me nothing but CTDs when the prior version never CTDed at all. This caused me to do a full reinstall because the normal opt-out broke my MSFS install badly. Maybe there is something related there too. I wonder how many users having the issue were beta participants?

Fortunately the live version of SU9 is working perfectly for me now!

[John Dowson]

6 hours ago, SWhite said:

Documents folder was an issue though. It is for all our editable user data after all! 

Its an issue due to the interaction with OneDrive in windows 11 (and maybe other cloud-syncing services).

6 hours ago, SWhite said:

I am 100% able to reproduce the issue with each settings change so each of those things so it is most definitely my causes. Of course, that there may be other other constraints my machine doesn't trip that others might. The wonderful world of PCs eh.

Yes, I don't doubt it. What surprises me is that this issue seems to be happening when an FSUIPC7 folder is created outside of a windows protected folder for some people. I guess this can still be due to permissions based upon individual users condifurations, but such things are difficult for me to diagnose...

7 hours ago, SWhite said:

Fortunately the live version of SU9 is working perfectly for me now!

Yes, seems ok here as well (although I have had an occasional CTD...).

Thanks for your input.

Regards,

John