HUNTSMAN MINI - partial working

Oh my god, we have the exact same issue! I bought my Huntsman Mini last week. It was working fine, then all of a sudden this issue popped up. Either we have a faulty batch, or the problem is something like Synapse 3 or the keyboard's drivers. Maybe they updated this week and we just realized. I've disabled auto-updates, just in case, but the damage is done. I don't think I can rollback. I've been in contact with Razer support in another website, I'll link this thread to them. Maybe seeing two different people with the same issue will help them figure this out.

i have the same problem, i will be following. please wright if you get a solution

Okay, this could be a coincidence. But I'd recommend, first, to check out if your Synapse 3 has a new update today. If it does, download, install, reboot. Try the keyboard again. Now, this is what worked for me: If you bought the Huntsman Mini recently, you might already have an older Razer keyboard laying around. In my case, I had my Ornata Chroma, which I had put away this week. Since I had given up on my Huntsman Mini (it went completely "nuts" yesterday, with all keys behaving completely random and erratic), I took the Ornata back out and plugged it. As expected, the Ornata worked flawlessly. Synapse 3 asked me to download a new update for the Ornata keyboard, since I had performed a couple of clean installs trying to fix this issue with the Huntsman Mini. This is why I'm not sure if there has been an update or if it was a coincidence. Today I plugged in my Huntsman Mini again, because I'm stubborn and didn't want to give up on it. I kept the Ornata plugged in, in case the Huntsman Mini went "nuts" again... And the Huntsman Mini is behaving completely normal... I'm writing this message with it. The keys are not in any way acting up. I unplugged my Ornata, and the Huntsman Mini continues to behave normally. I changed USB ports, just in case there's a faulty one, and nothing has gone wrong. The chroma effects are at 100 brightness, and it's as if I had just gotten it out of the box the first day. I'm not sure if a non-Razer keyboard could also trigger this, but I'd give it a try. I'm a bit nervous that this will happen again. But so far, so good. I've rebooted the computer a couple of times, just in case it was a happy coincidence. For now, it continues to work. I hope this is the fix that will help you guys too, because there's nothing more disappointing than getting something new and it not working correctly. edit: Okay, something else I had to do when I switched to my Ornata is reconfigure the keyboard language settings, since the Ornata is Spain layout and the Huntsman Mini is English (US) layout. I doubt the issue is in Windows 10, but I thought it best to inform others about this.

Update: So, I've given it a few days. The issue returned after a couple of days. I've been trying everything, and I can't say if I've finally fixed it, but a new workaround is this: Clean install of Synapse 3, delete Huntsman Mini drivers (Device Manager), unplug it. Reinstall Synapse 3, disable auto-updates, and plug the Huntsman Mini again. Don't get the update for it. The downside is that you can't configure the chroma effects and are stuck with the spectrum cycle. For now, it seems to be working, but something tells me it will return. And since it works, it's possible that a software update would fix this. This is a real bummer, I've had the keyboard for almost two weeks and haven't been able to move past this mess.

Yeah, i did something simular. I removed and reinstalled the whole Thing too, and had it in default mode. But I reinstalled it in the end and keept it low brigtness. It works like 80% of the time. But I use a laptop with a second screen so ive just been using it for the gamming part, and used my laptop when i needed too Wright someone, becouse it does somhow not afeck Any of the buttons i use for gaming ‍♂️

Thank you very much for your contribution @TiredCube and @Theboesen Unfortunately I still have the same problem, sometimes it is not the same keys but others, and so on in an infinite loop. I have followed her explanations and details but the malfunction continues to persist, I honestly no longer know who to turn to. It is best to report it to support. This is an outrageous situation, have we paid money (which is not little), to acquire a keyboard with failures (be it hardware or software)? I think not, for that I buy a keyboard for € 10 and it saves me all time from problems. The most powerless thing for me is that we should seek solutions among ourselves when a Moderator or a supervisor of this forum should be here. I understand that they may have support person problems but at least they release communications informing of the failures and that they will be resolved. Or is this not happening to anyone else? Or could it be that they have not sold more units? I don't know, I honestly feel cheated. If they answer me in the support I will send it to you. Thank you and good afternoon.

Yeah. I've tried further things. Safe Mode, no Synapse 3, etc. There's nothing that can fix this. I've talked through another website with Razer support and one guy gave me a guess as to what could be happening: in some keys, the LED light on the key interferes with the switch's mechanism. Therefore, the defect might be physical and there's nothing we can do about it, other than insist to the vendors to give us a replacement. The switches present no visible faults when removing the keycaps, but as this is the first mechanical keyboard I've gotten, I'm not confident enough to open it and inspect it further. I've seen videos where people disassemble the switches, but that goes way beyond what I'm willing to do. I've initiated a replacement request today, and I'm hoping to get answers tomorrow. If all goes well, I'm hoping to get another one within a week or two, and then I'll see if it's solved. Either way, I will return to this thread. By the way, @frontPearlAquatalk085, are you, by any chance, South American? I think I saw Spanish in the video?

Good Morning Finally I have already started the ticket for the replacement of the keyboard, it will be under observation for a few days until they can approve it. These days have been somewhat unfortunate because they have also begun to fail part of the numeric keyboard. @TiredCube, I'm glad to know that they can also give you a solution, I think it's the most normal thing since the manufacturing defect is not something that concerns us. On the other hand, I do speak Spanish although I am not South American, i'm from Spain. In this thread I always try to write it in English since I don't know if the forum moderator or technician understands it (I save having to explain my situation twice). Curiously today the keyboard is working well although it will surely be momentary, I still do not understand the fault it may have (I have already left the synapne. Later I will comment on the replacement process as it has been done. Best regards

Ahhh, gotcha! I was wondering because the vendor got a batch of Huntsman Mini with linear switches very recently, and maybe we were nearby and affected by the same batch. The vendor has accepted to replace the keyboard, so this week we'll do the exchange. Hopefully, I'm getting the new keyboard by next week. We'll see if the issue is solved with a replacement. Good luck!

Quick question, who here is running Windows 10 20H2 (Insider)?

Hey everyone! Thanks for initiating this thread and posting all the progress of your workarounds. I'm glad that you guys were able to contact your reseller or our Support Team for assistance with the replacement. If in case you are still experiencing the issue, please send me the Razer Synapse 3.0 logs so the team can review it. Also, if you have contacted our Support Team, please send me your email address or case number so I can check your account and review the case.

Hi! Glad to hear from you! :smile_: I've returned the keyboard and I'm waiting for the replacement. I just remembered that I have one set of logs saved, though I had done several clean installs of Synapse before running the logger and the start of this problem (whatever triggered it) is probably not there. I will send these to you. I've asked around about the Windows 10 version because someone in this post theorized that the Windows Insider version 20H2 might be interfering with Synapse 3 somehow. It's as good as anything, as another Huntsman Mini post I was following (with a different issue than this post) has uncovered an incompatibility with Ryzen processors. I will proceed to send you the logs.

TiredCube
Hi! Glad to hear from you! :smile_: I've returned the keyboard and I'm waiting for the replacement. I just remembered that I have one set of logs saved, though I had done several clean installs of Synapse before running the logger and the start of this problem (whatever triggered it) is probably not there. I will send these to you. I've asked around about the Windows 10 version because someone in this post theorized that the Windows Insider version 20H2 might be interfering with Synapse 3 somehow. It's as good as anything, as another Huntsman Mini post I was following (with a different issue than this post) has uncovered an incompatibility with Ryzen processors. I will proceed to send you the logs.

Thanks for the follow-up. This needs to be investigated further. By the way, I've replied to your PM.

Good afternoon. Thank you for your message @Razer.SpeedCr0ss, in my case the package was picked up today but I had already stopped using the keyboard. Now I am waiting to receive the replacement. Unfortunately I do not have any log about the operation of the keyboard since I have repeatedly deleted the application, so in the end I have also used the device without any software. Thank you for your concern.

frontPearlAquatalk085
Good afternoon. Thank you for your message @Razer.SpeedCr0ss, in my case the package was picked up today but I had already stopped using the keyboard. Now I am waiting to receive the replacement. Unfortunately I do not have any log about the operation of the keyboard since I have repeatedly deleted the application, so in the end I have also used the device without any software. Thank you for your concern.

Thanks for letting me know. Please send me a PM should the issue persists with the replacement keyboard. I'll be locking this thread now.