My wooting 80he key stucked (Solved,The solution is write.)

[rapid stratus]

As mentioned in the subject, I’ve encountered a key stuck issue with my keyboard. When a key gets stuck, pressing it again will stop the character movement. However, unless pressed, the key remains endlessly inputting commands.

Additionally, I’m unable to type an underscore (_). Using PowerToys on Windows 11, I found that the key assigned to input an underscore on JIS-layout keyboards is showing as unassigned. This indicates that the key itself is not functioning.

I believe both of these issues are related to bugs in Wootility. It seems the keyboard is not recognizing settings configured in Wootility.

Could you please provide a solution?

I contacted Wooting via email, but it’s been over two weeks, and I haven’t received a response yet.

[tawdry robin]

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!

[spiral hare]

I experience exactly the same issue with charachter moving endlessly unless the key is pressed again.

[rapid stratus]

I’m relieved to know that someone else is experiencing the same bug.
Just one question: in your case, when does this bug occur? During gameplay? Or at any time?

[spiral hare]

Gameplay only, it's always movement keys so wasd. I do feel that it happens when 2 keys are being pressed at the same time e.g. jump + wasd or ctrl + wasd, but cannot be sure that.

[rapid stratus]

it’s almost exactly the same issue.The keys respond when pressed simultaneously.In my case, this happened with all keys, not just WASD.
I’ve tried all the solutions I could find online, but nothing works. Haha.

[amber gyro]

ssame issue

[spiral hare]

I assume it depends on what you play, in FPS it's mostly WASD,CTRL & JUMP that you are going to be pressing at the same time, but yeah. The character keeps on going until I press the same key again, if I press a different one e.g. let's say A is stuck, if I press D, it will counter the movement and the character will just stay in place, but once I let go of D, the character goes back to moving left, so A is still stuck.

[rapid stratus]

Exactly, that’s how I understand it too. I was playing Minecraft, and at first, the bug only occurred with WASD, so I thought it might be an SOCD issue to prevent character locking. But eventually, the same bug started happening with other keys as well. I suspect it’s a problem where the "key released" signal isn’t being processed properly. But honestly, the biggest issue is that Wooting isn’t addressing this problem at all.

[spiral hare]

@rapid stratus @amber gyro Would you be able to dm me with a screenshot of your system tray or post it here please... I have an idea, but not sure.

[rapid stratus]

Copy that. Just a minute.

Is this okay?

[spiral hare]

Yeah... as I thought....

[rapid stratus]

Did you notice something?

[spiral hare]

So... what I did is I tried to check what's happening when I'm not playing any games and I'm just pressing lots of WASD, CTRL SHIFT and SPACE... the only thing that happened is.... when you press the key first and then hold it and press space afterward and hold it at the same time, it enables PowerToys Quick Accent thing, so it basically let's you select kind of like "special characters".

Just go to your browser and e.g. press and hold S, then at the same time press and hold space and it will start cycling through special characters like $ etc.

While this does not really cause the key to get stuck, it pointed me in the PowerToys direction. It seems some people reported PowerToys to cause keys to stuck. So far I have disabled running it on StartUp and closed it and will check if it's that and I would recommend you the same as you have PowerToys running.

[amber gyro]

I’m playing geometry dash so yeah… probably

[rapid stratus]

I see. I'll try turning off PowerToys as well. Thank you for suggesting a solution. However, I have one concern—I've only been using PowerToys since about the day before yesterday, but this bug has been around since before that. Anyway, I'll give it a try first. Thanks again.

[spiral hare]

I assume you have Sticky Keys disabled in Ease Of Access thing or whatever it is called.

[rapid stratus]

Yes, I have indeed turned off Sticky Keys.

[spiral hare]

Well worth a try, report back please.

[rapid stratus]

Please give me a little time.

Hmm, it didn’t work. Am I doing something wrong...?

"I'm certain that PowerToys is turned off, but still...

[spiral hare]

What do you mean it didnt work?

As in.. it's still happening?

[rapid stratus]

yes

[spiral hare]

well I guess in this case it's not that

[rapid stratus]

Did turning off PowerToys fix the issue for you?

Hmm, I might be doing something wrong, so I’ll try a few different things. This might take some time.

[spiral hare]

No idea yet, I only played one game and it didn't happen, but it's not like it's happening every single game.

[rapid stratus]

Thank you. I'll try uninstalling PowerToys for now.

[amber gyro]

Nope

I have a feeling it’s an issue with low end devices

Because I brought my 80he on a small trip with my not so good laptop and that’s when the issues started

[rapid stratus]

I see,
your experience reminded me of something. It’s hard to explain, but you know how they say that if one component in a PC breaks, it can affect and potentially damage other components?
In my case, I’m wondering if that might be related. Before my current PC, I used the Wooting 80HE on an older, unstable, and almost broken PC. I experienced a bug back then, and while I wouldn’t say the Wooting 80HE was damaged, it’s possible it was affected in some way.
That said, if that were the only issue, resetting it should’ve fixed it, right? But with the Wooting, I feel like once a bug occurs, the PCB might misinterpret it as the correct behavior and store it in memory.
Of course, this is a bit of a leap in logic, but it’s just something I’ve been thinking about.

In my case, the PC’s performance isn’t low, and the bug existed even before I started using PowerToys. So, while the symptoms might be the same, the cause could be slightly different for me.

[amber gyro]

I know what you mean

[amber gyro]

@rapid stratus @spiral hare

The issue has seemed to go away for me (strange)

Maybe it was the different usb port

Idk

I’ll try to replicate it again, I feel like my theory of the laptop being the issue and not the laptop was correct

I just don’t want to issue to pop up again

[rapid stratus]

I see, so using a different USB port might be the cause. That certainly applies to me as well. Please let me know the results if you can reproduce it again. There's nothing more I can do at this point.

[rapid stratus]

@amber gyro @spiral hare

I received a reply from Wooting, and they decided to proceed with a replacement.
I tried various solutions, but nothing worked.

[amber gyro]

I see

I would if the issue gets worse for me if I could get it replaced

[spiral hare]

let us know if it fixes the issue for you

[rapid stratus]

@amber gyro @spiral hare

The replacement hasn’t been completed yet, but I managed to fix the keyboard after trying various things.
I believe the issue was related to Wootility, Windows Sandbox, and the registry editor (regedit).

[amber gyro]

How

[rapid stratus]

First of all, this is just a method I tried that worked for me, so it may not work for everyone.

As a prerequisite, I had Wootility and the Windows 11 built-in feature Sandbox installed. Most people probably don’t have Sandbox installed.

Step 1: Remove all Wooting-related entries from the Device Manager and Registry.

Refer to this site: https://help.wooting.io/article/173-how-to-flush-all-dead-registry-entries. Follow the instructions to delete everything related to Wooting.

Step 2: Completely uninstall Wootility and wootomation.

Open the settings menu by pressing Windows Key + I. Navigate to Apps → Installed Apps → Wootility, wootomation and uninstall it.

Then, go back to Apps and check the Startup section. Depending on your system, you may find an entry showing where Wootility, wootomation is stored in the Registry. If it’s not listed, you’ll need to locate it manually.

Look in one of the following locations:
• HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
• HKEY_CURRENT_USER\Software\Wow6432Node

Delete any entries labeled “Wootility , wootomation”

There is one more place to check:
• HKEY_LOCAL_MACHINE\Software\WOW6432Node

Delete any Wootility-related entries here as well. and wootomation.

It’s also a good idea to uninstall the game where the bug occurred. However, if your bug occurs in games like Apex, Valorant, or CS:GO, recovery may be impossible at this point. This is because wooting conflicts with the anti-cheat systems in these games.

Final Note:

There are still more steps to take, but it’s late at night in my country. I apologize, but I’ll provide the rest tomorrow.

Important: Modifying the Registry can potentially damage your PC, so please proceed at your own risk. It’s highly recommended to back up your Registry before making any changes.

Sorry for the long explanation.

The most important thing is to completely remove everything related to the keyboard.

Honestly, I don’t know the root cause. It seems to be conflicting with something.

Please contact Wooting and request the link to the Analog Monitor. It should help you identify what’s interfering with the keyboard.

[spiral hare]

To be honest... I don't know if you experienced the same when starting using the keyboard, but I had an issue with initializing it. It took many attempts due to losing connection or something like that, I just wasn't able to allow the browser to connect as it seemed like the request has expired before the keyboard showed up on the device list to approve if that makes sense...

so I guess it could mess up registry or there's more than one keyboard device now... "working in the background"

That's me speaking out of my ass tho as I don't know if that is how it works.

[rapid stratus]

The issue seems to be caused by keyboard virtualization.

When virtualization is enabled, the keyboard appears to be running in the background.

[rapid stratus]

Here are the steps to resolve the issue:
1. Uninstalling Applications:
Press Windows Key + R, type Control, and hit Enter.
Navigate to Programs → Uninstall a program → select and uninstall the relevant application.
2. Disabling Virtualization Features:
Go back to Programs and select Turn Windows features on or off.
Uncheck the following options:
• Virtual Machine Platform
• Windows Sandbox
• Windows Hypervisor Platform
Once done, restart your PC.

At this point, the bug where keys remain indefinitely pressed disappeared for me.

Registry Information:
In my previous explanation about the registry, I might have missed mentioning that entries related to WOW6432 can often be found in the Uninstall section and should be removed there. After further testing, I confirmed that Wootomation was the root cause. However, this time, I couldn’t locate the exact registry entries for Wootomation. That said, in most cases, uninstalling the application via the Control Panel should also clean the registry.

Important Note:
Simply uninstalling the application from the Windows Settings → Apps section is not enough. I had to manually delete the Wootomation startup entries from the Run section in the registry.

Possible Additional Cause:
Do you have the 32-bit version of Java installed? I believe this might be a major contributing factor.

For Future Reference:
Here are the steps for anyone encountering this issue in the future:
• Remove all keyboard-related application startup entries from the registry.
• Uninstall tools like Sandbox and Powertoys.

If you have any questions, feel free to ask.

[fast stone]

How long did it take for you until you received a reply? It's been now exactly 1 month for me and still no reply... I get there's xmas and everything in between, but from expected 2 weeks to one month...

[rapid stratus]

I waited a month after sending my first email, but I still haven’t received a reply. On the other hand, I received a response to another email I sent within three weeks.

The person who assisted me not only responded via email but also handled inquiries on Discord. From what I observed, there doesn’t seem to be a fixed schedule for responses. It feels more like volunteers are replying, though that’s just an impression—I’m sure they’re not actual volunteers. That being said, the response speed likely depends on their availability.

[fast stone]

@rapid stratus I'm wondering about one thing... you wrote "Step 2: Completely uninstall Wootility and wootomation." ... idk if it's different on Win 11, I'm on Win 10... but one of the main features of the Wooting KBs is that you don't need to install anything... for Wootility I access through the browser, and I haven't seen anything that I'm aware of by the name of wootomation... could you please clarify this?

For now I disabled everything related to Hyper-V

[tawny urchin]

Wootility is offered as installable apps.

[fast stone]

Ah thanks! I'll try without Hyper-V for now, and check the registry if it keeps on happening (please don't 🙏 )

[formal scaffold]

That issue is definitely not HyperV/Windows sandbox (which uhh requires HyperV enabled) or PowerToys related. I use these pieces of software daily, even while having HyperV VM in background and I never had any issues with my 80HE (neither with or without Tachyon mode, but always with pooling rate set to 8kHz). PowerToys are also used in my daily routine (without keyboard stuff enabled). I keep my 80HE connected with stock cable & provided USB-C -> USB-A adapter. I must say that I'm also on Dev channel of windows 11 insider (build 26120.2705). As much as we can blame microsoft for stupid issues, they didn't do anything related to HyperV device emulation in last years...

hardware:
Intel i7-12700KF
AMD RX 7800XT
GIGABYTE B760 GAMING X DDR4 / 48GB RAM

[fast stone]

Thanks for the input... if that's the case and at this point I think I've been "blessed" by RNGesus with a faulty unit... never had this issue with any of the other 3 Logitech keyboards I had before

Will have to try on a different PC for a while

maybe it's the PC... maybe it's a Win 10 thing... I'm lost

[formal scaffold]

There probably is an explanation for it, but windows itself can be at fault in so many ways that it's just sometimes hard to find an issue

[formal scaffold]

oh, and yubikeys are definitely not at fault, they work on usb 1.1 anyway so xD

i always keep mine plugged in

[fast stone]

Yeah... I just confirmed, it hasn't to do with the Hyper-V features ...

[spiral hare]

I haven't had the issue happen to me since I stopped running PowerToys... that obviously doesn't mean that PowerToys was a direct issue but... yeah idk.

[fast stone]

I uninstalled PowerToys, so, not the issue for me

[formal scaffold]

did you have every powertoys feature enabled tho?

or only like the ones you needed

that's what i have enabled

[spiral hare]

I wasn't really using it anyway, I can turn it on and see

quite a lot of shit on, but as I said... I wasn't even using it, it was just sitting in the background

[formal scaffold]

could've been keyboard manager related

[formal scaffold]

yeah then definitely no need to keep it on

[spiral hare]

yeah, in the free time I may try to turn it back on just to see if the issue happens again

but again, it's been proven that it isn't THE ultimate issue here given disabling it helped me, but not other people...so I think there is SOMETHING, but it doesn't have to be the same thing for everyone

[formal scaffold]

It definitely is one issue, but trying multiple things at once and somehow getting it to work doesn't help narrowing it

[spiral hare]

I don't think anyone here tried it all at once tbh, in fact @fast stone seems to be taking one step at a time to try and figure out what the cause is, it's just everytime he tries, the issue ends up coming back.

[formal scaffold]

I have noticed, yeah

[spiral hare]

I checked the virtualization thing, but I don't even have it on, so that's not the one for me.

[formal scaffold]

I just wanted to debunk that it's HyperV/PowerToys issue 😇

If it doesn't happen on another hardware, then it must be host related

[rapid stratus]

I suspect the issue with PowerToys arises when using the Keyboard Manager feature. I had the Keyboard Manager enabled as well.

[formal scaffold]

Could be. I disable every feature I don't use. If that's the case, it would be cool to raise the issue on powertoy's github repo about it

[rapid stratus]

Wootomation is also an official application for creating macros. Both @spiral hare and I experienced issues potentially caused by virtualization and keyboard input-related settings. In @spiral hare ’s case, the issue arose while using PowerToys, while in my case, it was linked to Wootomation. That’s why your mention of YubiKey caught my attention—it seems entirely unique in this context.

I haven’t had the chance to read through all the updates on this thread, but as @spiral hare mentioned, we haven’t tested every possible solution. Could it be that recurring issues are arising because multiple solutions are being tried simultaneously?

[spiral hare]

Ok... so in my case I can confirm it's related to PowerToys, not sure which component tho. It took only a few tries to reproduce the stuck movement keys once I reenabled PowerToys. I tried disabling KeyboardManager, but I was still able to reproduce it, turned PowerToys off and cannot reproduce it anymore.

or to say it differently... whatever happens when PowerToys is on, possibly affects something else within my host that triggers this, either way... I think it's not related to the keyboard itself

[rapid stratus]

Exactly, what I’ve been trying to say is that it’s not Powertoys or Wootomation themselves that are the problem, but rather that they affect something else, which ultimately impacts the keyboard. That’s why my solution hasn’t really been a root cause fix either.

My wooting 80he key stucked (Solved,The solution is write.)

[rapid stratus]

The issue has reoccurred! I think I might have figured out the cause. Maybe, maybe...

I have a question for everyone: which brand of motherboard are you using? I’m using MSI!

[spiral hare]

Not msi 🙂

ASRock or Asus

[rapid stratus]

Ah… I see. Thank you.
I was wrong in my thinking. Back to square one then! 😂

[fast stone]

I'm on MSI, too

Z590-A PRO

@rapid stratus does your issue only happen while gaming? It appears to occur way less frequently than in my case (even if mine still can take hours to occur)

In my case it also happens simply while typing

[fast stone]

@spiral hare are you also still having random issues or did yours get solved?

[spiral hare]

mine got resolved I would say

[fast stone]

Lucky you 😆 glad for you though. It was related to powertoys?

[rapid stratus]

The initial issue occurred only during gameplay (consistently). However, recently, the bug reappeared and started happening all the time. That said, the bug during typing was different—it was an issue where certain keys wouldn’t respond at all.

Based on your earlier analysis, I thought the conflict might have been caused by MSI Center, but it seems that wasn’t the case.

By the way, I’ve resolved all the bugs. As of now, neither typing nor gaming triggers any issues.

[fast stone]

What did you do to solve it?

[rapid stratus]

Basically, it’s as I mentioned before. #1319475549906931732 message However, I personally feel that it’s better not to use the keyboard restoration feature in Wootility. Every time I tried it, the situation worsened. Honestly, I’m not even sure how I managed to fix it this time. I’m sorry about that.

[spiral hare]

i believe so, but who knows

[fast stone]

Ah, alright. In my case that didn't apply since I hadn't wootility or wootomation (wooting doesn't make it easy with the names xD) installed.

[fast stone]

As long as it doesn't happen again...

[rapid stratus]

I think the best choice is not to install it at all.
That said, not being able to pinpoint the cause is starting to get a bit frustrating—it’s almost funny!

[rapid stratus]

Hmm, today I tested on an entirely new PC with only Wootomation installed (using Wootility via the web) and no other software, but the exact same issue occurred.

What I’ve realized from this is:
1. Wootomation itself isn’t the problem (especially considering no other similar reports have been made about it).
2. Wootomation isn’t affecting something else that’s ultimately impacting the keyboard.

Could it be an issue with the hardware components…?

[fast stone]

It sounds a bit like the random issue I was having, just that in your case it seems to be happening even less frequently. Although it's odd that it's happening on a different PC. Is that PC connected to the same outlet where your original PC is/was connected? Do you have your cable near other cables or has it loops somewhere? I know all of this is quite far fetched, but so are these random issues.

Can you please remind me of what it is exactly that you are experiencing? Like, is it always the same behaviour?

[rapid stratus]

Hmm, I’m not sure where to start, but I do know the solution to this issue—or rather, I did know it.

The first bug that occurred was that keys would get stuck, but only while gaming. I managed to fix this, but when I tried to return to the same conditions, the issue started happening outside of games as well. This time, either simultaneous key presses wouldn’t register at all, or different keys would respond instead.

The reason you might think my issue occurs less frequently is because I already know how to fix it. The first time, it wasn’t intentional, but from the second time onward, I deliberately tried to reproduce it. And sure enough, the same bug occurred, along with an additional issue where some keys wouldn’t register at all.

When I tested on another PC, none of the possibilities you mentioned applied. They’re currently working on a software fix, so I haven’t done anything in the meantime. That’s also why I haven’t been active in the community for a while, and now I’m struggling to catch up.

Let me know if anything is unclear, and I’ll respond again.

I installed Wootomation on another PC to test it, and the bug occurred again. It seems to be a compatibility issue between Wootomation and the keyboard itself. However, since no one else has reported bugs with Wootomation, I’m starting to think it might be a component issue.

I know how to check for component defects, but I just don’t feel motivated to do it. Either way, I’ll wait for a Wootomation update.

[fast stone]

What do you need Wootomation for? Just wondering.

[rapid stratus]

It is necessary for creating macros. There are plenty of third-party applications available for macro creation, but they are not the best choice. There are various reasons for this, but I will omit them.

[plain vessel]

There are reported bugs in Wootomation, but I don't know if I've heard of this specific issue. Wootomation is currently not in development tho so if you're waiting for an update you might wait forever

[rapid stratus]

I understand that there are bug reports for Wootamation itself, and that is to be expected. Since this is my ticket, I summarized it based on my bug and noted that it has not been reported in Wootamation. I won’t offer any suggestions about the current status of the software team here, but I am aware of it. I don’t know whether any fixes are being made, nor do I particularly care.

It seems like you are related to the software team, but has the bug I found not been shared? I know the reason why updates might never be made.

[plain vessel]

I don't work for Wooting no, but I have been following the discussions about Wootomation here on the Discord. This is the most information I've seen about it #1301320998209196052 message and the latest updates to it was almost a year ago.

You did mention this in your message: "They’re currently working on a software fix, so I haven’t done anything in the meantime"
have they mentioned working on a firmware or Wootomation fix for the issue?

Just wanted to mention the status of Wootomation so you're not waiting on a fix for it that might not come

[rapid stratus]

I have had many conversations with the Wooting team via email. If you’re not related to the Wooting team, I can’t share more details, but I just want to let you know that Wootamation is currently taking quite a bit of time, and they are “working on a fix.” I apologize, but I am quite frustrated and no longer wish to discuss the Wooting bugs. From my perspective, it’s strange that there are so many bugs with a keyboard. My anger might have been projected onto you, and I apologize for that.

[tawny urchin]

Wootomation was an intern project that isn't currently being actively developed. We're looking at a longterm alternative.