Skip to content

Bridge Module not connecting

Confirm a ChasePlane Bridge connection failure, restore the installed components, and collect the right evidence if it continues.

Updated View as Markdown
For humans
SupportChasePlaneHelp and troubleshooting

This article covers the following platforms

If Bridge Module shows Not Working in ChasePlane’s status list, this guide shows how to confirm the failure and restore the Bridge. The Bridge is the background Windows component that connects ChasePlane in the simulator to its local services. It normally has no window or taskbar button.

Confirm the failed component

  1. Open ChasePlane from the simulator toolbar.
  2. Open Preferences.
  3. Find Troubleshoot, then review Status.
  4. Continue below only if Bridge Module shows Not Working. If it shows Connected, use the status of the other modules to identify the problem instead.

Restore the Bridge

  1. Close Microsoft Flight Simulator completely.
  2. Open Task Manager and check for CP MSFS Bridge.exe. If it remains after the simulator has closed, end that process.
  3. Open your Downloads and download the latest ChasePlane installer for the simulator you use.
  4. Run the ChasePlane Manager and reinstall ChasePlane. This restores the Bridge and its required simulator components.
  5. Start the simulator, load a flight, and open ChasePlane from the toolbar. Opening the panel starts the Bridge in the background.
  6. Return to Preferences → Troubleshoot → Status and confirm that Bridge Module shows Connected.

If setup reports an error

  • Bridge is already running: close the simulator, end CP MSFS Bridge.exe in Task Manager, then run the Manager again.
  • WASM Integrity Check Failed: reinstall ChasePlane with the latest Manager. The Bridge stops on purpose when it cannot validate the installed WASM module.
  • The Manager cannot find or start the Bridge: download a fresh Manager from your account and retry while the simulator and Bridge are closed.

Still not connected?

Restart the simulator once more, open ChasePlane, and reproduce the failure. Then contact Parallel 42 Support with:

  • a screenshot of the Status list;
  • your simulator version and whether you use the Microsoft Store or Steam edition;
  • the contents of the ChasePlane Logs folder from that fresh attempt.

Which files to send: MSFS 2024 or MSFS 2020.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close