Huntsman mini broke my windows | Razer Insider
Skip to main content
I just bought the huntsman mini which I totally love in terms of look and feel... but I'm returning it right away :(
This is the 2nd time I buy a razer product and have to return it, both times the product had so much potential and both times seems like "lack of test" is the reason the product is barely usable, a real pitty cause I truly love the look and feel.

Well, I go to the point. Got the keyboard yesterday and I wasn't able to use the "onboard" profiles, synapse lets me load them and all that but when I cycle trough them in the keyboard with synapse turned off they do not work (I always get the same "Spectrum cycling" lighning no mater what I loaded into the profile).

So I headed to the support page for the keyboard and found that there is firmware update, I though "Great! this might fix the issue"... After installing the driver the keyboard FN combos were messed and the windows taskbar unusable, the FN combos were fixed once I launched again synapse but the windows taskbar is broken for the span of 4 to 5 minutes every time I start windows (that is simply unbearable, I have to reinstall windows now but I cannot keep a keyboard that I know can cause that, not the keyboard itself, but the support attached to it).
jakw0lf
Which site did you download the firmware updates?

Synapse has never broken a Windows PC like what you are saying. You might want to give more details as to what exactly happened and also get in touch with the official tech support to find the real root cause.

It's definetly a official firmware update: http://drivers.razersupport.com//index.php?_m=downloads&_a=view&parentcategoryid=1056&pcid=1018&nav=0,77,1018 can be accessed from here: https://mysupport.razer.com/app/answers/detail/a_id/3609/

The issue is tied to the keyboard somehow, I don't even have synapse configured to start up with windows and I tried pluggin the old keyboard and the windows taskbar does not have the issue with it, is only with the huntsman mini connected (after the firmware update).

And I'm not pursuing support for this, the keyboard is 1 day old so 'm simply exchanging it with another one (from another brand) with the vendor. Pitty cause I read Razer improved a lot in the last years and I was ready to jump in when I saw the looks of this keyboard.
I use Windows 11 due this problem (Windows 11 not occurs the crash). It's amazing that I can't use Windows 10 because explorer.exe crash when I start the PC. I use the Razer Huntsman Tournament Edition :frown_:
I am also experiencing this issue and have a Ryzen based system.
Has anyone found a solution? Just got a Huntsman mini and experiencing same problem.
Hey everyone! Thanks for initiating this thread. And yes, the team is aware of the issue and currently investigating the software's behavior. Please send me your Razer Synapse 3.0 logs by following the steps on this link. Save the files via Google Drive or to any online drive. Once done, repair the Razer Synapse 3.0 by following the steps below:



Should the issue persist, please send me the online drive link with the Razer Synapse logs and your case number (if there's one) via PM so I can forward it to our devs. I appreciate everyone's cooperation.
marthofdoom
I was able to open a ticket with Razer on this issue. Will hopefully be resolved soon.


Well i have the same issue and have tried all on AM4 platform from Ryzen 3600 - 3950X and B450 - X570 on the newer 5800X with the same issues. My second Huntsman Mini i didnt update the firmware and that was fine for a while then slowly started to get slower and slower until it ended up like the rest on here freezing the taskbar on startup or when plugged in once booted up.

Now because the shocking service i received from my RMA replacement that turned up in white rather than black and them not swapping it without going through another full RMA procedure. I threw it in the bottom draw and just thought id been robbed of £129 and went on to use my Anne Pro 2 for a month or so.

Now i love the feel of the switches and the keyboard itself so got it out the other day and plugged it back in and upon the first few boots since then its been ok..... FOR NOW....

Will it rear its ugly head again? Yes i have no doubt it will.

So here is hoping that Razor actually listen and provide a firmware fix for AM4 platforms.
MkyAs
Did you get anywhere with support after this?

Hi there! The team is still investigating this behavior and will be working on a fix. I'll update this thread once I have an update.


No luck so far and highly doubt they will have this resolved anytime soon. Since SpeedCr0ss helped with notifying the development team, I've dealt with another 3 different technicians (total of 7 now) and all have asked me to perform the same troubleshooting steps (as the previous 4). Its like talking to a brick wall as they either don't read any notes from previous conversations or have zero care to actually resolve this issue. They wont even acknowledge there is a problem with the keyboard firmware and are still fobbing it off to 3rd party software that i have installed (even though they cannot tell me which software)
I just received the first non-template answer from Razer, where they also admit that they know about this for a while.

Razer.SpeedCr0ss
I understand the urgency for this issue to be fixed. The team is on it. However, I can't provide an ETA yet. The Razer Support/Insider Team is watching this thread. I'll update this thread once an official fix has been generated.


It's important for Razer to understand how badly you have handled this case. If you check the links I provided and also Youtube, you will see that people have been reporting this issue since late november/early december, but it only got to your L3 and to Razer recognition with my ticket, which was opened on mid January.

You need a severe change in your support process. Your L1 consultants could be easily replaced by bots as they just send template answers and barely read the tickets and this is what people have complaining about, a ground-breaking issue that makes people RMA hardware and has been reported 3 months ago, got to your L3 only a few days ago and still has no ETA for a fix.

The only choice people have is to return their keyboards, and those are the lucky ones who know how to use Google and have the will to fight with your extremely bad L1 Support Process. Most of the affected people are just RMAing their hardware due to having no idea that the keyboard is causing the issue, as it makes no sense.

Please launch a communication or something to prevent this. I spent 15 days myself on this issue and was ready to RMA my motherboard when I discovered it was the Huntsman mini.
ak5hat
when you reached out to them what did they say?

I've never contacted Razer, it's on them to fix the bug with a firmware/synapse update. I'm not in the mood to get an automated response and a few useless followup responses asking me to check drivers or my usb ports, that would be a complete waste of time.
But what on earth... I'd like to think you just misunderstaood my post as a rant, but it really is not the case. I said that I load the profiles with synapse indeed, the idea of that is to put them on the onboard memory so you don't need synapse running or even the same computer for that matter to get that profile working on the keyboard. I thought it was pretty obvious. So yeah, I can turn on synapse do stuff and then turn it off.

I don't understand now you looking down on me for wanting to change a product that gives me troubles. Feel free to buy the huntsman mini and install that firmware to test if it works because sure as hell I'm not gonna be testing a product "until it works", that is something that a company should do on their own. I also understand is hard to foresee all issues or possible compatibility issues, but like you said.. I never heard of a keyboard messing up anything, so something must be pretty off there.
BradC6
Hey everyone,

Im also having the same issue where my huntsman mini is messing up windows taskbar. At boot up the taskbar does not load until I click it a few times, then the screen flickers and the icons appear. If my computer is already on and I unplug then plug it in again, multiple buttons stop working on the taskbar (Start, search, and notification center) for around 5 min.
I could not find any solutions online.


Exactly what I am experiencing!

I am speaking to a technical support member by the name of Hunter. I’ve sent him system and synapse logs for reference and even made a youtube video of the problem as per his request:

I am asking for a copy of the original firmware so I can flash my keyboard back to factory and test it out. This all started because of the firmware update I believe.
I just want to say that it doesn't happen to me, but I find it weird that happens to you. Maybe something happened inside the keyboard, so you might want to check that out
Hi all,

Quick question - what systems are you running at the moment (i.e. CPU and motherboard)? Also, have you tried the keyboard on another desktop/laptop etc?

Reason I ask is because I've tried the keyboard on both a surface 3 and a Lenovo laptop with no issues whatsoever! I am completely baffled.

As soon as I plug my keyboard into my primary desktop (Ryzen 5600X and MSI B550 Tomahawk motherboard), the problem occurs.

I've already tried formatting to a fresh copy of windows and it seems even before loading Razer Synapse 3, the issue is present (so it cannot be Synapse as it wasn't even installed at the time). I feel that I've ruled out the OS as well, given that I fresh installed Windows10 and the keyboard issue was apparent straight away when I booted to windows desktop.

What I am thinking, is that there may be a hardware incompatibility issue here...

I am running an AMD system so wanted to get everyone's opinion on what systems you are running. Who knows maybe a pattern exists somewhere?
ValkyrieX
Hi all,

Quick question - what systems are you running at the moment (i.e. CPU and motherboard)? Also, have you tried the keyboard on another desktop/laptop etc?

Reason I ask is because I've tried the keyboard on both a surface 3 and a Lenovo laptop with no issues whatsoever! I am completely baffled.

As soon as I plug my keyboard into my primary desktop (Ryzen 5600X and MSI B550 Tomahawk motherboard), the problem occurs.

I've already tried formatting to a fresh copy of windows and it seems even before loading Razer Synapse 3, the issue is present (so it cannot be Synapse as it wasn't even installed at the time). I feel that I've ruled out the OS as well, given that I fresh installed Windows10 and the keyboard issue was apparent straight away when I booted to windows desktop.

What I am thinking, is that there may be a hardware incompatibility issue here...

I am running an AMD system so wanted to get everyone's opinion on what systems you are running. Who knows maybe a pattern exists somewhere?


I'm running a ryzen 3700x and an asus b550f-wifi board.
I tried the keyboard on my dell xps 15 with intel cpu and the keyboard works fine. so It must be a Ryzen issue.
I am also running an AMD processor and have the same issue. Razer Please update your drivers to work with AMD systems!!!!
I was able to open a ticket with Razer on this issue. Will hopefully be resolved soon.
same problem I tried all of the above as well, nothing works. Does anybody have another fix?
Same issues here. I disabled all my start up apps except icue and synapse. After I restart I can hit any key on huntsman mini and my task bar fills up and synapse launches. Then hit a key on my K95 and I cue starts. Not sure if this will help anyone. B4 I did this if I hit the start menu it would bring up my task bar and I could open each app from there. Either way this is very annoying and honestly a 120 dollar headache I dont need. Hopefully they get a update soon.

Ryzen 9 3900
2080 ti
MSI x570 a pro
Same here.
Hey everyone! Thanks for sharing your keyboard's ongoing concern here. Our Support Team is currently investigating the issue and will ensure to post an official fix once it is available. For now, please send me your Razer Synapse 3.0 logs by following the steps on this link. Save the file via Google Drive or to any online drive account, then paste in your PM.
I have read this issue doesnt exist in previous version of the firmware so maybe they can give us this previous version for now so we can use our keyboards while they working on solving this issue on latest firmware.
Same problem.

X570 and Huntsman Mini.

I have spent two weeks troubleshooting my PC since I assembled it.

Bought a b450m and a QVL memory kit to troubleshoot, took my PC to a friend's house to test with his CPU.

RAZER people are RMAing motherboards and other PC Parts due to this issue.

After I figured out that the issue was the Huntsman Mini, I saw posts from November and December/2020 about this, saying that they have reported it to Razer.

TBH It's absurd that you guys still have not found a solution for this crap. This is a blocker issue that causes people not only RMA their keyboards, but their PC parts as well.

Please, take some action. I am in the process of returning the keyboard (which I love btw) and ask for a full refund because another Huntsman Mini will not fix my issue and Razer does not have other optical versions to offer.

DO SOMETHING
Razer.SpeedCr0ss
I understand, urbanSpaceCadetflow257. As a moderator, I want every user to voice out their thoughts as it can help others and even Razer resolving concerns while implementing our house rules. Anyhow, let's keep this thread open with a welcoming ambiance while the team is investigating the issue.

Hello everyone! Thanks for understanding the situation and for your cooperation. Feel free to send me a PM anytime.


I just received an e-mail from Razer Support asking for the same troubleshooting as everyone. Seriously, your support process need a FULL REWORK. This copy/paste crap is probably the reason why this issue has been reported since November/2020 and still does not have a solution.

RAZER, people are RMAing their brand new PC parts due to this issue, not only your faulty keyboard. Please do something.
CookiesCookie settings