Fix GSX slow loading in Microsoft Flight Simulator by checking Couatl, airport-cache rebuilds, Community links, antivirus and scenery conflicts.
GSX usually loads slowly because its Couatl engine is rebuilding the airport cache, scanning a large scenery library, or being delayed by antivirus, broken package links or an outdated installation. Let one cache rebuild finish, then update GSX, verify its Community links and permissions, and isolate conflicting scenery if the delay returns every launch.
What is GSX doing while it loads?
GSX Pro relies on Couatl, a separate Windows process that reads airport data and connects it to the in-simulator toolbar menu. When installed scenery changes, Couatl may need to scan the package library and regenerate its airport cache before services become available.
A one-off rebuild after installing GSX, updating it, or adding and removing airports is normal. If the status continues changing, allow it to finish; repeatedly closing Microsoft Flight Simulator can prevent the cache from being completed and saved.
| Where the delay occurs | Likely cause | First action |
|---|---|---|
| Before the MSFS main menu | Simulator add-on scanning, storage or online services | Use our diagnosis for slow Microsoft Flight Simulator start-up |
| During an airport-cache rebuild | New, removed or updated scenery | Let the changing progress complete once |
The toolbar remains on Loading GSX... | Couatl has not started, has crashed or is being blocked | Restart Couatl, then update or repair GSX |
| Only one airport causes the delay | Conflicting airport scenery or a custom GSX profile | Test that airport with its add-ons disabled |
How do I fix GSX slow loading?
- Identify which component is slow. If MSFS itself has not reached the main menu or loaded the flight, GSX may not be responsible. If the delay starts only after selecting the GSX toolbar icon, concentrate on Couatl, the airport cache and GSX package links.
- Allow one cache rebuild to finish. Leave the simulator alone while the status or progress is changing. A rebuild that completes once is not a fault; rebuilding from the beginning on every launch is.
- Update and repair GSX. Close MSFS and use the GSX installer to update all installed GSX and Couatl components. Confirm that it is targeting the simulator you actually launch, especially when MSFS 2020 and MSFS 2024 are both installed. Our GSX installation and update checks cover failed updates, simulator selection and package-link problems.
- Perform a clean Couatl restart. Exit MSFS, close any remaining Couatl process from the Windows notification area or Task Manager, and restart Windows if its state is uncertain. Launch MSFS again and wait until the flight has settled at the gate before testing the GSX menu.
- Check the Community-folder links. GSX packages are normally linked into the simulator's
Communityfolder by its installer. A link whose target was moved or deleted can leave GSX incomplete. Do not copy a second set of GSX folders beside the links; use the installer to repair or recreate them. - Check security and write permissions. Antivirus scanning every scenery file can slow a cache rebuild, while quarantine or Windows Controlled Folder Access can stop Couatl saving the result. Confirm that the Couatl executable belongs to your GSX installation, restore it if it was quarantined, and create only a targeted exception. Do not disable security software globally. MSFS, Couatl and the installer should normally run under the same Windows account and privilege level.
- Rebuild the airport cache once. After correcting updates, links and permissions, use GSX's own cache-rebuild function if it is available in the installed version. Avoid deleting unfamiliar files manually. If rebuilding always stops while processing the same package, that package becomes the main suspect.
- Isolate scenery in batches. Temporarily disable third-party airport packages and scenery libraries while leaving the required GSX package links active. Test half the collection at a time, then narrow the failing half until the delay returns. For an airport-specific problem, also test without its custom GSX profile.
A large scenery collection naturally makes a genuine rebuild take longer, particularly when packages are stored on a slow external drive or inspected heavily by antivirus. It should not force a complete rebuild indefinitely after every normal launch.
Why does GSX rebuild its airport cache every time?
Repeated rebuilding means GSX cannot preserve the cache or believes the scenery library changed between sessions. The usual causes are blocked write access, an interrupted Couatl shutdown, broken add-on links, automated cleanup software removing cached data, or an add-on manager remounting packages differently at each launch.
- Keep the GSX installation and linked package targets in stable locations.
- Make sure the Windows account running Couatl can write to GSX's data folders.
- Exclude GSX cache data from aggressive cleanup tools.
- Close MSFS normally after the first successful rebuild so Couatl can finish saving its state.
- Place large scenery libraries on a healthy local SSD when practical, rather than a disconnected, cloud-synchronised or sleeping external location.
What if the GSX menu stays on Loading GSX?
An unchanged Loading GSX... message is usually a Couatl start-up failure rather than an unusually long airport scan. Check whether Couatl is running, repair GSX through its installer, and inspect its status or log for a scenery path or package name repeated immediately before the failure.
If Couatl will not remain running or the toolbar never connects after an update and clean restart, use our Couatl and toolbar recovery steps for GSX start-up failures. Reinstalling the whole simulator is rarely justified; repair GSX and test the scenery library first.