Re: Getting fed up..... #FT8
toggle quoted messageShow quoted text
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.
On Wednesday, April 14, 2021, 04:43:40 PM CDT, Phil Cooper via groups.io <pcooper@...> wrote:
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
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: