How do I install FSUIPC7 for Microsoft Flight Simulator?

To install FSUIPC7 for Microsoft Flight Simulator 2020 or 2024 on PC, download and fully extract the FSUIPC7 archive, run Install_FSUIPC7.exe, choose a permanent writable folder, and let the installer detect MSFS. Start a flight, run FSUIPC7, and leave it open while any dependent add-on is in use.

How do I download and install FSUIPC7?

FSUIPC7 is a separate Windows application rather than a conventional MSFS Community-folder mod. Close Microsoft Flight Simulator before installing it, then follow these steps:

1. Download FSUIPC7: obtain a compatible release using our FSUIPC7 archive and extraction notes. The release must support the Microsoft Flight Simulator edition you intend to use.
2. Extract the complete archive: copy every file from the downloaded ZIP into a temporary folder. Do not launch the installer from inside the compressed archive; that can prevent supporting files from being found.
3. Run the installer: open the extracted FSUIPC7 folder and run Install_FSUIPC7.exe. Accept the proposed installation folder or choose a permanent writable location such as C:\FSUIPC7.
4. Check the simulator paths: confirm that the installer has detected MSFS 2020 or MSFS 2024 correctly. Microsoft Store and Steam installations can use different package locations, while MSFS 2020 and 2024 do not necessarily share a Community folder.
5. Select the optional components: enable automatic start-up if you want FSUIPC7 to open with MSFS. Select the FSUIPC WASM component when an aircraft, preset or hardware configuration requires local variables or advanced events.
6. Handle registration: enter a valid FSUIPC7 key if you own one, or continue unregistered. Registration is not required merely for most companion applications to communicate through FSUIPC7.
7. Test the installation: start MSFS and load a flight, then open FSUIPC7.exe manually if automatic start-up was not selected. Its window or log should report a simulator connection, and FSUIPC7 must remain running while it is being used.

Where should FSUIPC7 be installed?

Install the main FSUIPC7 application in its own permanent Windows folder, not in the MSFS Community folder. Keeping it in a dedicated writable folder also makes FSUIPC7.ini, logs, profiles and registration data easier to find and back up.

The optional WASM package is the exception: the installer places that component in the appropriate Community folder. A mistake we see often is moving the entire FSUIPC7 application there, which does not turn it into an MSFS package and can break updates or configuration paths.

Does FSUIPC7 work with MSFS 2024 and MSFS 2020?

FSUIPC7 supports the Windows PC editions of both Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024 when you use a compatible FSUIPC7 build.

Steam and Microsoft Store PC installations are both suitable; their folder locations are simply different. FSUIPC7 is the MSFS generation of FSUIPC, so do not substitute an older release intended for FSX or Prepar3D just because an add-on uses the general name “FSUIPC”.

Do I need an FSUIPC7 key?

You do not need an FSUIPC7 key for installation or for most third-party applications that use FSUIPC as a communications interface. A registered licence unlocks FSUIPC7’s own facilities, including controller assignments, aircraft profiles and calibration.

If you have a valid key, enter the registered details exactly as issued when the installer requests them. The resulting registration information is stored in FSUIPC7.key; back up that file but do not publish or share it.

A rejected key is usually for a different FSUIPC generation, has mismatched registration details, or cannot be written because the installation folder is protected. There is no legitimate universal FSUIPC7 key, and downloading a shared key risks both an invalid registration and altered files.

Do I need the FSUIPC WASM module?

The FSUIPC WASM module is needed only when a client or aircraft configuration requires local variables, calculator-code events, presets or similar advanced functions. Basic SimConnect communication and many companion applications work without it.

The installer places WASM in the selected simulator’s Community folder while leaving FSUIPC7.exe in its normal Windows folder. If FSUIPC7 connects but aircraft-specific variables are missing, verify that WASM was installed into the Community folder for the edition you launched, then restart MSFS.

How do I confirm or fix the FSUIPC7 connection?

FSUIPC7 is connected when its window or FSUIPC7.log reports an active simulator connection after a flight has loaded. A waiting-for-simulator state is normal if FSUIPC7 starts before MSFS.

FSUIPC7 does not appear as an aircraft, toolbar panel or installed controller. If it remains disconnected, check these common causes:

• Unsupported or outdated build: install a FSUIPC7 release compatible with your MSFS edition, especially after moving from MSFS 2020 to MSFS 2024.
• SimConnect problem: FSUIPC7 communicates with MSFS through SimConnect, which is supplied with the simulator. Use our SimConnect checking and repair procedure rather than adding unrelated legacy components.
• MSFS is not ready: wait until a flight has loaded into the cockpit. Starting FSUIPC7 before the simulator is harmless, but it cannot connect before the SimConnect session becomes available.
• Mixed permissions: run MSFS, FSUIPC7 and the dependent application at the same Windows privilege level. Normal user mode is preferable unless a specific error requires administrator access.
• Broken automatic start-up: launch FSUIPC7.exe manually. If that works, rerun the installer and reselect its start-up option instead of editing MSFS start-up files by hand.
• Security software interference: check whether the executable was blocked or quarantined. Verify the archive and permit only the trusted FSUIPC7 files rather than disabling protection globally.
• Duplicate installations: keep one active installation and run only one instance. Multiple copies often result in the wrong configuration or log file being inspected.

The log in the FSUIPC7 installation folder records connection attempts and often identifies the failed stage. If the cause remains unclear, work through our full FSUIPC connection diagnosis, which covers versions, start-up order, permissions and log evidence.

Why doesn’t MSFS recognise FSUIPC7 control inputs?

MSFS does not list FSUIPC7 as a controller because it is an external application, not a virtual joystick. You configure physical controls either in MSFS or through the registered assignment facilities in FSUIPC7.

The most common input fault is the same axis or button being assigned in both places. Duplicate bindings cause twitching controls, repeated button presses, reversed movement and throttles that will not remain in their detents.

If FSUIPC7 detects the device but the aircraft does not respond, remove conflicting MSFS bindings and check that the chosen event is suitable for that aircraft. Our FSUIPC input troubleshooting steps explain the distinction between the external program and MSFS Controls Options.

How do I update FSUIPC7 without losing my settings?

Update FSUIPC7 by closing MSFS and FSUIPC7, backing up the installation folder, and running the newer installer into the same location. Do not delete the existing folder first unless you are deliberately performing a clean installation.

At minimum, retain FSUIPC7.ini, FSUIPC7.key if registered, and any separate profile, macro or script files you created. The installer should preserve existing settings, but the backup protects customised assignments and calibration.

After updating, recheck automatic start-up, the selected simulator and the WASM Community-folder path. Moving from MSFS 2020 to MSFS 2024 is more than a routine update: aircraft events, package locations and control profiles may differ, so test them before removing the older configuration.