Fix AIG Traffic Controller not opening in MSFS by checking blocked files, antivirus quarantine, extraction, permissions, runtimes and corrupt settings.
AIG Traffic Controller usually fails to open because Windows has blocked or quarantined a file, the program is being run from a ZIP or protected folder, its configuration is corrupt, or a required runtime is missing. Extract a fresh copy to a writable local folder, unblock it, check security history, then reset its settings.
For Microsoft Flight Simulator 2020 and 2024, this is normally a Windows application problem rather than an in-simulator traffic setting. AIG Traffic Controller is a Windows desktop program and cannot run on Xbox or PlayStation versions of MSFS.
What does AIG Traffic Controller not opening mean?
The exact symptom indicates where to start troubleshooting.
| Symptom | Likely cause | First check |
|---|---|---|
| No window or process appears | Blocked executable, quarantine, incomplete extraction or missing runtime | Windows Security and a fresh extracted copy |
| The process appears, then disappears | Corrupt settings, missing component or startup crash | AIG logs and Windows Reliability Monitor |
| The process remains but no window is visible | Off-screen window, hidden prompt or damaged window-position setting | Taskbar, monitor shortcuts and settings reset |
| The window opens but says it is waiting or disconnected | Simulator detection, compatibility or SimConnect issue | MSFS-specific setup rather than launch troubleshooting |
How do I fix AIG Traffic Controller not opening?
Work through these checks in order, testing the controller after each one.
- End any hidden AIG process. Open Task Manager and close AIG Traffic Controller if it is still running in the background. Repeatedly launching it can leave several stalled processes without producing a visible window.
- Extract a complete fresh copy. Do not run the controller inside a ZIP archive, copy only its executable, or merge files from different releases. Before extracting, open the downloaded archive's Properties and select Unblock if Windows shows that option. Put the program in a user-writable local folder such as
%USERPROFILE%\FlightSimTools\AIG, not insideProgram Filesor the MSFSCommunityfolder. Our complete AIG installation and folder checklist covers the associated aircraft libraries and package paths. - Check Windows Security. Open
Windows Security > Virus & threat protection > Protection historyand look for an AIG component removed at the time of launch. Restore or allow it only when it came from your trusted AIG package. Add a narrow exception for the AIG program folder if necessary; do not disable antivirus protection system-wide. - Repair the required Microsoft runtimes. Install or repair the Microsoft .NET or Visual C++ runtime requested by the AIG package, then restart Windows. Do not download individual DLL files from unofficial DLL collections, as that can create a different version mismatch or introduce unsafe files.
- Reset the controller configuration. Close every AIG process, back up the controller's settings, and rename only its configuration folder by adding
.old. Depending on the package, settings may be beside the program or in an AIG-named folder under%LOCALAPPDATA%or%APPDATA%. Do not delete the aircraft models, OCI packages, flight-plan libraries or the entire AppData directory. A clean launch should recreate default settings. - Recover an off-screen window. Select AIG Traffic Controller with Alt+Tab, then use Win+Shift+Left Arrow or Win+Shift+Right Arrow to move it between displays. This commonly follows a monitor change. Resetting the controller settings also clears a saved window position in many builds.
- Test permissions once. Use Run as administrator as a diagnostic test. If that makes the program open, its normal folder is not writable or security software is blocking it. Move it to a user-owned folder or correct the permissions rather than relying permanently on administrator mode.
Does Microsoft Flight Simulator need to be running first?
A missing simulator connection should not prevent the AIG Traffic Controller window from appearing; it should open and then wait for or report the simulator connection.
If the application opens but cannot detect the simulator, follow the appropriate MSFS 2020 connection and setup checks or the separate MSFS 2024 compatibility and package-path checks. Do not mix controller files intended for different releases, and replace the whole application folder when updating rather than overwriting selected files.
What should I check if it still closes immediately?
The AIG log and Windows crash record should identify whether the remaining fault is a runtime, permissions or compatibility problem.
Look for a recent log in the controller's folder or its AIG settings directory. Windows Reliability Monitor and the Application section of Event Viewer can also show the faulting module. An access-denied entry points back to folder permissions or security software; a missing runtime component calls for repairing that runtime; repeated failure after a clean configuration suggests an incompatible or incomplete controller package.
Reinstalling Microsoft Flight Simulator is rarely justified here because AIG Traffic Controller is failing before it connects to the simulator.
What if AIG Traffic Controller opens but no traffic appears?
Once the controller window opens normally, missing aircraft are an injection or model-library problem rather than a launch problem.
Check the simulator path, SimConnect connection, installed AIG models, active traffic source and conflicts with other injectors. Avoid running MSFS live traffic, offline AI and another external injector together unless the chosen setup explicitly requires it. Our external AI traffic diagnostic checklist covers that next stage without repeating the Windows launch fixes.