Muadweeb

Absolutely not. Nothing on this issue has been fixed.

Sorry about being short, I am just frustrated with a 70 dollar hum that is half (or less at times depending on "Updates") Functional. Want to know the crazy part? I just found out that this issue WAS (sort of) in their release notes for version 4.9.4.28: Known Issues: Users connecting Lighting Node PRO or AXi USB dongle to Commander PRO USB hub may experience detection issues if Commander PRO is connected to an AMD chipset or ASMedia USB controller. (Fix ongoing.) CPU core numbering may not report correctly for some users. (Fix ongoing.) Extra fans may appear under motherboard info after Link is left running over an extended period of time. (Fix ongoing.) Systems with AMD graphics cards may report one extra graphics card. (Fix ongoing.) Mechanical hard disks may not enter sleep state. (Fix ongoing.) Changing profiles does not change DRAM lighting. (Scheduled to be fixed in next release.) LL RGB fans will require the Corsair LINK software to function. This is a limitation of the Lighting Node PRO and Commander PRO hardware. CPUs with more than 16 cores will not report all cores. This is a limitation of Corsair LINK being a 32-bit application. I wonder why it has been left off the "Known Issues" recently...and if thats a bad indication that they've given up? Not too sure.

I finally got my cable from China, and unfortunately it did not solve my issue.

I have seen ZERO threads or posts ANYWHERE that says they are working on the compatibility issue between the USB headers on AMD boards and the Commander Pro/Link. As usual, with the latest update ZERO has been done on this problem. Like I said, it would be nice to hear from SOMEONE at Corsair that would even acknowledge that its an outstanding issue. Even their "known bugs" list on the latest release has yet to note it!! I'm getting pretty fed up with this.

Still waiting on my cable, and of course, any kind of word from corsair that they are actually working on a solution...

So THIS should get me around my hub problem? https://www.moddiy.com/products/USB-9%252dPin-Internal-Motherboard-Male-Header-to-USB-Type%252dA-Adaptor.html?gclid=Cj0KCQjw1-fVBRC3ARIsAIifYOMnk4kfgGidooP9WgNxYaSapwjJIKquIiP8JkwgQOwJXukyWyDbOCMaAsTgEALw_wcB

So basically, you got around the issue with the hub not being recognized by (essentially) attaching it to a rear I/o port? Interesting . I may have to try that, as my case has a HDMI pass-through that I can thread a USB cable out of. It will take up a rear port, but at this point if it works I dont care.

It actually takes a while to rear its head on mine. Typically after I leave the system off for most of the day, it will come back up. 1. AMD Chipset drivers were installed, i didn't let window auto do it. 2. I have disabled both of these functions, has no effect on the issue. 3. I tried forcing an update, but windows states that it already has the best driver. Strange, because the driver provider is Windows, the date on the driver is 6/21/2006; version 10.0.16299.15. I haven't been able to find a corsair specific driver at all. FYI, the newest Link update did nothing to fix the issue.

Is there any kind of an update on this issue? My Ryzen system is constantly showing a strange "Unknown USB Device" with a driver error in the control panel. ive traced this down to the USB hub portion of the commander pro, after many hours of troubleshooting. Not only that, but with my Commander pro hooked up, it randomly hangs the boot sequence with a GPU debugging LED lit. This is pretty unacceptable, considering that this has been an issue (from what I can tell) for at the very minimum 5 months. I need to know if I should hold out for the fix, or return both the lighting expansion kit and the commander pro since they are incompatible with my system. :mad: