Are you sure you have the correct version of Net 5.0.x installed? When go to PC Settings -> Apps and scroll down, do you see "Microsoft *DESKTOP* Runtime - 5.0.17" or is it something else (missing *DE

Did you update the settings in JT Alert to point to the new database/ODBC instead of the old log? 73, ... Joe, W4TV

Have you modified your "Power Options" to disable monitor sleep and USB Selective Suspend? 73, ... Joe, W4TV

"Count" eQSL or QRZ "awards" at a real DX gathering like the DX dinner at Hamvention or Visalia or W9DXCC and you will be laughed out of the room. "Pretender" will follow you out the door ... 73, ...

eQSL "confirmations" are useless for DXCC, VUCC and FFMA awards - not worth the time/effort (I will upload those QSOs confirmed by LotW to eQSL as a courtesy to those who use eQSL but also use LotW).

What do you mean by "remove eqsl from my pop up"? 73, ... Joe, W4TV

Start by updating to JT-Alert 2.51.3 (current public version). 73, ... Joe, W4TV

What changed with your system? Software does not "just stop working". 73, ... Joe, W4TV

#FT8

Since the current version of JT-Alert is 2.51.3, I'd say 2.16.7 is retired. I believe there has been a change in the format of the database files sometime in the past two years. I strongly recommend b

That *WILL NOT* prevent an application (e.g., web browser, Facebook, TikTok, etc.) that uses the "Default Device" from sending its audio to your radio if the radio CODEC is the "Default Device". Again

https://www.top-password.com/blog/set-windows-to-power-on-off-usb-devices-in-sleep-mode/ Option 2 is the far better, more reliable approach. While you're there, select "Sleep" and disable "Hybrid Slee

Cliff, Windows will send its "noises" as well as any website/streaming audio to the "Default Device". *NEVER* allow Windows to make a CODEC in the radio the Default Device (or Default Communications D

Increase the delay after logging to check the record. JTAlert Settings -> Logging -> Check QSO Record 73, ... Joe, W4TV

Which version of WSJTX and JT-Alert did you install? If your WSJTX installer was wsjtx-2.5.4-win64.exe use the 64 bit version of dotNET. If your WSJTX installer was wsjtx-2.5.4-win32.exe, use the 32 b

"Unknown Band, Unknown Mode" is typically the result of not having installed the correct *desktop* version of dotNet 5.0. See the red banner at the top of the page at <www.hamapps.com>. Note: the curr

Did you install the required *DESKTOP* version of Miscosoft dot NET5.0 as documented *IN RED* at the top of the JT Alert Help file and at the top of www.hamapps.com? 73, ... Joe, W4TV

Are you running JT-Alert/64 or JT-Alert/32? Your screen capture says you have the 32 bit version of dotNET 5.0 installed (dotNet 5.0.16 (x86)). If you are running JT-Alert/64 you need to have dotNET 6

#FT8 #DXLAB

It sounds like you do not have the correct version of dotNET 5.0 installed on your system. See the *BIG RED BANNER* at www.hamapps.com 73, ... Joe, W4TV

#FT8 #DXLAB

Does it work if N3FJP is not running? Have you followed the instructions in JT-Alert Help, specifically Logging -> ACLog? on Loopback" See the Help file in JT-Alert, Specifically "WSJT-X UDP Setup" 73

1) What is selected for the "outgoing interface(s)" in the WSJTX Reporting tab? 2) what other applications are running? 3) Have you tried 224.0.0.1 as recommended in JT-Alert help? 4) Have you checked