#Wooting 80HE starts with Capslock ON

1 messages · Page 1 of 1 (latest)

clear inletBOT
#

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!

dusty river
#

That’s not supposed to happen. 3 things I can think of doing. First, of course make sure wootility and your keyboard are both up to date. Second, try a different profile to see if it was just a bug in that profile. Third, share the profiles and paste the profile codes in notepad or something similar and run restore process in wootility. I’m sure one of the staff members may have a better solution, but those are the steps I’d personally take 🤷🏻‍♂️

misty hemlock
#

Thank you!
Keyboard and Wootility are updated

this is the profile
59eb3d56a1354fd21b572c39617926527627

dusty river
#

If you do restore process, just copy that profile code and it’ll be easier to just import it back in instead of having to redo it all.

regal moat
#

This is not the keyboard, this is your operating system.

misty hemlock
#

I was thinking it'd be the keyboard as the previous one wasn't behaving this way

regal moat
misty hemlock
#

I just tried restarting a couple times and the issue seems like it fixed itself so.. I'll delete the post.
Thanks everyone for the help so far in any case