John Dowson

Strange...but I have already DM'ed you your key details... John

This probably ,means that you are using an unregistered version, i.e. there is no license/key file (FSUIPC7.key) in your installation folder. Did you install into a different folder? When you re-installed. were your previous key details shown on the last screen, and did you skip key validation? Installation does not touch your FSUIPC7.key file, unless you opt to re-validate. John

Log in to your SimMarket account and get your purchased key from there. I can also PM you your key details. John

Sorry - for MSFS 2024 it would be C:\Users\[YOUR USERNAME]\AppData\Roaming\Microsoft Flight Simulator 2024\UserCfg.opt

You need to delete/rename the steam UserCfg.opt file, located at C:\Users\[YOUR USERNAME]\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt If this file is present, the installer presumes you are installing for Steam and not MS Store. John

I don't think FSUIPC will create this folder, but not 100% sure. The FSUIPC installer reads the InstalledPackagesPath entry/line, then removes the first 23 characters (i.e. the characters 'InstalledPackagesPath "', then removes the last two characters, which should be the closing quotes and the new line character. Maybe there is no new line after your InstalledPackagesPath entry? If not, then the last character of the path will be removed. So, check there is a new line after the InstalledPackagesPath entry. This is obviously not ideal - I will correct the installer for the next release to actually check for the new line and only remove if present. Let me know what your entry looks like when you get a chance. Regards, John

👍

The Community folder location is taken from the InstalledPackagesPath entry in your UserCfg.opt file (usually the last line) - what is the value there? Where was the WASM actually installed? Does the folder C:\Users\Carlos\AppData\Roaming\Microsoft Flight Simulator\Package\ exist as well? John

As you quoted, in the FSUIPC7.ini file (which is in your FSUIPC7 installation folder) - did you not look there? I have moved your post to the FSUIPC7 sub-forum. John

Here's the analysis from Microsoft: This was from yesterday. Should be ok with the latest virus definition update. John

You can just remove/delete that line. This is the only place that FSUIPC stores that information - if it re-appeared, FSUIPC must still have been running when you removed it - I can't see how else it could have re-appeared. Only edit the LuaFiles section when FSUIPC is not running. John

Here's the analysis from Microsoft: John

The on-line submission to Microsoft also detected no malware - you probably won't be able to access this but here's the link: https://www.microsoft.com/en-us/wdsi/submission/4df57e58-4a1e-4d81-ac6f-ad28e26e1fdf Hopefully this will be fixed in a virus definition update shortly. Cheers, John

It was reported on the exe I believe. And I have had it stopped at run-time and removed from the installation folder by Windows Defender. As you are using windows defender, you should look at the threat removal/quaranteen and restore it from there. That exe is the previous version, 7.4.3.

I think it may be your anti-virus blocking and quarantining the FSUIPC7.exe. I have also experienced this on occasion with this release, but not always. It is very strange - I have reported this as a false-positive to Microsoft so hopefully should be fixed with a virus definition update. Check your anti-virus - if you are using anything other than Windows Defender you should report this o your anti-virus definition provider. John

Also, what happens if you manually start FSUIPC7 once MSFS2024 is already running? You don't need to re-install to test this - just double click the FSUIPC7.exe (for your MSFS2020 installation) and it should run ok (although you won't have access to the WASM facilities if this is not installed in MSFS2024).

Please use the FSUIPC7 sub-forum for all issue/questions on FSUIPC7 / MSFS2020 / MSFS2024. I have moved your post. Thanks, There is no fix. This was also reported in the MSFS2024 SU16 beta a while ago, but was later fixed see If MSFS2024 is crashing, then it is an issue for Asobo and you should check the CTD reports there - there is nothing I can do to investigate crashed in MSFS2020/MSFS2024. And if it is crashing, it will be something that needs to be addressed/fixed by Asobo. I also just fired up MSFS2024 here to check and everything seems fine here. John

I am now getting this again in Windows Defender - I will report to Microsoft.... John

Such connection issues are usually due to FSUIPC7 running at a different privilege level to APL. If you had previously changed FSUIPC7 to be ran as admin, this will have been lost when you re-install. So maybe try running the latest version with admin privileges, to see if it then connects.

Can you show me / attach your FSUIPC7.log file please. The previous version is attached below. Rename your current FSUIPC7.exe (e.g. FSUIPC7.exe.754) and save the attached to your FSUIPC7 installation folder and see if that still works. Please send me the log for the current version before you do this. Thanks, John FSUIPC7.exe

That will be a false positive - please report to the ant-virus provider you are using. I have also had this issue with Windows Defender. I reported this and it seems to be ok now, although I did get one download attempt blocked due to a threat, but subsequent downloads and installs seemed to be ok. If I get further false=positives from Windows Defender, I will report, but if you are using other anti-virus software you will need to report this yourself, or allow the threat/rstore the file, as there is not much I can do. There is no virus in FSUIPC7. John P.S. This is for FSUIPC7 so I have moved your post to the FSUIPC7 sub-forum.

👍 Thanks for the update. John

You will have to do this manually. First remove all the [LuaFiles] entries that you are no longer using, and move the corresponding lua scripts out of your FSUIPC7 installation folder. Then, for each lua script remaining, you can renumber it and also change the assignment reference. So, for example, if you changed: 16=Elevator_Trim to 1=Elevator_Trim You would need to replace all occurrences of 'CL16:' with 'CL1:', i.e. change the lua reference numbers in the assignments to the new index number of the lua script. If you are re-organising your luas, you should also consider moving them all to a subdirectory and using the LuaPath ini parameter under the [LuaFiles] section. John

No idea. FSUIPC7 does not generate that file on its own - there must be something else running that is generating those files, probably a lua script. Check your assignments and lua files in your FSUIPC7.ini file.

Better to keep the terminate function - always a good idea to close com connections. Cheers, John