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
For ALL auto-start issues, please see the FAQ entry on this issue:
https://fsuipc.com/community/fsuipc-faq-issues/msfs-fsuipc7-auto-start-with-msfs2020-2024/
If you cannot figure it out, please show me / attach your InstallFSUIPC7.log file (you should check this for errors!) and your EXE.xml file (location will be in the InstallFSUIPC7.log file).
John
Unistalled the program and reinstalled it. The folder is always the same. With the old version no problem, wtth this yes.
The installer with administrator right
Posted by: @muffoThe installer with administrator right
Do not run the installer with admin rights. Just double-click it and then accept elevated privileges.
As I tried to tell you, it is the encoding of your EXE.xml file - it is in UTF-8-BOM. I am surprised that this was even updated by the installer. I will run some tests on this when time permits.
Try the attached EXE.xml where I have changed the encoding, and also moved the launch of FSUIPC to first position.
John
John,
I came across the post I have pasted below, and thought it was worth making sure you aware in case you had not seen it. I don't know if it might explain some of the above reported issues. The post, and related posts are from here (scroll down a bit):
https://www.avsim.com/forums/topic/642527-msfs-auto-fps-app/page/266/#comments
Al
Today, while updating FSUIPC to the latest version, I found its uninstaller stuck in a loop while trying to update the MSFS exe.xml. After digging into it, the issue turned out not to be FSUIPC at all, but a legacy AutoFPS behaviour: recent versions saved the exe.xml in a non‑standard format when enabling Auto‑start with MSFS. MSFS accepted it, but the FSUIPC uninstaller did not.
The fix is now in place — the installer automatically detects this legacy format and rewrites the exe.xml into a fully compatible one without altering any of its contents.
If this is affecting you, the fix is available in 0.4.6.4‑test1 or later and will be formally released shortly. Please don’t raise this with the FSUIPC developer if you hit the issue after using AutoFPS with Auto‑start enabled — it’s an AutoFPS problem, and it’s already being resolved for everyone.
Posted by: @ark1320I came across the post I have pasted below, and thought it was worth making sure you aware in case you had not seen it
Thanks, I hadn't seen that. There have been 3rd party app installers that corrupt the exe.xml file (i.e. don't write it as a fully formed xml document), ones that delete it completely and create a new one (and thus removing other 3rd party apps entries) and others that change the format to a *-BOM (or UTF-8). But these installers tend to get fixed over time, as is being done with the AutoFPS installer.
There is not much I can do if the EXE.xml document cannot be loaded (as an xml document), due to the format or encoding. However, the uninstaller shouldn't hang / loop really - it should just log a message, leave the exe.xml as it is and continue. I will see if I can update the uninstaller to do this.
Cheers,
John
Hi John, I substitute my exe.xml with your. Nothing. I tried to load fsuipc with msfs.bat, nothing. I think that there is a problem on my windows registry.
If I load fsuipc on manual, it woks