Huntsman mini broke my windows | Razer Insider

Huntsman mini broke my windows

A
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).
This topic has been closed for comments

384 Replies

A
I was wondering if some people plugging it in monitor hub and it solves the issue, maybe plugging this in usb-c in graphic card will work too? Im gonna test this out today, just need to get usbc-usbc cable.
Razer.Speedcr0ss
Userlevel 7
Hey everyone! Our Support Team is still investigating the behavior. Please submit a case to our Support Team or send me a PM should you need additional assistance.
M
Razer support has not provided any "support" so far, so we are helping ourselves.

I just tried both of these options one after the other:

https://www.reddit.com/r/razer/comments/fim3jn/disable_razer_installer_auto_install/

https://www.overclock.net/threads/how-to-stop-razer-synapse-installer-when-plugging-in-razer-devices.1773757/

The second option looked promising but it still crashed my explorer when I plugged the keyboard back in.
ChillyRide
Userlevel 1
MkyAs
Razer support has not provided any "support" so far, so we are helping ourselves.

I just tried both of these options one after the other:

https://www.reddit.com/r/razer/comments/fim3jn/disable_razer_installer_auto_install/

https://www.overclock.net/threads/how-to-stop-razer-synapse-installer-when-plugging-in-razer-devices.1773757/

The second option looked promising but it still crashed my explorer when I plugged the keyboard back in.

Synapse has nothing to do with this issue. Long boot and dead taskbar is on fresh Windows without any drivers and synapse installed.
P
ChillyRide
Synapse has nothing to do with this issue. Long boot and dead taskbar is on fresh Windows without any drivers and synapse installed.

I believe the problem we are having is with a newest version of firmware that razer updated through synapse or shipped with the newest batches of the keyboard.
M
ChillyRide
Synapse has nothing to do with this issue. Long boot and dead taskbar is on fresh Windows without any drivers and synapse installed.


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.
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.


Issue is related to AMD (B450 & X570) and the keyboard firwmare, doing stuff with Synapse won't help.
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
The install may not happen but the registry key still gets created.

I have tried the keyboard on an intel machine and another x570 machine and it works fine on both of those, synapse didn’t trigger at all during windows install for some reason. I have seen other users having the issue on intel.

something is causing it to be detected as a boot device. Disabling all processes that could cause it to be detected as a boot device seemed like a logical thing to do.

Anyway clearly it didn’t fix the problem so let’s just try other things.

Do you have an X variant processor? On other threads people were thinking it might be specific to those processors rather than just x570. As I said I have tried it in another x570 machine that doesn’t have an x variant processor and it was fine.
G
MkyAs
The install may not happen but the registry key still gets created.

I have tried the keyboard on an intel machine and another x570 machine and it works fine on both of those, synapse didn’t trigger at all during windows install for some reason. I have seen other users having the issue on intel.

something is causing it to be detected as a boot device. Disabling all processes that could cause it to be detected as a boot device seemed like a logical thing to do.

Anyway clearly it didn’t fix the problem so let’s just try other things.

Do you have an X variant processor? On other threads people were thinking it might be specific to those processors rather than just x570. As I said I have tried it in another x570 machine that doesn’t have an x variant processor and it was fine.


I'm exepriencing the issue with a Ryzen 3600 and a MSI B450-A-PRO
U
MkyAs
The install may not happen but the registry key still gets created.

I have tried the keyboard on an intel machine and another x570 machine and it works fine on both of those, synapse didn’t trigger at all during windows install for some reason. I have seen other users having the issue on intel.

something is causing it to be detected as a boot device. Disabling all processes that could cause it to be detected as a boot device seemed like a logical thing to do.

Anyway clearly it didn’t fix the problem so let’s just try other things.

Do you have an X variant processor? On other threads people were thinking it might be specific to those processors rather than just x570. As I said I have tried it in another x570 machine that doesn’t have an x variant processor and it was fine.


5800x and then 5900x, both had the issue. Did not test on earlier gen but it looks like people have the same issue with older gen.

The only thing that "solved it" for me was to use a capped LTSC Enterprise version of Windows 10 (1809), but after a Windows update (which has to be forced in that version), the issue with Black Ops Cold War (the boot is not the only issue) came back.

Give up on Synapse, it's a waste of time, regarding the boot device thing, I have no idea. I spent two weeks on this and waited for another two weeks for Razer to provide a solution, cannot help you further with tests as I returned the keyboard today. Every single person I saw with this issue was using AMD (B450 & X570). I did not have this issue with my Intel rig.
ChillyRide
Userlevel 1
MkyAs
The install may not happen but the registry key still gets created.

I have tried the keyboard on an intel machine and another x570 machine and it works fine on both of those, synapse didn’t trigger at all during windows install for some reason. I have seen other users having the issue on intel.

something is causing it to be detected as a boot device. Disabling all processes that could cause it to be detected as a boot device seemed like a logical thing to do.

Anyway clearly it didn’t fix the problem so let’s just try other things.

Do you have an X variant processor? On other threads people were thinking it might be specific to those processors rather than just x570. As I said I have tried it in another x570 machine that doesn’t have an x variant processor and it was fine.

I repeat dont do stupid things! After fresh windows install, when Hello appeares and u waiting for first boot and Ethernet NOT CONNECTED, U wait for 5+ mins to boot, while without keyboard it is less than 1 min.

Only 1 fix. Windows Insider builds for now. Im sititng for couple days and pretty stable with latest updates and no issues.
H
Have the same issue ! Ryzen 5600x + aorus b450
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.
U
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.
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.
Razer.Speedcr0ss
Userlevel 7
Hey urbanSpaceCadetflow25. Please send me your case number or email address via PM.

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.
CookiesCookie settings