Troubleshooting

FSFO Troubleshooting Guide

Common setup, connectivity, speech recognition, aircraft-specific, and crash-reporting issues for Flight Simulator First Officer (FSFO).

Use this page first when FSFO is not working as expected. Most issues are caused by startup order, FSUIPC7 connection problems, missing LVARs, microphone permissions, or aircraft-specific configuration.

Recommended startup order:
Start programs in this order unless a section says otherwise:
Microsoft Flight Simulator → FSUIPC7 → FSFO

---

Page Appearance Guide

Blue boxes are used for general notes, explanations, and helpful background information.

Orange boxes are used for warnings, important requirements, or likely causes of a problem.

Green boxes are used for confirmed fixes, required configuration entries, or values the user should copy exactly.

Path boxes are used for Windows folder paths, configuration files, and other technical locations.

---

Quick Navigation

• FSUIPC7, LVAR, and Connection Issues
• Simulator Settings Issues
• Aircraft-Specific Issues
• Speech Recognition and Microphone Issues
• FSFO Crashes
• Still Need Help?

---

FSUIPC7, LVAR, and Connection Issues

Copilot does not move any switches

This usually means FSFO cannot properly communicate with FSUIPC7, the aircraft LVAR system, or the selected aircraft profile.

Step 1: Verify FSUIPC7 is connected

1. Open the FSUIPC7 tray icon near the Windows clock.
2. Right-click the icon.
3. Select Show.
4. Confirm FSUIPC7 reports Connected.
5. Confirm LVARs are available.

If LVARs show as missing or display as 0 Lvars, go to Step 4: LVARs fail to load.
If the WASM menu is disabled or missing, go to Step 5: Reinstall FSUIPC7 if needed.

Step 2: Verify FSFO is connected to FSUIPC7

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

If no FSUIPC7 version is shown, FSFO is not connected to FSUIPC7.

Step 3: Confirm the aircraft profile and checklist

1. Open the FSFO Start Flight page.
2. Confirm the correct Aircraft Profile is selected.
3. Confirm the correct Checklist is selected.
4. Start the flight.
5. Confirm the active aircraft profile appears in the lower-left corner.

Step 4: LVARs fail to load

1. Make sure Microsoft Flight Simulator is fully loaded into the cockpit before starting FSFO.
2. Confirm FSUIPC7 shows Connected.
3. If using a complex aircraft, give the aircraft extra time to finish loading its systems.
4. Start FSFO only after FSUIPC7 is already connected.
5. If the issue continues, close everything and restart in this order:
   1. Start Microsoft Flight Simulator and load into the cockpit.
   2. Start FSUIPC7 and confirm it shows Connected with LVARs loaded.
   3. Start FSFO last.

If LVARs still do not load, adjust the FSUIPC WASM scan settings. This should be treated as a last-resort troubleshooting step.

Adjust FSUIPC WASM scan settings

1. Close Microsoft Flight Simulator, 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:

LvarScanDelay=15
LvarScanFrequency=0

What these settings do:
LvarScanDelay=15 gives the aircraft more time to initialize before FSUIPC scans for LVARs.
LvarScanFrequency=0 disables repeated rescans, which may help if WASM is unstable or LVARs stop updating.

After saving the file, restart in this order:

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

If LVARs still fail to load, check whether the FSUIPC WASM module is missing or has crashed. Continue to Step 5.

Step 5: Reinstall FSUIPC7 if needed

If the steps above fail:

1. Close Microsoft Flight Simulator, FSFO, and FSUIPC7.
2. Reinstall the latest FSUIPC7 installer over the existing installation.
3. Restart Windows.
4. Start Microsoft Flight Simulator.
5. Start FSUIPC7.
6. Start FSFO.

If problems continue, perform a clean FSUIPC7 reinstall:

1. Uninstall FSUIPC7.
2. Delete the FSUIPC7 install folder.
3. Remove the FSUIPC WASM folder from the MSFS Community directory:

*\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\fsuipc-lvar-module

1. Reboot Windows.
2. Download the latest FSUIPC7 from:

   https://fsuipc.com/fsuipc7/

3. Unzip the installer.
4. Right-click Install_FSUIPC7.exe.
5. Select Run as administrator.
6. Make sure you select the simulator version you use: MSFS 2020, MSFS 2024, or both.
7. Make sure the WASM module is selected during installation.

After reinstalling, start programs in this order:

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

FSUIPC7 installer options

Back to top

---

FSUIPC Error #12: FSUIPC_ERR_SENDMSG

FSFO and FSUIPC7 must run at the same Windows permission level.

1. Right-click FSFO.
2. Select Properties → Compatibility.
3. Check whether Run this program as an administrator is enabled.
4. Repeat the same check for FSUIPC7.
5. Make sure administrator mode is either enabled for both applications or disabled for both applications.
6. Restart FSFO and FSUIPC7.

Back to top

---

FSUIPC Error #2

This error usually means FSFO could not complete the connection to FSUIPC7.

Common causes

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

Quick restart sequence

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

Additional checks

1. Make sure only one instance of FSUIPC7 is running.
2. Check the system tray near the Windows clock.
3. Temporarily disable Auto-Connect in FSFO and connect manually.
4. Whitelist FSFO and FSUIPC7 in your antivirus and firewall software.
5. Make sure Microsoft Flight Simulator, FSUIPC7, and FSFO are 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 restart the PC.
• After reinstalling, launch Microsoft Flight Simulator first, then FSUIPC7, then FSFO.
• If unresolved, perform a clean FSUIPC7 reinstall.

Back to top

---

WASM version mismatch

Example error:
WASM version X while WAPI expects Y

Recommended fix

Reinstall the latest FSUIPC7 installer. The installer includes matching WASM and WAPI components.

Manual fix for advanced users

Use this only if reinstalling FSUIPC7 does not resolve the mismatch.

1. Close FSFO, Microsoft Flight Simulator, and FSUIPC7.
2. Go to:

   https://www.fsuipc.com

3. Select Products → All Products.
4. Download the latest FSUIPC WASM Module and WAPI package.
5. Open the downloaded ZIP file.
6. Go to:

FSUIPC_WAPI.zip > FSUIPC_WAPI > dll

1. Copy:

FSUIPC_WAPID.dll

1. Paste it into the main FSFO V6 directory, where FSFO_V6.exe is located.
2. Go back to the downloaded ZIP file.
3. Copy the fsuipc-lvar-module folder.
4. Paste it into your Microsoft Flight Simulator Community folder and overwrite the existing folder.

Back to top

---

Simulator Settings Issues

Copilot executes actions at incorrect altitudes

This issue is usually caused by the simulator’s Units of Measurement setting being set to Metric.

When Microsoft Flight Simulator is set to Metric, altitude-related values may be reported or interpreted in meters instead of feet. FSFO expects altitude-related values to be in feet. If the simulator is using Metric units, the copilot may execute altitude-based actions too early or too late.

If your simulator Units of Measurement setting is set to Metric, your copilot may perform some actions using meters instead of feet.

Fix

• MSFS 2024: Go to General Options → Language → Units of Measurement and change the setting to Hybrid.
• MSFS 2020: Go to General Options → MISC → Units of Measurement and change the setting to Hybrid.

Hybrid mode is commonly used in aviation because altitude is shown in feet while most other measurements can remain metric.

Back to top

---

Aircraft-Specific Issues

These issues apply only to specific aircraft or aircraft families.

FBW A320 or Headwind A330: MCDU not programming

Edit this file:

Community\fsuipc-lvar-module\FSUIPC_WASM.ini

Set this value:

UseAirLocForHvars=Yes

Save the file and restart Microsoft Flight Simulator.

Back to top

---

Headwind A330: FCU or MCDU not responding

Copy this file:

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

Rename the copy to:

A330.hvar

Restart Microsoft Flight Simulator.

Back to top

---

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.
3. Navigate to the appropriate PMDG work folder below.

MSFS 2020 Work Folder

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

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 Notepad.
2. Add the following lines to the very end of the file:

[SDK]
EnableDataBroadcast=1
EnableCDUBroadcast.0=1

1. Save the file.
2. Restart Microsoft Flight Simulator.

Replace {username} with your Windows username.
Replace {aircraft_name} with the specific PMDG aircraft you are using, such as 737, 777, or another PMDG aircraft folder name.

Back to top

---

Speech Recognition and Microphone Issues

No English speech recognizer installed

If you are using the Microsoft Speech Engine, FSFO requires at least one English speech language pack. Your Windows display language and 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.
4. Select any English variant, such as English (United States) or English (United Kingdom).
5. Click Next.
6. Make sure Language pack and Speech are selected.
7. Click Install.
8. Restart Windows.

After restarting, FSFO should detect an en-* speech recognizer.

If English is already installed

1. Open Settings → Time & language → Language & region.
2. Click the three dots next to the English language.
3. Select Language options.
4. Under Speech, click Download if it is not already installed.
5. Restart Windows.

Back to top

---

Voice recognition troubleshooting

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

Basic microphone checks

1. Open Windows Voice Recorder.
2. Make a short test recording.
3. If you cannot record audio, fix the microphone issue in Windows before troubleshooting FSFO.

Windows 11 microphone permissions

Go to:

Settings → Privacy & security → Microphone

Make sure these are turned on:

• Microphone access
• Let apps access your microphone
• Let desktop apps access your microphone

Correct input device

1. Open Settings → System → Sound → Input.
2. Select the microphone you are using.
3. Speak into the microphone.
4. Confirm the input level meter moves.

Exclusive mode test

1. Open Control Panel → Sound → Recording.
2. Select your microphone.
3. Click Properties.
4. Open the Advanced tab.
5. Temporarily uncheck Allow applications to take exclusive control of this device.
6. Apply the change and test FSFO again.

Recommended microphone gain

1. Open the microphone Levels tab.
2. Start with a level between 70 and 90.
3. Avoid setting the level to 100 with boost enabled unless your microphone is very quiet.

Accuracy tuning

• Lower Input_VoiceAccuracy if commands are being missed.
• Increase Input_VoiceAccuracy if false triggers occur.

To change the accuracy setting:

1. Open FSFO.
2. Go to Settings.
3. Select Train Speech.
4. Click Next → Next → Next.
5. Adjust the voice accuracy setting.

Known conflicts

Close the following applications while testing voice recognition:

• Discord
• Microsoft Teams
• NVIDIA Broadcast
• Voicemeeter
• Audio enhancement tools
• Other applications that may take control of your microphone

Back to top

---

No microphones found

Use these steps if FSFO shows no available input devices.

Confirm Windows can see your microphone

1. Open Settings → System → Sound → Input.
2. Select your microphone under Choose a device for speaking or recording.
3. Speak into the microphone.
4. Confirm the input level meter moves.

Allow microphone permissions

Go to:

Settings → Privacy & security → Microphone

Turn on:

• Microphone access
• Let apps access your microphone
• Let desktop apps access your microphone

Enable the microphone in Control Panel

1. Open Control Panel → Sound → Recording.
2. Right-click your microphone.
3. Select Enable.
4. Right-click it again.
5. Select Set as Default Device.
6. Optional: Select Set as Default Communication Device.

Basic hardware checks

• Make sure the microphone is not muted.
• Check any headset mute button, inline mute switch, or hardware switch.
• Unplug and reconnect the microphone.
• Try a different USB port.
• Avoid USB hubs while testing.
• If using Bluetooth, reconnect the device and confirm the correct headset or hands-free input is selected in Windows Sound settings.

Back to top

---

FSFO Crashes

FSFO crashes or closes unexpectedly

Windows Event Viewer

When reporting crashes, include Windows Event Viewer logs.
These logs help support identify the actual crash module, exception code, and faulting application details.

How to collect Event Viewer logs

1. Type Event Viewer in the Windows search bar.
2. Open the Event Viewer app.
3. Expand Windows Logs.
4. Select Application.
5. Look for any Error messages associated with FSFO.
6. Confirm FSFO.exe is listed in the General field.
7. Click the Details tab.
8. Copy the contents.
9. Email the details to support.

Back to top

---

Still Need Help?

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