When I was updating my device I unintentionally unregistered and thought that factory resetting it before reinstalling it on the web would work, it didn't. I tried all your steps and I know it's not the usb cable because when I tried using a different one, it didn't work. Using different ports did nothing, even going through the process of flushing all dead registry entries didn't even work, I think it made it worse.
#I think I unintentially bricked my wooting UwU and the website won't let me send in a ticket
9 messages · Page 1 of 1 (latest)
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!
Also, when I was trying to use your support website it gave me this error code: 094f18593105478ab34f5a7d59d8016d
Tried it on another computer? Does it connect to the PC at all (sound/showing up in device manager)?
It does make a noise but doesn't show up in device manager. I did also try to connect it to my MacBook it was the same issue.
When you check device manager, do you have it set to show devices per container?
Tried that? ^
Now I did and it worked