Glen, I have By Individual band selected and only 6 m checked. Robie AJ4F

Trevor, View/Show Log Fields Robie AJ4F

Tom, /MM means maritime mobile, the grid you reference in international waters so the country is None! I have several of these confirmations in LoTW. Robie AJ4F

Bill, Thanks for the feedback! Robie AJ4F

Rich, This happens to me routinely. There was a post about the cause some weeks ago. I’m sure someone will revive it. Robie AJ4F

The JTalert main screen issue was resolved by deleting the ini file and letting JTAlert regenerate it, The issue of no communication between WSJT-X and JTAlert was intermittent an has not recurred aft

Mike, Thanks for the tip. Deleting the directory restored the JTAlert Main window and the alerts have been reconfigured. So everything looks "normal" now. However: 1. no WSJT-X decodes are being seen

All, I am assisting a local ham to troubleshoot the following problem. He has upgraded from an earlier version of JTAlert 2.16.17 I believe to version 2.50.5 X64. .NET 5 Desktop has been installed and

I installed today's windows update as well as the NET5 Desktop Runtime 5.0.8 X64 and still am not able to open the Callsigns Window. Task Manager shows that JTAlertV2.manager.exe is not running on my

Yes it matches both are X64

Joe, I did as you suggested and see no difference. Robie - AJ4F

Like Bob I am using 2.50.3 and do not have the callsigns window. I used task manager and determined that with 2.50.3 installed JTAlertV2.manager.exe is not running. With 2.50.1 installed JTAlertV2.man

Laurie, Here's a link to the FFMA (Fred Fish Memorial Award) http://www.arrl.org/ffma Work and confirm all 488 grid squares that cover the contiguous 48 US states. Robie - AJ4F

Laurie, I do the same as you and I have not had any issues so far. Robie - AJ4F