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

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

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

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).

I too experienced this audio defect after todays Windows update on two different hardware spec PCs. The audio was not being played because the process used to playback the audio, JTAlertV2.Manager.exe, was closing without recording or throwing an error. JTAlertV2.Manager closing will be noticed when any of its owned windows, Callsigns, Messaging, Activity & BandHeat close without warning. The fix... Open Control panel and uninstall the "Microsoft Windows Desktop Runtime - 5.0.7" that was installed today as part of the Windows update. Download version 5.0.6 of the desktop runtime and install that. Download the x64 or x86 type that matches the architecture type of JTAlert you have installed The direct download links for the runtime... 64bit (x64) https://download.visualstudio.microsoft.com/download/pr/6279dc90-f437-4481-82a5-73dd9f97da06/6519ef44735fd31115b9b1a81d6ff1e8/windowsdesktop-runtime-5.0.6-win-x64.exe 32bit (x86) https://download.visualstudio.microsoft.com/download/pr/315854e8-6857-4d0d-b7e0-57761e3f7d12/b31193ac2c9f1674b66cf7a65c2521de/windowsdesktop-runtime-5.0.6-win-x86.exe That's all that is need to restore JTAlert functionality.. Reproducible faults are far easier to diagnose and resolve then when the fault can't be reproduced at will. Once I was able to experience the fault at will, the solution didn't take too much time to uncover (this time). de Laurie VK3AMA

An update on the current status of broken JTAlert audio with the .NET 5.0.7 desktop runtime. I just now finished testing a new NET build with the fix that broke audio with NET 5.0.7. It worked flawlessly. After reporting my successful tests I asked the question, "Any idea on how long before the fix makes it into a public NET release, days, weeks or months?" I got the response... This will likely be more on the scale of months rather than weeks due to the servicing timeline. That response was unexpected, but I understand the issue. So I will be going with my plan "B", dropping the audio library which is broken by the NET 5.0.7 changes. That has already been coded and has been with the test team for a few days now. I will be targeting the JTAlert 2.50.2 public release for 21-June-2021. Please be aware that JTAlert 2.50.2 will no longer support audio output device selection. All audio output will be sent to the device set as the default under Windows. If JTAlert audio output device selection is important to you, my suggestion is to roll back JTAlert to version 2.16.17 If the affected audio library, NAudio, developer codes a fix before the new fixed NET runtime is released I will reverse the "playback on the default audio device only" change. I do note that the NAudio developer has been conspicuously quite regarding this issue, so I am not expecting a fix for the NAudio library any time soon. de Laurie VK3AMA