c-attack

Full clean install AND registry clean? Can you explain the “no color” part? We can see the AIO, QX fans, and CUE link hub are showing in your screenshot. Does this mean the items are missing from the UI in the underlying menu? They are there but lighting effects do not work?

There's a long thread about this in the troubleshooting section. The upgrade to allow the CUE Link controllers to handle up to 24 fans has messed up the enumeration and chaining. You'll need to do a clean install to clear the old data. The directions are below. Make sure you export any valuable profiles so they can be reimported back in later. This does erase all profiles and settings. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE If you want to try, go to Windows Settings> Apps and find Corsair iCUE. Click on the drop down menu at the end of the line and select "modify". Follow the prompts for a repair install. This takes 30 seconds and does not delete data. A couple of users mentioned this worked for them without the full wipe. Other users not affected at all, so it does seem to vary a bit.

They have changed some of the underlying associations with this build. It's not going to go back, so everyone is going to need to move forward sooner rather than later. Better to prepare, export your valuable profiles to make current backups, then clean install if there is an issue. It's not guaranteed you will have a fan count issue and some of us updated without encountering this.

It's 35mm from center to center. If I understand your intent, then any 24mm cap would extend only another 4mm on each side.

Yup, but should happen automatically on first load since the new FW is now public. The only issue with adding many CUE Link hubs is you will use up a lot of USB 2 ports and PCI-e cables. While I suspect you have the PSU and powered usb hub to handle it, I don’t how it will work out in reality. Last generation users ran into problems running 3+ Commanders on separate lines. I don’t know if anyone has tried 4 CUE hubs yet. If you want to be the test case, by all means try and let us know. In your position, I might stop at three using the 3rd for XD5 + GPU(?). You’ll also have the 1000D’s Commander Pro in there. That will handle the case logo, the cpu block with an adapter, and any strips you need. I keep waiting for CUE link strips, but we haven’t seen them yet.

There should be a shipping manifest in the package with the new 140mm fan, but frankly it doesn't matter what it says. You don't need to prove which department at Corsair made the mistake. Just show that one was made and get them to correct it. The Zendesk help email you've been corresponding in may have details. The original RMA request should also have the fans listed. If the shipping manifest shows 2x120 and there is a 140mm inside, a picture is likely sufficient to make your point.

No free lunch on this and that 4 way splitter is just that... 4 unpowered connection ports. It's real purpose is to allow you run multiple independent chains back to the system hub without having to run them through each other. Since your radiators are in side by side pairs, I don't see an advantage. You will need 2 CUE Link Hubs for 32 fans. I theory you could do this with three to avoid the 14 fan brightness clipping, but I think a 10% reduction for going 2 fans over (16 per hub) is worth it and these QX are really bright to begin with. One hub for each 480 radiator pair. 8 to one side and 8 to the other. Pump will need to go into one of these chains. I suppose that's what the 4 way splitter is for. You can run the XD5 back to the splitter on one end rather than being forced from a fan end point to the XD5 to the hub. Very case layout specific as to whether it helps. I can't tell if that GPU is block is CUE link of not.

Unfortunately I am not surprised. Respond again to the original ticket and remind them the RMA is for 2x120. Upload a picture of the wrong 140 fan box. It might not even match the shipping invoice.

You will have to leave the Commander Core that delivers power to the H150i Elite Capellix XT. That's the only way for the pump to get power, even if you don't use the fan ports. The Lighting Node Pro can go, unless you need it for strips or other 3rd party LED devices. 10 QX fans can run from 1 CUE Link Hub.

Go to the connected Link Hub device in CUE and run the setup Wizard again. See if it will detect it through normal means. If it does not, shutdown the PC and flip your PSU off. Hold down the case power button for 10 seconds to drain any residual power. Then flip the PSU back on and start normally. This should trigger all devices to check their connections again. Make sure all fans are selected in the Lighting Effects tab for the chosen pattern. What water cooling device?

The controller that comes with the AIOs is a “Commander Core”. It has a dedicated connection in the end to power the pump. The “Commander XT” is a stand alone fan speed and rgb controller with no AIO power port. It cannot delivery power to the pump.

Forced firmware update? The only other thing we see is sometimes the motherboard rgb software tries to grab control when CUE lets go. This is not common anymore with Asus and you likely can disprove this with a simple shutdown, PSU off-on restart. If the LED sticks during boot, the problem is likely with the module. Probably time to open a ticket with Corsair as it may be a hardware issue.

You probably need to clean out the files at this point and it's likely part of the installation package is corrupt leaving you in limbo. See the directions for a clean install below. Make sure you do the registry clean out. This is where problems tend to linger. This will erase all your profiles and settings, so hopefully you previously backed up any valuable profiles. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE

I don’t think there is any way for us to know on this end. However, installation errors if this type are the most common problem with CUE 5. Something caused it to crash and when that happened the files became corrupted. A bit hard to guess about what it might be, but likely it’s something that also tried to interact with Corsair components or blocked a communication pathway. Most users do not see repeated problems of this type, but if you do turn in debug logging in the CUE settings and then hopefully someone can trace it back to the origin.

Make sure you do a full clean install, especially the registry clean. This certainly appears to be corruption of those files. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE Are you able to uninstall it? Most users with corrupted install files have trouble getting g it out too. You may need to reboot to safe mode to remove it or this instance I would be inclined to use a professional uninstalled like Revo to take care of multiple issues. The free version should do the job.