So the question is: is this normal? what am I supposed to do to use these virtual COM ports? I tried deleting and recreating the COM ports in various ways (using the new "settings" window, via the Control Panel, or via the Device Manager), with no success: none of these outgoing ports will open. I tried a few different serial terminal programs with the exact same result. ![]() I can see them, list them with the UI or through WMI, but they just won't let me open any serial communication. Ports just refuse to open any connection, no matter what settings I use. But the big issue is I am totally unable to use any of these COM ports to communicate with the devices: the ingoing ports open but nothing happens (I guess this is normal since the devices are not supposed to initiate any communication), and the outgoing The two others only created one outgoing port. The first three created two COM ports for each: one outgoing (which I assume is the "regular" one), and one ingoing. OK, why not, I don't really mind a little cleanup. First, the migration process removed all virtual COM ports from the system without notice. Here is what happened with the migration to W10: I work with many devices that use the SerialPort Profile to communicate over Bluetooth.Įverything was fine on Windows 7 (each device had its own virtual COM port, which I could use with any serial terminal (mostly PuTTY). ![]() I just migrated to Windows 10 today, and I'm having trouble with the virtual COM ports over Bluetooth.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |