Jump to content
Corsair Community

CL 4 Doesn't Display Devices


joe6pac

Recommended Posts

Installed the new Corsair Link v4.2.0.162 on Win10 64 bit. Installation went smooth. However, no devices are displayed and no info messages of any kind. I can import a jpg of my computer image, adjust CL4 settings, but that's it! Tried a clean boot without firewall, but still no go. Anyone have any thoughts or ideas?

CL4-01.thumb.JPG.4ac5d521de2ca0c076c6bc8a13c0d887.JPG

CL4-02.thumb.JPG.87384cb395285ecb1962015457f587e4.JPG

468872324_CL3v3.2.5742asof20160210.thumb.JPG.5c42344b402b9071a37591cf58cff889.JPG

188878912_HWMonitor-20160211.thumb.JPG.1a01589e19cafac5d600fd839ad7ce35.JPG

Link to comment
Share on other sites

Interesting. I thought I was the only one who has this issue. The CorsairLink4 Service refuses to run. When I try to force it from the Services control panel it tries to run, then times out.

 

If it helps, I am using an H100i and an HX850i on Windows 7 (Ultimate if it matters), as per my listed specs. Also note that the HX850i is connected to the H100i through the CLink Digital port, and not through USB.

 

SiV seems to be able to read the information, so I know the info is available.

 

Firmware on H100i is currently 1.0.5, although I have also run 1.0.7.

Link to comment
Share on other sites

I'm having a similar issue. CL3 wouldn't run for me at all, it would crash every time I tried to run it. I had the same issue back when I was running an H100i instead of the H100i GTX I have now. The only way to deal with it back then was to run a very old version of CL2 but even that was iffy, so I ended up uninstalling it and connecting the fans straight to the motherboard to control them. With the release of CL4 I finally decided to try again. CL4 will run, but does not detect ANY devices in my system. I check for running services, and the Corsair Link 4 service is not running(it's also set to "Manual" which seems strange, one would think it should be automatic, but whatever). I try to start the service manually, and I get an Error 1053: the service did not respond to the start request in a timely fashion(I'm paraphrasing, but it basically said "nope, didn't work" which of course is all kinds of unhelpful). The only Link-enabled device in my system is the H100i GTX I'm currently running. It's USB connector is plugged in, and the driver for the device gets installed. SiV IS able to see it and change the fan profile, so the device itself is working.

 

Someone from Corsair, PLEASE tell me why in the heck your software still doesn't work on my system. This is incredibly frustrating, to the point where my next liquid cooler will likely be a different brand. I'm sick of dealing with this.

Link to comment
Share on other sites

SIV IS able to see it and change the fan profile, so the device itself is working.

 

Given SIV is reporting and controlling the H110iGTX then CL4 should. Do AIDA64 and HWiNFO also report it? I expect they will.

 

I expect the service being Demand Start is correct as it's only needed when the CL4 GUI is active, so I assume it starts it. On my system I can start and stop CLink4Service at will.

 

I am wondering why the CL4 service does not start and I suspect there is some aspect of your motherboard that confuses the CPUID SDK and causing the timeout. As it also uses the CPUID SDK I could try running HWM and see how far that gets.

 

Were it my H110iGTX I would log a call via https://corsair.secure.force.com/home/home.jsp and as the author of SIV would ask for a detailed explanation as to why my code can report my CL hardware and the Corsair supplied utility can't.

Link to comment
Share on other sites

Given SIV is reporting and controlling the H110iGTX then CL4 should. Do AIDA64 and HWiNFO also report it? I expect they will.

 

I expect the service being Demand Start is correct as it's only needed when the CL4 GUI is active, so I assume it starts it. On my system I can start and stop CLink4Service at will.

 

I am wondering why the CL4 service does not start and I suspect there is some aspect of your motherboard that confuses the CPUID SDK and causing the timeout. As it also uses the CPUID SDK I could try running HWM and see how far that gets.

 

Were it my H110iGTX I would log a call via https://corsair.secure.force.com/home/home.jsp and as the author of SIV would ask for a detailed explanation as to why my code can report my CL hardware and the Corsair supplied utility can't.

 

I tried uninstalling both CL4 and the device driver(it installed the "Generic Hydro" driver, rebooting and installing from scratch. I got the prompt to approve installing an Asetek driver, but when it finished there was an error in my system tray about no driver being found for the H100i GTX, and the generic driver was installed again. Trying to update the driver manually shows that there are specific drivers for the H100i v2, H80i v2 and H115i. No mention of earlier models at all. I uninstall the software completely and the device driver, and now when I reboot I've got under "Other Devices" the H100i GTX, with the ? by it indicating the system couldn't find drivers.

Link to comment
Share on other sites

Don't tell me what the screen shot says, Post the screen shot! Do you get as below?

 

Yes, that's what I get. SiV sees and controls the device just fine, HWM doesn't list it at all(I'm not at home right now, so any check I do of the home machine is through VNC, makes screen-capping tricky).

Link to comment
Share on other sites

Yes, that's what I get. SiV sees and controls the device just fine, HWM doesn't list it at all(I'm not at home right now, so any check I do of the home machine is through VNC, makes screen-capping tricky).

 

OK, just use the Corsair Hydro Series 7289 USB Device. This is for all of the H80iGT + H100iGTX + H110iGTX. I suspected this would confuse some CL users and Corsair should fix hydros7289.inf as I said in my post.

 

Link to comment
Share on other sites

OK, just use the Corsair Hydro Series 7289 USB Device. This is for all of the H80iGT + H100iGTX + H110iGTX. As I suspected it would this confused some CL users and Corsair should fix hydros7289.inf as I said in my post. I have just updated it to link to you post.

 

Given SIV reports your H110iGTX the driver is working as it should. Do not do any updates/changes to the driver.

 

 

 

HWM will not report the H110iGTX, I just wanted to check that it ran and from what you said it seems to. Again Post a Screen Shot so I don't have to guess!

 

Assuming it does what happens when you run CL4? How many seconds is CLink4Service in a starting state before it times out? You can check this from a command window by typing sc query CLink4Service.

 

C:\>sc query CLink4Service

SERVICE_NAME: CLink4Service
       TYPE               : 10  WIN32_OWN_PROCESS
       STATE              : 1  STOPPED
       WIN32_EXIT_CODE    : 0  (0x0)
       SERVICE_EXIT_CODE  : 0  (0x0)
       CHECKPOINT         : 0x0
       WAIT_HINT          : 0x0

C:\>

 

If I go into the Services window and try to manually start the Link 4 service, it takes all of about 2 seconds before I get the error message "Windows could not start the Corsair Link 4 service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."

 

if I run the sc query command you provided, I get the exact same response you showed as an example.

Link to comment
Share on other sites

You should not be manually starting the CLink4Service! Just run CL4 and this will start it for you.

 

Delete C:\ProgramData\CLink4\Service.log then run CL4. This should create a new log file. Does it give any clues as to why the service will not start?

 

I have no "C:\programdata\clink4" directory, but if you mean the folder where Link 4 was installed, that's "C:\Program Files (x86)\CorsairLink4", and there is no file in that folder named service.log, before or after I try launching CL4. There is no file named service.log anywhere on my hard drive, the only things closer are in the .NET folders, and the file names aren't exact matches. This is on Win7 Home Premium x64.

Link to comment
Share on other sites

Maybe that is the problem, you should have :eek:

 

Create C:\ProgramData\CLink4\ and see what happens :bigeyes:

 

Ah, looks like I do have it, but it's hidden(wish you'd mentioned that). Still no service.log file in there, however. Before OR after I launch CL4.

 

Only things in there are a couple of .config files.

Link to comment
Share on other sites

I uninstalled CL4(which removed the folder in C:\programdata), manually uninstalled the driver, rebooted. Installed CL4, allowed the driver install, rebooted. Launched CL4, and it's the same as before. No devices are detected by CL4. The Link4 service does not start. There is no service.log file that gets created in c:\programdata\CLink4.
Link to comment
Share on other sites

Hi all,

 

Thank you for patience, we are working on a fix for this in the next build. We will begin testing the build at the end of this week and if things go well, I can share a beta build with those who are experiencing this issue around the 24th-26th of this month.

 

I would definitely be interested in trying out that beta when you can share it, assuming the problem you're referring to is the same one I'm having.

Link to comment
Share on other sites

I'm with dewbak75 on this. I have the same issue (no working CL since version 2.x, the CL4 service refuses to run, no service log...) I am relieved to see that I am not the only one who has encountered this issue. I just find it so strange that SiV seems to work just fine. It sees the information being transmitted from my H100i and HX850i. I only run on an account that has admin privileges and I turned off UAC long ago as it was annoying and I am the only person who uses this PC.

 

I look forward to trying out the new version. Perhaps the new version of CL4 will do the trick.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...