FSUIPC —> APL no longer connecting

[wigmore]

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!

[John Dowson]

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

[John Dowson]

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.

 

[wigmore]

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?

Edited 22 hours ago by wigmore

[John Dowson]

1 hour ago, wigmore said:

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?

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

[wigmore]

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.

[John Dowson]

57 minutes ago, wigmore said:

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).

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.

1 hour ago, wigmore said:

but in the meantime the .exe you posted is a fix.

That exe is the previous version, 7.4.3.

[John Dowson]

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

[John Dowson]

Here's the analysis from Microsoft:

Quote

Analyst comments:

At this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.
1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
3. Run "MpCmdRun.exe -SignatureUpdate"

Alternatively, the latest definition is available for download here: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/manage-updates-baselines-microsoft-defender-antivirus

Thank you for contacting Microsoft.

Click here for more information

 

 

John