Mostly these states are a result of user action, not anything the kvm is doing wrong… If the kvm thinks the device has been misbehaving, you may need to powercycle the kvm as well. You may have to un/replug the receiver on each machine in turn – start with machine 1 then do the numlock thing, then try machine 2 with the numlock and switch back to machine 1.

the usb2 hub is a hub connected to usb3 root port, which sometimes doesn’t enumerate upstream. Otherwise an externally powered USB3 hub would give you a bit more usb3 connectivity.Īs for other devices not working on hid, double check device manager.

Both protocols are understood by the kvm but if one host uses one protocol and the other uses the other, it leads to exactly what you’ve observed. The logitech mx is by default using an 8 byte protocol but with the software uses a 20 byte protocol. Without realizing it your diagnostics confirm it’s a software issue because the usb3 ports don’t try to mess with the device they just reset and reconnect it whereas hid is a kind of passthrough where the device never really gets a reset. If that fixes it, it is yet more evidence to confirm its a software issue. You can try touble-tappiing numlock to try a bus reset.

However, I am not using the mx master software on any of the connected ports. The logitech mx master works fine on the hid ports. I also tried getting a few other mice to test out (a Razer Basilisk X and a Logitech M705), and to my surprise, they don’t work at all when connected to an HID port, whereas the Logitech MX Master at least mostly functions.

Logitech mouse mac scroll not working