#keyboard not workin after update and restore also not workin at the last step it says waitin for
1 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!
can you follow the steps below to open device manager and sort by "Device by container"
then find the keyboard and expand the tree and take a picture of the results
Just to check (before this did you unplug the keybaord and hold down the keys?)
if so can you replug the keyboard so it can start up normaly and shows the results
wtf
ok i removed a bluetooth adapter that i bought a year ago and now the led light turned on and its working
thats so weird
Yep driver issue
should be fine and on the latest firmware
okay brother thank you
i love your keyboards by the way!
amazing company
insanely fast support its crazy
My theory
- Keyboard firmware was uploaded
- wootility sent "restart command"
- Keyboard restarted
- on boot it was detected as a new device (we made slight changes to driver structer so this makes this a "New device")
- Windows "Plug in play" detected the "new device" and failed on the driver assignment
- Resulting in current issues
Maybe the related to the Bluetooth adapter (If on same usb-controller)
Atleast that is what i think happened
yes I think so also
definitely the bluetooth adapter fkd things up
thank you andrew
4am spelling....