Troubleshooting

Common setup, connectivity, and configuration issues for Flight Simulator First Officer (FSFO).

Use this page when something is not working as expected before contacting support.

Unless a section says otherwise, always start programs in this order: MSFS → FSUIPC7 → FSFO.

---

Copilot does not move any switches

This usually indicates a communication issue between FSFO, FSUIPC7, and the aircraft LVAR system.

Step 1: Verify FSUIPC7 is connected

• Open the FSUIPC7 tray icon (system tray near the clock).
• Right-click the icon and select Show.
• Confirm FSUIPC7 reports Connected and that LVARs are available.

If the LVARs are missing (0 Lvars); please go to Step 4

If the menu is disabled (WASM is missing), please go to Step 5

Step 2: Verify FSFO is connected to FSUIPC7

Before starting your flight, FSFO should display the connected FSUIPC7 version in the lower-left corner.

If no version is shown, FSFO is not connected.

Step 3: Confirm aircraft profile selection

On the Start Flight page, ensure the correct Aircraft Profile and Checklist are selected.

After starting the flight, the active aircraft profile appears in the lower-left corner.

Step 4: LVARs fail to load:

1. Make sure MSFS is fully loaded into the cockpit before starting FSFO.
2. Confirm FSUIPC7 shows Connected to the simulator (step 1).
3. If you are using a complex aircraft, give it extra time to finish loading its systems.
4. Start FSFO AFTER FSUIPC7 is already connected.
5. If the issue continues, close everything and restart in this order:
   1. Start MSFS and load into the cockpit.
   2. Start FSUIPC7 and confirm it shows Connected WITH LVARS LOADED (step 1) .
   3. Start FSFO last.

If the LVARs still do not load, adjust the FSUIPC WASM scan settings (last resort):

1. Close MSFS, FSUIPC7, and FSFO.
2. Open the FSUIPC_WASM.ini file in the WASM persistence/work folder.
3. Do not edit the copy in the Community folder.
4. Set the following values:
   1. LvarScanDelay=15 //Increase as needed...start with 15
   2. LvarScanFrequency=0

After saving the file, restart in this order:

1. Start MSFS and load into the cockpit.
2. Start FSUIPC7 and confirm it shows Connected.
3. Start FSFO last.

LVARs still fail to load, check whether the FSUIPC WASM module crashed (move to step 5) What these edits do:

• LvarScanDelay=15 gives the aircraft more time to finish initializing before FSUIPC scans for LVARs.
• LvarScanFrequency=0 disables repeated rescans, which can help if the WASM is unstable or LVARs stop updating.

Step 5: Reinstall FSUIPC7 if needed

If the steps above fail:

1. Close MSFS, FSFO, and FSUIPC7.
2. Reinstall the latest FSUIPC7 installer over the existing installation.
3. If problems persist, perform a clean FSUIPC7 reinstall:
   1. Uninstall FSUIPC7.
   2. Delete the FSUIPC7 install folder.
      1. This is the directory you installed FSUIPC7.
   3. Remove the FSUIPC WASM folder from the MSFS Community directory.
      1. *\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\fsuipc-lvar-module
   4. Reboot Windows.
   5. Download the latest FSUIPC7 from here: https://fsuipc.com/fsuipc7/
   6. Unzip and Install the FSUIPC7.
      1. Right-Click Install_FSUIPC7.exe and select "Run as administrator."
      2. Ensure you select the sims you use - MSFS2020 and/or MSFS2024 (see picture below)
      3. Ensure the WASM module is selected (see picture below)!

After reinstall, start programs in this order:

1. Start MSFS and load into a cockpit.
2. Start FSUIPC7 and confirm it shows Connected.
3. Start FSFO last.

Back to top

---

FSFO does not stay on top

This behavior is caused by Windows process-level restrictions.

Reasons:

• Windows prevents non-admin apps from staying above admin-level apps.
• Another application may re-assert its “Always on Top” flag after FSFO.

Restarting FSFO reapplies its topmost flag, but FSFO cannot remain above an admin-level window unless it is also run as Administrator.

Workaround:

• Run FSFO and FSUIPC7 at the same permission level.
• Or disable Always-On-Top in competing applications.

Back to top

---

FSUIPC Error #12 (FSUIPC_ERR_SENDMSG)

FSFO and FSUIPC7 must run at the same permission level.

1. Right-click FSFO and FSUIPC7.
2. Select Properties → Compatibility.
3. Ensure “Run as administrator” is either enabled for both or disabled for both.
4. Restart both applications.

Back to top

---

FSUIPC Error #2

This error indicates a failed or incomplete FSUIPC connection.

Common Cause

• FSUIPC7 is not running
• More than one FSUIPC7 instance is open
• Antivirus or firewall is blocking communication
• FSUIPC7 was installed in a protected folder
• FSFO is trying to connect before MSFS and FSUIPC7 are fully loaded

Quick Restart Sequence

1. Close FSFO, FSUIPC7, and MSFS.
2. Reboot Windows.
3. Start MSFS and load fully into a cockpit.
4. Start FSUIPC7 and confirm it is running.
5. Start FSFO and click Connect.

Additional Checks

1. Ensure only one instance of FSUIPC7 is running (review your system tray).
2. Disable Auto-Connect in FSFO temporarily and connect manually.
3. Whitelist FSFO and FSUIPC7 in antivirus and firewall software.
4. Make sure MSFS, FSUIPC7, and FSFO are all running at the same permission level.

Installation Checks

• Do not install FSUIPC7 inside Program Files or other protected Windows folders.
• Install FSUIPC7 to a simple folder such as C:\FSUIPC7.
• If needed, reinstall FSUIPC7 and then restart the PC.
• After reinstalling, launch MSFS first, then FSUIPC7, then FSFO.
• If unresolved, perform a clean FSUIPC7 reinstall.

Back to top

---

WASM version mismatch

Error example: “WASM version X while WAPI expects Y”.

Recommended fix:

• Reinstall the latest FSUIPC7 installer, which includes matching WASM and WAPI components.

Manual fix (advanced users):

1. Close FSFO, MSFS and FSUIPC7
2. Go to www.fsuipc.com
3. Select Products > All Products > Download FSUIPC WASM Module 1.0.7 + WAPI 1.0.4 (version numbers will be different)
4. Go to FSUIPC-WASMv1.0.7.zip > FSUIPC_WAPI.zip > FSUIPC_WAPI > dll > copy FSUIPC_WAPID.dll
5. Paste FSUIPC_WAPID.dll in the main FSFO_V6 directory. (note: this is the same directory where your FSFO_V6.exe is located)
6. Go to FSUIPC-WASMv1.0.7.zip > fsuipc-lvar-module.zip > copy fsuipc-lvar-module folder
7. Paste fsuipc-lvar-module folder in MSFS Community Folder (overwrite the existing folder)

Back to top

---

Aircraft-specific issues

These issues apply only to specific aircraft or families.

FBW A320 or Headwind A330 – MCDU not programming

Edit:

Community\fsuipc-lvar-module\FSUIPC_WASM.ini

Set:

UseAirLocForHvars=Yes

Save and restart MSFS.

---

Headwind A330 – FCU or MCDU not responding

Copy:

Community\fsuipc-lvar-module\modules\A320.hvar

Rename the copy to:

A330.hvar

Restart MSFS.

---

PMDG aircraft – Enable SDK Data Broadcast

Important: The aircraft must be loaded past the Ready to Fly screen at least once before these files exist.

1. Exit Microsoft Flight Simulator.
2. Open Windows File Explorer and navigate to the appropriate PMDG work folder below.

MSFS 2020 Work Folder (per aircraft)

Store / Xbox Version

C:\Users\{username}\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-{aircraft_name}\work

Steam Version

C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-{aircraft_name}\work

MSFS 2024 Work Folder (per aircraft)

Store / Xbox Version

C:\Users\{username}\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work

Steam Version

C:\Users\{username}\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\pmdg-aircraft-{aircraft_name}\work

1. Open the {aircraft_name}_Options.ini file in a text editor such as Notepad.
2. Add the following lines to the very end of the file:

[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1

1. Save the file and restart Microsoft Flight Simulator.

Where {username} is your Windows username and {aircraft_name} is the specific PMDG aircraft you are using (for example, 737).

Back to top

---

No English speech recognizer installed

If you are using the Microsoft Speech Engine, FSFO relies on English phrases to perform specific actions. At least one English speech language pack must be installed. Your Windows display language or region can be anything.

If English is not installed:

1. Open Settings > Time & language > Language & region.
2. Click Add a language.
3. Search for English (any variant is fine, for example English (United States) or English (United Kingdom)).
4. Select the English language > Next.
5. Ensure Language pack and Speech are checked → Install.
6. Restart Windows.

After restart, FSFO should detect an en-* recognizer.

If English is already listed or installed:

1. Click the three dots … next to the English language > Language options > under Speech, click Download (if not already installed).
2. Settings > Time & Language > Language > Add a preferred language > choose an English variant > make sure Speech is included in the install options.

Back to top

---

Voice recognition troubleshooting

Use this section for microphone, permissions, and recognition accuracy problems.

Basic Checks:

• Microphone works?
  • Open Voice Recorder (Windows) and make a short recording. If you can’t record, fix the mic first.

• Privacy permissions (Windows 11):
  • Settings > Privacy & security > Microphone
    • Microphone access: On
    • Let desktop apps access your microphone: On

• Correct input device
  • Settings > System > Sound > Input > Select the mic you’re using. Speak and confirm the input level moves.

• No “exclusive mode” lock
  • Control Panel > Sound > Recording > [Your Mic] > Properties > Advanced
    • Uncheck Allow applications to take exclusive control (as a test)

• Reasonable gain
  • In the same Levels tab, set between 70–90 to start. Avoid 100 + “boost” unless your mic is very quiet.

English Speech Pack Installed (required):

• FSFO relies on English phrases. At least one English speech recognizer must be installed.
  • Windows 11: Settings → Time & language → Language & region → Add a language → English → ensure Language pack and Speech are selected → Install → Restart.
  • Your Windows display language can be anything; only the English speech component is required.

Accuracy Tuning

• Lower Input_VoiceAccuracy if commands are missed.
• Increase it if false triggers occur.
• To change the accuracy setting go to FSFO > Settings > Train Speech > Next > Next > Next

Known Conflicts Close applications such as Discord, Teams, NVIDIA Broadcast, Voicemeeter, or audio enhancement tools while testing.

Back to top

---

No microphones found

Use these steps if FSFO shows no available input devices.

• Confirm Windows can see your mic
  • Windows Settings > System > Sound > Input
  • Select your microphone under Choose a device for speaking or recording
  • Speak and verify the input level meter moves.
• Allow microphone permissions
  • Windows Settings > Privacy & security > Microphone
  • Turn ON:
    • Microphone access
    • Let apps access your microphone
    • Let desktop apps access your microphone
• Enable it in Control Panel (and set default)
  • Open Control Panel > Sound > Recording
  • Right-click your microphone > Enable
  • Right-click it again > Set as Default Device
  • (Optional) Set as Default Communication Device too.
• Basic Hardware Checks
  • Make sure the mic isn’t muted (hardware switch, inline mute, or headset button).
  • Unplug and replug, try a different USB port (avoid hubs while testing).
  • If it’s Bluetooth, reconnect it and confirm the Headset or Hands-Free input is selected in Sound > Input.

Back to top

---

FSFO crashes

When reporting crashes, include Windows Event Viewer logs.

1. Type Event Viewer in the Windows Search Bar
2. Click on the Event Viewer App
3. Expand Windows Log > Expand Application
4. Look for any Error messages associated with FSFO; FSFO.exe should be listed in the General field.
5. Click The Details Tab, Copy and Email the contents to support

Back to top

---

If your issue is not resolved after following the steps above, see Support.