Huntsman mini broke my windows | Razer Insider

Huntsman mini broke my windows

Show first post
This topic has been closed for comments

384 Replies

M
Still not getting it. I understand that it doesn’t have anything to do with synapse it has to do with the fact that it appears to be registering the keyboard as a bootable drive and is trying to load synapse during startup/when you plug it in. I’m trying to find ways to stop it registering and it was suggested that completely disabling RazerInstaller on the board would help.

Also it’s not just amd boards there are people reporting it on intel.
U
MkyAs
you misunderstand what I was trying to do. I plugged the keyboard in at the start of the windows install process and it immediately was trying to install synapse (before I had even selected anything in the installation screen). If the software is that aggressive in trying to install itself it seemed like it was part of the problem. I’m looking at other ways of blocking that install from happening because I think that’s part of the issue. It’s overriding windows and appearing to be a boot device.


Same answer mate, I have tried it in a clean offline W10 retail installation (if there is no internet the Synapse install does not trigger), so I can confirm with absolute certainty that it is NOT RELATED to Synapse.

I used this keyboard on my 9990k / Z390 and never had any issues. The only thing that changed was W10 from 2004 to 20H2, I was able to reproduce the issue with my AMD rig in 2004, so I can confirm it's related to AMD.

See my video if you still haven't:
M
I think at this point most of us original posters have replaced our keyboards. This thread is constantly full of new people with the same issue. It's kind of sad that support hasnt got if solved. I would bet there is a solution but some doofus in marketing/management wont let them do it.
U
Just FYI everyone.

Razer support closed my ticket saying that a future update will resolve the issue, without ETA.

I strongly suggest everyone to just return their keyboards.
Razer.Speedcr0ss
Userlevel 7
Hey everyone. Our devs are investigating the issue and working on a fix. I appreciate everyone's patience and understanding. I suggest submitting a case to our Support Team by clicking this link or send me a PM.
P
We need more clarity about this fix, a timetable, whether it's been clearly diagnosed, etc.

You can't just leave customers with defective products and no clear communication on whether a solution is in sight.

Does Razer want to rebrand to "always have a backup piece of hardware from another model/brand cause we might not fix the problems with ours for months?"
Razer.Speedcr0ss
Userlevel 7
polyKenyanCopperclub810
We need more clarity about this fix, a timetable, whether it's been clearly diagnosed, etc.

You can't just leave customers with defective products and no clear communication on whether a solution is in sight.

Does Razer want to rebrand to "always have a backup piece of hardware from another model/brand cause we might not fix the problems with ours for months?"


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.
Razer.Speedcr0ss
Userlevel 7
urbanSpaceCadetflow257
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.


Your feedback is well taken. Admittedly, we could have handled this case better. I will cascade this to the team and update this thread with the Razer Huntsman Mini's case progress.

Hey everyone. I recommend submitting a case or sending me a PM as the team needs your computer event and Razer Synapse logs as they will use them in their investigation. Thanks for your cooperation.
S
I'm extremely disgusted to find Razer not doing anything about this since it was reported untill now. I've had this problem and reinstalled Windows 10 3 bloody times wasting my time. I myself am having this problem on my Huntsman Tournament Edition TKL on my Intel Z390 platform.

What makes it worse is that my Basilisk V2 mouse just died and bought a Viper 8KHz mouse and even that is giving me problems on every cold boot not detecting after updating to the new firmware. I have to plug it out and back in for it to be detected. Don't you ever test your firmwares?

Razer, please fix your incompetent mess. I'm at my wits end to dumb your thrash and move to another brand altogether.
M
I myself actually reinstalled once, and got a new motherboard before I discovered it was my Huntsman mini. This has trult been the worst experience ive had with a vendor in 10 years of enterprise IT experience. Not only was the issue simply not acknowledged directly when information. But to this very day all we hear is "The team is on it". If the team is on it how about actually providing information, what is the team on? Have they confirmed its related to AMD? Is it an issue with Motherboard firmware like a Agesa version? Windows thread managment with AMD? Are you working with AMD for a fix? Are any other products affected? Have you made a public release that you are working on the issue through your social media platforms or insider emails?

This is abhorrent and will most certainly turn many away from Razer in the future. As a long time customer I feel absolutely betrayed and disgusted with the way this has been handled. And will certainly never be purchasing, nor recommending any synapse enabled products again.
S
marthofdoom
I myself actually reinstalled once, and got a new motherboard before I discovered it was my Huntsman mini. This has trult been the worst experience ive had with a vendor in 10 years of enterprise IT experience. Not only was the issue simply not acknowledged directly when information. But to this very day all we hear is "The team is on it". If the team is on it how about actually providing information, what is the team on? Have they confirmed its related to AMD? Is it an issue with Motherboard firmware like a Agesa version? Windows thread managment with AMD? Are you working with AMD for a fix? Are any other products affected? Have you made a public release that you are working on the issue through your social media platforms or insider emails?

This is abhorrent and will most certainly turn many away from Razer in the future. As a long time customer I feel absolutely betrayed and disgusted with the way this has been handled. And will certainly never be purchasing, nor recommending any synapse enabled products again.


Absolutely mate. Half baked products and they don't even bother to test the firmware. Feel like dumping everything Razer and moving on to a brand with better support and reliability. Razer has become too complacent with genuine problems and it seems their development team does not test their firmwares properly before releasing it. Keyboard and Mouse are the 2 inputs that you interact with all the time and they have to mess this up. Well, too bad I think most have moved on to other brands and quite honestly I think I'll do that too if they they don't up with a fix within a week or two max.
D
Razer.Speedcr0ss

Hello everyone! The support team/devs mentioned that users reported that they suddenly experienced system lag after updating the keyboard firmware to v1.01 and most of them have AMD processors. The issue has been reported and is currently investigated. Should I receive any progress, I'll post it here.


Thank you, Your updates are appreciated, For now I have switched back to using my old no name brand 60% mech keyboard instead of my Huntsman Mini.
D
i have huntsman mini. so i should just return it? expect that razer wont fix this issue? sucks i really like the KB
ChillyRide
Userlevel 1
dewbe93
i have huntsman mini. so i should just return it? expect that razer wont fix this issue? sucks i really like the KB

3+ month and they cant fix it yet. Incompetent devs and too slow support. I am selling all my razer devices right now.
D
ChillyRide
3+ month and they cant fix it yet. Incompetent devs and too slow support. I am selling all my razer devices right now.


yeah im going to do the same. never buying razer products again.
P
I would like to add another data point. I'm experiencing the same issue with my new Ryzen 9 5950X and X570 motherboard. Took me ages and a lot of frustration to figure out it was my Huntsman Mini...
P
i have ryzen 5800x, asus b550-i, evga 3070xc3, same problem, but,
I was able to solve in a provisional way, placing the usb of the keyboard in the slots of the monitor, because my monitor has 2 usb extensions, if your monitors have, they can solve that way, while a firmware arrives
ChillyRide
Userlevel 1
PaszZhitaa
i have ryzen 5800x, asus b550-i, evga 3070xc3, same problem, but,
I was able to solve in a provisional way, placing the usb of the keyboard in the slots of the monitor, because my monitor has 2 usb extensions, if your monitors have, they can solve that way, while a firmware arrives

Doesnt solved for me.
T
I have started using the driver from my Tournament edition, it boots fine MOST of the time however I can't use the function keys with this driver.

I've also noticed if you uninstall the driver for the mini from device manager and reboot in my experience I have no issues ( So basically windows installs the driver once you boot in ) but obviously also not a solution as you would have to uninstall before shutting down every time...
P
ChillyRide
Doesnt solved for me.

For me it worked. So what I did: remove all Razer related software from my computer and connect the keyboard via some form of USB hub (the hub in my monitor works for me, but I'm guessing any hub should be fine)

The trouble now is that my keyboard tends to go into some kind of error mode from time to time (the keys light up red when I press the FN key). This happens especially on Linux and the only way to get it out of it is to boot into Windows and reapply the the config via Synapse.
ChillyRide
Userlevel 1
pbackx
For me it worked. So what I did: remove all Razer related software from my computer and connect the keyboard via some form of USB hub (the hub in my monitor works for me, but I'm guessing any hub should be fine)

The trouble now is that my keyboard tends to go into some kind of error mode from time to time (the keys light up red when I press the FN key). This happens especially on Linux and the only way to get it out of it is to boot into Windows and reapply the the config via Synapse.

4 hubs, non worked!
U
ChillyRide
4 hubs, non worked!


Lol man it impresses me that you are still trying. Just return it and buy another keyboard.
ChillyRide
Userlevel 1
urbanSpaceCadetflow257
Lol man it impresses me that you are still trying. Just return it and buy another keyboard.

Agree, but I like it very much and my pc turned on 24/7 , mostly. 🙂 Was on insider build for 1 week. Last update broke completely Windows. Cant reboot pc and turn off power 😃 So switched back to stable. My razer devices on sale right now. Probably will switch to Asus.
P
If it is frustrating all the time they have taken to solve, being such an expensive keyboard also, I have had many razer products, 2 laptops, 2 keyboards, this is the third, 2 mice, and the first time something like this happens to me
R
Well looks like I inadvertently joined this exclusive club. Just purchased the huntsman mini on Saturday to now have explorer crash on me. I love this keyboard and really don't want to return it, but I also don't want to be stuck with a broken product. I've got 14 days I believe with BestBuy.
CookiesCookie settings