RESOLVED: Issue using Keyspan adapter USA-19H with Parallels 18.2.0 on a M2 Mac with Windows 11 Pro

I'm having the same issue with the Keyspan adapter. The serial assistant still doesn't find the adapter. I tried adding legacy hardware in order to get the Ports (Com) grouping in Device Manager but there is nothing to find so it won't add. I also followed Tripp-Lite instructions below to manually add the driver for Windows 11 Pro and the adapter assistance still can't see the adapter. I assume since it can't be seen that there isn't an old driver to remove as the last paragraph states but I did delete the adapter which was listed under "Other Devices" to try to delete any old drivers before performing the instructions below.

Tripp-Lite instructions:
Windows 11 Pro

1. Do not initially attach the device.
2. Download the correct driver from the product's support page on www.tripplite.eaton.com and unzip the driver into a folder of your choice.
3. Locate and open the Device Manager program from your computer's system tools.
4. Using the menu at the top, choose "Actions | Add drivers".
5. Browse to the folder where the driver is located, OK the installation.
6. Connect the device to your computer's USB-A port using the included cable.
7. Open Device Manager. The device should be correctly identified and have a driver available.

When downloading the most recent driver for this product it is important that the previous driver be manually uninstalled and removed from the computer. If the old driver is not removed the Device Manager will still attempt to utilize the old driver despite the presence of the new driver.

 

Hello,
Thank you for your feedback.

The Apple M1 chip has an ARM architecture (unlike the x86/x64 architecture typical of classic desktop processors). And in a virtual machine on a Mac with an M1 chip, it is currently possible to run only Window 11 ARM--the Windows version for processors with ARM architecture (for example, it is used on devices with mobile chips like Microsoft Surface Pro X). And indeed, despite the built-in compatibility layer that allows you to run x86/x64 applications on Windows ARM, some applications, or drivers do not work.

According to the system requirements in the documentation, the drivers are only supported on the x86 architecture, so you cannot install the necessary driver.

https://tripplite.eaton.com/support/owners-manual/753950

We advise you to contact the Tripp-Lite support team to inquire about when the driver for Windows 11 ARM will be implemented.

 

Thanks. I assumed the driver for Windows 11 Pro that I tried to install was sufficient. I didn't realize Windows 11 Pro ARM was different. I'll contact Tripp-Lite.

 

Well, I have found out that one must obtain an ARM driver for the chipset used in your cable or external device. I've contacted keyspan to see if they have a driver and they do not at this time but was going to check with engineering to determine if one is being worked on for Windows 11 Pro ARM. They are supposed to get back to me. We will see how that goes.

In the meantime, I found out that there are FTDI drivers available for USB to Serial adapters if the USB to Serial adapter contains an FTDI chip. I ordered a Gearmo USA-FTDI-A36 ( https://www.gearmo.com/shop/single-port-usb-to-serial-adapter/ ) from Amazon ( https://www.amazon.com/dp/B01DT6K8G2?psc=1&ref=ppx_yo2ov_dt_b_product_details ). Then follow the instructions I uploaded below. Hope this helps someone.

 

Beyond amazing. I have been using my 2013 Retina MacBook Pro (which still works great) for the past 10 years to program my URC MX-850 remotes (via a Windows 7 VM using VirtualBox, with Keyspan Serial Adapter and SerialClient making it work). I recently upgraded to a new M2 MacBook Air and obviously none of that works anymore. I had basically resigned myself to keeping the old 2013 laptop around forever just for remote programming when I came across this. I got Parallels, bought the Windows 11 license, and ordered one of the referenced serial adapters (and a USB-A to USB-C adapter). I'll be darned - it actually works!!! A tip in case anyone has the same issue I did - if your application throws an exception, try going to the advanced properties of COM3 and change the Latency setting from the default of 16 to 1 (credit where credit is due: https://www.remotecentral.com/cgi-bin/forums/viewpost.cgi?907511) - that was the key for me. Now I can retire my 10-year-old laptop and just use my snazzy new M2! THANK YOU @RickW7!!!

 

You are very welcome.

 

Worked for me as well. Much appreciated!!

 

Hi RickW7 and others. Used your post relating to the Gearmo USA-FTDI-A36 adapter and downloaded the FTDI VCP driver 2.12.36.4A**** as per the info provided. My Win 11 parallels will not process the driver "Windows could not find drivers for your device". I hope I am not missing something obvious but am using this path \\Mac\Home\Desktop\CDM-v2.12.36.4-for-ARM64-Signed-Distributable (6)\ARM64 and also tried \\Mac\Home\Desktop\CDM-v2.12.36.4-for-ARM64-Signed-Distributable (6)\ARM64\Release - the include subfolders option is selected.

 

You should download the driver file onto your Windows desktop. Then unzip it there also. Then go to Device Manager and follow the pdf instructions.

 

Thanks. I'll try that as soon as I figure out how to change the default path from the shared downloads folder.

 

Bingo. That was it. The default download path for Edge was the shared download folder which lives on the MacOS side. The unzipped directories were not being recognized either when using that path in device manager to the MacOS downloads or when copying the unzipped directories to the desktop. Used the Edge settings to change the path to the PC environment desktop, did a fresh download, then used File Explorer to unzip the download. That worked. Did the driver update routine twice to get all the Virtual Com Port features to play. For some reason, didn't fully take on the first driver update. Happy to say that the Gearmo USA-FTDI-A36 serial hardware is playing on com port 4 with the SCS TNC, and Packet radio. Thanks Rick.

 

Many thanks for this!! Been looking for a solution for awhile now