Install and set up FSUIPC7 for Microsoft Flight Simulator, connect through SimConnect, configure controls safely and fix detection errors.
To install FSUIPC7 for Microsoft Flight Simulator on PC, download the FSUIPC7 archive, extract every file, run Install_FSUIPC7.exe, and accept or choose a permanent writable folder. Let the installer detect MSFS and add the optional components you need, then run MSFS and keep FSUIPC7 open while flying.
How do I install FSUIPC7?
FSUIPC7 is a separate Windows application for the PC editions of Microsoft Flight Simulator 2020 and 2024, not a conventional Community-folder mod. It cannot be installed on the Xbox or PlayStation editions, and it is unnecessary unless an application, aircraft or controller configuration specifically uses it.
- Download the archive: obtain a compatible release using our FSUIPC7 download and extraction instructions. Use a build that supports your edition of MSFS.
- Extract the whole archive: open the downloaded ZIP and extract all its contents into a temporary folder. Do not run the installer from inside the compressed archive.
- Run the installer: open the extracted FSUIPC7 folder and run
Install_FSUIPC7.exe. Accept the suggested location or choose a dedicated writable folder such asC:\FSUIPC7. Do not install the main application in the MSFS Community folder. - Check the detected paths: confirm that the installer has found the intended MSFS 2020 or MSFS 2024 installation. If you have both editions, Microsoft Store and Steam installations, or custom package locations, check the Community-folder selection carefully. Our explanation of MSFS package and Community-folder locations will help if detection fails.
- Select the useful options: enable automatic start-up with MSFS if the installer offers it. Install the supplied WASM component if you need aircraft variables, presets or other advanced functions described below.
- Start and test it: launch MSFS and load a flight, then start
FSUIPC7.exemanually if it did not start automatically. FSUIPC7 must remain running while another program or control profile is using it.
If the installer asks for registration, enter a valid key or continue unregistered. Registration unlocks FSUIPC's own user facilities, including assignments and calibration, but it is not generally required merely for a local companion application to communicate through the FSUIPC interface.
How do I confirm or fix the FSUIPC7 connection?
FSUIPC7 is connected when its window or log reports an active simulator connection rather than continuing to wait for MSFS. You should not expect it to appear as an aircraft, scenery package or MSFS toolbar panel.
Waiting for the simulator is normal when FSUIPC7 starts first. If it still does not connect after a flight has loaded, close both programs and check these common causes:
- Outdated FSUIPC7 build: an older installer may not recognise MSFS 2024 or a changed simulator installation. Update FSUIPC7 before editing configuration files.
- SimConnect failure: FSUIPC7 communicates with MSFS through SimConnect, which is included with the simulator. Follow our steps for checking and repairing the MSFS SimConnect connection rather than installing random legacy components.
- Mixed permissions: run MSFS, FSUIPC7 and the client application at the same Windows privilege level. Normal user mode is preferable unless a specific permission error requires administrator access.
- Broken automatic start-up: launch FSUIPC7 manually to prove that it works, then rerun the installer and reselect the auto-start option. This is safer than manually altering MSFS XML files.
- Security software interference: check whether the executable was quarantined or blocked. Do not disable protection globally; verify the archive and permit only the trusted FSUIPC7 files.
- Multiple copies: keep one installation and run only one instance. Duplicate copies make it easy to edit one configuration while MSFS is using another.
The file FSUIPC7.log in the installation folder records connection attempts and usually identifies whether the problem is simulator detection, SimConnect or an optional module.
Do I need to configure controls in FSUIPC7?
No control configuration is needed when another application only requires FSUIPC7 as a communications interface. Assign controls in FSUIPC7 only when you want its profiles, calibration or specialised event handling.
| Use case | Recommended set-up |
|---|---|
| Companion application requires FSUIPC7 | Leave axes and buttons unchanged; run MSFS, FSUIPC7 and the application. |
| Standard joystick, yoke or pedals | Assign each function in either MSFS or FSUIPC7, not both. |
| Aircraft with its own throttle calibration | Use the aircraft's expected MSFS events or presets; do not add FSUIPC calibration unless its instructions require it. |
| Different controls for each aircraft | Create an FSUIPC aircraft profile and test it before copying assignments to another type. |
A mistake we see constantly is the same axis bound in MSFS and FSUIPC7. This causes duplicated button presses, oscillating controls and throttles that will not hold their detents. Remove the conflicting MSFS binding before assigning that function in FSUIPC7.
For an axis, move only the intended lever during detection, assign the simulator control, and calibrate its minimum, centre and maximum only when FSUIPC calibration suits that aircraft. Keep view controls and other straightforward commands in MSFS unless there is a reason to move them. Our PC control set-up and conflict-checking guide covers the simulator-side profiles.
Do I need the FSUIPC WASM module?
The FSUIPC WASM module is needed for access to many local variables, calculator-code events and presets used by complex aircraft, but not for every basic SimConnect or FSUIPC client.
When selected, the installer places the module in the appropriate MSFS Community folder while the main FSUIPC7 application remains outside it. If basic connection works but aircraft-specific variables do not, the usual cause is a missing module, the wrong Community folder, or MSFS not having been restarted after installation.
How do I update FSUIPC7 without losing settings?
You can normally update FSUIPC7 by closing MSFS and FSUIPC7, backing up the installation folder, and running the newer installer into the same location. The installer should preserve existing configuration, but a backup protects customised assignments and scripts.
At minimum, retain FSUIPC7.ini, your profile files, scripts and FSUIPC7.key if registered. After updating, recheck the simulator path, WASM-module option and automatic start-up setting—especially when moving from MSFS 2020 to MSFS 2024 rather than updating the same installation.