vexed

I used to have a similar problem where my entire case and headset would light up but my k55 would be entirely dark. i raised it with WP engine via the steam discussion section and it now works without issue. My only issue with WPE atm but a workaround has resolved it would be if i put the pc into sleep / windows key + l (lock) no rgb would turn back on until i restarted WPE. The workaround i found was to add a delay timer to the plugin starting (30seconds) in settings and ticking the option for safe start after hibernation in settings and it works perfectly fine now.

Is there a fix for the Void pro wireless randomly disappearing from icue after win 10 being locked or boot. this issue is very inconsistent and somewhat random. It happens once or twice a week at most but unless i unplug the dongle and plug it back in icue doesn't register the headset being on but in windows it shows fine. i've never had this issue up until the last 2 versions of icue and i really dont want to have to revert back to my last "stable" version of icue which by now is pushing 2 yrs old just to avoid this problem. - Vex p.s My k55 also suffers with this issue but much less in frequency at around twice a month

Well.... I've come across an issue with the Void pro headset. when i mute the mic on the headset via the button or lift the mic up the headset turns mic feedback off when muting the mic, then turning the mic on it turns mic feedback on at least from voice prompts but i do not hear any feedback when on or off. Seems it could be related to the wrong voice prompt being used or something else - Vex

So..... i have to say i am pleasantly surprised by the lack of issues i am currently having. Cpu usage is where it should be instead of randomly taking up 2-6% of all cpu load for no reason. This is the only issue i have so far encountered after using the update is my Void pro wireless headset requires me to turn it on and off then on again as icue doesn't pick it up first time round. i have ran the repair option which made zero difference and everything is up to date driver wise elsewhere. The headset being detected in windows just not in icue itself and thus doesn't offer the 5.1 sound instead 2.1 until i turn it off n on again. Minor issue but an issue non the less. The last version i had installed was 3.24.52 which was my go to revision after the numerous issues since then but so far it's going ok and i hope it stays that way. We shall see Edit: - Not sure if this is the reason why things are working correctly compared to others in this thread but i have "enable plugins" turned off in icue's settings and my RAM etc are all acting fine. It is prob unrelated but it's worth a shot - Vex

Also suffering with this issue with my LED strips which are plugged in via my commander pro where the LED's. As soon as i revert back to an older version the problem no longer is there Also having the same issue when my void wireless dongle is plugged in and icue crashes immediately. I guess i'll rebuild my profile again and revert back to 3.24.52 which is far to old but seemingly the only build i've not had too many issues with. i really hope a hotfix for the above wont take until next release in a months time as i would really like to stop having to use very old builds just get things to function correctly. I have tested this across 2 builds of windows 10 both have the above issues across 1909 & 2004. I figured it may just of been a microsoft "feature" but seemingly not - Vex

I too have multiple backups of the different windows builds given how unstable microsofts updates can be :laughing:. I have since tried all icue releases from the last 16 months with win10 2004 and they all result in bsod's, errors or just eats cpu like its secretly mining crypto :laughing:. Whereas on 1909 the only "stable" build i found which doesnt eat cpu aka it stayed below 2% which is very high to say the least was build 3.24.52. But other people report they have issues with that build also. But at this point 3.24.52 is well over a year old and shouldn't be required to stay with older builds just to mitigate a widely reported issue across now multiple releases. Corsair your products are great, your support teams are great but by god whoever you have outsourced the software for icue need a wack round the head :laughing: to fix this widely reported issue. - Vex

As a fellow 570x owner i use 6 LL fans wired into a commander pro with the H115i fans hooked onto the sys fan header (using stock fans) and the usb from the cooler onto the commander unit and the commander connected via the usb header on the board. i used a guide Zotty made which was crazily helpful located here https://forum.corsair.com/v3/showthread.php?t=173880 wiring diagram Zotty did is here https://i.imgur.com/XSDWsneh.png to how i've wired them up just add the h115i to the mix - Vex

*Signs* I use both the k95 and k55 on my dual system setup and its irritating when everything is in sync apart from the k55 and defeats the purpose of all the lighting and rgb if its all out of wack

Just updated to 3.25.60 from 3.24.52 and icue is crashing as soon as i load any game if i leave icue in the system tray however if i leave it open in the background it doesnt. safe to say i'll be rolling back to 3.24.52 and hoping it resolves the problem. not sure if this is an icue issue or an issue as some other threads are saying its nvidia's ultra low latency mode causing it but i have it turned "off" /shrug - Vex **Edit** rolled back to 3.24.52 and the issue has gone away after uninstalling 3.25.60 then rebooting and reinstalling 3.24.52. only downside is that part of my profile within icue is now missing (mainly the macro's on my scimitar but that's easily resolved within 5 minutes everything else was intact)

I know this post is over a month old but I also have a k55 as a secondary keyboard and have the exact same issue. As soon as wallpaper engine is running my fans, ram, Aio, led strips headset and mouse all sync with wallpaper engine but the k55 just turns all the LEDS off and goes dark. Sort of defeats the purpose of having a backlit keyboard This is the information i have gotten from Tim the developer of Wallpaper engine. Not sure if this is an icue issue, a k55 issue or a wallpaper engine issue :dunno: - Vex

Doesn't seem like the Void headsets are going without plenty of issues. like bricking them, updating the firmware causing issues like leaving it in bootloader mode etc. I for one will not be purchasing another corsair branded headset after the lack of support & software update wise for the Vengeance series since it started, My biggest problem has been the lack of communication on these issues. I have been using the Razor software also since moving to windows 10 and it behaves like a different headset entirely with great audio & no deafening volume. I used to love your products corsair, even outfitting my entire rig in corsair products (where i could) but this is just the last nail in the box for me.

I've taken up using the Razer's software to control my v2100 after it been suggested to me by numerous user's about the driver problems, so far it works great and doesn't cause me to go deaf from extreme volume:laughing:. I'll go back to using corsairs one when these issues are fixed.

The drivers were published in September 2014, We are now in May 2015 and still no word or fix to issues that have plagued these drivers since windows 8.1's release. If someone from corsair could answer with "we are working on solving these problems" but so far nothing has been said. I think in future i will just purchase from another manufacturer, i expected alot more from corsair as i have used many of your products in previous builds but this is just a joke.

Any news on a update or.... anything? c'mon :(

My experience with customer service to do with things like RMA have been overall very good, since i had to RMA my V2000's three times due to the cracked earcup issue they suffered with. However the driver's, forum communication and general speed of development of these drivers on issues that have been requested since 8.1's release has been piss poor. It's a shame that the drivers are what lets this headset down. But Link suffers with the same problems that its the software side been the issue. Which is now reportedly changing and been "fixed" This overall software issue does concern me with windows 10 been released in the summer of this year and may make my headset unusable if the drivers do not work as they did for a few months after 8.1's release. I do hope corsair either puts more manpower on the job and sorts this issue out soon because having to use a competitors software to use your hardware function the way i could expect a $20 headset from wall mart to function is bonkers :confused: or at the very least be more vocal on the forums saying "We are aware of these issues you can expect something by 3 months from now" it wouldn't be perfect but at the very least it would be something.