BradB111

I have a slightly different issue but again related to 5.8.130 as this never happened previously. Looking at the log it fails during USB hid initialisation. I'll see the full icue window with 1 device briefly before this crash. Only seems to happen about 30% of the time though. Which is still to often. Give us the option to roll back while a solution is being worked on as this is extremely frustrating.

Thankfully yes this works for me. After removing all of the unnecessary packages.

This seems to have completely solved my issues I've been having for a while now. Many thanks for detailing this. I am extremely disappointed it has had to resort to this though. Would it not be at all possible to have a plugins list within iCue where you can pick and choose the appropriate ones for you, and in the case of the plugin that controls the the sync between corsair and ASUS motherboards have it completely independent from the ASUS installations so that a user can do away with any of the 2 terrible options available to us from ASUS? Armoury crate will just not respond to any changes made in iCue anymore although the the motherboard and all available zones show up. Or Aura which now works following the above but refuses to open to set the hardware lighting meaning that when my pc is between boot and iCue opening I have to put up with a ridiculous rainbow show on the motherboard. I have invested heavily into the corsair ecosystem and I am unfortunately not having the same premium top tier experience I have come to expect over the last 7+ years having corsair products with regards to this specifically. Now I can completely understand this is largely the fault of ASUS however if even the old aura sync is displaying these issues and that hasn't been updated in a considerable period of time whereas this was all working fine previously, this says to me that this would have been introduced by a software change from corsair if the versions from ASUS have remained unchanged. Would native support be completely out of the question? or even an installer which can completely remove any instance of ASUS software and install only the necessary software layers to allow the iCue integration to work. I ask this because I know there will be individuals who choose corsair and ASUS products for their reputation of producing high quality components however they may not feel comfortable with going anywhere near the "ProgramData" folder. Corsair, an indication to ASUS that your users feel let down will go down much better than 100 separate emails to ASUS from users. This has been one of the best collaborations between companies I have seen within the PC component space. It's a shame that a once brilliant integration that worked more or less flawlessly has led to users trying to find answers to restore previously available functionality.

Todays update for "AURA Kit" via armoury crate made no difference.

ASUS Crosshair VIII Impact, 5950x, 3090 FTW3 Ultra, Corsair SF750 Nothing seemed to work to resolve the disconnects and non-detection apart from using a separate USB Hub, I use the NZXT one however I have not needed to power it. Commander pro, Lighting node pro, Lighting node core all working fine.

Thank you for the clarification.

Any news on this being fixed? I shouldn't be expected to run an outdated version of software to regain compatibility. It works but takes approx 2 mins after startup before the board is recognised and will not launch to let me configure hardware lighting. So to ensure I don't have lights on in the middle of the night I am forced to use armoury crate (no the bios option 'Stealth mode' doesn't work, It's constantly overridden by Aura and I can't open it to change that). Not only this but half the time one or both of my DIMMs will be incorrect due to the conflict and I don't have Aura to start with windows. It was working completely fine no more than 1 month ago. I've lost count of how many times I've reinstalled windows. Specs: 5950x / 3090 FTW3 Ultra / NVME Gen4 RAID0 Storage / Crosshair VIII Impact (So it's not my specs) On another note when is 'Corsair.Service' going to be fixed so that any time I move my mouse in game when set to anything over 500Hz I don't lose 10 - 15 fps?

Yeah I converted all my EK stuff to MX2.54 Dupont connectors by re-terminating them for this reason. No way to do that with the MOBO LEDs though :/

Reinstalled armoury crate multiple times, iCUE multiple times, windows from UEFI via USB. No change, Only thing that works is uninstalling armoury crate and installing legacy aura sync. BUT.... That for some reason breaks my Vengeance pro RGB.

Just like to add my ASUS Crosshair VIII Impact has recently stopped responding to iCUE for me still shows up as a device though ("ASUS Motherboard"). One whole windows reinstall later I find this thread, ah well...

Any update on this? X570 Crosshair Impact 5950X Same issues as mentioned above.

Please can this be considered? Especially given you have a recent product release that can benefit from this feature also: https://forum.corsair.com/v3/showthread.php?t=189791

It seems this isn't supposed to be a feature although I would completely love it to be. and almost created a thread for this very suggestion. The issue seems to be is that the Void headset is seen by windows to always be available to use (It's always available to select via windows output even though the headset isn't turned on. as it sees the receiver as an available output regardless) The only software that seems to be able to detect if the headset is connected is in fact iCUE. I would love the option to turn on such an auto switch function.so: ---Turning On--- Audio playing through speakers for example User turns on the headset Connection is made iCUE recognises this and switches the windows audio output to the VOIDs on the users behalf Audio now coming through the headphones ---Turning Off--- Audio playing through VOIDs User turns off the VOID Headset Connection is lost iCUE recognises this and switches the audio output back to the original device in use prior to original connection. Audio is now playing through the original device. I would have thought the disconnection detection should have a timeout period of maybe 5 seconds for those (extremely) rare moments the connection is lost for a brief period to ensure it doesn't auto switch back to the speakers when the user didn't intend for this to happen. Unless the firmware in the Headset can be updated OTA to send a "I'm being turned off now" signal back to iCUE? Maybe similar can be introduced to turning on although less necessary as once connection is made it can be safe to assume the user would like to switch to the VOIDs as their output device. Surely this can be added as a feature, It would certainly add to the user experience as opposed to manually switching like I'm finding is necessary to change the output. When using Steam in home streaming Steam is able to switch outputs on the users behalf so I'm assuming something similar can be implemented for For the VOIDs and other iCUE compatible headsets? I would love to see any feedback from Corsair regarding this. I'm assuming this can all be integrated within iCUE to achieve such function? Many thanks.

It seems this isn't supposed to be a feature although I would completely love it to be. and almost created a thread for this very suggestion. The issue seem to be is that the Void headset is seen by windows to always be available to use (It's always available to select via windows output even though the headset isn't turned on. as it sees the receiver as an available output regardless) The only software that seems to be able to detect if the headset is connected is in fact iCUE. I would love the option to turn on such an auto switch function. so: ---Turning On--- 1. Audio playing through speakers for example 2. User turns on the headset 3. Connection is made 4. iCUE recognises this and switches the windows audio output to the VOIDs on the users behalf 5. Audio now coming through the headphones ---Turning Off--- 1. Audio playing through VOIDs 2. User turns off the VOID Headset 3. Connection is lost 4. iCUE recognises this and switches the audio output back to the original device in use prior to original connection. 5. Audio is now playing through the original device. EDIT: I would have thought the disconnection detection should have a timeout period of maybe 5 seconds for those (extremely) rare moments the connection is lost for a brief period to ensure it doesn't auto switch back to the speakers when the user didn't intend for this to happen. Unless the firmware in the Headset can be updated OTA to send a "I'm being turned off now" signal back to iCUE? Maybe similar can be introduced to turning on although less necessary as once connection is made it can be safe to assume the user would like to switch to the VOIDs as their output device. Surely this can be added as a feature, It would certainly add to the user experience as opposed to manually switching like both the OP and myself are finding is necessary to change the output. When using Steam in home streaming Steam is able to switch outputs on the users behalf so I'm assuming something similar can be implemented for For the VOIDs and other iCUE compatible headsets? I would love to see any feedback from Corsair regarding this. I'm assuming this can all be integrated within iCUE to achieve such function? Many thanks.