c-attack

You can't go back to a prior 5.xx version. It's all server side, so no way to pull down the file. The workaround for mdwflyer was to uninstall CUE 5, then install CUE 4.33 and run the normal lighting wizard. Then proceed to install CUE 5 again over the top of CUE 4. The configurations files stay and the lighting config remains intact. Note this only works for solving a configuration issue. It did not resolve the end of the line physical lighting issue and we are still working on that.

OK, can confirm I am seeing this as well. Likely in place for most users. In general, Sleep mode tends to be problematic for CUE and I locked CUE up several times working different combinations of effects and sleep/wake cycles. However, if you need to use it what did work for turning off your lights in sleep mode is to set a black static layer in Device Memory Mode and then leave DDM toggled on when you put the PC to sleep. That worked multiple times for me and turns the lights off prior to entering S3.

Not sure how this slipped by and probably too late now. Nevertheless… Did you finish already? Hopefully two separate loops for dual GPUs and CPU?

Murals are not part of the profile back up system and not part the profiles at all. It used to be something called “instant lighting”. Just a quick drop down color for your entire system. Toggle on/off. It has since grown into something more but doesn’t really have a wait to preserve the files and still exists as a toggle state. Good job tracking down the bad file. Hard to believe the DPI library is capable of preventing launch, but there it is. At least that’s an easy setting to recreate.

I’ll try later on tonight, but it seems like it’s not dropping into DDM mode in time. If so, it’s a bug and we’ll have to wait for a correction. Unfortunately there are going to be some of these and the new hardware mode is more than a name change under the hood.

If you can't uninstall the software, then the underlying registry files are corrupt. You need to remove it one of two ways. 1) Manual -> Reboot the PC to safe mode. Try the uninstall there. Then follow the directions below for how to delete Corsair User settings. Then you need to clean the registry. Corsair used to include directions for this, but have recently removed them. I imagine a few users did not follow them properly. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE You need to Command (R)un -> "regedit" to bring up the registry. Then navigate to H_Key Current User -> Software and find the Corsair folder. Delete it. Even when properly uninstalled, it always leaves behind an audio file here. Now go to H_Key Local Machine -> Software and again delete the Corsair folder there. Restart the PC to return to normal mode 2) Software Assisted - I have been recommending people user Revo Uninstaller or other professional software removal tools. Corsair is now doing the same, presumably so users don't have to tinker in the registry themselves. Revo will grant the elevated privileges necessary to remove it and the registry entries. Safe Mode is a pain too, so this is often the better path. The free version is sufficient. No need to buy anything. My recommendation is to use Revo, particularly if you don't normally use the manual tools. Rebooting to safe mode is annoying and a multi-step process.

This usually suggests a software conflict with another program. MSI Aura/Mystic Light and Gigabyte Fusion often do this when set to sync all and try to take over other devices. However, red is the default fallback color for Corsair lighting when something is wrong, so there are other possibilities. Device detection is mostly about the USB pathway. You are piggy backing the Lighting Node Pro through the same line as the Commander Pro. Not all motherboards will allow that. I realize you are likely still using the Commander for speed control, but try connecting the LNPro directly to the motherboard in the Commander's place to see if it will detect. If it does not detect there, that suggests a problem. If it does, then you need a powered USB hub rather than the passive unpowered Commander Pro ports. What motherboard are you using?

They have renamed "Hardware" Actions/Lighting/etc. to "Device Memory Mode" and it is a toggle state for setting it up. A lot of prior hardware settings have been wiped with these changes and need to be redone. 1) Go to the Home Screen and get out of Murals. 2) Click on your RAM. 3) On the RAM screen, select Device Memory Mode. 4) Create a static color black (0,0,0) and apply it to all modules. (Assuming you want them off in Sleep mode). 5) Click on the little save disk icon near the toggle. If you forget, CUE will auto-prompt you to save. 6) Make sure you toggle Device Memory Mode off. It will stay active and divorce the RAM from CUE until you deactivate.

CUE Link controlled fans do NOT follow a custom curve when in Device Memory Mode. The custom curve defaults to the Link XD5 Temp as it should, but when CUE is closed it substitutes CPU temp for the native coolant temp in the pump. This then causes the fans to run at maximum. I believe this is a prior issue, but now with the active saves in Device Memory Mode this needs to be corrected. Way too many opportunities for people to make mistakes with this setup. Recommend anyone using a CUE Link Hydro X system use the Balanced or Extreme fan preset for DDM mode until resolved.

AMD CPU? This is a known issue in the current release. Th rest is likely a result of the failed install (before you restarted) and unfortunately the most prevalent issue with CUE 5. You need to clean install CUE and there are two main paths to do it. But first, make sure you export and valuable profiles. Despite the missing gear, the profile data in CUE still contains the info for any missing devices including those not currently connected. You will be able to reimport them after to restore them. 1) Manual -> Reboot the PC to safe mode. Try the uninstall there. Then follow the directions below for how to delete Corsair User settings. Then you need to clean the registry. Corsair used to include directions for this, but have recently removed them. I imagine a few users did not follow them properly. https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE You need to Command (R)un -> "regedit" to bring up the registry. Then navigate to H_Key Current User -> Software and find the Corsair folder. Delete it. Even when properly uninstalled, it always leaves behind an audio file here. Now go to H_Key Local Machine -> Software and again delete the Corsair folder there. Restart the PC to return to normal mode 2) Software Assisted - I have been recommending people user Revo Uninstaller or other professional software removal tools. Corsair is now doing the same, presumably so users don't have to tinker in the registry themselves. Revo will grant the elevated privileges necessary to remove it and the registry entries. Safe Mode is a pain too, so this is often the better path. The free version is sufficient. No need to buy anything. The rub is for some users one way works and the other does not. We haven't figured out why, but it appears the files can become corrupted in different ways. I would try the Revo version first because it is easier and faster.

Asus motherboard? CUE has a lot of trouble with the Asus embedded controller and often reports junk values like 0C, 127C, or impossible fan speeds. Some other boards do this too, but with far fewer errors. The other possibility is if you have one of those AMD boards from X570 era with chipset fans, they do run at a high speed compared any normal, larger fan.

Sorry for the delay. Unforeseen complications putting things back together. From any Commander Core/XT FAN RGB port, you have the following options -> HD fan (12 LEDs), LL (16-> 12outer, 4 inner)), 8 Series LED Fans (8), ML-Pro (4), QL (double sided 34 LEDs, or "Pump Cap" (13 - 8 outer/5 inner). So this can work, but no strip option and it can't do more than 34 LEDs for any one connection. The LED port on the Commander XT has the full range normally found on Commander Pro or Lighting Node Pro controllers. All of the above except the "pump top", plus LED strips up to 6 x 10 LEDs, all the Hydro X combinations in 16 LEDs straight line strips or as a CPU block 16/8 LEDs, and most importantly external LED strips where you can pretty much do any number up to 204 LEDs. This makes the LED port the very valuable one and it takes a different adapter from the 4 pin LED one for the fans. There are a couple of possible combinations. You could do the CPU and GPU on the fan ports and set them as LL fans. You won't notice the one missing light on the GPU. However, a LL fan is dual ring device and a lot of it's effects are "inner vs outer" ring designs. That won't come through on a single ring or straight line 16 LEDs. It also makes the LED numbering a bit weird for linear effects. When I was doing this with my Lian Li SL v2 fans (16 LEDs), I would often change the designation from LL to 10 led strips to cover the length so the lighting patterns would follow a linear pattern. The case LED strip goes to the LED port and become LED strip (10) x 3. Any other options would involve connecting the case strip to a RGB fan port as a QL fan to cover the 28 LEDs, then some combination of either CPU or GPU on the LED port. No strong preference and it might depend on how visible the CPU or GPU is from your position. All else being the same, I put the GPU on the LED port so I can call it Hydro X XG7 and get a GPU UI in the CUE -- just to make things easier to identify. None of these are perfect options, but the first is likely the least troublesome. I worry the 28 LED strip will doing moving patterns in sections like a QL fan with it's synchronized two sided design. You might find that cool or completely annoying.

This should be updated soon and there was a similar problem with two Hydro X pumps back on the original release. Using two hubs can introduce a second problem -- you can't update the FW for hubs with two connected. Most users have been getting around this by disconnecting one hub while they update the FW and setup the other. The new DDM mode is an interesting workaround since it effectively separates the hub from CUE momentarily. I could not think of a reason when deliberately divorcing a single device from CUE would be useful when this was under discussion, but I guess this is one. It might work for any needed FW updates as well until that gets sorted.

Sorry, I misread the QX as QL in your original post. You are in the same position as everyone else with a CUE Link Hub. The recent firmware update to expand the capacity to 24 devices has re-arranged the fan numbering and designation. Anyone with a CUE Link Hub really needs to do a clean install for this version. Make sure you export all your profiles first, so you can reimport them later. You will need to redo settings and dashboard, but that is just as well because the new assignments will scramble them anyway. See below. Normal Clean Install (should work) - https://help.corsair.com/hc/en-us/articles/360025166712-iCUE-How-to-perform-a-clean-reinstallation-of-iCUE Corsair Explanation and recommended path - https://www.corsair.com/us/en/explorer/diy-builder/blogs/addressing-over-current-protection-issues-expanding-the-icue-link-system-hub-to-24-devices *If you are still getting missing file notices, definitely do the Revo clean install or manually delete the registry options.

Not in any practical sense. Theoretically someone with the necessary skill could chop up the AIO and run tubes to the gpu and back. However, that system wasn’t designed to include another device or add in the 250W+ from the GPU. It would not be a very good solution performance-wise or in terms of warranty. The XG3 was intended to be used in custom loops of any type, including the Corsair line if Hydro X CPU blocks, pumps, fittings etc. This a different world than AIOs.