Asylum Posted April 24, 2018 Share Posted April 24, 2018 I have a Commander Pro with 3 HD120 fans installed, a H100i v2, and a hx1200i. None of these devices will show up in iCUE. I have went through the various threads and googled possible fixes but none of the fixes or suggestions i found seemed to work for me. I even completely reinstalled windows and tried installing iCUE before any other drivers or programs and it still refuses to detect any of my devices but, corsair link works just fine. lol Link to comment Share on other sites More sharing options...
DevBiker Posted April 24, 2018 Share Posted April 24, 2018 Which version of Corsair Link are you using? If iCue is installed, Link should surrender control of the devices; if it's not doing this, you have an older version of Link and it's causing conflicts. Otherwise, can you export your logs and system info from iCue? (Under Settings ... there is a button at the bottom). Link to comment Share on other sites More sharing options...
Asylum Posted April 25, 2018 Author Share Posted April 25, 2018 Thanks for the help. The version of CL I'm using is "4.9.7.35" there doesn't seem to be a newer version available. +here are the logs from iCUE edit:i tried version 3.2.87 and it still is refusing to detect any of my devices.log1.zip Link to comment Share on other sites More sharing options...
DevBiker Posted April 25, 2018 Share Posted April 25, 2018 OK, that's the correct version of CL. And to confirm ... CL sees your devices but iCue doesn't? Is CL surrendering control once you have iCue installed? With your HD fans, are they controlled by a Lighting Node Pro or the push button controller? Link to comment Share on other sites More sharing options...
Dan_O Posted April 26, 2018 Share Posted April 26, 2018 I had this kind of problem but after I shut down EVGA led sync from booting on windows start then the problem was solved. If you have EVGA led sync on try to stop it from running on windows start and restart your pc. Hope this helps! Link to comment Share on other sites More sharing options...
Asylum Posted April 26, 2018 Author Share Posted April 26, 2018 OK, that's the correct version of CL. And to confirm ... CL sees your devices but iCue doesn't? Is CL surrendering control once you have iCue installed? With your HD fans, are they controlled by a Lighting Node Pro or the push button controller? correct, CL works just fine but iCUE doesn't. what's even stranger is yesterday i just installed a brand new x470 C7H motherboard and reinstalled windows and just installed iCUE and still it refuses to detect any of my devices. my HD fans do use the lighting node that came with them in the box which is then chained to my commander pro. Link to comment Share on other sites More sharing options...
DevBiker Posted April 27, 2018 Share Posted April 27, 2018 OK, take a look at USBDeView (http://www.nirsoft.net/utils/usb_devices_view.html) and see what it shows. Corsair devices have a Vendor ID of 1b1c. This will tell us if the system is detecting them on USB. Link to comment Share on other sites More sharing options...
Asylum Posted April 27, 2018 Author Share Posted April 27, 2018 OK, take a look at USBDeView (http://www.nirsoft.net/utils/usb_devices_view.html) and see what it shows. Corsair devices have a Vendor ID of 1b1c. This will tell us if the system is detecting them on USB. ok, here is what USBDeview is showing for my devices with that device ID. As far as i can tell everything is showing up mostly.. the blank one at the top is probably my power supply. Link to comment Share on other sites More sharing options...
DevBiker Posted April 27, 2018 Share Posted April 27, 2018 Yes, 1c08 is the HX1200i PSU. Now that we've verified that the devices are all present, our next step is to get a log from iCue. Can you go to Export System Info and Logs ... and then add the service logs from %ProgramData%\Corsair\CUE? Link to comment Share on other sites More sharing options...
Asylum Posted April 27, 2018 Author Share Posted April 27, 2018 Yes, 1c08 is the HX1200i PSU. Now that we've verified that the devices are all present, our next step is to get a log from iCue. Can you go to Export System Info and Logs ... and then add the service logs from %ProgramData%\Corsair\CUE? ok thanks! here are the logs that you requested.infolog.zipService_Trace.log Link to comment Share on other sites More sharing options...
DevBiker Posted April 27, 2018 Share Posted April 27, 2018 Is there a service_error.log as well? The trace seems to indicate that the service isn't detecting them either. Which is odd ... but could possibly be due to WMI database corruption/issues. I would hope that we'd see something in the error log from that. Link to comment Share on other sites More sharing options...
Asylum Posted April 27, 2018 Author Share Posted April 27, 2018 Is there a service_error.log as well? The trace seems to indicate that the service isn't detecting them either. Which is odd ... but could possibly be due to WMI database corruption/issues. I would hope that we'd see something in the error log from that. There isn't any "service_error.log" files in that location there is only that "service_trace.log" file. There's a "debuglogging" file in the settings folder but that's about it for the ProgramData folder. Link to comment Share on other sites More sharing options...
DevBiker Posted April 27, 2018 Share Posted April 27, 2018 And can you verify that the Corsair Service is running? This is quite odd. And Link picks everything up just fine? For the Link devices, both iCue and Link use very similar, if not identical, detection routines. So it's truly strange that one sees them and the other doesn't. Link to comment Share on other sites More sharing options...
Asylum Posted April 27, 2018 Author Share Posted April 27, 2018 And can you verify that the Corsair Service is running? This is quite odd. And Link picks everything up just fine? For the Link devices, both iCue and Link use very similar, if not identical, detection routines. So it's truly strange that one sees them and the other doesn't. link works great for controlling and monitoring my devices. I attached a couple more screenshots verifying that the service is running. the other two are what i see when i use CL vs what i see when i use iCUE. Link to comment Share on other sites More sharing options...
DevBiker Posted April 28, 2018 Share Posted April 28, 2018 Unfortunately, at this point, I'd have to suggest that you stick with Link and give the next iCue build a shot. :-( We've got nothing from the logs that would help us understand what the error is - and it's truly bizarre that Link picks up the devices but iCue doesen't. Link to comment Share on other sites More sharing options...
Whisky Lima Posted April 28, 2018 Share Posted April 28, 2018 Hey just out of interest, are all of your non responsive devices connected through the commander pro? If so, is there anything connected to it that does work with iCue? Link to comment Share on other sites More sharing options...
Asylum Posted April 28, 2018 Author Share Posted April 28, 2018 Hey just out of interest, are all of your non responsive devices connected through the commander pro? If so, is there anything connected to it that does work with iCue? no, nothing works with iCUE at all unfortunately. I tried plugging my h100i v2 into the second internal usb header instead of the commander pro but that also didn't work. This is happening with both my Asus Crosshair 6 and 7 so I'm starting to think it might have something to do with how Amd's new chipsets handle usb or something like that. ill just use corsair link for now (hope it's still going to get updates) thanks for all the help! Link to comment Share on other sites More sharing options...
Asylum Posted April 29, 2018 Author Share Posted April 29, 2018 here is what I'm seeing when I install icue over CL. Corsair link says that my devices are now controlled by iCUE but then iCUE says no devices are detected.. i exported a new log and so i attached that new log file to this post.. It seems to have some kind read out now that says: 2018-04-29T17:46:52 W cue.sensors.system_info: Values request failed: 5 "Request timeout"icuelog.zip Link to comment Share on other sites More sharing options...
DevBiker Posted April 29, 2018 Share Posted April 29, 2018 here is what I'm seeing when I install icue over CL. Corsair link says that my devices are now controlled by iCUE but then iCUE says no devices are detected.. Right ... and that's what I would actually expect. CLink looks for a registry key that's added when iCue is installed to see which devices it should "ignore" if it detects them. It doesn't actually "know" if iCue is seeing them. i exported a new log and so i attached that new log file to this post.. It seems to have some kind read out now that says: 2018-04-29T17:46:52 W cue.sensors.system_info: Values request failed: 5 "Request timeout" Any service_error log though? Link to comment Share on other sites More sharing options...
Asylum Posted April 30, 2018 Author Share Posted April 30, 2018 Any service_error log though? I see. So without that error log file it's hard to figure out whats happening. But that file isn't in the archive I uploaded from iCUE. thanks. Link to comment Share on other sites More sharing options...
DevBiker Posted April 30, 2018 Share Posted April 30, 2018 It's not in the archive. It would be under %PROGRAMDATA%\Corsair\Cue\Service Logs. Link to comment Share on other sites More sharing options...
Asylum Posted April 30, 2018 Author Share Posted April 30, 2018 It's not in the archive. It would be under %PROGRAMDATA%\Corsair\Cue\Service Logs. OK I understand. it's suppose to be in program data. but because of my luck no error log there either.. :roll: so I'm still in the same boat. lol thanks again man! Link to comment Share on other sites More sharing options...
Asylum Posted June 23, 2018 Author Share Posted June 23, 2018 Just a quick update. I tried the newest version (3.4.95) and it also doesn't detect any of my devices. I don't know what else i can try. Link to comment Share on other sites More sharing options...
Exsosus Posted July 9, 2019 Share Posted July 9, 2019 Hi, everyone. After 3-months + with Corsair support the answer is simple when devices do not show as they should in Corsair Link. The answer is not iCue, which I was told by support. Here you go! Step 1: Run Winver in Run command. Step 2: Uninstall iCue complete and if you have Link installed, that too. Step 3: Restart Windows. (Yes I know its windows 10 but this is hardware related. Do it). Step 4: Install Corsair Link 4.9.9.3 for Windows version 1809 OS Build 17753.557 or later. Step 5: If you want iCue for your keyboard RGB and other accessories install that now. You should have all devices showing in Corsair Link! Enjoy. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.