This are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
[Solved] FSUIPC7 ver 7.5.6 Won't Auto Start
I can't get the latest version of FSUIPC7 to auto start. The installer does install the new FSUIPC7.exe dated 27Jan2026, and the EXE.xml file is correct. In fact if I simply replace the new FSUIPC7.exe with the previous FSUIPC7.exe (delete and paste) auto start works. Since the new FSUIPC7.exe goes in the same folder as the previous version, I would not expect any changes in the EXE.xml file. The install log file does report the auto-start of FSUIPC7 will not be enabled error message. For test purposes, renaming the EXE.XML file and rerunning the installer did not solve the problem.
I have this problem with both FS2020 and FS2024.
Al
Disregard and delete the above post, finally got auto-start to work.
Thanks,
Al
Posted by: @ark1320Disregard and delete the above post, finally got auto-start to work.
What was the issue? I cannot see how replacing an FSUIPC7.exe can affect auto-start.
As I said, all I know about auto-start is in the FAQ entry. I can update this if you have any new information that may help with this issue.
John
Hi John,
Wish I had better insight into how the installer sets things up for auto startup. It took me at least 4 hours last night to finally get auto startup to work with the new FSUIPC7 7.5.6 version. I finally got it working by again renaming the EXE.xml and rerunning the installer so a new EXE.xml file would be created (this did not work the first time I tried it). I then went back into the new EXE.xml file and pasted in the required entries for all the other apps that use the EXE.xml. I then reformatted the FSUIPC7 EXE.xml entry from a looong single line into the multi-line format all the others apps use since that makes it easier to see what is going on. I wish the FSUIPC7 installer would use the multiline format like the other apps do to start with.
If auto startup has been in use (as it always is for me) when the installer is run to install a new FSUIPC7 version, the entry in the EXE.xml file really doesn't change, it always ends up to be exactly the same because (at least in my case) the location of FSUIPC7.exe does not change. So if auto startup doesn't work as expected after an update is install, it's not because the existing EXE.xml code is wrong somehow. Rather, it seems when the installer runs it must create a setting somewhere that triggers the FSUIPC7 EXE.xml entry to be "used". I would like to find where that setting is. I thought that setting might be in the Win11 Registry, but have not been able to find it. Do you know where that setting is, or what the installer does to "arm" auto startup via the EXE.xml file?
I don't know why auto startup worked after replacing the newly installed FSUIPC7.exe version by simply pasting in the previous FSUIPC7.exe file as described in my original post above. Wish I did understand that because it would probably be informative if nothing else.
In any case, bottom line is that now all is working with the updated FSUJIPC7.exe ver 7.5.6.
Thanks for help,
Al
Posted by: @ark1320Wish I had better insight into how the installer sets things up for auto startup.
Its nothing complicated: it just adds an entry to the EXE.xml file (for the default and recommended method of auto-start)
Posted by: @ark1320It took me at least 4 hours last night to finally get auto startup to work with the new FSUIPC7 7.5.6 version.
But why? Just run the installer and this should do this. If there are issues, then these are documented in the FAQ entry. The two main cuses of auto-start not being installed are:
1. The EXE.xml file being an invalid XML document. Some installers for 3rd-party add-ons seem to corrupt tjhis file
2. The EXE.xml being encoded in a format that prevents the EXE.xml file from being loaded by the installer.
Both of these issues are documented in the FAQ entry on auto-start. If you think this FAQ entry is missing something, then please let me know.
Posted by: @ark1320I finally got it working by again renaming the EXE.xml and rerunning the installer so a new EXE.xml file would be created (this did not work the first time I tried it).
If that didn't work, then you need to show me the InstallFSUIPC7.log file so that I can take a look. There is no point posting about these things if you do not provide me the files so that I can investigate.
Posted by: @ark1320I wish the FSUIPC7 installer would use the multiline format like the other apps do to start with.
Yes, that would be better, but just not possible with the tools I am using. White space is irrelevant in xml files anyway.
I would be a lot of wotk for me to do this (i.e. remove the xml plugin I am using and write my own - several weeks, just not worth it). 99% of users never need to look at this file anyway.
Posted by: @ark1320If auto startup has been in use (as it always is for me) when the installer is run to install a new FSUIPC7 version, the entry in the EXE.xml file really doesn’t change,
No, but when you update / re-install, the previous version is uninstalled, and so the EXE.xml entry is removed. This was just far easier to deal with when I wrote the installer, to handle such things as change in location, etc.
Posted by: @ark1320So if auto startup doesn’t work as expected after an update is install, it’s not because the existing EXE.xml code is wrong somehow. Rather, it seems when the installer runs it must create a setting somewhere that triggers the FSUIPC7 EXE.xml entry to be “used”.
Not at all. There is no such entry or setting. It is the functionality of MSFS that reads the EXE.xml and starts the launch items defined there.
Posted by: @ark1320Do you know where that setting is, or what the installer does to “arm” auto startup via the EXE.xml file?
There is no such setting.
Posted by: @ark1320I don’t know why auto startup worked after replacing the newly installed FSUIPC7.exe version by simply pasting in the previous FSUIPC7.exe file as described in my original post above. Wish I did understand that because it would probably be informative if nothing else.
Nor do I....! Could it not be that FSUIPC7 was auto-started, but crashed, as you copied across the initial 7.5.6 released exe that CTDs when processing your myevents.txt file? I can think of no other reason...
As I keep telling you, it is MSFS that auto-starts 3rd party apps defined in the EXE.xml. If this is not working correctly, and your EXE.xml is correct, report to ASobo. I cannot help with this.
Posted by: @ark1320In any case, bottom line is that now all is working with the updated FSUJIPC7.exe ver 7.5.6.
You seem to be using different installations for MSFS2020 and MSFS2024, and only installing for one and then copying files across. Why do this? Just run the installer twice - only takes a minute or so. And any issues, check your InstallFSUIPC7.log file.
As I keep telling you, the FAQ entry on auto-start contains ALL information needed to sort out any auto-start issues. Do you think this is missing something? I have yet to come across any issue not covered in that FAQ entry, and this is no exception.
If you think there is anything not covered, show me your files - attach your EXE.xml plus the InstallFSUIPC7.log file and I will take a look.
John
Posted by: @fsuipcYou seem to be using different installations for MSFS2020 and MSFS2024, and only installing for one and then copying files across.
Actually, I didn't do that. I just asked about the copy and paste approach since I couldn't get things to work. I did run the installer for each sim install.
After running the installer and auto startup did not work, I checked the EXE.xml file and the FSUIPC7 entry was correct, the same as always. The other apps with entries in the EXE.xml started as they should, so the EXE.xml was not corrupted. So it is a mystery why I was having the auto startup problem. I did download the new FSUIPC7 version as few times last night, so maybe I didn't initially have the updated version of FSUIPC7 7.5.6, but then did get that and so finally it all worked.
Thanks,
Al