TheDakk

Sweet deal, I had the same issue sort of, reinstalling it (several times) oddly fixed it for me as well.

https://help.corsair.com/hc/en-us/articles/360025348571-How-to-Reset-your-computer-mouse Google iCue Patch notes, usually can find version numbers that way. I gave you the last 2 versions prior to 3.35

Try my reply to you in the to other thread: https://forum.corsair.com/v3/showpost.php?p=1069553&postcount=25

Uninstall your current version (leave the user settings box unchecked) Download the version you want by replacing it in the URL. For example: https://downloads.corsair.com/Files/CUE/iCUESetup_3.35.152_release.msi https://downloads.corsair.com/Files/CUE/iCUESetup_3.34.170_release.msi https://downloads.corsair.com/Files/CUE/iCUESetup_3.34.161_release.msi If your lighting doesn't come back, you may want to try resetting your keyboard. https://help.corsair.com/hc/en-us/articles/360025465031-How-to-Reset-your-keyboard

The last two versions of iCue has broken hardware detection for my K70 RGB Rapidfire keyboard. When iCue starts up, it just hangs for 30 seconds or crashes. Last stable version is 3.34.161, reverted back to this version. I took System Logs export if needed. EDIT: I did some more testing. It seems as though sometimes after the iCue software upgrade it gets into a state where the keyboard or devices won't detect causing iCue to hang. I tried to uninstall 3.35 and revert to 3.34.161 without rebooting and experienced the same behavior. However, I then rebooted and the issue was resolved on 3.34.161. I then attempted upgrade again to 3.35 and this time it worked, no hang and devices were detected. I rebooted again to verify and my devices detected with no issues. Very strange!

Hey bud, follow this: https://superuser.com/questions/307678/how-do-i-extract-files-from-an-msi-package First, access an elevated command prompt, to do this: Click the Start button. Click All Programs. Go into Accessories. Right-click on Command Prompt. Select Run as administrator. When the UAC Prompt appears, click Continue. Once you have your elevated command prompt, input the following: msiexec /a drive:\filepath\to\MSI\file /qb TARGETDIR=drive:\filepath\to\target\folder using the desired locations to fill the above mentioned filepaths. Example: msiexec /a c:\testfile.msi /qb TARGETDIR=c:\temp\test

Just ran into this issue updating to 3.17 today. Never had any problems before and am running Windows 10 1903 as well. After the upgrade my machine went into a blue screen reboot loop with the error "INACCESSIBLE_BOOT_DEVICE". I was able to boot into Safe Mode successfully and tried to initiate a restore point prior to the install, but it failed with the following error: An unspecified error occurred during System Restore: (Installed DirectX). Additional information: 0x8007045b. Oddly enough, after that restore point failure, Windows booted fine even though I got the message that none of my system files were changed. 3.17 is still installed and everything appears to be working successfully (reboot, shutdown, ran games, etc.) I exported the system info and logs incase it's needed to help resolve this issue.

Confirmed, just upgraded to v.3.11, upon the next reboot it occurred. :(:

I made a post here about it a while back.. Corsair James was going to check into it, but never heard back :(

Just had this issue happen on my PC, here are details from the event log: Faulting application name: iCUE.exe, version: 3.10.125.0, time stamp: 0x5bf8698e Faulting module name: libGLESv2.dll, version: 0.0.0.0, time stamp: 0x5a5da43b Exception code: 0xc0000005 Fault offset: 0x000da111 Faulting process id: 0x2170 Faulting application start time: 0x01d4a429fcd93d3a Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe Faulting module path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\libGLESv2.dll Report Id: 437e189f-2afc-49b1-a9b6-3acb58f18548 Faulting package full name: Faulting package-relative application ID: Fault bucket 1383692415130177826, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: iCUE.exe P2: 3.10.125.0 P3: 5bf8698e P4: libGLESv2.dll P5: 0.0.0.0 P6: 5a5da43b P7: c0000005 P8: 000da111 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB4A7.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB5A2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB5B3.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB5B1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB5C1.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_iCUE.exe_583f6d93fabcfa925ebf5ec2c8a5329b71cca2c_cce0e3ef_4fe2b860 Analysis symbol: Rechecking for solution: 0 Report Id: 437e189f-2afc-49b1-a9b6-3acb58f18548 Report Status: 268435456 Hashed bucket: df85e9fb4d75f3f0f333dceba23c9122 Cab Guid: 0 Faulting application name: iCUE.exe, version: 3.10.125.0, time stamp: 0x5bf8698e Faulting module name: libGLESv2.dll, version: 0.0.0.0, time stamp: 0x5a5da43b Exception code: 0xc000041d Fault offset: 0x000da111 Faulting process id: 0x2170 Faulting application start time: 0x01d4a429fcd93d3a Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe Faulting module path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\libGLESv2.dll Report Id: a20e0953-d7b5-49b1-8436-18554686b0ba Faulting package full name: Faulting package-relative application ID: Fault bucket 2236802420129695949, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: iCUE.exe P2: 3.10.125.0 P3: 5bf8698e P4: libGLESv2.dll P5: 0.0.0.0 P6: 5a5da43b P7: c000041d P8: 000da111 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB93B.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA26.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA37.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA37.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBA48.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_iCUE.exe_1c57db45d8072e422499226aa9de5c1eb65c113_cce0e3ef_56e2bbfa Analysis symbol: Rechecking for solution: 0 Report Id: a20e0953-d7b5-49b1-8436-18554686b0ba Report Status: 268435456 Hashed bucket: a5690e3df87270d0ef0ab7f3349088cd Cab Guid: 0

I found that if I restart iCue application after my machine loads (after Steam loads too), the lighting resets and is OK afterwards. Are you able to confirm this happens for you as well?

Interesting, I have Steam installed as well (what gamer doesn't!?). Waiting to see if it happens with v3.10!

This usually happens to me after a cold start. Every time I start my PC, I have to double check to make sure the fan curves are working, lighting is working, etc. Quite annoying. I've found that killing the application and restarting it after seems to make it a bit more stable. If I restart the Corsair service, my fan curves on my Commander Pro bug out and I have to play around with switching profiles before it works again. No response on my ticket or indication they are working it. I've uploaded many logs as well to help resolve the issue if need be.

I think I have the same issue, have a support ticket as well. http://forum.corsair.com/v3/showthread.php?t=182848