locked Re: Getting fed up..... #FT8

Gilles beaulieu

Thanks Mike I'll keep that in mind for next time.

Another small problem is on WSJT-X Band Activity used to get some callsign were highlighted different color. I don't get that anymore... Did I miss something along the way? any ideas?


Gilles - VE3NPI

On 4/14/2021 5:48 PM, Michael Black via groups.io wrote:
Microsoft likes to mess with the USB device every few updates.
All you have to do if you have a problem is uninstall all your audio devices and reboot.

I (and many others) have had to do this multiple times over the last several years.

It's not every update...but seems like it's the major ones that tend to mess with USB devices.
Can happen to both audio and COM ports.

Mike W9MDB

On Wednesday, April 14, 2021, 04:43:40 PM CDT, Phil Cooper via groups.io <pcooper@...> wrote:

Hi all,


I am in the process of getting a new Win10Pro box set up for the shack, and one of the “horrors” of Win10 that I am aware of (especially relating to radio software) is the fact that audio devices often end up being messed up.


This idea sounds really good, so is it really true? Can others confirm that this is correct?


Also, I use a microHAM MK11 as a connection between the PC and my radio (IC7800) and I wonder if Joe W4TV can confirm whether it is permissible to change the name of the microHAM sound devices?


Any advice would be welcomed….


I am not even going to try and install v2.5.0 or .NET5 on my old Win7pro (32bit) PC, as it is struggling already, and I would like to be able to network it so that I can retrieve files, check ini files etc once I have swapped them out.


73 de Phil GU0SUP



From: Support@HamApps.groups.io [mailto:Support@HamApps.groups.io] On Behalf Of Ron / W4MMP via groups.io
Sent: 14 April 2021 17:02
To: Support@HamApps.groups.io
Subject: Re: [HamApps] Getting fed up..... #FT8



I never have this problem with any Windows update.  This I believe is due to the fact that I give a name to the sound devices I care about.  It appears that Windows updates don't mess with named sound devices.  Do a similar naming operation for any USB/Serial adapters you care about.  That is performed in the device manager.  Give the USB/Serial device a com port number away from the default com port number (com1,com3,etc) such as com14.  


Ron / W4MMP

On 4/14/2021 11:25, Michael Black via groups.io wrote:

Yeah...I had the same problem and so did a friend of mine with the latest update.


Had to uninstall all sound devices (make sure you select View/Show hidden devices too) and reboot to let them install again...


Mike W9MDB





On Wednesday, April 14, 2021, 10:23:23 AM CDT, Paul <w2ec@...> wrote:



Are you running windows 10? Tuesday they did an update, it has scrambled many usb drivers to different ports, changed parameters etc. Took me over an hour to recover all mu USB attachments. Just one more of the windows features they keep forcing on us. 


W2EC Paul


On Wednesday, April 14, 2021, 11:17:49 AM EDT, Michael Black via groups.io <mdblack98@...> wrote:



What "same messages" ??


Mike W9MDB





On Wednesday, April 14, 2021, 10:15:34 AM CDT, Gilles beaulieu <ve3npi@...> wrote:



Hi Laurie, really getting fed up with this FT* stuff. I have done many contacts in the past. Here's what I have here: Yaesu FTDX-1200, scu-17, running ACLog, WSJT-X (ver. 2.3.0) and the latest JTAlert. I had it running perfectly without any hassles yesterday. Today I rebooted my PC and started JTAlert and try to make a few contacts. I keep getting errors with the sound card. No matter what I change in the setup it keeps crashing on me with the same messages. Not impressed at all.
Gilles - ve3npi


Gilles - VE3NPI

Prescott-Russell Amateur Radio Club


Join Support@HamApps.groups.io to automatically receive all group messages.