yellowblanka

I don't know if that would change anything...it sounds like something with USB polling was changed in more recent Windows updates, and they never modified their drivers to compensate for this, so it creates some resource/assignment contention or something when USB controllers are plugged in simultaneously. They definitely need to fix this, but as long as they continue to maintain that it's a "Valve" problem, and not an obvious flaw with THEIR HID drivers, nothing will change.

1.) It's definitely not a Steam issue as they've claimed - it's an issue with their drivers/CUE...I've verified this by completely closing steam and still having any program that queried ANY USB controller freeze up my system (even the USB control panel) as long as the USB controller AND my K55 keyboard controller were plugged into the same system at the same time (Even bought a powered hub, so it's not a power/mobo issue) - unplugging the keyboard caused the system to instantly become responsive. 2.) The only way to "solve" this issue was to disable their HID drivers - unfortunately, as you've probably already found out, this locks the keyboard into the default lighting pattern and disables any extra functionality (media keys, macros, custom lighting etc. all require the HID drivers/CUE software). So I'm left with the option of my "gaming" keyboard becoming a basic keyboard with zero extra functionality or physically unplugging the keyboard before launching a game that uses a USB controller. Corsairs "solution" to this problem is to pass the buck to Valve, rather than admit there's a problem with their drivers/firmware and actually implement a competent testing procedure to fix it for their paying customers. I have NEVER had issues like this with any other peripheral.

And how many/what are the specs of your "in house" systems? 3 Skylake systems with $200+ motherboards? Given the number of issues reported in this forum I find it VERY hard to believe that you're not seeing any of these issues unless: 1.) The testing team is grossly incompetent. 2.) Your testing methodology is flawed. 3.) The test hardware is not varied enough (see 2)

These issues are definitely a problem with their hardware/firmware/drivers/software, I've done everything reasonable to troubleshoot the issues with my K55 and the only thing that worked was uninstalling their CUE software and disabling their HID drivers. Granted, this is a separate issue from key flicker, but I even went so far as to buy a powered USB hub, and the issue still occurred.

Yeah, they well and truly don't give a **** about their customers/their experience. I'm basically locked into the rainbow lighting on my keyboard because I can't run their software/drivers or my system locks up when trying to play a game that polls controllers with ANY USB game controller plugged in (360, Steam controller, cheap arcade panel, doesn't matter). I also can't use macros/hotkeys or any of that because it's all locked to their ****-tastic CUE software. They either don't properly lab test their hardware/software before release, or they release their products anyway, knowing they will malfunction for a percentage of their customers. It's a shame, because I like the feel of my K55/M65 Pro mouse, but can't take advantage of any of the extra features.

Another example of their subpar testing/support costing them a sale.

Which in itself is patently ludicrous - I've used plenty of different keyboards, including my previous Microsoft Sidewinder gaming keyboard, and NONE of them have been as problematic as my current Corsair. You know why? Because they likely actually tested against common motherboard chipsets etc. during the design/testing phase - it's called due diligence. I'm not saying Intel USB controllers etc. are perfect - but when they are so common in motherboards, you would think Corsair would tweak their designs/power draw etc. to account for this.

This - my K55 would hardlock any app/game anything that polled controllers when any controller (Steam Controller, 360 controller etc.) was plugged into ANY port on the computer. Thinking it was a power issue I plugged the keyboard/receivers etc. into a separate powered USB hub - no dice, same deal. Miraculously, unplugging the keyboard would cause the app/game to spring to life, and this was without Steam/CUE running. The only way to eliminate this issue for me was to either unplug the keyboard each time I want to use a controller in a game, or to disable all the Corsair "HID" devices - the first option puts excess wear on the connector and I obviously lose the use of the keyboard entirely while playing controller-supported games, and the second option means I can use the keyboard but it's locked into the default "rainbow" lighting pattern and I lose all use of the macro/media keys. I still don't know why they maintain this is a Valve/Steam issue vs. taking a closer look at their hardware/firmware/drivers. I can say in my case it is 100% most definitely NOT an issue isolated to Steam/CUE.

It seems a common element in these discussions is either a complete lack of communication from Corsair, or they throw out the usual "update your firmware/re-install etc.". If your hardware/software/drivers are faulty, re-installing them isn't going to do squat - you need to FIX the problem.

It's obviously a hardware issue with the switches they are using in these mice, as evidenced by a user in this thread fixing the issue by bending the switch up slightly. They keep hoping they can fix a physical hardware issue with firmware, because they know it will cost them lot of money in shipping etc. to have to replace all the affected mice. Very similar issue with the game controller issue and their K55 etc. keyboards - they continually claim it's a Steam issue despite it happening when Steam isn't even open. It's a driver issue with THEIR HID drivers/Windows.

I'm hoping Corsair is working on a firmware/driver/CUE fix for this issue, but given the general lack of useful support in these forums, I'm not holding my breath. I certainly will not be buying corsair peripherals in the future unless they are dirt cheap.

Perhaps I wasn't clear enough - if I disable all the requisite HID devices, I have no problems, but then of course the lighting is locked into rainbow and I lose all extra functionality. I had thought the latest CUE release had solved the problem, but then attempting to play a game last night the controller was disconnecting UNTIL I disabled all the HID devices. So I have a choice of either unplugging the keyboard and losing the use of it while playing a controller game, or disabling the HID devices and losing custom lighting/all extra functionality - neither is ideal. One puts excess wear on the port/connector, and the other negates all extra functionality of the keyboard. As I said, this is issue is not isolated to Steam as they've often claimed, it's clearly an issue with their software/drivers conflicting with the OS/an OS update.

As I said, even with Steam and CUE closed - if either my Steam controller OR my 360 controller are connected to ANY USB port at the same time the keyboard is the "Set up USB Game controllers" panel hangs/freezes when I try to open it, the MOMENT I unplug the keyboard/disable all the Corsair HID devices the panel springs to life - I'm 99.9% certain this isn't a Steam-specific issue but a problem with their HID drivers. Also, if I try to launch a game that uses a controller with the keyboard plugged in, it will either refuse to launch/crash or freeze up a few moments/minutes after getting in game - when this happens. Again, this can be remedied by disabling all the "Consumer HID" devices the keyboard installs, but this removes all but the basic functionality of the keyboard and locks it into the default rainbow pattern. I had initially thought to try a fresh Steam install, but the fact that this problem occurs even with CUE and Steam closed tells me it's not a Steam issue as they often claim. I guess for now I'm just going to have to use it as a basic keyboard, as I'm certainly not going to unplug it every time I want to use a game that uses a controller - that constant unplugging/re-plugging would wear out the connector/port fast. Thanks for trying to help, it's sad that forum users seem to be of far more help than their official support that just regurgitate the same "we're looking into the problem" crap with no useful information.

So I think it's safe to assume Corsair either don't know what's happening, or don't care.

Also, is there any reason this keyboard/mouse needs to install 9 different "HID" device drivers for two devices?