Current Sensors etc.,
Aquacomputer cuplex kryos NEXT with VISION AM4
53129 Aqua Computer flow sensor MPS Highflow incl USB port (WAZU-324)
53230 Hubby 7
Aqua Computer D5 NEXT RGB Smart Pump

Over the last few weeks I've been adding the above components to my loop.
The top 3 have worked great I've been using aquasuite quite happily, this last weekend I added the D5 Next, that is fine in Aquasuite
but the flow sensor is not registering in Aquasuite.
When I boot into windows I get one or the other of these symtoms:-

Windows USB devices shows "Windows has stopped this device because it has reported problems. (Code 43)" & "Unknown USB device( Device Descriptor Request Failed)"


https://ibb.co/b33VjLd
and https://ibb.co/1LJx061
or
No detection but a repeating beeping as when Windows detects a new USB device.
Any help greatly appreciated. I have 2 USB 2 headers on my motherboard, have disconnected the Hubby temporarily and am using 3 of the four ports whilst trying to trouble shoot this.
Edit: Forgot to mention also tried running with the d5 Next Usb unplugged, the MPS Highflow still didn't register.

Thanks K2Viper for your interest. Answers in no particular order
Firmware was updated on installation when it was working, last week.

Have spent a fruitless morning uninstalling & reinstalling different versions of the chipset drivers. without success.
Discovered that my uefi usb settings let me enable/disable selected ports so disabled the 2 USB2 headers restarted windows, confirmed that the Vision & d5 pump usb was off restarted an enabled them in bios, therefore forcing Windows to reinstall the drivers, Vision and D5 upgraded fine was left with "repeating beeping as when Windows detects a new USB device" from earlier. Did notice Action centre showed a USB icon that the error was still there, the icon repeatedly flashing in synch with the sound, until I was shut down.
There are only the 2 x USB2 headers on the motherboard I have the Hubby which I've reconected, have tried different headers and order with no change.

sorry duplicated

Ahh thanks for that will have a look at it.

I've just added a small old EVO 960 m2 drive3 to my rig and installed a drive image backup I made on the 13th before I chcnged my loop to add the D5 next. Sadly it didn't work as the USB ports of the devices have changed as can be seen in the installed aquasuite from that time.

The Highflow usb appears but is unconnected following port change & driver failure.


https://ibb.co/1TN1zZQ


I've migrated from Intel z390 to AMD earlier this year, lured by the 3900X which is brilliant, seems I'm just beginning to understand the warts in AMD's drivers.

I used to have and old pcie 2 port hunb which was a realtek one with internal ports, could plug the hubby into that.Should do the trick with non amd drivers. Just have to find it lol. Many thanks for the heads up on that post. will order a USB-A cable to 4 pin MB header if I've lost it. Shelved till tommorow whilst I watch the football, maybe a wee bit more optimistic, tomorrow is another day !! Thanks.

Well the weekend came and went doing other things, congrats Bayern , finally got round to testing the Hi flow USB yesterday. Used a Intel z170 build. Cables long enough to reach across to plug into the spare usb 2 header on the z170.
Results the same.

z170-hi-flow-usb
https://ibb.co/WxjSxJ9

Usb driver version
The date that Microsoft gives is pretty uninformative as far as driver origins go. To find more right click select properties
and the version date is shown, copy the driver version 10.0.18362.693 preceed it with driver so google doesn't think it's a ip address and you can find some interesting results. https://support.microsoft.com/en-gb/help…pdate-kb4535996 . I did find on my AMD rig that the drivers were AMD sourced, not Microsoft, together with other info.
https://ibb.co/VJL9N58

z170 device manager
https://ibb.co/NNK749q

Same error as seen on X570
https://ibb.co/Srr5Zd9

So in this case I've sadly eliminated the issue being a usb compatability one. It appears there is a problem with my hi flow USB unit itself. Unless someone has any alternate suggestions I can't see any other options than removing it from the loop and requesting an RMA.