How do I fix AutoFPS not connecting or starting in MSFS?
Fix AutoFPS not connecting or starting in MSFS 2020 and 2024, including no file found errors, SimConnect, security, reset and uninstall steps.
AutoFPS usually fails in Microsoft Flight Simulator because the build or simulator selection is wrong, files were not fully extracted or Windows blocked them. Extract a trusted current build, load the correct MSFS version into an active flight, launch AutoFPS at matching permissions, then check that its status changes to connected.
Quick fix for AutoFPS not connecting or starting
Use this four-step sequence before changing AutoFPS or Microsoft Flight Simulator settings.
- Extract a clean current build. Exit the existing copy, obtain the release from the project’s trusted source and extract the entire archive into a new local folder. Do not run it inside the archive or copy only the executable.
- Load the correct simulator into a flight. Start MSFS 2020 or MSFS 2024, enter the cockpit and wait until the aircraft is fully active.
- Launch with matching permissions. Run MSFS and AutoFPS normally. If either has been forced to run as administrator, remove that setting or use the same permission level for both during testing.
- Check the AutoFPS status. Confirm that it selected or detected the simulator you actually launched. If no AutoFPS window appears, troubleshoot the application launch; if it opens but remains red, waiting or disconnected, troubleshoot simulator detection and SimConnect.
What does the AutoFPS symptom mean?
The point at which MSFS AutoFPS fails separates an application launch problem from a simulator connection problem.
| Symptom | What it means | Start with |
|---|---|---|
| No window appears, the console closes or nothing happens | AutoFPS itself failed to launch | Fresh extraction, Windows Security, required runtime and configuration reset |
| The window opens but the status stays red, waiting or disconnected | AutoFPS launched successfully but cannot connect to MSFS | Simulator compatibility, selected version, launch timing, permissions and SimConnect |
| It connects and then disconnects | The simulator session ended, compatibility changed or another utility interfered | Restart both programs and remove competing tuners |
| It reports connected but FPS does not improve | The connection works; configuration or the underlying performance limit is the problem | Target FPS, adjustment limits, CPU, GPU, VRAM, traffic and add-ons |
Does AutoFPS work with MSFS 2020 and MSFS 2024?
AutoFPS compatibility is release-specific, so a build should be used only when its release notes explicitly support your installed Microsoft Flight Simulator generation and update.
- Obtain the current release from the project’s trusted source. Avoid old copies retained in download folders or repackaged archives whose contents and supported simulator versions cannot be verified.
- Read the release notes before replacing your working copy. Support for MSFS 2020 does not automatically mean support for MSFS 2024. A simulator update can also require an updated AutoFPS build even when the correct generation is selected.
- Verify the simulator after loading a flight. Select MSFS 2020 or MSFS 2024 where the utility provides a selector. If detection is automatic, check the detected version in its status or log after the cockpit becomes active.
An incompatible build may still open normally, which is why a visible AutoFPS window does not prove that it supports the running simulator. Once the correct build connects, use our settings guidance for matching AutoFPS to MSFS 2020 or 2024 rather than importing an unexplained configuration from another version.
How do I fix AutoFPS not connecting to MSFS?
If the AutoFPS window opens, focus on simulator matching and SimConnect; missing-file and runtime repairs belong to the failed-launch branch below.
- Close stale processes. Exit MSFS, AutoFPS and any automatic graphics or dynamic-LOD utility. Check Task Manager for an AutoFPS process left in the background, then restart Windows if it will not close cleanly.
- Use an active flight for the test. Load a default aircraft at a simple location and wait for the cockpit to respond. The main menu and loading screens are not reliable connection tests.
- Check the simulator target again. A saved MSFS 2020 selection can prevent connection to MSFS 2024 and vice versa. Confirm the selection or detected simulator in the AutoFPS status or log.
- Match permission levels. Run both applications without administrator privileges first. If one is forced to run elevated, change it so both use the same level; AutoFPS should not normally require permanent administrator access.
- Stop competing tuners. Do not run another utility that changes terrain LOD, object LOD, clouds or the same simulator values. Two tuners can overwrite one another, cause oscillation or make a valid connection appear ineffective.
- Restart after an MSFS update or crash. A previous SimConnect session may not have closed cleanly. Start a fresh simulator session, load the flight and then open AutoFPS.
Why won’t MSFS AutoFPS start or show up?
If AutoFPS produces no window or closes immediately, the application itself has failed to launch; MSFS and SimConnect are not yet the problem.
AutoFPS says “no file found”, won’t start, or just does nothing
A complete fresh extraction fixes the most common missing-file failure, but preserve your configuration before resetting anything.
- Keep the old folder as a backup. Rename it rather than extracting a new release over it. Copy any configuration you want to retain, but do not import that configuration into the clean copy until the program has launched successfully.
- Extract every supplied file again. Use a new, simple local folder that is writable and not a protected system or synchronised directory. A mistake we see repeatedly is copying only the executable and leaving its supporting files inside the archive.
- Check whether Windows blocked the download. Open the downloaded archive’s Properties and select
Unblockif that option appears, then extract it again. Review Windows Security protection history for quarantined AutoFPS components. Restore or allow a file only when the complete archive came from the project’s trusted source; do not disable protection globally. - Install the exact required runtime. If the error names a Windows desktop framework or runtime, install or repair the version specified in that AutoFPS release’s documentation. Do not download individual DLL files from unrelated sources or guess at runtime versions.
- Test with clean user settings. Depending on the build, configuration may be stored beside the executable or in the Windows user profile. Back up and rename the clearly identified AutoFPS settings folder or configuration file, then let the application create defaults. Restore the old settings only after the clean launch works.
- Find the exact missing-file name. Check the AutoFPS log in its application folder or documented per-user settings location. If no log is created, open Windows Event Viewer, examine
Windows Logs > Applicationat the failed launch time and record the missing assembly, faulting module or runtime named in the event details.
If AutoFPS opens and the message instead refers to finding or detecting the simulator, the executable has launched successfully. Return to the simulator-version and SimConnect checks rather than repeatedly reinstalling runtimes.
How do I tell whether SimConnect is the problem?
SimConnect is the likely fault only when AutoFPS opens normally but remains disconnected after an active flight has loaded.
MSFS supplies the SimConnect interface, so installing random legacy DLL files is not the first fix. Restart MSFS and Windows, test a default aircraft with competing utilities closed, and check another known SimConnect-based companion application if one is already installed.
If every SimConnect tool fails, use the supported verify or repair function for your MSFS installation and retest after restarting Windows. If other tools connect but AutoFPS stays red or disconnected, SimConnect is probably healthy; concentrate on the AutoFPS build, simulator selection, blocked files and configuration.
A local AutoFPS connection does not require router port forwarding. Investigate firewall or security rules only when their logs specifically show that the AutoFPS executable was blocked.
Why does AutoFPS connect but not improve frame rate?
A connected AutoFPS cannot create performance that the PC, simulator workload or chosen target cannot supply.
- Choose a target frame rate the system can approach without AutoFPS instead of setting one far above its normal performance.
- Confirm that automatic adjustment is enabled and that minimum and maximum values are not pinning terrain LOD, object LOD or clouds to one value.
- Judge the result inside an active flight, using the same aircraft, airport, weather and camera view for each comparison.
- Use the simulator’s FPS display to distinguish a main-thread limit from a GPU limit; our guide explains how to show the MSFS FPS counter and interpret the limiting component.
- Reduce AI traffic, airport detail or other CPU-heavy settings when main-thread limited. For the 2024 simulator, follow our checks for diagnosing an MSFS 2024 main-thread limit.
- Lower resolution or GPU-heavy settings when GPU utilisation or VRAM is the constraint. AutoFPS cannot compensate for every graphics bottleneck.
- Test without complex aircraft, scenery and traffic packages if the slowdown occurs only in particular flights; we explain how add-ons can reduce simulator FPS.
If performance worsens only after a long session, investigate the long-flight workload or simulator stability rather than treating it as an AutoFPS startup failure.
How do I uninstall MSFS AutoFPS?
For an extracted AutoFPS installation, uninstall it by closing the program and deleting its application folder; remove user-profile settings only when you also want a complete configuration reset.
- Exit AutoFPS and MSFS. Check Task Manager and end any remaining AutoFPS process so that its files are no longer in use.
- Preserve settings if wanted. Back up any AutoFPS configuration stored beside the executable or in its per-user settings location before deleting anything.
- Delete the extracted application folder. Remove only the folder created for AutoFPS. Portable builds may not appear in Windows Installed apps because no conventional installer was used.
- Remove profile settings only for a full reset. Delete the clearly identified AutoFPS configuration or settings folder in the Windows user profile if you want no preferences retained for a later reinstall. Leave it in place if you want to preserve those settings.
- Remove any shortcut or automatic-start entry you created. This prevents Windows from trying to launch an executable that no longer exists.
Uninstalling AutoFPS does not uninstall Microsoft Flight Simulator and does not remove the simulator’s Community folder, aircraft, scenery, liveries or other add-on content. Do not delete the MSFS Community or Official folders while removing AutoFPS.
Can AutoFPS run on Xbox or PlayStation?
AutoFPS is an external Windows companion application and cannot run alongside Microsoft Flight Simulator on a console.
This applies to MSFS 2020 on Xbox Series X|S and MSFS 2024 on Xbox Series X|S, PlayStation 5 and PS5 Pro. MSFS 2020 was not released on PlayStation. Console users must rely on the simulator’s available graphics, traffic and performance options because they cannot install or execute the Windows AutoFPS application.