How do I install FSUIPC for FSX?

To install FSUIPC for FSX or FSX: Steam Edition, download FSUIPC4, extract the archive, close FSX, run the included installer, and let it locate your simulator. Registration is optional. Restart FSX, accept any trust prompts, then confirm FSUIPC appears under the Add-ons menu.

Which FSUIPC version does FSX need?

FSX and FSX: Steam Edition use FSUIPC4. FSUIPC3 belongs to FS2004, while FSUIPC7 is for newer Microsoft Flight Simulator releases and is not an FSX replacement.

Use the latest compatible FSUIPC4 package for FSX and Steam Edition. Avoid old copies bundled with aircraft or utilities, especially on Steam Edition, because they may pre-date support for its executable and folder arrangement.

If you are unsure why an aircraft or utility requests the module, our explanation of what FSUIPC does in FSX covers the difference between its add-on interface and its optional control features.

How to install FSUIPC4 in FSX

The supplied FSUIPC4 installer should handle both the module files and the FSX loading entry; manually copying only the DLL is a common cause of failed installations.

1. Run FSX once. Open the simulator, load a flight, close it normally, and then close any related utilities. This creates the per-user configuration files the installer may need.
2. Extract the complete download. Unzip all files to a temporary folder rather than launching the installer from inside the compressed archive.
3. Protect existing settings. If this is an update, back up Modules\FSUIPC4.ini from the FSX installation folder. That file contains assignments, calibration and profiles created through FSUIPC.
4. Run the included installer. It should detect the FSX folder through Windows. If it asks for a location, select the simulator folder containing fsx.exe, not an aircraft, gauge or Documents folder.
5. Check the detected edition. A boxed installation usually has a folder ending in Microsoft Flight Simulator X; Steam installations commonly end in steamapps\common\FSX. Custom Steam libraries can be on any drive.
6. Skip registration if you do not have a licence. The unregistered module can still provide the interface required by most add-ons. Do not enter invented details or a key belonging to somebody else.
7. Read the installation result. Confirm that the installer reports a successful module installation and that it updated the FSX module-loading configuration. Retain its log if an error is shown.
8. Start FSX and approve the module. If FSX asks whether to run or trust FSUIPC4.dll, approve it when the package came from the trusted download above.

The installer normally places FSUIPC4.dll in the simulator's Modules folder. After the first successful load, the same folder should also contain files such as FSUIPC4.log and FSUIPC4.ini.

How do I check that FSUIPC is working?

A successful FSUIPC4 installation adds an FSUIPC entry to FSX's Add-ons menu after a flight has loaded.

1. Load an aircraft at an airport and wait until the cockpit is 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 options window opens and identifies version 4.

The absence of an Add-ons menu on the Free Flight selection screen does not prove the installation failed; check from inside a loaded flight. If the menu appears but another application cannot connect, run FSX and that application at the same Windows privilege level. Prefer running both normally rather than keeping FSX permanently set to run as administrator.

Why does FSUIPC not appear in the Add-ons menu?

FSUIPC usually goes missing because FSX did not trust the module, the installer targeted the wrong copy of FSX, or the module-loading configuration is damaged.

• Wrong FSUIPC generation: remove the incompatible copy and install FSUIPC4, not FSUIPC3 or FSUIPC7.
• Wrong FSX folder: if boxed FSX and Steam Edition share the computer, verify that FSUIPC4.dll is under the Modules folder belonging to the edition you launched.
• Old Steam-incompatible build: replace an add-on's bundled FSUIPC file with the newer FSUIPC4 package rather than installing both copies.
• Rejected security prompt: close FSX and launch it again so the module prompt can reappear. A blocked or quarantined DLL may need to be restored before reinstalling.
• Permissions failure: rerun the installer as administrator if FSX is protected under Program Files. Elevating the installer is different from forcing FSX itself to run elevated every time.
• Broken module entry: back up the existing FSX module-loading configuration and rerun the official installer. Other add-ons can leave this XML file malformed, preventing every module below the damaged entry from loading.
• Missing runtime components: repair FSX if FSUIPC4.log or the installer reports a SimConnect or side-by-side error. Boxed FSX should also be patched to Service Pack 2 or have Acceleration installed.

If no FSUIPC4.log is created, FSX probably never attempted to load the module. If the log exists, inspect its final lines: they usually distinguish a loading failure from an add-on that simply cannot connect.

Do I need to register FSUIPC4?

Most people installing FSUIPC solely because another FSX add-on requires it do not need a registered licence.

Registration does not determine whether the Add-ons menu entry appears. If FSUIPC is missing from that menu, fix the installation rather than entering a key.

How should I update FSUIPC4?

Update FSUIPC4 by backing up FSUIPC4.ini and running the newer FSUIPC4 installer over the existing installation.

Do not delete the entire Modules folder, as other FSX add-ons may store their files there. After updating, load a flight, verify the version through the Add-ons menu, and check that existing assignments and profiles remain available.