1stMora Posted July 29, 2015 Share Posted July 29, 2015 For me corsair link doesn't update the fan speed automatically it will only work when you start the program and click on each fan. Link to comment Share on other sites More sharing options...
Specter Posted July 30, 2015 Share Posted July 30, 2015 Where is the v1.1.3. firmware for the H80i???? When I updated to CL 3.2.5676 my H80i firmware still reads 1.0.7........ I click check for updates, nothing comes back, I choose manual update and nothing is displayed! And to top it off my Commander mini LEDs change to red when I launch Corsair Link and all my fans connected to the H80i and Commander Mini goes to max until I click on each gadget individually , then they recognize their setting and goes back to normal. Link to comment Share on other sites More sharing options...
ph3nak Posted July 30, 2015 Share Posted July 30, 2015 For me corsair link doesn't update the fan speed automatically it will only work when you start the program and click on each fan. SAME I updated to win10 then updated all drivers. uninstalled CL but I didn't delete the profile folder. CL works all except for auto fan profiles Link to comment Share on other sites More sharing options...
mlai Posted July 30, 2015 Share Posted July 30, 2015 Win 10, and CL 3.2.5676 does not detect my AX860i. Under Win8.1 and CL 3.1.5570RC works fine. Link to comment Share on other sites More sharing options...
red-ray Posted July 30, 2015 Share Posted July 30, 2015 Where is the v1.1.3. firmware for the H80i???? When I updated to CL 3.2.5676 my H80i firmware still reads 1.0.7........ Is the H80i connected via the CLCC? I needed to USB Connect my H100i to get the firmware to update. See http://forum.corsair.com/forums/showthread.php?p=792164#post792164. Link to comment Share on other sites More sharing options...
Darkom Posted July 30, 2015 Share Posted July 30, 2015 still says that CL isnt compatible with w10 but still using w7 bc still waiting for the download Link to comment Share on other sites More sharing options...
davl7 Posted July 30, 2015 Share Posted July 30, 2015 OK, so I've followed all the instructions, got an old commander, h100i, and windows will not recognise it now matter what I do. The amount of time I have had to invest into getting this product working over the last 18 months I have owned it is unbelievable, I mean honestly, do you even have a developer team onsite?. MS have had beta version of 10 available for a long time now, seems like Corsair only bothered to look around 2 days ago at what the problem could be. Come on guys, you could be great if you got your act together. Release a version that works, without having to mess around for hours on end, just works. Yours Annoyed Link to comment Share on other sites More sharing options...
LoWRiDeR82 Posted July 30, 2015 Share Posted July 30, 2015 Guys I have windows 10 and downloaded the latest 3.2.5676 version. It works quite ok except one issue. On startup it cranks the fans of my H110i GT to the max, and they stay like that unless I click on each fan so that the custom curve setting column appears. I don't need to change any setting I just need to select each fan individually once and they go back to normal. Can someone suggest a fix for this so that I don't have to do it every time I reboot? Many thanks in advance Link to comment Share on other sites More sharing options...
Specter Posted July 30, 2015 Share Posted July 30, 2015 Is the H80i connected via the CLCC? I needed to USB Connect my H100i to get the firmware to update. See http://forum.corsair.com/forums/showthread.php?p=792164#post792164. Yes. It is connected to the commander mini via the CLCC. Link to comment Share on other sites More sharing options...
ntzphyr Posted July 30, 2015 Share Posted July 30, 2015 Thank you so much for this newest version. Works beautifully on win10, my H100i showed up with out the need of disconnecting it. Win 10 didn't advise that CL wouldn't work with it and the firmware updated without so much as a hiccup. Shame on you Corsair for making a grown man cry! I'm actually ecstatic! Woot! Link to comment Share on other sites More sharing options...
JohnOrion Posted July 30, 2015 Share Posted July 30, 2015 CL Version: 3.2.5676 Windows Version: Microsoft Windows 8.1 Professional with Media Center (x64) Build 9600 Summary: Only shows Temp for R9-390X does not show fan - program still doesn't set AX760i fan after waking from sleep mode. Details: The first bug is self explanatory. The second issue has been ongoing since V2.7 at least. If you set the fan for your Corsair PSU to a fixed percentage it will not keep that setting when you wake your computer from sleep. You need to open the Link window from the tray and wait until you see the PSU fan start spinning. Then everything is ok until your computer goes into sleep again. So basically to use this software with a Corsair PSU you need to open the programs main window every time you come out of sleep or the PSU defaults to the Default (no fan) option. Edit: Updated to Windows 10. No change. Still have the same issue. Link to comment Share on other sites More sharing options...
iFr0z3n Posted July 30, 2015 Share Posted July 30, 2015 CL Version 3.2.5676 Windows Version: Windows 10 Professional 64bit Corsair Commander version: Old corsair commander link firmware 2.0.6 Corsair commander not detected in CL. Installed correct drivers and tried the Windows 8 reg fix. No luck Link to comment Share on other sites More sharing options...
hyperionx Posted July 30, 2015 Share Posted July 30, 2015 I own the 'H100i and your "Corsair Link" software, It does not create the connection to the hardware properly.It has never worked well in all versions, updated and not. There is always a problem and never once functions without bother. win pro 8.1 x64 updated: 1. I removed AI Suite II. 2. I modified the USB registers as your guide. 3. I deleted hidden folders as your proposal. 4. I have reinstalled your software N times. 5. Something else I forgot to do for you? Nothing, in the device manager, there is no corsair link under the category USB. I regret the h100 without the software, only the name seems a mockery. for me became "Corsair No-link" :\ P.s: also add a feedback aesthetic. The interface is really ugly was fine in the 90's. but this is less of a problem. Link to comment Share on other sites More sharing options...
red-ray Posted July 30, 2015 Share Posted July 30, 2015 I own the 'H100i and your "Corsair Link" software Nothing, in the device manager, there is no corsair link under the category USB. Have a look at Devices and Printers what is there? Is there a Corsair Integrated USB Bridge? The H100i is a HID device Link to comment Share on other sites More sharing options...
MCansik Posted July 30, 2015 Share Posted July 30, 2015 Bugreport, as usual the software doesn't work as intended. For some reason all my fans are going really high speed for no apparent reason and the only reason I've found to stop them is to set fixed RPM (completely defeating the purpose of the unit). Pictures attached showing curves and speed. I've also got a problem where every so often all my LEDs flash on and off (Bought the LED-kit, like a retard I guess) if I have them on a lower value than maximum lightning (for example, if blue is set to 140) Link to comment Share on other sites More sharing options...
fisherd80 Posted July 30, 2015 Share Posted July 30, 2015 Hello, I cant get the Corsair Link Commander (the older one, not the mini) to be recognized by the Corsair Link software. I have followed the instruction given on the forum solving this problem. However none of the fans, LED light strips will appear. Also, I don't know if this is in the right topic. Any help please. fisherd80 Link to comment Share on other sites More sharing options...
Specter Posted July 30, 2015 Share Posted July 30, 2015 Bugreport, as usual the software doesn't work as intended. For some reason all my fans are going really high speed for no apparent reason and the only reason I've found to stop them is to set fixed RPM (completely defeating the purpose of the unit). Pictures attached showing curves and speed. I've also got a problem where every so often all my LEDs flash on and off (Bought the LED-kit, like a retard I guess) if I have them on a lower value than maximum lightning (for example, if blue is set to 140) You might want to take a look at your fan curve settings as if your max temp is 24C unless your temps are that low that you need your fans running at 4000RPm if something in your system hits 24C you may want to change those numbers to something realistic like 50c Link to comment Share on other sites More sharing options...
ph3nak Posted July 31, 2015 Share Posted July 31, 2015 Well it was working, now I can't open the window to the program from the menu. Link to comment Share on other sites More sharing options...
Specter Posted July 31, 2015 Share Posted July 31, 2015 Even the manual firmware update does not work. I get this error!!! See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index at System.ThrowHelper.ThrowArgumentOutOfRangeException() at System.Collections.Generic.List`1.set_Item(Int32 index, T value) at CorsairLink.PlugIns.ManualForm.combobox_SelectedIndexChanged(Object sender, EventArgs e) at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e) at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m) at System.Windows.Forms.ComboBox.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- CorsairLink Assembly Version: 3.2.5676.29375 Win32 Version: 3.2.5676.29375 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.exe ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- CorsairLink.Common Assembly Version: 2.7.0.0 Win32 Version: 2.7.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.Common.DLL ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34250 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 12.0.20806.33440 built by: FX45W81RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- Microsoft.Win32.TaskScheduler Assembly Version: 2.2.0.18504 Win32 Version: 3.2.5676.29375 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.exe ---------------------------------------- Telerik.WinControls Assembly Version: 2013.3.1127.40 Win32 Version: 3.2.5676.29375 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.exe ---------------------------------------- Telerik.WinControls.Themes.VisualStudio2012Dark Assembly Version: 2013.3.1127.40 Win32 Version: 3.2.5676.29375 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.exe ---------------------------------------- Telerik.WinControls.UI Assembly Version: 2013.3.1127.40 Win32 Version: 3.2.5676.29375 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.exe ---------------------------------------- TelerikCommon Assembly Version: 2013.3.1127.40 Win32 Version: 3.2.5676.29375 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.exe ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34243 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Management Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll ---------------------------------------- CorsairLink.PlugIns.CCVI Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.PlugIns.CCVI.DLL ---------------------------------------- CorsairLink.PlugIns.JoycePsu Assembly Version: 3.2.5676.29374 Win32 Version: 3.2.5676.29374 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.PlugIns.JoycePsu.DLL ---------------------------------------- CorsairLink.PlugIns.Clink Assembly Version: 3.2.5676.29374 Win32 Version: 3.2.5676.29374 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.PlugIns.Clink.DLL ---------------------------------------- CorsairLink.PlugIns.Flextronics Assembly Version: 3.2.5676.29374 Win32 Version: 3.2.5676.29374 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.PlugIns.Flextronics.DLL ---------------------------------------- CorsairLink.PlugIns.Robbins Assembly Version: 3.2.5676.29374 Win32 Version: 3.2.5676.29374 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.PlugIns.Robbins.DLL ---------------------------------------- CorsairLink.PlugIns.CpuId Assembly Version: 3.2.5676.29374 Win32 Version: 3.2.5676.29374 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.PlugIns.CpuId.DLL ---------------------------------------- CustomMarshalers Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/CustomMarshalers/v4.0_4.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll ---------------------------------------- Microsoft.GeneratedCode Assembly Version: 1.0.0.0 Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- CorsairLink.Ui.Legacy Assembly Version: 3.2.5676.29374 Win32 Version: 3.2.5676.29374 CodeBase: file:///C:/Program%20Files%20(x86)/Corsair/Corsair%20Link/CorsairLink.Ui.Legacy.DLL ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. Link to comment Share on other sites More sharing options...
PDG888 Posted July 31, 2015 Share Posted July 31, 2015 Upgraded to Win 10 New version of CL 3.2.5676 Everything working except 3 front fans that are connected to commander mini Also in CL no power supply tab or readings for AX860i Link to comment Share on other sites More sharing options...
JAMIE1000 Posted July 31, 2015 Share Posted July 31, 2015 done the schtasks.exe /Run /TN "\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser" and unstall etc still no luck, hopefully it MS side Link to comment Share on other sites More sharing options...
Administrators Technobeard Posted July 31, 2015 Author Administrators Share Posted July 31, 2015 done the schtasks.exe /Run /TN "\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser" and unstall etc still no luck, hopefully it MS sideWhen you ran that, did you run it in a command prompt that was ran as admin? It's not instantaneous. The Compatibility Appraiser will take some time to update. Link to comment Share on other sites More sharing options...
paesan Posted July 31, 2015 Share Posted July 31, 2015 Wow this finally works for me without any extra crazy workarounds. Using win 10 x64 with the h100i. Thanks. Link to comment Share on other sites More sharing options...
Dragon_Kin Posted July 31, 2015 Share Posted July 31, 2015 I must be doing something wrong because I tried multiple times and it's still saying it's not compatible. I updated the software and updated the firmware then I right clicked on cmd prompt and ran as admin and type exactly what was shown, hit enter and it said success then i closed the window. I also tried just copy and pasting what was posted and same thing, hit enter and it said success this time i left the cmd window open for 30mins before i closed it still nothing? Link to comment Share on other sites More sharing options...
William1 Posted July 31, 2015 Share Posted July 31, 2015 Yesterday, I ran the 'Reset Compatibility' for Win 10. Today, I installed the latest version of CL. I did not uninstall the previous version. On reboot, I was told of the firmware update for my H100i and of a second upddate for an 'un-named device'. I manually ran the update just for the H100i. I left my AX860i connected to my pump. Previously, it was rec. to disconnect all CL devices but the one you wanted to update. I felt brave. On reboot, all devices showed, and additional temp sensor on my motherboard was displayed. No manual configuring/hoop jumping was needed. However, CL did not run on start. I rebooted again and this time,. CL started on boot. Finally. The only complaint I have is the fan for the AX860i is not always able to be activated. I barely tax the PSU and with the fan running, it is just about 10 degrees F. over ambient. No fan and it is close to 30 F over ambient. So I like to let the fan run at about 40% (800 rpm). Sometimes it runs, sometimes it does not. CL mode (Quiet/Balance/Performance) has no effect on the PSU fan. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.