#Command error 3
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!
I told him to open a support ticket but I guess this is also worth a shot?
Tell your friend to restore using a different cable and motherboard USB port
He has tried it and same error
In case any background software is interfering, disable all background applications, reconnect the keyboard, and try restoring again
Has your friend tried to mess with Zadig software? AI loves to recommend it when similar issues occur, and it almost always makes things worse
He woke up and tried to update his keyboard and this was the message
He hasn't used Zadig or whatever that is
He has sent a support ticket, thank you for your help @undone leaf non the less, I know wooting has an amazing support team 🙏
https://help.wooting.io/article/173-how-to-flush-all-dead-registry-entries tell your friend to follow the article
Sometimes even after following this guide Issue - Wootility doesn't detect the Wooting the Wootility still can not detect the keyboard, this can be because of d
He is doing it rn, sec
Same error code @lilac turtle
Let me get you the einsten that broke his keyboard here
@meager canopy
Can you go in Device Manager, click on View > Devices by container, then expand Wooting Restore and take a screenshot
He is still in the 10minute wait period
The USB Keyboard above is a office keyboard as he can't even use his wooting
fixed
Hey sorry for the late response. Glad it's fixed, who I would like to know how you fixed it? 
i was doing the restore the wrong way, its on me lol i was kinda stupid
thanks though
