Hi there. I’m the owner of (so far) two Huntsman V2 Analogs. I fell for the marketing gimmick of the variable actuators, but that aside, I love them to bits. I use one, and my boyfriend uses another. My keyboard will, at seemingly random, repeat the last dozen keys or so that have been pressed in the last minute. The result is an infuriating situation where the keyboard will repeat windows key presses, enter keystrokes, alt-tab inputs (which makes games more interesting), grenade key (g) inputs (which makes games slightly more interesting), fire-mode selector (x) inputs (which makes games significantly more interesting), and spewing the last few seconds of conscious thoughts I’ve just typed a second time in an instant, trashing whatever sentence I’m trying to formulate. If that happens while I’m typing this, I’ll leave it in as an example.
So it registers as actual inputs, so I immediately suspected hardware, or some kind of conflict. I haven’t noticed if the chroma lights respond to these echoed inputs, and I don’t know if that would tell me anything useful about the issue at hand. The issue has presented through a refresh of windows, driver reinstallation, firmware updates, uninstalls and reinstalls and rollbacks and port changes and every which method of restoring and repairing software I can think of. I caved, and submitted a support ticket with Razer.
They were prompt in getting me set up with a replacement unit which, of course, exhibited the exact same behavior. My PC is a $5,000 wreck from a large pre-build manufacturer who shipped it with an inadequate power supply, so I thought maybe “Hey, something on the mb is probably just shagged, I probably have to replace it, but incase something is only corrupted or something in my SSD, I’ll reinstall my OS”. So I did that, much to my chagrin. Then, my boyfriend, the owner of the second keyboard we’ve purchased, reported that he’s been having the same damn issue.
The issue is confounding, because it happens so randomly that I can’t put a nail in any one particular cause. I think it’s a software conflict somewhere, but I’m not sure how to check precisely what might be throwing the conflict on two entirely different machines. As far as I’m aware, the only applications we both have installed are the big ones that probably millions of people have installed. (Steam, Discord, Synapse 3, etc)
I believe recalling the issue repeating while synapse wasn’t initialized, which would be a hell of a thing, but I wouldn’t swear on it because my mind is shot full of holes, so this is a sort of last hurrah attempt to solve the issue before I just convince myself to tear the 3090 out of my rig and slap it into a new one when my expenses can afford it.
Am I crazy? Does this issue sound familiar to anyone else? Is someone burning toast? Please help.
Thanks bunches!
Huntsman V2 Analog repeating previously pressed keys
Best answer by Cody0866
Razer has sent me an e-mail saying they’ve tracked down the cause of the issue. Due to it’s complexity however, they cannot give me a time frame that a solution will be provided within. 🙃Very premium feel to hear after 2 months of patiently waiting, I’ve got nothing to show for it and a closed support ticket.
New version, 3.8.1231.120811 (20231208). The bug is still there.
Why topic appears with status solved? because we can confirm, this bug still here!!!!
Finally started googling this issue, as I had been battling it for a few months now (when the keyboard worked flawlessly for the 2 years prior). I tried everything I could think of to resolve it… and ended up here in my search. Good to know I’m not alone in this problem. Yet, pretty unsettling to know Razer can’t fix the issue.
Well its a new year and this issue still persists.
Looks like its going to be time for a new keyboard too since Razer cant fix this
Looks like its going to be time for a new keyboard too since Razer cant fix this
This is my exact solution. I placed my pre-order for a different brand keyboard the other day. I’ll live with this flawed Razer keyboard until the other one arrives, but that will be the last Razer keyboard I waste my money on. 5+ months with no resolution, to an issue that wasn’t there prior to whatever they messed up, is inexcusable. Bottom line… they have our money already, it’s an aged / older model keyboard, and I don’t foresee them correcting the issue. They’ve had more than ample time. I’ve probably spent $2k or more on Razer peripherals over the years, dating back to the original ‘99 Boomslang mouse in the tin can. Never had any major issue until this. But when you use the keyboard for work and leisure, and you’re battling this issue several times during the work day, it’s time to toss in the towel. Lesson learned.
Looks like its going to be time for a new keyboard too since Razer cant fix this
This is my exact solution. I placed my pre-order for a different brand keyboard the other day. I’ll live with this flawed Razer keyboard until the other one arrives, but that will be the last Razer keyboard I waste my money on. 5+ months with no resolution, to an issue that wasn’t there prior to whatever they messed up, is inexcusable. Bottom line… they have our money already, it’s an aged / older model keyboard, and I don’t foresee them correcting the issue. They’ve had more than ample time. I’ve probably spent $2k or more on Razer peripherals over the years, dating back to the original ‘99 Boomslang mouse in the tin can. Never had any major issue until this. But when you use the keyboard for work and leisure, and you’re battling this issue several times during the work day, it’s time to toss in the towel. Lesson learned.
I feel the exact same way. Like you I have spent lots on razer gear over the years and am always happy with their hardware but the software doesnt match and I hate how they never even acknowledge issues. I mean this thread says “solved” when it definitely isnt.
I will persist with it for now but next peripheral I buy will not be razer and I will start the slow process of gradually moving away from them.
its a damn shame.
Looks like its going to be time for a new keyboard too since Razer cant fix this
This is my exact solution. I placed my pre-order for a different brand keyboard the other day. I’ll live with this flawed Razer keyboard until the other one arrives, but that will be the last Razer keyboard I waste my money on. 5+ months with no resolution, to an issue that wasn’t there prior to whatever they messed up, is inexcusable. Bottom line… they have our money already, it’s an aged / older model keyboard, and I don’t foresee them correcting the issue. They’ve had more than ample time. I’ve probably spent $2k or more on Razer peripherals over the years, dating back to the original ‘99 Boomslang mouse in the tin can. Never had any major issue until this. But when you use the keyboard for work and leisure, and you’re battling this issue several times during the work day, it’s time to toss in the towel. Lesson learned.
same here!!
made an account for the express purpose of stating that this bug has actively gotten significantly worse each update to the point of needing to turn off synapse when I am using the keyboard for anything other than minor tasks. when the issue first happened it would happen maybe once a day, now it happens at least a dozen times an hour. just writing this the issue has happened 3 times and i now consider synapse completely unusable. absolutely disgusting that razer would let this issue persist for so long, i was skeptical buying a razer keyboard to begin with and i now see that my skepticism was warranted and I will never purchase a razer product again.
I can’t believe this hasn’t been solved in way over 2 years.
At this point, I’m fairly certain the product is flawed on an hardware level and can not be fixed. Razer knows that hence why they keep leading people on forever till the warranty runs out. Even falsely marking unsolved bugs as solved.
If you have a Huntsman V2 Analog and you are still under warranty, SENT IT BACK NOW.
I have waited for years for a fix and I was stupid enough to believe that there would be one eventually. But the harsh reality is that this product was DEAD ON ARRIVAL.
I’m also fairly certain that most if not all Razer Huntsman v2 Analog’s have this issue. But most people don’t bother looking it up when sometimes keys get repeated, nor do they know it’s from the keyboard and not from their operating system or something else.
The Razer Huntsman V2 Analog has been faulty for years and they keep selling it knowing full well it is broken. They should officially apologize and offer everyone a full refund or a different keyboard. But it is Razer so that won’t happen.
I can’t stress this enough - If you still can, GET RID OF IT RIGHT NOW! - My Keyboard literally reposted a handful of words twice during this post.
Censorship at its finest, goob job Razer! 😁
Let’s play a game what comes first, the fix of this product, or my previous message?
Neither, it was a trick question.
Analog v2 was a scam since release. They never fixed synapse and analog v2. They replaced my keyboard with new one and again same. Just dont buy razer. I stopped buying their products after analog v2.
Oh and razer huntsman elite with red switches also have simillar problem. You need to unplug and plug back keyboard to fix it. Good thing retail store refunded my money.
+1Censorship at its finest, goob job Razer! 😁
Let’s play a game what comes first, the fix of this product, or my previous message?
Neither, it was a trick question.
FYI it's not censorship. It's just forum automatic anti spam mechanism, sometimes it flag some posts for approval. None mechanism is ideal.
At this point, I’m fairly certain the product is flawed on an hardware level and can not be fixed.
Surely it can’t be hardware-related if many users report that the keyboard works flawlessly when the Synapse software is turned off?
If the problem only raises its head when Synapse is running, the problem should be solved with the correct software fix. Hopefully Razer care enough to solve this issue.
Its not hardware related, its software only.
I read it here that someone had tested that out and said it so, but also recently I decided to try something myself as they keystroke repeating was getting too much and I didnt want to gamer rage and destroy it. And getting a new, proper keyboard wasnt something I can do right now.
So I downloaded the newer Synapse, the one thats in beta? Synapse 3 I believe?
Annnnnnnnnnnd… it doesnt currently support this keyboard, the Huntsman V2 Analog at all.
So I went into windows keyboard settings and turned up the repeat delay and repeat rate to max and everything on the keyboard has been working fine for me. The media keys work, Ive had no ghosting or keystroke repeats at all.
I cannot control the RGB though, so its just cycling through all the colours as I sit here typing.
So, if you are having to deal with this keyboard, just close synapse, its their software that is causing the keystroke repeating. At least for me anyway. I will say that with the software, typing is a better experience? I think it does help with touch typing and such, but the repeated keystrokes is rage inducing. The software is garbage.
Just waiting for the new synapse 3 beta to update and support this keyboard and the problem comes back and I have to suffer again.
Its not hardware related, its software only.
I read it here that someone had tested that out and said it so, but also recently I decided to try something myself as they keystroke repeating was getting too much and I didnt want to gamer rage and destroy it. And getting a new, proper keyboard wasnt something I can do right now.
So I downloaded the newer Synapse, the one thats in beta? Synapse 3 I believe?
Annnnnnnnnnnd… it doesnt currently support this keyboard, the Huntsman V2 Analog at all.
So I went into windows keyboard settings and turned up the repeat delay and repeat rate to max and everything on the keyboard has been working fine for me. The media keys work, Ive had no ghosting or keystroke repeats at all.
I cannot control the RGB though, so its just cycling through all the colours as I sit here typing.
So, if you are having to deal with this keyboard, just close synapse, its their software that is causing the keystroke repeating. At least for me anyway. I will say that with the software, typing is a better experience? I think it does help with touch typing and such, but the repeated keystrokes is rage inducing. The software is garbage.
Just waiting for the new synapse 3 beta to update and support this keyboard and the problem comes back and I have to suffer again.
I disagree and here is why.
Old Keyboards never had problems with N-Key rollovers and ghosting. This is because they were connected via a PS/2 connector and directly interrupted the CPU for each keystroke.
Nowadays Keyboards run via USB that periodically polls for new data, for example at a rate of 1000Mhz. This however makes it technically impossible to achieve no-ghosting and infinite N-Key rollovers.
However there is a solution, by having an additional chip on the keyboard that stores all the button presses and then sends them out at the next USB poll. This is probably where the fault is if I had to guess because it is the only point that actually stores the data, which gets repeated when the fault happens.
That this works is a combination of Hardware (the Chip) and the software. That they haven’t managed to fix it after so many months makes me believe the fault lies with the chip itself and they attempted to bypass the fault via software fixes that seem to only lessen the effects, depending on the version (but probably introduced new bugs, hence why it seems to be worse now than it was with previous versions).
This chip is also responsible for all the additional features. So if you don’t use Synapse, you don’t use the chip removing all benefits of the “smart” keyboard. Sure you also get rid of the bug but then why even have a Huntsman V2 Analog in the first place and not a cheapo 30$ Keyboard.
You could probably be right, I dont really know all the ins and outs of the hardware and software and am just going off of my experience with this keyboard.
All I know is that the problem didnt exist at all when I first got this keyboard a year or two ago now and then a few weeks to a month before my first post here, which was 3 months ago according to this thread, is when this problem started. And the problem arrived with a synapse update, not sure if they did a firmware update to the keyboard at the same time as I didnt pay attention to what was in the updates back then. Also trying to find patch notes to see what they change appears to be impossible, at least I cant find any patch notes except for when its actually patching itself and tells you.
So, no problems for a long time, suddenly it starts happening, and since then Ive kept an eye on all the patches as they happen to see that they have attempted updates stating that they are for this exact keyboard and nothing has worked at all.
My solution above isnt -the- solution, its just letting me use the keyboard and not get frustrated or angry as I cant just go and throw money at a keyboard right now. Like sure I can get a cheap one, but, I do a lot of typing, so I want to get a good one.
Also just holding onto hope with the new synapse software, that when it does finally support this keyboard, maybe the problem with be fixed. Who knows. I enjoyed the keyboard when it was working properly.
As frustrating as it is that they have marked this clearly still persisting (and frustrating) issue as solved, I too will hold out hope for this new synapse version.
It feels like being gaslighted as this is an issue I noticed and googled when I first got the keyboard over 2 years ago and I could only find one person who was talking about it. But my keyboard had a second issue, which I thought was related, so got a replacement and thought things were working fine for a while. At least we now know its software and can shut down synapse if we want to get some temporary relief, but you’d think for a flagship model, they’d put some extra time and effort into getting this working correctly, so people continue to buy their flagship equipment. as it is, though I’m happy with the quality of the hardware, but the way razer has handled this makes me want to look at other brands for my next keyboard.
Is it only me that very recent Synapse versions didn’t reproduces this problem? I didn’t saw update notes mentioning Huntsman V2 Analog but it suddenly stopped happening on my side after Synapse updates in this year.
My current Synapse version is 3.9.109.11015. Some days passed after update, didn’t saw it yet. The version right before this (can’t remember version, sorry!) was also not showing symptom, but versions in last year was bugged all the time.
I remember that I experienced same problem multiple times per day, until I got an update of Synapse after 1st week of 2024.
Razer Support still repeating that they don’t have ETA and problem is still going on.
Is it only me that very recent Synapse versions didn’t reproduces this problem? I didn’t saw update notes mentioning Huntsman V2 Analog but it suddenly stopped happening on my side after Synapse updates in this year.
My current Synapse version is 3.9.109.11015. Some days passed after update, didn’t saw it yet. The version right before this (can’t remember version, sorry!) was also not showing symptom, but versions in last year was bugged all the time.
I remember that I experienced same problem multiple times per day, until I got an update of Synapse after 1st week of 2024.
Razer Support still repeating that they don’t have ETA and problem is still going on.
I’m on the same version and it’s the worst it’s ever been but hopefully this is a sign of them at least attempting to fix it.
I have been having this bug happen for over 2 years now. I have had two different keyboards, and I update as often as I can. The issue is pretty consistent, usually once or twice a week. But it has caused some embarrassing Slack messages, and some nearly dangerous console commands.
Might have to say goodbye to Razor over this.
I have got the latest Huntsman V2 Analog Firmware (v1.06.00_r2) and the latest Razer Synapse (Version: 20240111).
Unfortunately I’m also still having that issue.
Additonally I have another issue since the latest Razer Synapse Update:
I can’t control the Audio Volume using the Audio Wheel, but I can use the mute button.
That’s why I mostly exit Razer Synapse to make everything work, but then I can’t use my Profiles and RGB Color, it’s so annoying and I really hope for fixes soon.
I have never had any problems with my previous Keyboard which was the Ornata V2…
I personally really love the Huntsman V2 Analog but those issues are actually so annoying.
If anyone got anything new regarding those issues or any fixes etc.
Please let me know!
Thank you!
Hi.Same problem here since November 2023, when I bought the keyboard. Unbelievable that the problem still exists (unwanted keyboard input from the clipboard...passwords, etc. LOL).
Everywhere should be warned against buying something like this (reviews on Amazon, etc.).
I can’t control the Audio Volume using the Audio Wheel, but I can use the mute button.
Contact Cleaner Spray would be fixed.
If the problem not occured when Synapse closed, I’m not sure.
I have the same issue. Latest firmware & Synapse Update.
This trash barely usable - I can’t even type text without it’s being wrecked by this repeating keys bug!
AND THERE STILL IS NO FIX !
But V3 is out already… Not woth it I guess.
Reply
Sign up
Already have an account? Login
Log in with Razer ID to create new threads and earn badges.
LOG INEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.