3.7k. Posted April 28, 2020. in HWinfo, when starting it, hit settings and under the Safety tab, disable Corsair and Asetek support. This will prevent HWinfo from conflicting with the Corsair services and it should work fine. (but you won't have any reading of corsair devices within HWinfo).

My current install path is: 6×LL120 -> Corsair RGB Hub -> Lighting Node Pro -> Motherboard via USB. All are fully connected to SATA power and separate fan power hubs. All fans turn on immediately upon startup, but are locked into a red color with the exception of Fan#1 being partially green.
Four fans worked fine, bought two more, they did not light up, then I read about turning on the two new fans using a Corsair RGB hub and the Commander Pro device: 1. Launch iCUE software. 2. Select the Commander Pro device. 3. Click lighting setup. 4. Tell the software how many fans. Guys, i just went through hours of trouble shotting this to find the most simple fix. (usually how that goes). The wide cable that goes from the AIO cooler to the commander pro is poorly manufactured and is probably most peoples problem. Take it out and re-seat it into the commander pro very firm and flush. Then re-boot and you should be cooling. In this video, we'll show you how to install and set up the CORSAIR iCUE COMMANDER CORE XT.The CORSAIR iCUE COMMANDER CORE XT lets you intelligently control

It depends on the fans. Corsair devices, even if resized correctly, have a hardware limit depending on the fans. EX: a lighting node pro maxes out at 204 LEDs per channel, but in reality it can only handle 3 QL fans per channel due to hardware limitations. 1. dewman45.

pVxGoYO.
  • ncud3pk1m9.pages.dev/175
  • ncud3pk1m9.pages.dev/316
  • ncud3pk1m9.pages.dev/156
  • ncud3pk1m9.pages.dev/392
  • ncud3pk1m9.pages.dev/525
  • ncud3pk1m9.pages.dev/371
  • ncud3pk1m9.pages.dev/176
  • ncud3pk1m9.pages.dev/276

    • corsair commander pro not working