Griff_

What gets me is the complete ignorance of the issue which I have presented. There isn't even an acknowledgement that a problem exists, and thus it appears there is no hope to ever see any improvement. Well, thanks very much Corsair Notepad. You have cemented my commitment to recommend against Corsair products in favour of literally anything else. In order to avoid this, you could have: Acknowledged my frustrations and attempted to understand my grievances Pointed to iCUE2 in an attempt to assert that my grievances may end up being resolved Provided relevant advice and alternatives to a "clean-install" every time something goes wrong during every update However, you chose to avoid this topic entirely. Brand loyalty? I think not for you Corsair. You may never expect another positive recommendation from myself due to the UX of your software. I'm done, and will begin to transition away from your product lines in favour of more stable alternatives. Regards, an unsatisfied customer.

Much wow, very help. Nice way to avoid the topic Mr. Corsair Notepad. Do you have anything relevant to add?

Why do I feel so anxious every time I hit the "Update" button? Hi all, I'm sorry, but I need to let this out somewhere for fear of destroying hardware. First, let me begin by saying that this is not caused by a one off incident, but has been progressively eating at me update after update, to the point that I put off updating iCUE as long as I possibly can, until a bug that I am already experiencing absolutely must now be fixed. I do this, knowing full well that I am likely only swapping one bug for another different bug. Most recently, I have been experiencing what may only be described as an audio driver crash, which I believe is caused by alt tabbing between applications, which kills both the audio output and microphone input for discord. This problem is incredibly inconsistent, and difficult to track down, as it appears to happen "at random". Finally, after annoying my friends, and being annoyed at these events which cause me to lose communications, I decided to bite the bullet and update my iCUE. So, first thing's first, as my previous experience has taught me, we backup %APPDATA%/Corsair in the likely event that something will be broken beyond reasonable usability, which will undoubtedly force me to downgrade my iCUE version to something a little less "beta". If anyone is unaware why you need to backup this folder, its because, corsair in their infinite wisdom have decided that even the most minor change between versions is worthy of invalidating your ENTIRE personal configurations, macros and profiles, instead of simply failing to parse specific configs/settings which do not make sense. Now that we have our backup, we can go ahead and fire off the update and cross our fingers and toes that nothing breaks this time... But, we all know that's not the case as I would not be posting here otherwise. Upon completion of the update, I reboot as requested, and so far everything seems to work as normal. I eventually hop into discord and attempt to PTT to speak with my friends and... No voice activity is indicated from me. Going to discord's settings I double check my keybind, and the bind is unchanged. I attempt to set the bind again just in case, and find that I am now unable to input any extra mouse inputs, such as mouse4/5 (thumb backward/forward). So I debug this issue further and double check the keybinds in windows explorer and chrome, and sure enough, the forward/backward functionality is entirely missing - uhh oh! So, as per usual, I figure there's always the safe bet of regressing to the previous version I was stable with, but decide to take a quick google just to make sure there isn't something obvious I've missed, and eventually land upon: https://help.corsair.com/hc/en-us/articles/360025168512-Mouse-Button-Is-Not-Working Hold on, what do we have here? Step 2: Perform a clean reinstallation of Corsair Utility Engine. Oh joy! Now I get to wipe all of my profile settings and customisation and start from scratch EVEN THOUGH I HAVE A WORKING BACKUP! So, as per the instructions, I remove iCUE, purge the appdata's, purge and leftover metadata in programfiles, reboot, re-install, reboot, and tada! My thumb buttons work again! At this point, I'm just glad that my buttons are working, I've not even begun to contemplate and test my alt tabbing voice comm issues yet. So, at this point I've just about had it with iCUE, yet find myself with 3 devices from Corsair, and while the physical products I find to be fit for use, I am now seriously considering revoking all my recommendations of corsair products due to piss poor software, drivers, and UX. So, Corsair, here you have it, you have one shot, one last opportunity before you lose a customer (and their recommendations of your hardware) who loves your physical products, who is absolutely distraught with the horrendous UX that you inflict upon all of your userbase. What exactly do you have to say for this pitiful excuse for device management software?

What bull****. Just came to this thread from google suffering from the same issue. Corsair please, get your **** together. This is a basic feature. I really hope the new iCUE thats being beta tested gets a new macro threading implementation.

Can confirm nvidia's 446.14 driver fixes this issue as well as the right click of iCUE is now instant instead of having a severe lag between click and display. Sometimes, it appears that it really is "Not my problem". I understand corsairs perspective here too, as what nvidia are doing for their overlay is hooking into all processes which use a graphical window / DX handle. iCUE just happened to be one of them. This doesn't mean that iCUE should not use a non standard windowing system, but it does mean that nvidia need to refine how they are detecting which windows they capture, and they did, and now everything is fixed :)

I don't suppose you guys will have a beta version before christmas do you? I'd be very interested to get this issue resolved, & submit any feedback required.

Normally, iCUE works well and does exactly as you might need.

Seems you are right, after further usage of the method i posted above, i have discovered this workaround only kicked the can further down the road. With all macro's set up for the escape row, the "unconsented macro binding" issue has now mapped all further macros in the actions library to the numeric row, just bellow the function keys. For some weird reason the software is now overflowing the problem further down the rows of the keyboard, exclusive of PGUP / numpad sections. I assume that unless I want to manually bind all of my keys then the only real solution, assuming that I do not want to wipe my macros, is to create a temporary profile to store my actions library so that i can keep the library empty.

See: https://forum.corsair.com/v3/showpost.php?p=1024341&postcount=26 for my workaround which keeps your actions library

Thank god, I'm not the only one. Eversince I updated to 3.22.74 i've experienced the same issues, and what i've discovered is: Actions LIBRARY are mapped to the keyboard's escape row in order. Pressing Escape will execute Macro #1, pressing F1 will execute macro #2, and so on. Reordering the list will be applied upon restarting iCUE. The workaround is to enumerate all Fkey macros manually and keep them ordered, so that when you press F1, the F1 remap to F1 is executed (if this makes sense). Its a real pain and i've honestly no clue how something so breaking could get through testing. Please fix this ASAP Corsair!. UK Keyboard layout on Corsair K70 using "English (American English)" iCUE setting in Windows 10 18362.476

The issue is not the battery being full or not. The issue is not being informed when it is full, the result is simply the annoyance that i need to turn off the power to the headset and check the power level in the settings manually before turning it back on. The result of which is preferring to leave it plugged in rather than go through that effort, which essentially turns it into a wired headset. I would really like to know if anyone knows where i can find legacy drivers/firmware so i can get the audio cue working again. I really dislike not having the cue and desperately want it back.

After another 4 days of use, it has still failed to provide "Batter Full" notice, when one day i left it plugged in for 6~ hours.

Did as was suggested. Its been plugged in for 4 hours and has still not output "Battery full" even though it took only 3 hours on first charge. Unplugging and checking battery shows 88% even after 4 hours. Similarly its still running 0.64. What exactly is holding mute supposed to do?

Hi all, after a bit of googling i was unable to find any similar issues, so I came here to ask: I recently bought the corsair HS70, and from the moment i charged it to full (3h) and then turned it on, I was incredibly satisfied with its audio quality, performance, longevity, and quality of life / utility features. Literally could not be happier with my very first wireless headset. However: perhaps maybe 1/2 weeks after my purchase, I applied another firmware update, and ever since then (not sure if coincidence or not) the "Charge complete" notification is absent. When I plug the headset in, it will cue "Charging battery". Then at multiple periods throughout its charge it will cue the same, at seemingly random intervals. Then from what i can tell, when its actually at full battery it will cue "Charging battery" twice in a row, I think? I experience no battery degradation, and the charge seems to take as long now as it did on the second day of use, and similarly can last entire days of usage and still not run out of battery. The only thing thats been niggling at me is this lack of "charge complete" which would prompt me to disconnect the charge cable - essentially turning the headset into a wired headset for the portion of the day where i forget / have no reason to disconnect the USB cable. Similarly, if i leave the cable in and disconnect after 5 hours, the battery level shows at 93% or 90%. However leaving it in for 2 hours~ and removing shows a battery level of 100%? Can't be certain this is true in all cases, I have not had the patience to test extensively. So I come here to ask you all, has anyone else experienced the same? Using firmware 0.64? And similarly I was unable to find legacy firmware versions, so I've currently been unable to test previous firmware images on the device, which i would very much like in order to rectify this issue. Does anyone know where its possible to obtain previous firmware versions for the device?