I moved from the Market Place to Inibuilds today. After downloading from the Inibuilds site and rebooting etc, I loaded up 2024 in the anticipation of doing a flight. However, that wasn't to be.

These are the problems I have encounted while parked at a gate;

• Nothing happens when I turn the two battery switches on. The aircraft is still completely unpowered.

• The strobe lights are flashing while the aircraft is parked, even with no power and all light switches are turn off.

• In the EFB, after clicking on "wheel chokes" the green confirmation appears at the top, but chokes are not visible.

• The throttle levers are stuck in Max Reverse and won't budge.

Is there something I've failed to do? I had no problems at all while the aircraft was with Market Place.

Bruce R

Taken from a post by Harsh on the Synaptic Discord:

"If you're having any issues after switching to the ini Store version of the Synaptic A220, reference the checklist below

1 - Uninstall the MS Marketplace version to avoid any conflicts, and disabled the Marketplace version in the in-game store. We strongly recommend deleting the A220 WASM/work folder as well, when switching to the iniManager version.

2 - Restart your flight, sometimes the sim doesn't load the WASM correctly on initial boot.

3 - Uninstall the CPDLC mod as it's not working with v1.0.7, that will require a community mod update that we don't support or oversee.

4 - Please also ensure you're installing the aircraft with the latest iniManager version (v2.6.0), as we require this version to avoid issues.

5 - Uninstall and reinstall iniManager and the Synaptic A220

We'd like to thank everyone for the amazing support over the past month, happy flying!"

Thank you for getting back. That’s something I missed. I’ll look at it tomorrow.

Bruce R

Have followed ALL of the above instructions with no luck - loads cold & dark. Must I delete the radar map module?

Did not have the CPDLC mod.

Edited August 29Aug 29 by Trevor

My apologies - problem solved - I did not realize that I had a 2020 AND a 2024 version streamed. I had only disabled the 2024 version 🤣

10 hours ago, Bruce R said:

I moved from the Market Place to Inibuilds today. After downloading from the Inibuilds site and rebooting etc, I loaded up 2024 in the anticipation of doing a flight. However, that wasn't to be.

These are the problems I have encounted while parked at a gate;

• Nothing happens when I turn the two battery switches on. The aircraft is still completely unpowered.

• The strobe lights are flashing while the aircraft is parked, even with no power and all light switches are turn off.

• In the EFB, after clicking on "wheel chokes" the green confirmation appears at the top, but chokes are not visible.

• The throttle levers are stuck in Max Reverse and won't budge.

Is there something I've failed to do? I had no problems at all while the aircraft was with Market Place.

Bruce R

I have the same issue and I purchased it from inibuilds, I never bought it until today when it came out for direct purchase. I have spent several hours trying to sort it out to no avail. This is for 2020

Edited August 29Aug 29 by mwa05

9 hours ago, noisytwit said:

Taken from a post by Harsh on the Synaptic Discord:

"If you're having any issues after switching to the ini Store version of the Synaptic A220, reference the checklist below

1 - Uninstall the MS Marketplace version to avoid any conflicts, and disabled the Marketplace version in the in-game store. We strongly recommend deleting the A220 WASM/work folder as well, when switching to the iniManager version.

2 - Restart your flight, sometimes the sim doesn't load the WASM correctly on initial boot.

3 - Uninstall the CPDLC mod as it's not working with v1.0.7, that will require a community mod update that we don't support or oversee.

4 - Please also ensure you're installing the aircraft with the latest iniManager version (v2.6.0), as we require this version to avoid issues.

5 - Uninstall and reinstall iniManager and the Synaptic A220

We'd like to thank everyone for the amazing support over the past month, happy flying!"

Thank you.

For those migrating (2024), I had 2 A220 folders in the WASM folder. Initially, I deleted only "synaptic-aircraft-a220". Still had the issue. Then, I found and deleted "inibuilds-aircraft-a220" from the same WASM folder. Plane works fine now.

Yep, your issues sound familiar with mine. First it looked okay when I downloaded it last night, but now since I disabled the automatic ground power (switched it back and forth)in the settings all is crazy.

Thanks everyone. Now have the 220 up and running. This is what I did;

Opened up 2024 and disabled the 220 in "My Library". Rebooted and went back into 2024 to find it was still broken, despite it being installed in the IniManager.

Opened the IniManager and uninstalled the 220.

Opened up the MSFS2024 folder in C/Users/My Name/App Data, etc, and deleted any reference to the A220 I could find.

Re-installed the 220 in the Inimanager, rebooted and opened 2024. Everything now works.

Bruce R

On 8/29/2026 at 2:13 PM, mwa05 said:

I have the same issue and I purchased it from inibuilds, I never bought it until today when it came out for direct purchase. I have spent several hours trying to sort it out to no avail. This is for 2020

Me too!

I managed to get it running once by rebooting my PC and then placing the aircraft on to a runway - everything was OK. Then with GSX, I moved the aircraft to a gate, shut the engines down and all was OK. Before I started the flight, I went back to the main menu and restarted it at a gate. Yep, nothing happened when I turned the batteries on.

On 8/29/2026 at 3:08 AM, noisytwit said:

Taken from a post by Harsh on the Synaptic Discord:

"If you're having any issues after switching to the ini Store version of the Synaptic A220, reference the checklist below

1 - Uninstall the MS Marketplace version to avoid any conflicts, and disabled the Marketplace version in the in-game store. We strongly recommend deleting the A220 WASM/work folder as well, when switching to the iniManager version.

2 - Restart your flight, sometimes the sim doesn't load the WASM correctly on initial boot.

3 - Uninstall the CPDLC mod as it's not working with v1.0.7, that will require a community mod update that we don't support or oversee.

4 - Please also ensure you're installing the aircraft with the latest iniManager version (v2.6.0), as we require this version to avoid issues.

5 - Uninstall and reinstall iniManager and the Synaptic A220

We'd like to thank everyone for the amazing support over the past month, happy flying!"

After did all of step it not work then I been in Market Place, I removed the aircraft and disabled it. Now it work !

15 hours ago, Peterwk10 said:

I managed to get it running once by rebooting my PC and then placing the aircraft on to a runway - everything was OK. Then with GSX, I moved the aircraft to a gate, shut the engines down and all was OK. Before I started the flight, I went back to the main menu and restarted it at a gate. Yep, nothing happened when I turned the batteries on.

I rebooted the PC, did a fresh install in MSFS202. First attempt - great, everything worked. second attempt - back to normal.

Most of the things suggested by Harsh are not applicable to me, and the remainder didn't do anything to enable a consistent proper start up of the aircraft.

I'm going to give up on this aircraft and I'll wait until there's some positive developments from inibuilds/Synaptic.

On 8/31/2026 at 3:58 PM, Peterwk10 said:

I rebooted the PC, did a fresh install in MSFS202. First attempt - great, everything worked. second attempt - back to normal.

Most of the things suggested by Harsh are not applicable to me, and the remainder didn't do anything to enable a consistent proper start up of the aircraft.

I'm going to give up on this aircraft and I'll wait until there's some positive developments from inibuilds/Synaptic.

Exactly the same to me. Every day I have to reinstall MSFS2020 version from the inibuilds installer, for the screens to light up. I think I might go back to the marketplace version; that one always worked. I'll give 1.0.9. a last chance :)