Hardware IDs for FTDI devices are not parsed correctly on Windows about pyserial HOT 3 CLOSED

When you talk about the wrong VID/PID/Serial, do you mean this line:
FTDIBUS\VID_0403+PID_6001+A600ARJHA\0000?

If yes, I think the problem is not related to pyserial as this string is directly taken from the SetupDiGetDeviceInstanceId or SetupDiGetDeviceRegistryProperty function from the setupapi library.

But I have quite a few FTDI Devices connect to my PC and all the serial numbers are just expanden with a single A character. So splitting this extra character off is my quick fix.

from pyserial.

"normal" devices start with "USB" and list_ports detects that, then deconstructs that hardware ID into the fields such as shown by the other example (COM7). So it looks like there needs to be a special case because some driver writer decided to do things differently :/

from pyserial.

Partial fix included in new release (v3.0.1), USB information is now added in the format used by other devices too. However the location information provided by Windows is hidden by the FTDI driver, so there is no LOCATION part (and I have currently no plan to spend time on this).

I do not know if there are additional chars in the serial number such as extra As. With hwgrep:// you can also match the partial serial number or just match what list_ports returns anyway.

from pyserial.