60 HE V2 Unresponsive/Bricked

[fickle ravine]

Hey all, looking to get some help here.

I recently purchased the Wooting Detachable USB-C Coiled/Straight Cable Set for my new 60 HE V2, everything was going fine for a few hours until the LEDs went out and the keyboard went unresponsive. I've tried restarting my pc and swapping cables, and no dice.

I've tried plugging directly into my pc, into a usb hub, and into a laptop, but I'm still unable to get it back on again. Is there any reset switch on the the board I can hit or combo of keys to reset it?

[tardy venture]

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

• Cancel an order?
• Return/Refund an order?
• Get assistance with placing an order?
• Change the items in your order?
• Change your shipping address to a different country?
• Return a recent purchase?
• Get warranty support?

All of these types of requests need to be made via the Wooting Support Wizard!

[fickle ravine]

to add to this, pressing backspace + fn when plugging in the board shows me the blue LEDs but the device is stuck in Device Descriptor Request Failed

[fickle ravine]

On the desktop version of Wootility it times out trying to find the bootloader

[teal goblet]

Can you go in Device Manager, click 'View' > 'Devices by container', then take a screenshot

[fickle ravine]

Here's what it looks like without the keyboard plugged in vs with the keyboard plugged in

Previously I did have a Wooting Restore listed along side of the Unknown USB device, but it was greyed out so I cleared it out as per the instructions on the site

[teal goblet]

Have you tried different USB port? preferably one farther away from the current one.
Also you mentioned that you recently got the coiled cable from Wooting, can you try using the included cable instead and see if that helps?
If the issue persists, flush the drivers. Follow this guide https://help.wooting.io/article/173-how-to-flush-all-dead-registry-entries

If it still says "Unknown USB Device", this may indicate possible port damage. I'd recommend removing the module from the case, taking pictures of the USB port, and then creating a support ticket here https://support.wooting.io

[fickle ravine]

Yeah, I've tried seperate USB ports on my desktop along with on my laptop. So far I've used the coiled cable, the cable it came with, and a third party one to no luck. I've flushed everything from the registry and ever used USBDeview to clear out every device before restarting the PC.

I've opened a ticket already but it seems pretty clear the device isn't enumerating properly. I was hoping since maybe I can see the restore LED's light up there'd be some workaround but it doesn't appear to be the case, the keyboard was working fine until I tried the coiled cable so I'm worried it got fried by it.

The wootility logs had the following last night:

[2026-02-16T23:59:48.923Z] [debug] Setting in focus to  false
[2026-02-17T00:00:05.301Z] [debug] Setting is updating to  false
[2026-02-17T00:00:05.302Z] [error] Error: Timed out finding bootloader```

[plush stirrup]

The log files are a bit short so can't really say (i assume no detection of device from images of device manager)

For references
Unknown USB Device (Device Descriptor Request Failed)

This tends to indicate that one of the data lines (Data+ or Data-) is disconnected or unstable, causing the system to detect that a device is connected but unable to request the device descriptor to determine what type of device it is, resulting in this error.

As you have ruled out the system/cable as the cause this leaves:

• The port internals may be damaged or have something inside preventing a proper connection.
• The port may be disconnecting from the PCB.
• There may be some debris on the pins of the PCB (as this is the 60HE v2, this seems unlikely).

i would check the Port inside and remove the Module and inspect the area incase for anything strange (hopfully it is a easy fix) otherwise best to send a ticket