Serialtap fixed a Windows discovery bug that could give a development board a new identity after it moved to another Universal Serial Bus (USB) port. Windows keeps old entries for unplugged composite devices. When two active boards shared the same vendor and product identifiers, those stale entries made Serialtap fall back to the location of the port instead of the board's own serial identity.
The new lookup matches the active interface to its composite-device parent using Windows' ParentIdPrefix, then anchors the board to its media access control (MAC) address when that is the serial identifier. The maintainer tested two boards with the same identifiers plus one stale registry entry. Both active boards kept distinct keys and names after the daemon restarted.
Stable identity sounds small until a bench has weeks of logs, flash history, and error signatures attached to each device. A port-derived key quietly splits one board's evidence across several records, which makes a regression look intermittent or assigns it to the wrong unit. Teams using shared Windows benches should replug two identical boards into swapped ports and confirm that their log directories follow the boards before trusting unattended capture.