Huntsman V2 Analog - Single Key Double Entry | Razer Insider
Skip to main content

I believe this issue started within the last few weeks, but it’s become extremely bothersome (to the point where I am close to moving to a new brand of peripherals despite being a longtime Razer enthusiast)

I’m using a Huntsman V2 Analog and have the latest firmware/drivers & Synapse 3 Installed. Windows 11.

 

I have one, and only one, key - “G” - that constantly registers a double press when typing.

Example: “Havingg a ggood time workingg today” - in normal usage I must remove the extra “g” each time I use that key. It’s extremely annoying to the point of being almost unusable.

Sometimes the issue will show as a delayed double entry - usually when I’m typing a sentence quickly.

Example: “Havingg a gogod time” (the “g” registered a 2nd time after I had already moved on to entering “o”)

I have dusted, removed the cap and inspected the switch (I did not see any damage or debris). I have tried disabling Synapse, but that makes the issue worse (it registers 4 presses instead of 2). I’ve tried increasing the actuation required - I raised it higher and higher and eventually just made it to a point where my strokes wouldn’t register at all without a deliberately long press… and even then, it still makes the double entry.

I’ve read about similar issues, but since my issue is only a single key that seems to be malfunctioning I can’t tell if it is the same problem. Is there another fix to try? Razer, you have a long-time customer that is on the ropes here.

 

Another odd thing - when I hold down any other key, it produces a long repeat of the entry 

Example: I hold down “J” and I get “jjjjjjjjjjjjjjjjjjjjjjjjj” until I let up on the key

 

When I hold down “G”, I get “g” (it registers the press once I let up on the key, but it does not register before then)


Update: I fixed the issue by uninstalling Razer Synapse Beta & Chroma Beta, which were still installed alongside Synapse 3. I also removed the keycap to the “G” key again and after fiddling with the switch, re-attached the keycap. Now I can type “g” again and the issue seems resolved.


Reply