0.4.0/0.2.4 - Lose KB+M control after mounting USB image #278

New issue

Open

opened 2026-02-20 08:21:41 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 08:21:41 -05:00

Owner

Originally created by @Rahzadan on GitHub (May 21, 2025).

Originally assigned to: @ym on GitHub.

As the title says, I'm finding that I will lose keyboard and mouse control if I reboot a connected machine with a USB drive image mounted. Anyone else experiencing this? The PC in question has the DC Power control block as well. Powering off/on the PC with an image mounted also causes loss of control. UI still reports USB is connected however. Rebooting the JetKVM using the web terminal restores control.

Originally created by @Rahzadan on GitHub (May 21, 2025). Originally assigned to: @ym on GitHub. As the title says, I'm finding that I will lose keyboard and mouse control if I reboot a connected machine with a USB drive image mounted. Anyone else experiencing this? The PC in question has the DC Power control block as well. Powering off/on the PC with an image mounted also causes loss of control. UI still reports USB is connected however. Rebooting the JetKVM using the web terminal restores control.

deekerman added the

component: usb/hid

component: usb

component: usb/storage

labels

2026-02-20 08:21:41 -05:00

deekerman commented

2026-02-20 08:21:42 -05:00

Author

Owner

@ym commented on GitHub (May 22, 2025):

I'm trying to reproduce the issue, but haven't succeeded yet. Could you confirm which USB classes and identifiers you are currently using?

If possible, could you also send me a screen recording of the steps to reproduce the issue? My email address is siyuan+gh493#buildjet.com.

@ym commented on GitHub (May 22, 2025): I'm trying to reproduce the issue, but haven't succeeded yet. Could you confirm which USB classes and identifiers you are currently using? If possible, could you also send me a screen recording of the steps to reproduce the issue? My email address is `siyuan+gh493#buildjet.com`.

deekerman commented

2026-02-20 08:21:42 -05:00

Author

Owner

@Rahzadan commented on GitHub (May 24, 2025):

I think it was because I was mounting USB drive image that I created from an existing real USB drive, using this tool:

https://www.alexpage.de/usb-image-tool/

I noticed that in JetKVM, the virtual drive was even called "Lexar xxxxx" which the original USB drive was, so it inherited the properties of that drive as well.

If I mount something like the official Windows 11 image, this doesn't happen.

@Rahzadan commented on GitHub (May 24, 2025): I think it was because I was mounting USB drive image that I created from an existing real USB drive, using this tool: https://www.alexpage.de/usb-image-tool/ I noticed that in JetKVM, the virtual drive was even called "Lexar xxxxx" which the original USB drive was, so it inherited the properties of that drive as well. If I mount something like the official Windows 11 image, this doesn't happen.