Huntsman Mini Slowing down system start after firmware update

Discussion in 'Razer Support' started by UA_2old4this, Dec 21, 2020.

Thread Status:
Not open for further replies.
  1. Here you go forward anywhere you feel it might get some traction
    Video Part 1 I posted 3 days ago -


    Part 2 - posted today with my problems with the support team -
     
    UA_2old4this likes this.
  2. UA_2old4this

    UA_2old4this New Member

    It's unbelieveable that Razer is just flat out ignoring this!..
     
  3. merlin69-420

    merlin69-420 New Member

    Hello. I have this same issue out of the box. Do you guys think I should contact them or just straight up ask for a refund. Do you think they're actually doing something on this fix or new firmware cause I dont wanna get rid of it knowing that it might get fixed anytime soon. Thank you...
     
  4. Asthman

    Asthman New Member

    Contact them first, if more people will report this issue maybe it will be fixed soon.
     
    UA_2old4this likes this.
  5. MkyAs

    MkyAs New Member

    I just spoke to razer support on the phone and they were very unhelpful. Their advice was that I needed to contact AMD and make it their problem... So I need to contact AMD and tell them that they need to fix their architecture so that defective razer firmware will work on the system.

    Returning the keyboard and mouse.
     
  6. UA_2old4this

    UA_2old4this New Member

    Wow... very "professional" of them
     
  7. Just to clarify this isnt an amd exclusive issue. I purchased this kb 4 a new zen3 build but after experiencing the issue and clean installing twice i finally realized it was the kb causing it. I switched the huntsman mini 2 my intel build and sum uf the same issues aruse. If peuple are saying it was wurking fine be4 the newest firmware then it is ubviusly un their end.

    Guess which key has decided tu stup wurking 4 me until i switch usb purts lul
     
  8. MkyAs

    MkyAs New Member

    Oh mate... that sucks. At first I was like did they have a stroke while writing this?

    That's interesting that it happened on intel for you as well. Given your issue with the O key you may have received a genuinely faulty copy of the board.

    Mine destroy's windows explorer on my AMD machine but works flawlessly on my intel machine. It's a real shame because I have been waiting for a decent 60% keyboard and don't have time time or patience to do a custom. Oh well back to waiting.
     
  9. VeeOneShot

    VeeOneShot New Member

    If i end up doing this replacement that razer is giving me, how do I stop the firmware from updating if it isn't already on this crappy firmware that caused all these problems people are talking about ?
     
  10. Asthman

    Asthman New Member

    Thats what they replayed me, so they are aware of this issue, guess we just wait now, hope this not gonna take them too long.
     

    Attached Files:

    UA_2old4this likes this.
  11. VeeOneShot

    VeeOneShot New Member

    Ok, so that means that they are at least working on it. A replacement for this is going to suck because I have keycaps on mine already. Hopefully they can get a fix for this quickly. It would be a shame if they just let this issue persist for as long as they have
     
    UA_2old4this likes this.
  12. UA_2old4this

    UA_2old4this New Member

    Thank you guys for sharing your experience and keeping everyone here posted! THIS kind of problem for the whole system, just because of a keyboard is just crazy, hopefully our joint effort gets Razer's attention and there will be a fix
     
  13. UA_2old4this

    UA_2old4this New Member

    Firmware is updated manually. If you don't do it on purpose AND firmware version of the KB you receive is free of this huge issue - you're safe
     
  14. Asthman

    Asthman New Member

    UA_2old4this likes this.
  15. UA_2old4this

    UA_2old4this New Member

  16. Razer.Speedcr0ss

    Razer.Speedcr0ss Speed Hunter Staff Member

    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.
     
    UA_2old4this likes this.
  17. UA_2old4this

    UA_2old4this New Member

    Done, thanks!
     
  18. Just another update from my end with support, after gather several different logs from my machine and taking a video of what happens when I have a differennt keyboard to my machines as well as what happens when I connect the Razer to it, they have come back with the follwing statement;

    "Thank you for taking time in providing all of the necessary details, Looks like it could be I/O controller issues with Huntsman mini and AMD devices. if you may can I forward this our Developers Team for further investigation. we send you feedback once we get the solution."

    Can some anyone from Razer that is monitoring this forum please explain to me why we can't role the firmware back to the previous release, at least for the users that are facing this issue. I had no issues with the keyboard until this update and would be happy to go back to the previous firmware if it will resolve the issues I face.

    Sean

    PS - Just before I could click on Post reply, my Anne Pro 2 just showed up
     
  19. Razer.Speedcr0ss

    Razer.Speedcr0ss Speed Hunter Staff Member

    Hi heavenradioOrchid229! Thanks for sharing. Razer has always been updating device firmware, not rollback. Once there' an official fix, I'll post it in this thread, or you can visit the Razer Huntsman Mini's support site by clicking this link.
     
  20. MkyAs

    MkyAs New Member

    This is ridiculous. The previous firmware worked. I have a $200 keyboard that I can’t use because the new firmware broke it. So you can provide the previous firmware, you are just choosing not to and in doing so are leaving your customers with defective products while we wait for razer to fix this.

    might be time to go to the ACCC and see what they think.
     
Thread Status:
Not open for further replies.
Sign In with Razer ID >


Don't have a Razer ID yet?
Get Razer ID >