#Keyboard randomly does not start on power-up / disconnects after use

1 messages · Page 1 of 1 (latest)

fleet thicket
#

Hi, I've been lately experiencing a problem with my Wooting two HE where it either does not start up properly during computer power-up. I.e. some keys work, some don't and the keyboard profile reverts to default.

Starting the Wootility desktop tool seems to help. If I recall correctly I have also had occasions where the keyboard acts similarly after start-up, but lately the more occurring problem is during PC start-up. I have tried different USB-ports to no avail.

Wootility says that my drivers on the keyboard are up to date and I have the latest Wootility patch installed.

On a possibly related side-note, the keyboard seemed to worked perfectly without any problems before I decided to install Wootility. Wanted a faster way to access my keyboard settings. I am not sure if the two are related or just coincidence.

zealous lightBOT
#

Thanks for posting your support request!

Please note, the support center is only for community-based support with technical troubleshooting and general questions.

For official Wooting Customer Support, please use the Contact Us button on the Wooting Hub or email your request to social@wooting.io
note: use the email address associated with your order for fastest resolution

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, change/confirm 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!
https://hub.wooting.io

last cedar
fleet thicket
last cedar
arctic marten
#

First thing I can think of to check if the keys activate is to use the "RGB Fx" - "RT Display." It will showcase when the key is

  • Activated (Green)
  • Released (Red).
    Test when the computer doesn't recognize the key being pressed, then look at the RGB effect to see if it detects the press.

Also, another thing to check would be the profile that is in use. Make sure that it has the appropriate binds. or that gamepads binds are not bound to same key

fleet thicket