Reinstall Logitech or Saitek Radio Panel drivers for FSX cleanly, restore the required plug-in, and diagnose a blank or undetected panel.
To reinstall Logitech or Saitek Radio Panel drivers for FSX or FSX: Steam Edition, disconnect the panel, uninstall both the Windows panel software and the FSX plug-in, restart Windows, install the correct panel driver first, then reinstall the FSX plug-in. Reconnect when prompted and approve the trusted-software prompt when FSX next starts.
Does the FSX Radio Panel need both a driver and a plug-in?
The Radio Panel needs its Windows software and an FSX-compatible plug-in; reinstalling only one often leaves the display blank. Unlike a yoke, the panel is not configured through FSX axis or button assignments.
| Component | What it does | Typical failure |
|---|---|---|
| Windows panel driver or Flight Panels software | Lets Windows communicate with the USB hardware and usually supplies a test utility. | The panel is absent from Device Manager or fails its hardware test. |
| FSX panel plug-in | Transfers radio frequencies and control inputs between FSX and the panel. | The Windows test works, but the display stays blank or the controls do nothing in FSX. |
Use driver and plug-in packages from the same Logitech or Saitek release family where possible. Mixing an old Saitek driver with a different-generation Logitech plug-in is a mistake we see regularly.
How to perform a clean Radio Panel driver reinstall
- Obtain both installers before removing anything. You need the Windows Radio Panel or Flight Panels software and the plug-in specifically intended for FSX. Match the driver installer to your Windows architecture, not to FSX: FSX is 32-bit, but a 64-bit Windows installation still needs the appropriate 64-bit Windows driver package. Windows 11 users should also follow our clean Logitech/Saitek driver installation checks for Windows 11.
- Close FSX and panel software. Check the notification area and Task Manager for a running Logitech, Saitek or Flight Panels application, close it, then unplug the Radio Panel.
- Uninstall the existing software. Open Windows Installed Apps or Programs and Features. Remove the Radio Panel or Flight Panels software and the Microsoft Flight Simulator plug-in. If old Saitek and newer Logitech entries coexist, remove the relevant copies from both brands, but leave unrelated yoke and pedal software alone.
- Remove a stale device entry only when necessary. In Device Manager, enable hidden devices and look for an entry clearly identified as the Radio Panel. Uninstall that device and select the driver-removal option if Windows offers it. Do not remove generic HID devices, USB controllers or root hubs indiscriminately.
- Restart Windows. A full restart clears panel processes and releases driver files that the uninstall process could not remove.
- Install the Windows panel software first. Run the installer with administrator permission and leave the panel disconnected until the installer requests it. Connect it directly to the computer rather than through an unpowered hub during diagnosis.
- Test the hardware outside FSX. If the package includes a panel test utility, operate both selector knobs, the tuning controls and every button. A successful test proves that Windows can communicate with the panel. The display may go blank again when the test closes; that alone is not a fault.
- Install the FSX plug-in second. FSX should have been launched at least once under the Windows account you use for flying. Keep it closed while installing the plug-in, and select the correct FSX installation if the installer presents more than one simulator.
- Start FSX and permit the panel software. Approve any prompt asking whether the panel application or module should run. Load a default aircraft, switch on its battery and avionics master, then test the panel before trying a complex add-on aircraft.
Why is the Radio Panel still blank after reinstalling?
The point at which the panel fails identifies whether the remaining problem is USB hardware, the Windows driver or the FSX plug-in.
| Symptom | Likely cause and next step |
|---|---|
| No USB connection sound and no named device | Try another direct USB port, inspect the cable and avoid a passive hub. This is not yet an FSX plug-in problem. |
| Windows recognises it, but the panel test fails | Remove mixed or incomplete Logitech/Saitek packages and repeat the driver installation. |
| The hardware test passes, but FSX remains blank | The FSX plug-in is missing, blocked or not starting. Reinstall that plug-in rather than repeating the USB driver installation. |
| It works in a default aircraft only | The driver is working. Check the add-on aircraft’s electrical state and panel-software compatibility. |
| It disconnects intermittently | Test a direct USB port and check Windows USB power-saving settings. Multiple panels may require a powered hub. |
For faults that remain after the clean installation, our Radio Panel fault-isolation checklist covers USB power, blocked panel processes and simulator-side failures in more detail.
Can I run the official plug-in with other panel software?
Run only one application that controls the Radio Panel. The official Logitech/Saitek FSX plug-in and a third-party panel manager can compete for the same device, producing blank displays, delayed inputs or rapidly changing frequencies. Disable one before testing the other.
What changes for FSX: Steam Edition?
The installation order is the same, but the plug-in must register against the Steam Edition profile actually used by FSX. If boxed FSX and Steam Edition coexist, an older installer may detect the boxed installation first; select Steam Edition when offered, or launch Steam Edition once, close it and rerun the plug-in installer.
FSX configuration files are normally under %APPDATA%\Microsoft\FSX. A side-by-side Steam installation may instead use %APPDATA%\Microsoft\FSX-SE. Check which folder FSX has updated rather than assuming that every Steam installation uses the latter name.
Should I delete FSX’s exe.xml file?
No. Panel launchers commonly use exe.xml to start with FSX, but that file may also contain entries for other add-ons. Back it up before inspecting it, then let the correct plug-in installer repair or add its own entry. Deleting the whole file can fix one panel while silently stopping several other utilities.