me too 

Version 1.0.21 is problematic.
Prompted  for X17 mouse firmware update and stuck forever and bricked the mouse. 
Had to find removal tool in forum and modded the script to make it work. 
 
 
Was able to manually updated it but now same thing happened to my Z20 keyboard.
Reverted to 1.0.20 and found firmware was gone along with all features and settings. 
 
Please help. 

My keyboard is plugged to pc. No hub or such. I used a second rig and downloaded Unleash 10150. Firmware update did fine. All lit and features do as expected. I suspect my old board to cause these problems on usb.

Thanks, we're looking into it!

I have the same problem as the OP. I use a Cable Matters 4 Port USB 3.0 Switch Hub and now every time I boot, I have to switch inputs, i.e. disconnect/reconnect the keyboard, for it to work. Also, when switching inputs, the keyboard occasionally becomes disconnected. I had no problems with my Z15 prior to Unleash RGB v1.0.21.0 & firmware v1.38.

Still no fix?

I'm still havinng horrible debounce/double keypress issues.  What's the last known working firmmware and how do I force a rollback?

I don't even care about llights, etc. I NEED to have mmy keyboard working properlly for work.  This is atrociouss and unacceptable!

Not be flippant, but what does "looking into it" mean? I'm unplugging & plugging my EVGA keyboard in daily to make it work. It's very disappointing there isn't better communication, as well as a method of rolling back broken firmware. As things stand, I would not recommend an EVGA keyboard to anyone.

I suggest anyone having this issue open a case with support - they don't seem to be taking it seriously...
I opened a case and this was the last response I got:
 
---
Hello,

Thank you for reaching out. I have forwarded this information to our Product Management team to see if we can reproduce the situation and include the fix in a future patch. I'm also going to be checking on whether a replacement will resolve the issue or not. Please allow 1-3 business days for the team to get back to me with additional information.

Regards,
EVGA
---
 
That was 5 days ago...

The response I received is bellow.  Basiccally there is no ssolution and those of us who relly on typing for daily work at > 120 wpmm are screwed and are reduced to not onlly < 40 wpm but a disrupted train of thought and a llot of frustration. I've tried both my originall keys and replacements.  The problem seems to be with the keyboard itselff.

EEveryone needs to complain here and file a ticket.  This is unacceptable.  I wonder what Gamers Nexus would think of this debacllle ongoing and unresolved with no solutions in sight, not even a temporary band-aid like a firmware rollback tooll that would lilterally take onlly a couple of hours to code at most.

EVGA was my go-to after BFG Tech folded up, but this is beyond inexcusable. Months with basically no response except stringing us along beyond return periods.  This is reprehensible.

Ticket response:
 
Hello,

Thank you for reaching out and sorry to hear you are having issues with your keyboard. Unfortunately there is no way to rollback a firmware on these devices. I have passed this information and forum post along to our product management team to ensure that we are currently working on a fix. It can typically take them 1-3 business days to get back to us with an update, in which we will report back to you with our findings. If you do not hear from us within that time frame, please feel free to reach back out to us and we would be happy to assist further.

Please feel free to reach out if you have any further questions or concerns.

Regards,
EVGA

worthgarian
Hopefully Hexadecimus will have an update in the new year.

They didn't even make an effort to respond to me, so I fired back a pretty critical response.  A revision to the updater or packaging a new one to allow roll-backs (say with a prior version bug disclaimer) would take less than an hour.

There's no reason whatsoever to not be in communication with the public about this problem, what they plan to do, and what their timeframe looks like for it.  None.  Zero.  I could do it myself if I had the source code and firmware.  This is unacceptable in every way.

I definitely agree that the lack of resolution with a bug caused by firmware is unacceptable. 
 
Gamers Nexus does seem to have had a good amount of coverage and conversation with EVGA as it left the video card market. I think it would be valid to suggest this discussion topic seeing as there is no resolution in sight. 
 
EVGA at the very least should remove the firmware 1.38 to avoid more of their users being plagued with the problem in the meantime.
 
 

Awesome thanks for the email Chris !
 
I have successfully applied the update 1.39 you sent me and although I sometimes would still get some odd BIOS/UEFI 'Keyboard not detected' messages at startup, I could still get into the BIOS/UEFI by pressing a key. And once entering Windows my keyboard was detected right away without needing several plugging and unplugging. This is a clear improvement and I'm really happy with your assistance !

So far, 1.39 is working for me as well. I use my keyboard in conjunction with a Cable Matters 4-port USB 3.0 switch. I'm back to switching between PCs without a lag in the keyboard connecting, and I haven't had any disconnection issues yet. Thank you very much, Chris.

No problems here on 1.39
a full change log might be nice
 

I had reconnection problems again ttoday when resuming from suspend/sleep using Windows 10 as well as occasional double keystrokes in the meantime despite swapping key switches.  I'll continue swapping key switches to see if the problem follows the keys or the location on the board, but I can't consider this problem resolved in full.