icue Commander Pro No Longer Detecting Fans or XD5 After Upgrade to v5.1 - still not working after downgrade to v4.33.138

[p2im0]

[X-posted my comment from the Release Notes Thread]

 

I have a Commander pro, corsair fans attached, and an XD5 attached.  Everything has worked fine for 2+ years.

I just updated iCUE in place to 5.1 and it lost all fans and my XD5 connected to my commander pro.  I have a separate flow sensor/alarm that immediately started going off when my pump stopped spinning.

I cannot seem to get the new iCUE to detect my fans or pump.  When I force a firmware update on my commander pro they're detected for a second and I get a message "iCUE has updated 1 module: COMMANDER PRO" and then they disappear and my pump stops working again.

I just downgraded to  v4.33.138 and I now have the same issue. No voltage reported, all fans and pump missing from my Commander Pro.  They spin up full speed for a second when I force a Commaner Pro firmware update and then disappear from the app.

NOW WHAT?!

Fans  & Pump show up for 5 seconds after a force of firmware update on commander pro

 

 

Not working on v4.33.138, after the in-place upgrade to 5.1

[p2im0]

GIF of what happens when I update firmware in v4 iCUE.  Some fans show up for a second and poof, disappear again. (sped up the firmware update time to fit as a GIF)

[G_Sector]

Same thing , I lost all my sensors.  It looked like they had some new add-on for the Sensors... then it looked like it was updating the add-on, but the icon just kept spinning and nothing happened and now there is nothing showing at all under Sensors.  This software just went from great to crap in one update.

[G_Sector]

I just went back and reloaded 4.3 and all my sensors are back... I won't update now for a while.

Edited May 9 by G_Sector

[p2im0]

FYI the way I ended up fixing this was disabling "CorsairLink and Asetek support" in HWINFO64.  I'm not sure how it got re-enabled, but doing that in combination with hard-reset the Commander Pro, and completely wiping out iCUE and all settings and I have it working again.

Still frustrating.

[c-attack]

Unfortunately that is a common result when running AIDA or HWinfo at same time as CUE and they get entangled fighting over polling. In hwinfo you can directly disable monitoring of Corsair internal devices (fan controllers, AIOs, PSU) and you should be fine. AIDA tends to be a bit trickier. You may still see some impossible values reported in either program on occasion. Anytime you see 0s, missing UI elements, or ridiculous values you most likely are seeing a software conflict. 

[gumbislice]

On 5/9/2023 at 7:10 PM, p2im0 said:

FYI the way I ended up fixing this was disabling "CorsairLink and Asetek support" in HWINFO64.  I'm not sure how it got re-enabled, but doing that in combination with hard-reset the Commander Pro, and completely wiping out iCUE and all settings and I have it working again.

Still frustrating.

This Just fixed it for me too. I just bought a commander pro for a decent price on eBay and was scared I got ripped off with a defective unit. I already had to turn off the Corsair monitoring from HWINFO64 because it was affecting my lighting but I did not disable it, just turned off the monitoring. Now my commander pro is working. Thank you!