Hydro H100i (V1) Not Detected
Closed this issue · 5 comments
I haven't been able to get this to detect properly for years, and coming across this project gave me some hope considering the original Corsair Link was dropped so long ago. I see it's fully compatible, and I followed the install instructions, but all I get is "Corsair Link could not initialize, or has no sensors" upon reopening FanControl post install. Same issue even in 1.6.0-beta.3.
I have always had a fan readout sensor sitting around 2300rpm that's never responded to anything, so I'm thinking that may be it. What steps are needed to give you the information needed?
From what I gathered, the log.txt only says "4/2/2024 3:55:22 PM: CorsairLink could not initialize or has no sensors.".
As for more, the only active device with vendor ID 1b1c is:
Port_#0011.Hub_#0001 USB Input Device HID (Human Interface Device) Yes Yes No No 4/2/2024 1:58:14 PM 9/30/2023 3:08:44 AM 1b1c 0c04 2.00 03 00 00 DESKTOP 7&2d3e72ab&0 HidUsb @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver hidusb.sys (Standard system devices) 100 mA 2.00 USB Input Device 10.0.22621.2506 HID_Inst.NT input.inf USB\VID_1B1C&PID_0C04\6&2f27204&0&11 Removable, SurpriseRemovalOK
Hi @Reaper511, can you post your CorsairLink.log file (located in the Fan Control directory)? Please attach it as a file to a new comment. Thanks!
Sure thing! Looks like an initialization issue. I didn't even notice said log.
CorsairLink.log
A weird update that was rather strange. Upon opening my start menu, suddenly there's a Corsair Link 4 shortcut. Opening it seems to have installed it and then opened Link 4. The H100i now shows up as well as sensors and such in FanControl. I have no idea whats occurred. All I did in the last 20 minutes was install Intel Presentmon, of which the Corsair Link 4 shortcut was created 4 minutes after it.
Based on the error in the log file, the device was malfunctioning and likely just needed to be reset (USB reconnect or power cycle). Are you still having trouble with this device?
Based on the error in the log file, the device was malfunctioning and likely just needed to be reset (USB reconnect or power cycle). Are you still having trouble with this device?
While my issue is fixed, unfortunately something else triggered it. Through several years of no detection even with Corsair Link 4 installed at times to test, along with hundreds of general restarts, and two rebuilds, not once did it get detected post Windows 10. It could have been a legacy driver changes on Corsairs side, but who knows. Thanks for taking a look.