locked Re: JT-Alert not recognizing WSJT-X is running
They’re both running un-elevated.
From: HamApps Support (VK3AMA)
Sent: Wednesday, January 16, 2019 7:12 PM
Subject: Re: [HamApps] JT-Alert not recognizing WSJT-X is running
On 17/01/2019 6:37 am, Edward Dowdy wrote:
Thanks for the update.
A pure guess... I suspect that Webroot is preventing JTAlert for enumerating the running WSJT-X processes on your PC. JTAlert does this in-order to automatically assign JTAlert instances to WSJT-X instances and and determine the Settings of a running WSJT-X instance to allow for auto-setup of JTAlert to work with WSJT-X. Windows itself prevents JTAlert from doing this if it detects a mismatch in the privileges level of the running processes, that is if WSJT-X is set to run as Administrator. This is normal per the Windows security model, what is not normal is when the interaction is blocked for processes that are not running elevated and they are both operating at the same privilege level. I suspect this is what Webroot is doing.
de Laurie VK3AMA