USB Wavlink ST334UA cloning storage dock fails when connected on W11Pro laptop

I've used this doc on Win 10 laptops and worked great, but attaching to my 11 Pro i get a brief screen pop- The unknown usb device could not be loaded and experienced an error - port redirect failure. Note: this occurs when using the usb-a port on the laptop. I have tried using the usb-c adapter they included, but i get no response at all from the PC when using usb-c connection. i have my suspicions, but thought i would ask a new set of eyes for your thoughts.
Here are the 3 event logs that are directly related to my connection attempt via usb-a:
Wavlink storage clone doc WL-ST334UA- Events listed under device manager- Unknown USB device (Port Reset Failed).

Events:

Device Settings not migrated:
-Event viewer: Source: Kernel-PnP Event ID:442
Device settings for USB\VID_0000&PID_0001\5&274d72c6&0&19 were not migrated from previous OS installation due to partial or ambiguous device match.

Last Device Instance ID: USB\VID_0BC2&PID_AB30\MSFT30NA7TWC71
Class GUID: {4d36e97b-e325-11ce-bfc1-08002be10318}
Location Path: ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(SS03)
Migration Rank: 0xF000FFFFFFFF0033
Present: false
Status: 0xC0000719
*****
Device Configured (usb.inf):
-Event viewer: Source: Kernel-PnP Event ID: 400
Device USB\VID_0000&PID_0001\5&274d72c6&0&19 was configured.

Driver Name: usb.inf
Driver Package ID: usb.inf_amd64_34674696d738c56d
Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.26100.9444
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device ID: USB\RESET_FAILURE
Outranked Drivers: usb.inf:USB\RESET_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\ROOT_HUB30\4&32051b5f&0&0
****
Device not started:
-Event Viewer: Source: Kernel-PnP Event ID: 411
Device USB\VID_0000&PID_0001\5&274d72c6&0&19 had a problem starting.

Driver Name: usb.inf
Class GUID: {36fc9e60-c465-11cf-8056-444553540000}
Service:
Lower Filters:
Upper Filters:
Problem: 0x2B
Problem Status: 0x0

I had co-pilot analyze your thread and here's the answer I got:

Short answer: The dock isn’t failing because of drivers — it’s failing because Windows 11 can’t complete USB enumeration. The logs show a hardware‑level reset failure, not a software issue.

What the logs actually show:

• Settings not migrated → Windows 11 never receives a valid VID/PID from the dock, so it can’t match it to any known device profile.
• Configured using usb.inf → BADDEVICE.Dev.NT → Windows falls back to the “bad device” handler because the USB stack can’t read descriptors.
• Matching Device ID: USB\RESET_FAILURE → The controller is reporting a reset‑level failure.
• Device not started (Problem 0x2B) → Enumeration never completes; Windows can’t bring the device online.

None of these point to a driver problem. They point to the dock failing at the electrical/firmware handshake stage.

Why it worked on Windows 10: Windows 10 is more tolerant of borderline USB devices. Windows 11’s newer XHCI stack is stricter and rejects devices that don’t respond cleanly during reset or descriptor readout.

USB‑A vs USB‑C behavior:

• USB‑A gives you a brief popup and then a reset failure → the port provides enough power to wake the dock, but enumeration fails.
• USB‑C (via the included passive adapter) gives no response at all → the adapter likely doesn’t pass through the signaling the dock needs. Do with it what you will.

Most likely root causes:

1. The dock’s USB bridge chipset is too old or incompatible with Windows 11’s stricter USB stack.
2. Power‑up timing issues — the dock may not stabilize quickly enough for the laptop’s controller.
3. Marginal cable or port quality amplifying the reset failure.
4. The laptop’s USB controller firmware being less tolerant than the one on your Windows 10 systems.

Practical things to try:

• Put a powered USB 3.0 hub between the dock and the laptop. This often isolates timing issues and allows enumeration to succeed.
• Try a different USB‑A 3.0 cable — flaky cables can cause exactly this reset‑failure pattern.
• Try different ports, especially on the opposite side of the laptop (often different internal hubs).
• Test the dock on another Windows 11 machine to confirm whether the issue is universal.
• Check whether Wavlink offers firmware updates for your specific ST334UA revision (many do not).

Bottom line: The event logs show a USB‑level reset failure, not a driver or OS configuration problem. If a powered hub doesn’t fix it, the dock’s chipset simply isn’t compatible with your Windows 11 laptop’s USB controller.