I have been happily using CP for months.  No longer!  For the past week or so, the bridge module refuses to work, although I have not knowingly changed anything relevant in my system.  I have searched hi and low for suggestions and tried a few without success:

- I have deleted and reinstalled the latest CP 

- I have re-installed the latest runtime .NET

- I have started the bridge manually before MSFS

- I have run CP and bridge as admin.  This results in constant UAC warnings that prevent MSFS use.

- I have added CP and bridge to the Windows Defender "good guys" list

- I have raised a ticket but don't know how to follow up

- I have tried and failed to locate a user community on the //42 Discord.  This may be because of my inability to navigate Discord (which is by far the most user-hostile software I have ever seen)

There might be a very simple solution that I am too thick to find and I need help.

Thanks!

Ph. Thibault CYUL

I'm guessing if you get UAC warnings it is trying to access folders forbidden by UAC. When you get the UAC warnings it should allow you to approve/deny access. That's what I had to do to get CP bridge to work.

Yes but when I approve access the same UAC popup comes back every few seconds and prevents me from getting the focus back to MSFS.  Weird!

This only happens if I run CP as admin.

OK. I will see if there is a way to give permanent access and then I'll run again as admin.  I don't remember having had to run as admin before (when CP was  OK).

Edited February 25Feb 25 by jetlag
addition

UPDATE:   I have installed an older version found in my backups.  

It makes no difference so the cause of the problem is somewhere in my system.

Would anyone have had that same issue and found a solution?  Any clue much appreciated.

RESOLVED thanks to Keven's sharp eye.

I am sharing the solution in case somebody else needs help.

Turns out that I had used FSUIPC to log some value and I had innocently selected the title bar to display the log.  As a result, Chaseplane could not locate the expected "Microsoft Flight Simulator..." window title and aborted.

This was not in the long list of possible causes offered by ChatGPT.  I bet it will be now.