Does not work in win10

win10 64 bits, up to date
Nothing happens even if I tick the options in the context menu.

[avishorp]

What device are you trying to detect? Does it appear in Device Manager? Does it gets assigned with a COM port number?

Both devices I tested were FTDI FT232RL converters, and they do get assigned port numbers.

If you detect ports via their internal device names it is possible that FTDI does not use the same device name format as usual USB CDC ports.

Here are some info strings from device manager

FTDIBUS\VID_0403+PID_6001+A501LI6JA\0000
FTDIBUS\COMPORT&VID_0403&PID_6001
ftdibus\comport&vid_0403&pid_6001
USB\VID_0403&PID_6001\A501LI6J
\Device\00000267
\Driver\Serenum
\Driver\FTSER2K
\Driver\FTDIBUS

Enumerator is FTDIBUS

[f6fvy]

If you detect ports via their internal device names

Apparently, it's rather using the class GUID (line 130 of Popper.cs) normally set to 4D36E978-E325-11CE-BFC1-08002BE10318 for COM (and //) ports.

I see this:
full name USB Serial Port (COM10)

class guid {4d36e978-e325-11ce-bfc1-08002be10318}
bus type guid {00000000-0000-0000-0000-000000000000}
container id {4d0f32ce-e418-5ec1-8147-cfbce55459d8}
base container id {4d0f32ce-e418-5ec1-8147-cfbce55459d8}

[GitMoDu]

I'd like to add that besides the fact the some update made Popcom stop working, I had to uninstall because it was hogging WMI-Host (checked in event logs).

[avishorp]

Can you please share your full OS details (build number, edition etc.)? I have several Win 10 installation and they work without any issue. ‫בתאריך יום ו׳, 14 בדצמ׳ 2018 ב-21:35 מאת ‪André‬‏ <‪ notifications@github.com‬‏>:‬

…

I'd like to add that besides the fact the some update made Popcom stop working, I had to uninstall because it was hogging WMI-Host (checked in event logs). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABImMgVI5B3T8GlAtJ2vhCqdUUrQeo5Tks5u4_2IgaJpZM4VydRw> .