How do I install FSUIPC for FSX?

To install FSUIPC for FSX or FSX: Steam Edition, download FSUIPC4, extract the archive, close the simulator, and run its installer. Point it to the folder containing fsx.exe if asked, skip registration unless you own a licence, then start a flight and confirm FSUIPC appears under Add-ons.

What is FSUIPC, and which version does FSX need?

FSUIPC is an interface that lets aircraft, utilities and hardware software exchange data and commands with Microsoft Flight Simulator.

FSX and FSX: Steam Edition use FSUIPC4. Steam Edition is also commonly abbreviated to FSX-SE or FSX SE. The other FSUIPC generations are not interchangeable:

• FSX and FSX: Steam Edition: install FSUIPC4 as an in-simulator module.
• FS2004: uses FSUIPC3, which should not be installed in FSX.
• Microsoft Flight Simulator 2020 and 2024: use FSUIPC7, an external application that is not an FSX replacement.

FSUIPC does not improve FSX performance, and the simulator does not need it merely to run. Install it when an add-on explicitly requires the FSUIPC interface or when you want its control-assignment and calibration facilities. Our plain-English explanation of FSUIPC's role covers that distinction in more detail.

Is FSUIPC for FSX a free download, and is registration required?

FSUIPC4 can be downloaded and installed free in unregistered mode, which is normally all an add-on requiring FSUIPC needs.

Registration unlocks FSUIPC's user-facing control features; it is not required simply to load the module or expose its interface to compatible software.

No registration key is needed for the FSUIPC entry to appear in FSX's Add-ons menu. If the installer displays registration fields and you do not own a valid licence, continue without registering rather than entering invented or borrowed details.

How to install FSUIPC4 in FSX and FSX: Steam Edition

The supplied installer should copy FSUIPC4 into FSX and add its entry to the simulator's module-loading configuration.

1. Run the intended FSX edition once. Load a flight, close FSX normally and shut down any utilities connected to it. This creates the active per-user configuration files and is particularly useful when boxed FSX and Steam Edition coexist.
2. Download the correct package. Use the compatible FSUIPC4 download for FSX and Steam Edition, not FSUIPC3 or FSUIPC7. Avoid old copies bundled with aircraft and utilities.
3. Extract the complete archive. Unzip every file to a temporary folder. Run the supplied FSUIPC4 installer from that extracted folder, not from inside the compressed archive.
4. Back up existing settings. When updating or reinstalling, copy Modules\FSUIPC4.ini and any user-created FSUIPC macro, Lua or profile files to a safe location.
5. Close FSX and run the installer. Let it detect the simulator. If Windows prevents it from writing to an installation under Program Files, rerun the installer as administrator; this does not mean FSX itself must always run as administrator.
6. Select the correct simulator root. If detection fails, choose the folder containing fsx.exe. Do not select the Modules, SimObjects, Documents or saved-flight folder.
7. Continue without registration if necessary. Declining the optional registration stage should not cancel installation of the free module.
8. Read and retain the result. Confirm that the installer reports a successful FSUIPC4 installation. Keep its log if it names an error or an unexpected FSX path.
9. Start FSX and approve the module. Accept the run or trust prompts for FSUIPC4.dll when it came from the trusted package above. Then load a flight.

The installer normally creates or updates the per-user dll.xml entry that tells FSX to load Modules\FSUIPC4.dll. Copying only the DLL is a mistake we see constantly: the file may be present, but FSX has no valid instruction to load it.

Which FSX folder should I choose?

The correct folder is the installation root containing fsx.exe and directories such as Modules and SimObjects.

• Boxed FSX: a common location is C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X, although a custom installation may be elsewhere.
• FSX: Steam Edition: a common location ends in steamapps\common\FSX. A custom Steam library can be on any drive.
• Both editions installed: confirm that the selected fsx.exe belongs to the edition you intend to launch. Do not assume the first FSX path found by an old installer is correct.

The associated user configuration can be under %APPDATA%\Microsoft\FSX or %APPDATA%\Microsoft\FSX-SE, depending on the installation history and whether both editions coexist. Let the FSUIPC installer identify the active configuration rather than copying another user's dll.xml.

How do I check that FSUIPC is working?

FSUIPC4 is working when its options window opens from FSX's Add-ons menu after a flight has loaded.

1. Load an aircraft at an airport and wait for the cockpit to become usable.
2. Press Alt if the FSX menu bar is hidden.
3. Open Add-ons and select the FSUIPC entry.
4. Confirm that the FSUIPC window opens and identifies the version 4 generation.

The Add-ons menu may not be available on the initial Free Flight screen, so its absence there does not indicate a failed installation. A successful first load also normally creates FSUIPC4.log and FSUIPC4.ini beside the DLL in the Modules folder.

If you plan to use FSUIPC for assignments rather than solely as an add-on dependency, follow our guidance on registration, trust prompts and control setup after confirming that the basic module loads.

Why is FSUIPC not showing in the FSX Add-ons menu?

FSUIPC usually fails to appear because FSX targeted the wrong DLL, did not trust it, could not read its dll.xml entry or never reached the point where modules are loaded.

• No flight is loaded: enter a flight before checking the menu, and press Alt to reveal the menu bar.
• Wrong FSUIPC generation: remove the incompatible file and install FSUIPC4. FSUIPC3 and FSUIPC7 cannot substitute for it.
• Wrong FSX copy: check that FSUIPC4.dll is in the Modules folder belonging to the exact boxed or Steam edition you launched.
• Trust was refused: reset only FSUIPC4's saved trust decision in the active FSX configuration after making a backup, then restart FSX and approve the prompt.
• Security software blocked the file: check whether the installer or DLL was quarantined. Restore it only after confirming that it came from the trusted package, then reinstall.
• The installer lacked write access: close FSX and run the installer with administrative permission. Avoid permanently elevating FSX unless another add-on specifically requires it.
• The module configuration is malformed: a broken dll.xml can prevent FSUIPC and every module listed after the damaged entry from loading. Back it up before repairing or replacing it, because it may contain entries for other add-ons.
• FSX components are incomplete: if the log reports SimConnect or side-by-side errors, repair the simulator installation. Boxed FSX should have Service Pack 2 or Acceleration installed.

If no FSUIPC4.log is created, FSX probably never attempted to load the module. If the log exists, read its final lines; they usually separate a module-loading failure from a later connection problem.

What does “malformed EXE/DLL detected” mean?

The “malformed EXE/DLL detected” message usually means the installer could not read a Windows executable or DLL because the file is incomplete, corrupt, modified or not the file it expected.

1. Identify the named file. Read the installer log or full error message before changing anything. The fix depends on whether it names the installer, FSUIPC4.dll or fsx.exe.
2. Replace a damaged download. If it names the installer or FSUIPC DLL, delete the downloaded archive and extracted folder, obtain a fresh copy, extract it completely and try again.
3. Restore FSX rather than replacing its executable manually. If it names fsx.exe, use the original installation media's repair facility or Steam's file verification. Modified or incomplete simulator executables can fail the installer's checks.
4. Review security interference. Antivirus software can quarantine or truncate a file during extraction. Review its history rather than disabling all protection.
5. Do not download loose replacement DLLs. Never put a random FSUIPC, SimConnect or system DLL into System32, SysWOW64 or the FSX folder to suppress this error.

A malformed dll.xml is a different problem: the executable files may be valid, but the XML telling FSX which modules to load has broken tags or entries. Preserve a backup and any unrelated add-on entries before creating or repairing that file.

Why can an add-on still not connect after FSUIPC is installed?

An add-on can fail to connect even when FSUIPC4 itself is installed correctly because compatibility, Windows permissions and network requirements are separate issues.

• Confirm the FSUIPC options window opens inside a loaded FSX flight.
• Check that the other application supports FSX through FSUIPC4 rather than requiring FSUIPC7 or another simulator interface.
• Run FSX and the application at the same Windows privilege level. Prefer running both normally instead of elevating only one.
• Wait until the flight is fully loaded; some utilities do not connect from the Free Flight screen.
• For software on another computer, check its WideFS and network requirements.

Our FSUIPC connection troubleshooting checklist covers rejected DLLs, permissions, security software and the useful log files without repeating the installation.

How should I update or reinstall FSUIPC4?

Update FSUIPC4 by backing up your settings and running the newer compatible FSUIPC4 installer over the existing installation.

Do not delete the entire Modules folder; other FSX add-ons may store DLLs and configuration files there. After updating, load a flight, open FSUIPC through Add-ons and confirm that your assignments, calibrations and profiles remain available. If an aircraft installer later replaces FSUIPC4.dll with an older bundled copy, reinstall the newer compatible package again.