MrBraydogg

Yes! Now using the powered NZXT internal usb hub and everything is working how it should be!

Just purchased that hub for myself. Considering everything is being detected properly I'm sure power draw is the issue. I will update & hopefully seal this post when its on my rig in two days :biggrin:. Thanks for your input DevB, & all the help you bring.

DevB, in most of these senarios, is it common ground to use NZXT's device for my issue?

Yes. No, iCUE does not detect the LNP when its connected to the extender by itself. This part is where i was going with my hypothesis as well... until I did some digging into USBDeView and found that the device is displaying an output of 50mA when connected to the extender... suffice to say that may be the problem. Then I plugged the LNP straight to the MOBO header, and USBDeView persisted to display LNP with an output of 50mA...

PREVIOUSLY READ POSTS (I won't let @DevBiker down): https://forum.corsair.com/v3/showthread.php?p=940351&p=940351 https://forum.corsair.com/v3/showthread.php?t=178995 Prerequisites: Turn off fast startup in BIOS?: YES Turn off fast startup in WINDOWS?: YES DISABLE HXCI in BIOS? YES Does USBDeView show NoPRO connected with a green dot? YES NoPro Firmware wipe? YES Complete iCUE reinstall? YES Relevant Information: MOBO: ROG Crosshair Hero VI (ONE usb 2.0 header) Windows Version: 10 Home, Build 1909 iCUE Software Version: 3.23.66 Corsair Products: H115i PRO Lighting Node PRO x3 LL120 RGB (connected to NoPRO) As previously stated, my current MOBO only has ONE USB2.0 internal header. Because of this, I need to use a USB2.0 Extender (That is the one I purchased). The H115i PRO IS detected by iCUE when either directly connected to the MOBO or the extender. The NoPRO on the other hand is detected by USBDeView when either directly connected to the MOBO or the extender, but fails to be detected by the iCUE software when connected to the extender. I'm at the point of believing that this is an oversight in iCUE software... Any more information/operations that you all would like me to try, I would gladly give a shot.

Type iCUE in your windows start menu > Right-click, open file location > Right-click iCUE in file explorer, properties > Compatibility tab > Change High DPI Settings > Check the box "Override High DPI Scaling Behavior," and in the drop down right below change "Application" to "System (Enhanced)" > click OK, then Apply > Restart the application. Thanks Toasted :biggrin:

Hey there, just wanted to post a quick bug I happened to come across regarding the sizing of the iCUE window when both my monitor (1080p, primary screen, 100% scaling) and connected TV (4k, secondary screen, 200% scaling) are on. The issue is my connected TV is scaled to 200% normal size, thus making the iCUE window twice its original size, and not able to resize smaller, making the program non-practical to use on my monitor display when my TV is turned on. (dragging the iCUE window to the TV screen, it is usable). Any chance you guys can look into this resizing issue? I included a zip with two example images. Thanks! Software Ver 3.10.125iCUE bug report.zip