: Todays Windows update and broken JTAlert audio - THE FIX


g4wjs
 

On 09/06/2021 07:57, HamApps Support (VK3AMA) wrote:
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...
  1. Open Control panel and uninstall the "Microsoft Windows Desktop Runtime - 5.0.7" that was installed today as part of the Windows update.
  2. 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

Hi Laurie,

on WIndows 8.1 I experienced the issue after Windows Update delivered the Windows Desktop Runtime update to 5.0.7, but here the JTAlert Manager process crashes with an access violation in a thread that appears to be playing audio. I do hear a few clicks and pops before that. It doesn't look like a completely silent abend to the process to me.

Either way, re-installing the Windows Desktop Runtime v5.0.6 (x64 in my case) restores correct audio playback behaviour. FWIW I am using JTAlert 2.50.0.


--
73
Bill
G4WJS.


Don Roden
 

How do you know which version of runtime to use ?       W4DNR


Jim N6VH
 


On 6/10/2021 6:26 AM, Don Roden wrote:

How do you know which version of runtime to use ?       W4DNR

_._,_._,_


Don,

If your computer is 64 bit, use that one. If it is 32 bit, use the 32 bit version. That applies to the versions of WSJT-X and JTAlert, also.

73,

Jim N6VH


g4wjs
 

On 10/06/2021 14:42, Jim N6VH wrote:


On 6/10/2021 6:26 AM, Don Roden wrote:

How do you know which version of runtime to use ?       W4DNR

_._,_._,_


Don,

If your computer is 64 bit, use that one. If it is 32 bit, use the 32 bit version. That applies to the versions of WSJT-X and JTAlert, also.

73,

Jim N6VH

Don and Jim,

the correct answer is use the version that matches the version of JTAlert you installed. 64-bit package for the 64-bit JTAlert, 32-bit package for the 32-bit JTAlert.


--
73
Bill
G4WJS.


Dave (NK7Z)
 

Open a term window, and type:

dotnet --info



73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist, RFI
ARRL Asst. Director, NW Division, Technical Resources


Jim N6VH
 


On 6/10/2021 7:12 AM, g4wjs wrote:
On 10/06/2021 14:42, Jim N6VH wrote:



Don,

If your computer is 64 bit, use that one. If it is 32 bit, use the 32 bit version. That applies to the versions of WSJT-X and JTAlert, also.

73,

Jim N6VH

Don and Jim,

the correct answer is use the version that matches the version of JTAlert you installed. 64-bit package for the 64-bit JTAlert, 32-bit package for the 32-bit JTAlert.


--
73
Bill
G4WJS.

Bill,

That is what I was trying to say, but I see I could have worded it better. Yes, they all should be either 64 bit or 32 bit. In general, my preference is to use 64 bit programs when they are available. There are some exceptions, however. Several years ago, Microsoft advised against using the 64 bit version of MS Office (I think it was Office 10, but I'm not sure), even on 64 bit machines.

73,

Jim N6VH