Set up FSUIPC7 in MSFS 2020 correctly: install it, enable auto-start and WASM, verify SimConnect, bind controls and fix connection faults.
To set up FSUIPC7 with Microsoft Flight Simulator 2020, download the FSUIPC7 package, run its installer outside the simulator’s Community folder, enable its MSFS auto-start option, then launch the sim and confirm FSUIPC7 reports a SimConnect connection. Assign controls in either FSUIPC7 or MSFS—not both—to prevent duplicate inputs.
Install FSUIPC7 correctly
Install the FSUIPC7 application outside MSFS, while allowing only its optional WASM module to be placed in the Community folder. FSUIPC7 is a separate Windows program, not an old-style simulator DLL.
- Download the correct edition. Use FSUIPC7 for Microsoft Flight Simulator 2020; FSUIPC versions intended for FSX or Prepar3D are not interchangeable. Our FSUIPC download archive identifies the MSFS-compatible package.
- Extract the downloaded archive. Do not run the installer from inside the compressed ZIP file. Close Microsoft Flight Simulator before continuing.
- Run the installer. Accept its suggested standalone installation folder unless you have a specific reason to change it. Do not choose the Community folder or an MSFS package directory for the main FSUIPC7 program.
- Enable automatic startup. Select the option that starts FSUIPC7 with MSFS 2020. This normally creates or updates the simulator’s
EXE.xmlstartup entry. - Install the WASM component if needed. The optional module supports local variables, presets and deeper integration with complex aircraft. Basic SimConnect applications may work without it, but installing it avoids a common limitation later.
- Register only if required. Third-party applications can generally connect through unregistered FSUIPC7, but controller assignment, calibration and other user facilities require the appropriate FSUIPC7 licence. Keys from another FSUIPC generation do not unlock FSUIPC7.
- Launch MSFS and load a flight. FSUIPC7 should open as a separate Windows application and report that it is connected through SimConnect. It does not appear as the traditional in-simulator Add-ons menu used by older Flight Simulator versions.
The process is the same for Microsoft Store and Steam installations. The installer may need to locate the active MSFS packages path when adding the WASM module, particularly if the packages have been moved to another drive.
Should I assign controls in FSUIPC7 or MSFS?
Use one assignment system for each flight control axis or button; sending the same command from both systems causes double inputs, flickering switches and throttles that refuse to stay in position.
| Requirement | Better starting point | Reason |
|---|---|---|
| Basic yoke, pedals or HOTAS | MSFS controls | Quicker setup and direct access to the simulator’s sensitivity settings. |
| Aircraft-specific profiles | FSUIPC7 | Profiles can separate assignments for different aircraft and hardware combinations. |
| Advanced axis calibration | FSUIPC7 | Useful for centre zones, reversers and independent axis ranges. |
| Airliner throttle detents | Aircraft’s supported method first | Some add-on aircraft expect native bindings or their own calibration and can conflict with generic FSUIPC calibration. |
| External application connection only | No remapping required | An application can use the FSUIPC interface without moving controller assignments out of MSFS. |
If you choose FSUIPC7, remove only the corresponding MSFS flight-control bindings; there is no need to erase camera, menu or keyboard commands. Check every connected device because MSFS may automatically assign an axis on more than one controller.
- Open the FSUIPC7 window and select its axis or button-assignment section.
- Move one control at a time so you can identify the correct device and axis.
- Create an aircraft profile before assigning controls if the bindings should apply only to that aircraft or aircraft family.
- Choose the command method carefully. Standard aircraft usually accept normal simulator controls; complex add-ons may require a specific preset, local variable or custom event.
- Calibrate only where appropriate. Set minimum, centre and maximum values after assignment, then test the full range in the cockpit. Our FSUIPC joystick and throttle calibration procedure covers this separately.
Why is FSUIPC7 not connecting to MSFS 2020?
A disconnected FSUIPC7 session usually comes from a failed auto-start entry, mismatched Windows permissions, security software or an outdated build after a simulator update.
- FSUIPC7 never opens: run its executable manually. If that works, reinstall with auto-start enabled or repair the
EXE.xmlentry rather than reinstalling the whole simulator. - FSUIPC7 opens but waits for MSFS: load an aircraft into a flight, confirm both programs run at the same Windows privilege level and inspect
FSUIPC7.logfor the connection state. - The WASM module is missing: confirm it was installed in the Community folder belonging to the active MSFS packages location. Moving the packages later can leave it in an obsolete folder.
- Controls move twice or oscillate: search MSFS assignments by input and remove the duplicate axis or button from every device profile.
- FSUIPC sees the button but the aircraft ignores it: the add-on may not use the generic simulator event. Select its supported preset or custom event and make sure the WASM component is installed where required.
- Security software blocks the program: check its quarantine history and allow the trusted FSUIPC7 installation folder. Avoid running only one of MSFS and FSUIPC7 as administrator.
For cases where the connection works but aircraft controls do not, follow our FSUIPC input troubleshooting checklist to isolate profiles, duplicate bindings and unsupported aircraft events.
How do I update FSUIPC7 without losing my settings?
Close MSFS and FSUIPC7, back up FSUIPC7.ini plus any profile, macro or Lua files, then install the newer FSUIPC7 release into the same application folder. Do not restore an older executable over the update.
After updating, verify that automatic startup still works and that the WASM module remains in the active Community folder. Keeping a backup of the configuration files is especially useful before changing controller profiles or moving the MSFS packages directory.