What is FSUIPC for FS2004, and how do I install it?

FSUIPC for Flight Simulator 2004 (FS2004 or FS9) is a module that lets compatible add-ons read data from and send commands to the simulator. Install the FS2004-specific FSUIPC 3 package, placing FSUIPC.dll in the simulator’s Modules folder, then start FS2004 and approve the module if prompted.

What does FSUIPC do in Flight Simulator 2004?

FSUIPC stands for Flight Simulator Universal Inter-Process Communication and provides a standard interface between FS2004 and compatible software. It exposes simulator data through locations commonly called offsets, allowing programs to read position, altitude, speed, weather and aircraft-system states or send supported controls back to FS9.

Flight loggers, weather utilities, ATC programs, hardware interfaces and cockpit applications are typical users. A program running on another computer may also require a matching network component such as WideFS; installing the local FSUIPC module alone does not create that remote connection.

FSUIPC is not an aircraft, gauge, scenery package or graphics upgrade. It will not increase frame rates, and FS2004 does not need it unless an add-on requires the interface or you want its additional control-assignment and calibration facilities.

FSUPIC, FSUICP, FSIUPC, FSUIP and SUIPC are common misspellings of the same product. The correct module and filename use the spelling FSUIPC.

Which FSUIPC version does FS2004 need?

Flight Simulator 2004 requires the FSUIPC 3 family; FSUIPC4 and later simulator-specific families cannot replace it.

FSUIPC’s major version number identifies the simulator generation, not an interchangeable upgrade. The highest-numbered download is therefore not automatically the right one for FS2004.

Can I use FSUIPC4 or an FSX free download in FS2004?

No. FSUIPC4 is the FSX-generation module and will not load as FSUIPC for FS2004. If the simulator is actually FSX, follow our FSX-specific FSUIPC installation instructions instead of copying files into an FS9 installation.

Is FSUIPC free, and which official package should I download?

Most FS2004 add-ons can use FSUIPC’s communication interface without the user purchasing or entering a personal registration. Registration concerns FSUIPC’s additional user-facing controls, not the basic dependency required by most compatible applications.

Choose the full, author-maintained distribution explicitly labelled FSUIPC 3, FS2004 or FS9. Read the documentation included with that package because registration availability and installation methods changed during the long life of FS2004.

We advise against downloading a loose FSUIPC.dll with no documentation or source information. Older aircraft, panels and utilities sometimes include a period copy of the DLL; installing one of those packages can silently overwrite a later compatible build. If that happens, reinstall your chosen FSUIPC 3 build after the older add-on.

How do I install FSUIPC in FS2004?

Install FSUIPC into the Modules directory belonging to the exact copy of fs9.exe that you use.

1. Close FS2004 and related utilities. Do not replace an in-use module while FS9 or an FSUIPC client is running.
2. Locate the real FS2004 folder. Find fs9.exe; the same directory normally contains Aircraft, Gauges, Modules and Scenery. Check the target of your FS2004 shortcut if more than one installation exists.
3. Confirm the FS9 executable is supported. Later FSUIPC 3 builds are intended for the standard FS2004 9.1 installation. An unpatched, altered or unsupported fs9.exe can produce a simulator-version error even when the DLL is in the correct folder.
4. Back up an existing installation. Preserve FSUIPC.ini and FSUIPC.key if present. Move any backup DLL outside the Modules folder or give it a non-.dll extension so FS9 cannot try to load both copies.
5. Extract the complete download. Unzip it to a temporary folder first. If Windows Properties offers an Unblock option for the verified archive, apply it before extraction.
6. Run the supplied installer or copy the DLL. When an installer is included, point it to the FS2004 directory containing fs9.exe and verify the destination it reports. For a manual package, copy FSUIPC.dll directly into the existing Modules folder.
7. Check the final path. It must end in Flight Simulator 9\Modules\FSUIPC.dll. Do not place it beside fs9.exe, in Gauges, in a nested Modules\FSUIPC directory or in a Windows system folder.
8. Start FS2004 and approve the module. Accept the security or trust prompt only when it identifies the FSUIPC file from the package you intended to install. Registration can be skipped if you only need the normal add-on interface.
9. Verify the load. Open a flight and look for FSUIPC in FS2004’s Modules menu. A successful start normally creates or updates FSUIPC.log in the same directory; FSUIPC.ini stores configuration settings.

Do I need to register FSUIPC for FS2004?

No personal registration is normally needed when an add-on merely lists FSUIPC as a dependency. The add-on’s own documentation still takes precedence, particularly for specialised or networked software.

Registration unlocks FSUIPC’s user facilities, including advanced axis and button assignments, joystick calibration and related configuration options supported by that build. Keys are tied to their FSUIPC version family, so an FSUIPC4 registration does not register FSUIPC3.

When updating a registered FS2004 installation, retain FSUIPC.key and FSUIPC.ini and replace only the module unless the package says otherwise. Our guide to locating and preserving an existing FSUIPC registration key explains where FS2004 stores it and when it is required.

Does FSUIPC for FS2004 work on Windows 11?

FSUIPC 3 can run with the 32-bit FS2004 application on Windows 11; there is no separate 64-bit FS9 DLL to install. Most Windows 11 problems involve protected folders, blocked downloads or mismatched permission levels rather than the module’s bitness.

• Protected installation folders: an FS9 installation under Program Files or Program Files (x86) may prevent an older installer from writing to Modules. Approve the file operation or run the verified installer with administrator permission, then confirm that the physical DLL was updated.
• VirtualStore redirection: Windows may redirect settings written by older programs. If FSUIPC loads but changes do not persist, check that FSUIPC.ini is being updated in the real FS9 Modules directory rather than a per-user virtual copy.
• Different privilege levels: run FS2004 and its external add-on at the same privilege level. Starting FS9 as administrator while the client runs normally, or the reverse, can interfere with communication.
• Blocked or quarantined files: unblock only a package whose origin you have verified. Do not restore an unexpected security detection merely to force the DLL to load.

Windows compatibility settings will not make FSUIPC4 work in FS2004 or cure an unsupported fs9.exe. Correct the module family and simulator version first.

Why does FSUIPC not appear or connect in FS2004?

A missing FSUIPC entry usually means FS2004 did not find, trust or load the DLL; a visible menu entry with a failed add-on connection points to a different problem.

A mistake we see repeatedly is troubleshooting the external add-on before confirming that FSUIPC itself loaded. Start with FSUIPC.log: if it does not exist, concentrate on the DLL path, Windows blocking and the trust prompt. If it exists, its opening lines usually identify the loaded build and any simulator-version rejection.

For startup messages, duplicate modules and FS9.1 mismatches, use our more detailed FS2004 FSUIPC error checklist rather than repeatedly copying different DLLs into the folder.