[Elecraft] Remote computer won't communicate with K3 after re-installing Windows 10

[Fred Jensen]

Jim, just disconnect and reconnect each USB cable while watching the COM 
ports in Device Mangler. You'll see the port disappear and then reappear.

FWIW:  I never had any problems with Prolific USB-Serial chipsets until 
Win10 graciously installed itself in the middle of the night without 
asking.  Turns out, there are several generations of Prolific chipsets, 
and there are no Win10 drivers for a couple of the oldest ones.  I found 
an adapter with one of the more recent chipsets and it works fine.

73,

Fred ("Skip") K6DGW
Sparks NV USA
Washoe County DM09dn

On 8/14/2017 10:27 AM, Jim Reisert AD1C wrote:
>> On my Win 10 machine I can tell by going to Device Manager, Ports, selecting
>> the specific port in question, then right clicking and going to Properties.
>> There, on all of my USB connections, it says "Manufacturer: FTDI".    Hope
>> that will help.
> Thanks, Bill, but I don't know which interface cable he has - it could
> be Prolific or FTDI,  depending on how old it is.  Because there are
> two COM ports not associated with the microHAM device (the generic
> "USB" and the one that has a Silicon Labs driver), I guess I have to
> assume that the generic USB COM port is the one that the K3 needs.
> I'll see what type of device it is, and if I can find the right driver
> for it.
>
> - Jim
>