Jump to content

SajuukCor

Members
  • Posts

    40
  • Joined

Reputation

10 Good

About SajuukCor

  • Birthday 07/24/1984
  1. I've already been on the fence with Corsair since iCUE 3.x came out. For years I've tried to work with them to send logs and specs to fix issues of crashing, buttons/macros not working, and high system resources being used. But now I see they now no longer care about the quality they put into their hardware and would rather us to pay them every 3-4 years for the feeling of staying supported. I have a number of Corsair products with my current build, including a Void Wireless headset and H80i v2 cooler, which are now no longer supported in iCUE 4.x software. The H80i v2 is still being sold on various retailer websites in New condition, the most notable being Amazon (shipped and sold by Amazon) with no mention that the cooler is considered no longer supported and is at End of Life. It's not like a new Windows operating system was released that would prevent software support. This is to force PC users to "want" the newest and latest hardware. It makes people like us who invested in the brand, quality, and ecosystem of Corsair to feel left behind because Corsair hardware is so interconnected and dependent on the iCUE software. Yes, you give us the option of staying on v3.38.61 but there are still constant and persistent issues even with that build to which we can no longer hope will be worked on. What's the reason why a keyboard won't work with newer software? A CPU cooler? A mouse? A headset? I can understand firmware support being dropped on a device considered "End of Life" but that shouldn't prevent said device to be held at the gate because of software. Even video cards which we would consider ancient are still supported on currently released software and drivers. This doesn't feel right to brand loyalty and, at least for me, puts a bad taste in my mouth for investing in products I thought wouldn't have an issue being supported even after iCUE 3.x introduced tighter software dependency and integration. As always the best way to show dissatisfaction with the decision is to talk with your wallet, and that's what I intend to do with future builds.
  2. I still hope one of these patches will fix Actions not working after bootup. One day...
  3. Corsair Scimitar Actions still broken on reboot where they won't work, even when the profiles are saved to the onboard mouse hardware. I feel a bit of insanity over the years and years of this bug, wondering on the second, the third, the fifth reboot will activate my Actions. I'm tired of giving logs and getting no answers.
  4. I've been trying out the Hardware Profiles and noticed that too. All the more reason to show that the iCUE software is not working correctly. Many of us can't remove iCUE because we need it for the keyboard and headsets as well, so this issue still needs to be resolved.
  5. iCUE v3.27.68 still has this issue.
  6. Bumping because I found that I posted these bug issues, along with others, since 2 years ago now. This needs to be looked into please.
  7. I wish it was that simple for me. This problem has been going on for years now since the release of v3 of iCUE.
  8. This bug has been going on for YEARS. Bringing the problem to light again to see about it finally getting it fixed. Problem: After rebooting the computer iCUE will say macros are not working (specifically for me the Scimitar side buttons) and try repairing the installation, which doesn't work. You have to continue to reboot the computer until something clicks for iCUE to register and execute the macros correctly. I've tried everything to fix it, from a complete system refresh to direct removal of everything Corsair on the computer. Here's the error log from the debugger: 2020-03-10 03:22:32.2612 | 20 | KAPISI | 3.26.0.5 | PowerManagementWatcher | -> System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.SinkForEventQuery.Cancel() at System.Management.ManagementEventWatcher.Stop() at CorsairLink4.Common.Shared.PowerManagementWatcher.Dispose(Boolean disposing) 2020-03-10 03:24:12.4576 | 5 | KAPISI | 3.26.0.5 | PowerManagementWatcher | -> System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.SinkForEventQuery.Cancel() at System.Management.ManagementEventWatcher.Stop() at CorsairLink4.Common.Shared.PowerManagementWatcher.Dispose(Boolean disposing) 2020-03-10 03:25:46.7904 | 17 | KAPISI | 3.26.0.5 | PowerManagementWatcher | -> System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.SinkForEventQuery.Cancel() at System.Management.ManagementEventWatcher.Stop() at CorsairLink4.Common.Shared.PowerManagementWatcher.Dispose(Boolean disposing) 2020-03-10 03:27:26.1077 | 5 | KAPISI | 3.26.0.5 | PowerManagementWatcher | -> System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.SinkForEventQuery.Cancel() at System.Management.ManagementEventWatcher.Stop() at CorsairLink4.Common.Shared.PowerManagementWatcher.Dispose(Boolean disposing) Windows 10 v1909 16GB RAM ASUS Z270-K Motherboard All my drivers and software are up to date.
  9. Same issues here. Traced my problems to a svchost.exe running high with audiodg.exe, about 25-50% CPU. Switching audio output from my Corsair VOID to my monitor speakers fixes the issue until I switch back to my VOID again. This issue has been in the iCUE software since 3.17. I've been running 3.16 and I'm tired of trying to see if the software devs are fixing these issues D: Edit: So after fooling around with some registry areas and tracking down specific Corsair files that were not deleted once iCUE was uninstalled I think I might have a solution to offer: 1. If you have a Corsair headset, unplug it. 2a. Backup your iCUE settings. 2b. Uninstall iCUE and reboot. 3. Go to your C:\Windows\System32\ folder. You'll find 2-3 .dll files starting with "Corsair". Delete them. 4. Make sure iCUE didn't leave anything in %programdata% or the install location it was in. 5. Reinstall 3.20 and reboot. 6. Plug your headset back in once the computer and iCUE are loaded. What I'm thinking is there was a bad driver in one of the installers and it wasn't being deleted when iCUE was uninstalled. Hopefully it fixes your issue.
  10. Installed this new iCUE software, gave it a reboot, and after a short while (between 5-10 minutes) all my Corsair devices disconnected from my system. Couldn't type at all and all the lights were out like the cord was unplugged. Uninstalled and reinstalled v3.16.56 and everything is running correctly again, or as correctly it can get since I have to test to see whether my Scimitar side buttons work or not with each reboot. There are constant, repeat constant issues with each iCUE release and I cannot under good conscience recommend anything Corsair to builders. Edit 07/24: Now there's no sound from my VOID headset after having my computer asleep. Need to uninstall and reinstall the v3.16.56 and pray they work again. This is just getting insane.
  11. Installed through the updater and having issues with a drive not mounting again. Need to revert back to 3.5 :/
×
×
  • Create New...