MatthewDoerksen

Apologies for reviving a dead thread but here's what I found (and it solved my issue). I encountered this same issue (same keyboard, also on a Win10 VM I use for gaming) recently as I was working on some scripts to auto-attach devices back to particular VMs (as I have a mouse + keyboard on a hub which I plug/unplug for use with a laptop). I started looking around and found this on the Corsair support page (https://www.corsair.com/us/en/Categories/Products/Keyboards/StandardGamingKeyboards/STRAFE-Mechanical-Gaming-Keyboard-—-CHERRY®-MX-Red/p/CH-9000088-NA): There are two USB plugs for my keyboard. Which one should I connect? For USB 3.0: Use one connector (the one with the keyboard icon) when connecting via USB 3.0 Connecting via USB 2.0 Use both connectors when using USB 2.0. Plug in the connector with the two arrows icon first, and the connector with the keyboard icon second. I was using a USB3 hub and had plugged both cables into it. Once I disconnected the arrow one, the keyboard finally became usable.

I have yet to verify exactly what caused it but I had this same error recently and here's what fixed it: switching the device to a new USB port (preferably on a different USB controller). In my case I had a keyboard and mouse which would light up but not work on the GUI login screen (in addition to the UPS). I suspect either the ports on the motherboard are dying/fried since before switching ports my UPS would also randomly disconnect or, the controller being used isn't initialized early enough (UNRAID or BIOS issue?) for it to get picked up correctly and attach the device.

I have yet to verify exactly what caused it but I had this same error recently and here's what fixed it: switching the device to a new USB port (preferably on a different USB controller). In my case I had a keyboard and mouse which would light up but not work on the GUI login screen (in addition to the UPS). I suspect either the ports on the motherboard are dying/fried since before switching ports my UPS would also randomly disconnect or, the controller being used isn't initialized early enough (UNRAID or BIOS issue?) for it to get picked up correctly and attach the device.

I'm also having this issue, I can however still telnet to the box (but of course losing the GUI makes administration more difficult). It also happens in safe mode so it shouldn't be related to any configuration or plugins I have installed. System Specs: Unraid OS 6.3.3 AMD Ryzen 1700X ASUS X370 Prime MB 32GB G. SKILL TridentZ 2133MHz DDR4 AMD Radeon R7 240 (for unraid) AMD Radeon R9 Fury (for VM) Logs can be provided upon request.