All Activity

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

I see. I was too fast saving the .ini file after ending FSUIPC. Thank you, Karl

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

John, this is a lot of work, so I thought I could do this: In section [LuaFiles] There are some scripts listed I don't use anymore, as an example: 5=kaha_msfs_lua is not needed anymore, the file doesn't exist. Also there's no CL5 entry in the .ini file. I replaced the line with 5=someluascript but at the next start of FSUIPC the line again reads 5=kaha_msfs_lua. Where does FSUIPC store this information? Karl

I managed to simplify the processInput function, which reduced the size of the Lua script by about one third. In case anyone's interested, I've attached the current working version of the script. Cheers, Isak KeypadRadio.lua

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 don't get it on Windows 10 for the 7.5.4 release.

Ok, all makes sense. I’m just running Windows Defender FYI, no other antivirus. I’m wondering if it’s tied in to another user reporting in a separate post about Windows Defender identifying something in the package as a threat (I get that too). I’ll do some more tinkering with it on my side, but in the meantime the .exe you posted is a fix. Thanks again for the quick support here, really impressive stuff.

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

Hi, thanks for the super quick response, really appreciated. This is quite curious, because I just had a poke around my FSUIPC folder for a log file and no such file had been generated. Eventually I realised that there was no FSUIPC.exe application either. Although the MSFS batch file exists so I still get the "preparing the cabin" notification when opening MSFS.... but it seemed that FSUIPC wasn't starting because it simply didn't exist!? I tried reinstalling and same thing. Then tried downloading the .exe you sent in your post to this thread and placing it directly in my FSUIPC folder, and now it's working with no issues. So I think what's happening is that the installer for the new version isn't actually installing FSUIPC.exe at all? Could there be a cause for that?

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

*** Moved from main support forum to FSUIPC7 support sub-forum *** Good day, Great product. For some reason, MSFS 2024 started crashing after the installation of FSUIP 2024. It works fine with MSFS 2020. So, I had to uninstall the FSUIP 2024 version and MSFS began working again. Is there anything I need to do to fix this? Regards. cehallow

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

Hi! Installed the new version of FSUIPC this morning. As soon as this was installed, A Pilot’s Life immediately starting failing to connect to MSFS via FSUIPC - it doesn’t detect sim at all. Have tried all the usual steps… restarting sim, restarting APL, restarting PC, reinstalling FSUIPC, but can’t get it to connect. Is there anything else I can try to fix this one / any more info you need? Failing that is it possible to roll back to previous version for now? Thanks in advance!

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.

https://www.virustotal.com/gui/file/dd0230e61b29ac2c5511a9527441254e37de772264d60063007dde4789891dcd?nocache=1

👍 Thanks for the update. John

John, this now works in 7.5.4, thank you. Karl

Ahhh, I understand. Thank you, I will do this. Karl

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