Determine which bit version of Windows you are running, 32bit (x86) or 64bit (x64). See this helpful link from How-To Geek. Install the .NET 5 Desktop Runtime choosing the bit version that matches

Not everyone uploads their QSOs to QRZ, either manually or in real-time. QRZ is not a reliable source in this regard. I personally never upload to QRZ. As for

I'm using wsjt-x windows 10 .Not using any contest mode. When I say gong to their page I mean I go to their page on QRZ.COM and check their log to see if was good contact and no it's not there. ALT +

Subject Line changed to reflect true nature of problem. I picked up the HRD log reference in another members signature and incorrectly took it as part of your message.

Hello! if I'm following correctly, im using DX Keeper not HRD so in need to find the correct file for DX keeper to use? Can you tell me which one? My log file path I see in both JTAlert and DX keeper

Tnx Willi. In my opinion, Protection software that interferes in program operation without notifying the user that blocks have been implemented or files deleted/quarantined is

I just found the reason for logging problems on my Win7 Prof. system. There was no transfer of logs from JTDX via JTAlert (or GridTracker) to Log4OM, although all CAT commands worked ok, as well as

That message tells me that you don't need to worry about UDP setup with WSJT-X as that is working as JTAlert correctly received a logging messaged from WSJT-X. That message

Set up the option for wsjt udp multicast on loopback, no joy, still receiving the unable to confirm qso. Any additional guidance is welcome... thanks mark

Thanks Ron, I will set that up!

If you decide you need to use multicast, then you must set the option in JTAlert.: Settings, "WSJT-X UDP multicast on loopback" -- 73 Ron, W3RJW FTdx-5000, Timewave Navigator, WSJT-x 2.5.0, rc1,

Still receiving the error message...

Thanks Mike. Changed the Check QSO log delay to 15 seconds, the TCP Network Service port is 52000 and the log file path is good. Will see if this works, thanks

Thanks, they are in the WSJT-X ADIF file but do. Ot go to Lotw automatically as I had hoped...

Are your QSOs still logging or not? If they are getting logged anyways you can increase the timeout value here Also make sure you have the correct path to your database Mike W9MDB

Hello! New user of JTAlert and DX Keeper so my apologies if this has been addressed. Getting this confirmation error window after every QSO. Have tried reading through the online help but i'm pretty

Same, was advised to ignore the alert and the file is safe. For defender I went to virus & threat protection, under current threats you can unblock it.

Laurie, A few of us have windows defender showing the latest release as a trojan Trojan:Win32/Hynamer.A!ml I am sure it is a false positive. Chuck K0XM I set an exception in Windows Defender

All those functions are controlled by the "JTAlertSettings.exe" file located in the "Plugins" sub-directory of your JTAlert installation directory. It is either missing or being

Since I updated to latest version last night I have not been able to do any updating….rebuild alert database, anything “wanted” and also none of the main settings are available. I have attached