PortDock

When a USB-serial adapter keeps disconnecting — cable, hub, power saving, driver and COM number checks

The COM port vanishes and returns, changes number when replugged, or stops after days. Check cable, hub, USB power saving, driver and COM reservations in order.

Tools for this guidePort Inspector Windows program · freeSerial Windows program · freeSerial Timing Calculator web · no installWeb Serial Terminal web · no install

To the PC, a USB-serial adapter (USB to RS-485 or RS-232) is a USB device. When the USB link drops, Windows removes the COM port device and creates it again, and any program that had the port open gets «device not found» or write errors. This guide is about that case — the connection itself going away. If the link stays up but replies are late or frames split, that is the latency timer (see the USB-serial latency guide); if there is simply no reply, it is usually wiring or settings (see the Modbus no-reply guide).

Sort it by symptom first

SymptomLook at first
The port briefly disappears from Device Manager and comes backThe USB link dropped and re-attached — steps 1–4 below
The COM number changes when repluggedThe adapter has no serial number, or a different USB port was used — section 5
Only the first send after a long idle failsPower saving — section 3
The port stays but shows a warning icon in Device ManagerDriver and problem code — section 4
The port stays, only some replies go missingNot a disconnect — check latency timer, timeouts and wiring

Confirm it really disconnected by looking at the record. The Windows event log (Kernel-PnP) logs every time the device starts, so a day with several restarts means the link dropped and came back. The «History» card in PortDock Port Inspector collects these events per port and flags any day with three or more reconnects as «Look at».

1. Cable and connector — does the symptom follow?

2. Hubs — what sits in between?

3. Power saving — does it drop after idling?

Windows can put an idle USB device to sleep port by port («USB selective suspend»). Microsoft's documentation says the feature is on by default and strongly recommends not disabling it, because without it the CPU cannot reach deeper sleep states and power use rises. So rather than switching it off by reflex, first check whether the drops line up with power saving.

4. Driver — the problem code in Device Manager

5. Why the COM number changes

Windows takes COM numbers from its «COM port database» and keeps a number reserved even after the device is unplugged. That is why a new adapter can come up as COM15 or higher.

If the same adapter gets a new number in a different USB port, it most likely has no serial number (iSerialNumber). As a Microsoft blog post explains, Windows tells such devices apart by their parent — the port or hub they are plugged into — so in another port the adapter becomes a «new device» and gets a new COM number. An adapter with a serial number is recognised as the same device in any port.

What the program must do after a drop

Once USB drops, the open port is gone; even after replugging, the program has to open the port again. With «Reconnect when plugged back in» on, PortDock Serial opens the same device automatically when it reappears — even if the COM number changed — and logs «RECONNECT COM3 → COM5». If several identical adapters without serial numbers are plugged in, it cannot tell which one is which and keeps waiting; then pick the port and connect by hand.

What the PC cannot see

The checks above are on the PC side. The PC cannot see the RS-485 wiring behind the adapter (A/B swapped, termination, bias), grounding and shielding at the equipment, or noise when large loads switch on. If drops only happen when a particular machine starts, look at its wiring and grounding (see the RS-485 wiring guide).

Sources

Published 2026-10-29