I own the Fenix A320 since exactly 2 months now and wasn't able to get this add-on running inside the MSFS. Two months of intense troubleshooting and e-Mail back and forth with Fenix support, but this thing won't start. And not in a "cold & dark" way. When I load the aircraft and the airport the Fenix app would start automatically, but when I enter the flight deck only a placeholder graphic on the PFD appears and everything else is dead and I can't interact with it, except for turning the switches. But the EFB is completely dark. A couple updates ago it said at least that it is unable to connect. I'm certain that I've spend over 50hrs of troubleshooting and one complete re-install of the MSFS because the Fenix denies itself to work, no matter what I do. The PMDG 736, the JustFlight BAe 146, the BlackSquare Dukes and the Heatblur F-14 worked straight out of the box and I never had any issue with anything in MSFS, except for the Fenix. Do anyone of you have the slightest idea what could cause this? It appears to be some kind of validation issue, but then again the Fenix App itself works just fine. I just can't engage with anything in the aircraft. Any ideas?

Show less

 

 

46 minutes ago, Thommas said:

I own the Fenix A320 since exactly 2 months now and wasn't able to get this add-on running inside the MSFS. Two months of intense troubleshooting and e-Mail back and forth with Fenix support, but this thing won't start. And not in a "cold & dark" way. When I load the aircraft and the airport the Fenix app would start automatically, but when I enter the flight deck only a placeholder graphic on the PFD appears and everything else is dead and I can't interact with it, except for turning the switches. But the EFB is completely dark. A couple updates ago it said at least that it is unable to connect. I'm certain that I've spend over 50hrs of troubleshooting and one complete re-install of the MSFS because the Fenix denies itself to work, no matter what I do. The PMDG 736, the JustFlight BAe 146, the BlackSquare Dukes and the Heatblur F-14 worked straight out of the box and I never had any issue with anything in MSFS, except for the Fenix. Do anyone of you have the slightest idea what could cause this? It appears to be some kind of validation issue, but then again the Fenix App itself works just fine. I just can't engage with anything in the aircraft. Any ideas?

Show less

 

 

Post your problem on their Discord page.

2 minutes ago, Bobsk8 said:

Post your problem on their Discord page.

But I posted it here as just another option. I've spend dozents and dozents of hours following directly what Fenix support suggested to me. And over 50 hours later of doing so I'm still on square one. So I think it is just valid to start asking other people everywhere I can.  And opening a topic on avsim made a lot of sense to me. 

All I can suggest is to do a complete uninstall of the Fenix app and delete any leftover files. Restart your PC and install from scratch.

Ensure that your PC's antivirus program isn't quarantining any Fenix files upon reinstallation and that the Windows Firewall is permitting Internet access to the Fenix app.

Don't use any third party add-ons, nor any third party liveries and test if you can run the Fenix A320 in as close to a vanilla MSFS setup as possible.

1 hour ago, Thommas said:

But the EFB is completely dark.

If  your  efb is  dark its  most likely  your either  not  running  the fennix  app as  addmin,  has  to be  the  same  as  per  your msfs  , or  that  your  av  is   some  how  blocking  it

2 hours ago, F737MAX said:

All I can suggest is to do a complete uninstall of the Fenix app and delete any leftover files. Restart your PC and install from scratch.

Ensure that your PC's antivirus program isn't quarantining any Fenix files upon reinstallation and that the Windows Firewall is permitting Internet access to the Fenix app.

Don't use any third party add-ons, nor any third party liveries and test if you can run the Fenix A320 in as close to a vanilla MSFS setup as possible.

I did all that, including an entire re-install of the MSFS. And I excluded absolutely everything with the name Fenix in it in my AV. I don't use any third party add-ons except for other payware aircraft, like the PMDG 736, the JF BAe 146, the Black Square Dukes and the Heatblur F-14. And I even uninstalled those once, so the Fenix A320 was the  only add-on at all.
I have done everything they(Fenix) suggested on their homepage and had dozents and dozents of e-Mail back and forths with them and nothing they've suggested changed anything. And all the log files that I've send to them repeatedly told them nothing either. Additionally to that I've send many screenshots of the state that the aircraft is in. I've also uninstalled my AV and deactivated Microsoft Defender and then ran MSFS and the Fenix -it didn't change anything. I've started the Fenix App manually and before the MSFS, I ran both(MSFS & Fenix) and only one of them as admin. I tried every possible combination. I looked up my excluded port range and searched for used, or blocked ports, but none of them were even remotely touching port 8083.   

Edited October 4, 20241 yr by Thommas

5 minutes ago, Thommas said:

And I excluded absolutely everything with the name Fenix in it in my AV.

The only thing I can think of is instead of using the name Fenix, exclude the entire MSFS directories from AV. I did this a while back due to some weird issues.

Uninstall your AV, then Fenix.

Re-install Fenix as an admin and retry.

Then you will know whether its your AV.

You could also try disabling User Access Control in Windows.

Just now, flyingscampi said:

Uninstall your AV, then Fenix.

Re-install Fenix as an admin and retry.

Then you will know whether its your AV.

You could also try disabling User Access Control in Windows.

Edit: sorry just saw you've already tried this 😞

9 minutes ago, BrammyH said:

The only thing I can think of is instead of using the name Fenix, exclude the entire MSFS directories from AV. I did this a while back due to some weird issues.

I did that too, but thanks for your suggestion.

 

 

 

Have you tried disabling UAC?

Turn down the slider in control panel to 'Never Notify', then edit the following registry key and reboot:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

Set 'EnableLUA' DWORD to 0 (disable) or 1 (enable)
 

it would  help is  you list what windows your  running  and  pc  specs, if  you have  tried  all  the  above  methods  it  could  be  also your  windows could  be  corrupted  some  how you could  try this  as  a last  resort i did this  awhile  ago with no issues

 

https://www.youtube.com/watch?v=ldqFdcGL1X0&t=287s

 

16 hours ago, pete_auau said:

it would  help is  you list what windows your  running  and  pc  specs, if  you have  tried  all  the  above  methods  it  could  be  also your  windows could  be  corrupted  some  how you could  try this  as  a last  resort i did this  awhile  ago with no issues

 

https://www.youtube.com/watch?v=ldqFdcGL1X0&t=287s

 

You Sir deserve a medal, because you saved my life. I was struggeling with this issue for almost exactly two months. Around sixty emails filled with log files, screenshots and descriptions, to and from the developer and dozents over dozents of hours of troubleshooting, uninstalling, re-installing and searching for files that may, or may not exist. And now it is finally over and I almost can't believe it. Hats off and all thanks to you.

A very, very grateful flight-simmer

11 hours ago, Thommas said:

You Sir deserve a medal, because you saved my life. I was struggeling with this issue for almost exactly two months. Around sixty emails filled with log files, screenshots and descriptions, to and from the developer and dozents over dozents of hours of troubleshooting, uninstalling, re-installing and searching for files that may, or may not exist. And now it is finally over and I almost can't believe it. Hats off and all thanks to you.

A very, very grateful flight-simmer

so it  was  a windows  issues  some  corrupt  files  i take  it,glad  it  got  sorted,  now  you know  what to do  next  time  if  windows  starts  to act  up  🙂