Evergrace

Too bad Lemon Laws only apply to cars, this thing would have been nipped in the bud back in 2020 when the problem first started to surface. Time to keep plastering GamersNexus, LTT, and Jayz2Cents with this ****. Corsair needs to be held to a standard of not ********ing over your customer on $250 keyboards.

My favorite part about the RMA process for this thing is that not only does it seem that they're just sending out the same K100s with earlier firmware (that's still broken) but on top of it you have to pay 30-50 bucks to ship the damn thing to them. 10 months (at least) with no solution in sight, no progress updates, and two firmware versions that have made things worse. Time to see if Steve at GN is up for another exposé as to why these Tech companies refuse to issue recalls on obviously defective hardware, that Asus one seemed to light a fire under their ass. Just recall the damn board, all Corsair is doing at this point is ruining their reputation.

And you gotta pay to ship the broken one to us!

I was finally able to create an RMA ticket a couple days after my post. The page would not load the form when "Warranty RMA (...)" was selected, was just completely blank.

First (reliably) reported instance of this bug (on the Corsair forums) was in August of 2022. I wish this had only been going on for 6 months.

I have an RMA currently active, so far, no. But the stories I've read from people who have it sounds like they just send you out another K100 with the 1.9.xx firmware on it that works for like a week and then starts having the same problems. So no, not really helpful at all.

Their system hardware still seems reliable, but man their peripherals are just having problems. My headphones (Void RGB) have usb issues, my mouse wheel doesn't scroll right (Scimitar Elite x 2) and now this K100 issue has gotten me to start not recommending Corsair for anything that's not internal, and even then I'm hesitant since everything goes through the crapshow that is iCue. It's disappointing to say the least.

The fact that it's been 3 firmware versions and a whole iCue version later and it's still not fixed points to faulty hardware, but god forbid Corsair actually submit a recall for thousands of ~$300 pieces of hardware, that'll hurt the bottom line. Honestly after the whole Asus frying intel chips debacle and all the other stuff that's been going on as of late you'd think Tech companies would be on the ball of getting in front of issues like this. Guess Corsair is going to need that "pariah" moment before it clicks.

This has just become asinine at this point, now your RMA system doesn't even work and I can't submit an RMA for this K100. I'm done, I want my money back for this brick of a product. Corsair is lucky lemon laws only cover vehicles, it's been 12 months and they're continuing to sell defective boards at full retail value. @Corsair Nick @Corsair Art @Corsair Albert Have someone DM me with contact information so I can get a return label and I'll provide my receipts. I don't want another one of your broken boards, I want my money back. This company should be absolutely ashamed of fleecing their customer base with this $300+ scam product.

I just gave a report of this 10 month long issue to LTT in their submissions forum. Might not go anywhere, but it's adding visibility of the issue to another tech board. Spread the word.

v.0.32.262 is an entirely different control board, and one that doesn't have any issues. Corsair appears to have switched control boards around a year ago and these new boards are the ones having issues. If anyone is willing to post or DM me their sticker from the underside of their board I can compare it to mine and see if we can narrow down product number difference to have reference in case a retailer has old stock of the keyboard that wouldn't have an issue.

The boards with 0.33.265 are completely different hardware, we don't even see any updates in iCue. Seems like they switched hardware at some point in the last couple years and that board is rife with issues. If i knew how to rip the firmware I'd post it to see if you could Frankenstein the firmware with the hardware.