* Determine which bit version of Windows you are running, 32bit (x86) or 64bit (x64). See this helpful link from How-To Geek ( https://www.howtogeek.com/howto/21726/how-do-i-know-if-im-running-32-bit-or-64-bit-windows-answers/ ). * Install the .NET 5 *Desktop* Runtime choosing the bit version that matches your Windows bit version determined in step 1. Download from here ( https://dotnet.microsoft.com/download/dotnet/5.0 ). It is Important to choose the " *.NET Desktop Runtime* " NOT the non-desktop ".NET Runtime". At the time of this writing, the latest is .NET 5.0.8. Direct download links are ... * 64bit (x64) windowsdesktop-runtime-5.0.8-win-x64.exe ( https://download.visualstudio.microsoft.com/download/pr/9b564b8a-a26d-4bb3-8f30-1101ae71a55a/2cee4f9e4c0e77e3d0f866fdf690864e/windowsdesktop-runtime-5.0.8-win-x64.exe ) * 32bit (x86) windowsdesktop-runtime-5.0.8-win-x86.exe ( https://download.visualstudio.microsoft.com/download/pr/c1c0117b-3565-4661-9a77-7629c937f808/90a45135929796778a9fd418bbad6bb3/windowsdesktop-runtime-5.0.8-win-x86.exe ) * Download and install the latest JTAlert version from here ( https://hamapps.com/JTAlert/ ). Choose the bit version that matches your Windows bit version and the .NET 5 Desktop Runtime bit version. At the time of this writing, the latest is JTAlert 2.50.4. Direct download links are ... * 64bit (x64) JTAlert.2.50.4.Install.X64.exe ( https://dnl.hamapps.com/JTAlert/37eec2ff5f60d82832f4725c1a4b15e3 ) * 32bit (x86) JTAlert.2.50.4.Install.X86.exe ( https://dnl.hamapps.com/JTAlert/bf8fad76d06563f56c964d36200254fa ) * After installing the .NET Desktop Runtime and JTAlert. Run the ".NET Framework Check" shortcut installed under the "HamApps JTAlert" Windows start-menu group (which is automatically created by the JTAlert installer). If all has been installed correctly, you should see a window similar to this... Note: This image is from a 64bit (X64) Windows environment. The results will be similar for a 32bit (x86) Windows environment with changes in the bit version and OS Architecture reported. de Laurie VK3AMA

The latest JTAlert version 2.50.4 is now available @ https://hamapps.com/JTAlert/ <https://hamapps.com/JTAlert/> This release corrects a defect with 2.50.3 that prevented some users from opening the Callsigns window along with failed sound and UDP comms. de Laurie VK3AMA Release Notes. > 2.50.4 (2021-Jul-15) > > *** Includes Callsign database file version 2021-07-12 (2021-Jul-12) > > Fixes: > > Miscellaneous crtical faults: Callsigns window and other 2.50.x > series windows > not opening, no sound, no UDP comms with WSJT-X. > JTAlertV2.Manager.exe process > continually stopping and starting. This did not affect all > JTAlert users. > (2.50.3 defect) >

Copyright 2011 - 2021, Laurie VK3AMA, All Rights Reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to use the Software subject to the following conditions. The software is provided "AS IS", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and non-infringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software. Specifically: 1. You may install and use an unlimited number of copies of JTAlert on any number of computers for personal use ONLY. Commercial use is expressly forbidden. 2. You are not permitted to sell JTAlert or any portion of it. 3. You are not permitted to host JTAlert files on external websites, forums, bulletin-boards, blogs, etc. 4. You are not permitted to distribute JTAlert in any form. 5. You are not permitted to include JTAlert or any portion of it in any commercial software. 6. You are not permitted to decompile, disassemble, reverse engineer or modify the JTAlert executable or any portion of it, including support files (eg. plugin, sound and callsign files).

While I permit discussion of JTDX and WSJT-X issues here on this forum, especially when they relate to JTAlert, this group is not for JTDX or WSJT-X specific bug reports or operation questions. These application specific questions (bug reports, how-to questions) should be posted to the support groups of those applications. For your convenience, the official support groups are... *WSJT-X https://groups.io/g/WSJTX/ JTDX https://jtdx.groups.io/g/main* de Laurie VK3AMA

The services running on the HamSpots Server that manage Band Activity data and Text Messaging for old (pre 2.15.0) versions of JTAlert have been disabled. Spots upload to HamSpots is not affected by this change. Server load has seen a significant increase in recent weeks. This change is part of the current Server load reduction activity. It is very unlikely they will be re-enabled in the future. If either of these two disabled services is important to you, a JTAlert upgrade to a more recent version will be needed. Sorry for the inconvenience. de Laurie VK3AMA

Since JTAlert was released in 2011, there have NEVER been any documented virus/malware/trojan infections caused by JTAlert. Prior to making a new JTAlert release publicly available, the JTAlert Installer is submitted to the VirusTotal Online Scanner where scans from over 70 commercial scanners are performed. Detection's that don't identify a specific named threat, but contain words like "Gen", "Generic", "Malicious", "Confidence", "Malware", "Riskware", "Reputation", "Score", "Heuristic", "Autoit", "Script", are typically false-positives. They don't identify a genuine threat. These sort of threat identifications are typically due to the compiler used to generate the JTAlert code or due to a lack of use among the user base of this Virus protection software (typically for niche-market Amateur Radio software) If your concerned about unsafe JTAlert files reported by your Virus/Malware software please do the following... Don't install the software. Send a false-positive submission to your Protection software company. Wait for them to confirm that the file is safe and they update their definitions files before installing/upgrading JTAlert. Reputable Protection software companies offer a false-positive reporting/testing service. If your software doesn't provide this fundamental service, you should seriously consider changing to a company that does. Users are ultimately responsible for their PC/Windows infrastructure, as such they should take the initiative and report suspicious files to their Protection software provider, rather than simply accepting third party advice to apply file/directory exemptions. If you believe there is a genuine threat contained within the JTAlert files, stop using/installing the program and immediately submit the file to your Protection software vendor for analysis. If your vendor reports a threat (not a possible threat or potential risk) submit a message to this group. de Laurie, VK3AMA