Fix GSX Pro not working in MSFS 2024 by repairing Community links, Couatl, the toolbar and profiles with our symptom-based checklist.
GSX Pro usually stops working in Microsoft Flight Simulator 2024 because its Community-package link points to the wrong simulator, GSX or Couatl is outdated or blocked, the toolbar panel is disabled, or an aircraft/airport profile conflicts. Update it, repair the MSFS 2024 link, confirm Couatl runs, then test a default aircraft and airport.
Can GSX Pro run on console versions of MSFS 2024?
GSX Pro requires the PC version of MSFS 2024. Its Couatl scripting engine runs as an external Windows program and communicates with packages linked into the Community folder. Those components cannot run on Xbox Series X|S, PlayStation 5 or PS5 Pro, so there is no console-side setting that can make GSX work.
How do I fix GSX Pro in MSFS 2024?
- Close every GSX component. Exit Microsoft Flight Simulator, the GSX installer and Couatl. Check Task Manager for a Couatl process left behind after the simulator closed, end it, then continue.
- Update GSX through its installer. Let the updater check both the GSX package and Couatl rather than copying files from an older installation. A working MSFS 2020 installation does not mean its MSFS 2024 links or supporting components are correct.
- Repair the MSFS 2024 Community link. Confirm that the installer has selected MSFS 2024 and the Community folder actually used by that installation. This matters after moving the Packages location, changing drives or using a third-party package linker. Do not copy the installer-managed GSX folders manually from the MSFS 2020 Community folder. Our guide to repairing the GSX installation, licence and Community links covers this part in more detail.
- Make sure MSFS loaded the panel. Start the simulator normally and confirm the GSX panel is enabled in the in-sim toolbar. If MSFS started in Safe Mode after a crash, third-party packages are intentionally excluded, so the missing GSX icon is expected.
- Check that Couatl is running. An endlessly loading panel, blank window or message that the scripting engine has not started points to Couatl rather than an airport profile. Check Windows Security or other security software for a quarantined component. Restore or permit only a verified GSX file; do not disable protection globally. Run MSFS and Couatl at the same privilege level, preferably both as normal user processes.
- Run a clean baseline test. Load a stock airport and a GSX-compatible default aircraft at a recognised parking stand. Keep the aircraft stationary, set the parking brake and satisfy any engine, door or chock request shown by GSX. This separates an installation failure from a problem tied to one add-on.
- Remove competing packages temporarily. Leave GSX enabled but move unrelated toolbar utilities, ground-service add-ons, airport sceneries and custom profiles out of the active Community folder. Add them back one at a time after GSX works.
- Reinstall only as a last step. If updating and repairing the links fail, uninstall and reinstall through the GSX installer. Back up user-created profiles first, and avoid deleting unrelated Community packages.
What does each GSX failure symptom mean?
| Symptom | Likely cause | Best next check |
|---|---|---|
| No GSX toolbar icon | Wrong Community folder, broken package link, disabled panel or Safe Mode | Repair the MSFS 2024 package link and restart in normal mode |
| Icon opens but remains blank or loading | Couatl is outdated, blocked, crashed or running at a different privilege level | Close stale processes, update GSX and inspect security quarantine history |
| Services are unavailable or greyed out | Invalid parking position or aircraft state | Test at a proper gate with the aircraft stopped and follow the condition displayed by GSX |
| Vehicles stop incorrectly or doors do not match | Wrong or conflicting aircraft profile | Remove the custom profile and test GSX's default aircraft detection |
| Only one airport fails | Duplicate scenery, mismatched airport profile or unsuitable parking data | Disable duplicate airport packages and test without the custom airport profile |
| Only pushback fails | Brake, chock, stand, tug or control-binding conflict | Use our stand, brake, chock and binding checks for failed pushback |
| GSX works but SimBrief does not | Incorrect account identifier, stale configuration or blocked connection | Follow the dedicated GSX and SimBrief connection checks |
Why does GSX work at one airport but not another?
If GSX works at a stock airport, its core installation and Couatl engine are probably healthy. The failing airport usually has duplicate scenery packages, a profile made for another version of the scenery, changed stand identifiers or parking data GSX cannot use correctly.
Disable every duplicate version of that airport and remove its custom GSX profile temporarily. If the default behaviour returns, install only a profile made for the exact scenery edition in use; our explanation of profile locations, matching and priority helps identify which file is overriding GSX. Doubled or misplaced jetways also point to overlapping airport or jetway packages rather than a broken Couatl installation.
Should I clear the rolling cache or reinstall MSFS?
No—neither is a sensible first fix for GSX. The rolling cache stores streamed scenery data; it does not repair Couatl, toolbar registration or Community-folder links. Reinstalling the whole simulator is excessive unless MSFS itself cannot load any third-party package.
A GSX reinstall is justified only when its updater cannot verify the installation, the installer cannot recreate the package links or Couatl still fails during a clean default-airport test. If GSX starts working with other packages removed, restore them individually instead: the package that makes the fault return is the conflict.
How can I tell when GSX is fixed?
GSX itself is working when its toolbar panel opens without a Couatl error, recognises a stock aircraft at a default gate and lists the services available for that stand. If the fault returns only after restoring a particular aircraft, airport or profile, the core installation is fixed and the remaining problem is isolated to that add-on.