I have a dual WinWing MCDU setup. Capt & Fo. With both MCDUs active none of my WinWing products will work. Disabling/unplugging one MCDU and ops normal. 

I contacted WinWing support about this. 

This is the answer I got from WinWing support in regard to dual MCDU support for the A340:

Dear customer, currently due to issues of the Inibuild A340 plane model, we can only support MCDU of Captain side.

Please wait for the plane model manufacturer to update the plane.

 

Edited January 20Jan 20 by Eurosky

Hi. Sorry this is being communicated this way as we have not been notified about needing to do anything special on our side. 
I will ask the team to reach out to WW and see if what they say. 

On 1/20/2026 at 2:15 AM, Eurosky said:

I have a dual WinWing MCDU setup. Capt & Fo. With both MCDUs active none of my WinWing products will work. Disabling/unplugging one MCDU and ops normal. 

I contacted WinWing support about this. 

This is the answer I got from WinWing support in regard to dual MCDU support for the A340:

Dear customer, currently due to issues of the Inibuild A340 plane model, we can only support MCDU of Captain side.

Please wait for the plane model manufacturer to update the plane.

 

I only have one MCDU so I can't confirm or deny that you can use two units with the 340, but can you confirm that you have one MCDU set to CA and the other set to FO in SimAppPro? 

13 hours ago, Lude2Envy said:

I only have one MCDU so I can't confirm or deny that you can use two units with the 340, but can you confirm that you have one MCDU set to CA and the other set to FO in SimAppPro? 

I can confirm that. With both MCDUs connected and correctly configured, none of my Winwing products work (I have pretty much all of them). As soon as I disconnect the FO MCDU, everything comes back to life.

Worth mentioning that everything connected from Winwing works flawlessly on the Fenix A320.

Edited January 31Jan 31 by Eurosky

On 1/31/2026 at 12:39 AM, Eurosky said:

I can confirm that. With both MCDUs connected and correctly configured, none of my Winwing products work (I have pretty much all of them). As soon as I disconnect the FO MCDU, everything comes back to life.

Worth mentioning that everything connected from Winwing works flawlessly on the Fenix A320.

Ah, that stinks. Sorry man. Do you know if it works with FSL also? 

Hi. This should be working now as we have tested it with success on our side.
You have to set the MCDUs up as independent units where one is marks CA_MCDU and the other is FO_MCDU in Sim App Pro. 
Then restart the service and it should display correctly. 

IniSteave,

I cannot get it working with both WinWing MCDUs connected. Got it set up independently as you described in the SimApp Pro. I am on the latest firmware and SimApp version. With both connected none of my Winwing products work. When I disconnect FO MCDU, all good. 

I cannot understand how you guys got both working. 

3 hours ago, Eurosky said:

IniSteave,

I cannot get it working with both WinWing MCDUs connected. Got it set up independently as you described in the SimApp Pro. I am on the latest firmware and SimApp version. With both connected none of my Winwing products work. When I disconnect FO MCDU, all good. 

I cannot understand how you guys got both working. 

Did you install the 340 from the Marketplace or the iniManager? When I had mine installed through the Marketplace, I had it actually "installed" instead of "streamed." If there were updates I had to manually update it. Since they now offer it through the iniManager, I uninstalled it from the Marketplace and now have it installed through the manager. Just a thought in case you're in a similar position and running an older version of the 340. Try running SimAppPro as administrator too. 

5 hours ago, Lude2Envy said:

Did you install the 340 from the Marketplace or the iniManager? When I had mine installed through the Marketplace, I had it actually "installed" instead of "streamed." If there were updates I had to manually update it. Since they now offer it through the iniManager, I uninstalled it from the Marketplace and now have it installed through the manager. Just a thought in case you're in a similar position and running an older version of the 340. Try running SimAppPro as administrator too. 

Installed it from the IniManager. Deleted in the Marketplace.  SimAPP pro in administrator mode had no effect either. It's strange because everything works just fine in the Fenix with the dual MCDU setup. I honestly have no idea how to get both MCDUs to work with the A340. 

Edited February 5Feb 5 by Eurosky

I noticed the same Problem. Yesterday I updated the SimAppPro to Version 1.16.88 and proceeded with Firmware-

Updates for MCDU-Cpt (v1.04), MCDU-Co (v1.04) and btw.ECAM (v1.01). After loading MSFS2024 and iniBuilds A340-300

respectively restart SimAppPro all was working fine, that means : FCU, EFIS 2x, MCDU (2x), ECAM and AGP.

2 hours ago, Skycowboy said:

I noticed the same Problem. Yesterday I updated the SimAppPro to Version 1.16.88 and proceeded with Firmware-

Updates for MCDU-Cpt (v1.04), MCDU-Co (v1.04) and btw.ECAM (v1.01). After loading MSFS2024 and iniBuilds A340-300

respectively restart SimAppPro all was working fine, that means : FCU, EFIS 2x, MCDU (2x), ECAM and AGP.

Yep, all working now after latest SimApp update.