Preserve a known-good identity
- Record USB hardware IDs, adapter markings, driver provider/version and Windows build.
- Preserve the working driver installer before updating or moving the system.
- Check Device Manager status and test the assigned COM number in the legacy application's supported range.
- Reconnect across USB ports and reboots to observe enumeration stability.
- Measure latency, buffering and control-line behavior with the real workload.
Adapters sold under similar names may not behave identically. Hardware revisions and non-genuine or misidentified devices are possible, but diagnose from hardware IDs and observed compatibility rather than assuming a chipset story from appearance alone.
Decide whether to keep the adapter
| Driver cannot start | Verify hardware ID and supported driver/OS combination; avoid random driver packages. |
|---|---|
| Application cannot select port | Assign a stable lower COM number if the software has a legacy limit. |
| Bytes arrive but workflow fails | Measure timing, buffering and modem-control behavior. |
| Environment remains fragile | A documented industrial adapter with supported drivers may be safer than continued driver pinning. |
See the general USB-to-serial guide, virtual COM integration, VB6 MSComm troubleshooting and the serial pillar.