#Wooting 80HE not responding

1 messages · Page 1 of 1 (latest)

covert nebula
#

Hello; I own the Wooting 80HE and it's been sitting in a case for the last 6 months or so. I plugged it into my PC and Laptop and it won't respond. I've attempted different cables though when I hold the top right button and bottom right the LED do turn blue.

wanton cragBOT
# covert nebula Hello; I own the Wooting 80HE and it's been sitting in a case for the last 6 mon...

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...

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

burnt garden
covert nebula
#

Wooting 80HE not enumerating in Windows (restore mode works, no USB detection)

Looking for deeper troubleshooting before I go full RMA.

Issue:
My Wooting 80HE will enter restore mode correctly (top-right + bottom-right keys light up blue), but the PC does not detect it at all. It never shows up as “Wooting Restore” or any USB device.

Key detail:
This happens across multiple systems, so it doesn’t seem OS-specific.


What I’ve tested:

  • Multiple USB ports (rear motherboard, no hubs)

  • Separate laptop (same behavior)

  • 3 known data-capable USB-C cables

  • Restore mode triggered multiple times (consistent blue indicators)

  • Device Manager monitored live during plug/unplug:

    • No “Wooting Restore”
    • No unknown device
    • No enumeration event at all
  • Wootility versions tested:

    • Web (.io)
    • Web Beta
    • Desktop
    • 5.2.5
    • 5.6 v3 beta
  • Updated runtime/SDK to 9.1


Observed behavior:

  • Board powers and enters restore mode visually
  • No USB enumeration event (not even descriptor failure)
  • Wootility cannot see the device in any mode

My current theory:
This seems like a failure before USB enumeration—possibly:

  • Bootloader not actually presenting over USB despite LED confirmation
  • USB controller/ESD damage
  • Data lines not initializing even though power is present

Questions:

  1. Has anyone seen a case where restore mode LEDs work but the device never enumerates?
  2. Is there any way to force a deeper bootloader reset beyond the standard key combo?
  3. Would this align with the early 80HE ESD-related issues?
  4. Is there anything else worth testing before assuming hardware failure?

Appreciate any insight—trying to confirm whether this is 100% hardware before opening a ticket/RMA.

cedar sage
# covert nebula **Wooting 80HE not enumerating in Windows (restore mode works, no USB detection)...

The mention of the keyboard being able to enter "Wooting restore," indicated by the blue lights but not being detected by the system, tends to be a good indicator that the keyboard is working but can’t communicate with the system, which can be caused if the two wires are not connected ("Data +" | "Data -").

I recommend trying this guide and pushing in the JST connector at both ends to see if this resolves the problem.
https://help.wooting.io/article/333-my-80he-flashes-or-disconnects-when-i-type

If there is no change, it could be the result of a very rare issue where a specific component is faulty or floating.

covert nebula
covert nebula
#

So, it looked like that fixed the issue. I also updated the firmware and that fixed another issue.

#

Thank you very much for the suggestion that fixed the issue.