path=\\.\COM, name=COM, driver=\Device\BthModem6
path=\\.\COM3, name=COM3, driver=\Device\BthModem4
path=\\.\COM, name=COM, driver=\Device\BthModem2
path=\\.\COM3, name=COM3, driver=\Device\BthModem0
path=\\.\COM2, name=COM2, driver=\Device\BthModem1
path=\\.\COM2, name=COM2, driver=\Device\BthModem3
path=\\.\COM26, name=COM26, driver=\Device\VCP0
On Windows, it appears that the COM port might end up one byte too short. From some investigation, this appears to be due to assuming the buffer returned is a 0-sentinal: https://github.com/ZigEmbeddedGroup/serial/blob/master/src/serial.zig#L95-L99
This appears not to hold, at least on my testing on Windows 10 with some Bluetooth SPP ports.
Here's the motivating output:
list.exe
Note the BthModem COM ports are one character too shortlist_port_info.exe
I have a fix which I can PR when I have some time soon.