I have no idea how to fix USB issue

Question

Hello. I did this text with AI so I hope it made full review of the problem:

There’s a persistent issue with my Meta Quest 3 when trying to connect to my PC using Meta Horizon Link. The headset is detected by Windows and by the Meta PC software, but Link never finishes starting. It gets stuck on a black screen with three white dots indefinitely.

I'm hoping someone has encountered the same issue or can suggest something beyond the usual troubleshooting steps.

PC specifications

Headset: Meta Quest 3
CPU: AMD Ryzen 5 5600
Motherboard: Gigabyte B450M DS3H V2
GPU: NVIDIA GeForce RTX 3060 12 GB
RAM: 32 GB
OS: Windows 10 64-bit, freshly installed
Connection: USB cable directly connected to the motherboard

This is a fresh Windows installation, and Meta Horizon Link was installed for the first time. There are no remnants of previous Meta/Oculus installations.

The problem

When I connect the Quest 3 to the PC via USB:

The PC detects the headset.
The headset detects the PC and may automatically launch Quest Link.
The headset displays three white dots on a black screen.
The loading screen remains indefinitely. The PC Link application may also become unresponsive and cannot always be closed normally.

Sometimes I switch the connection mode from USB Link to Air Link and back to USB Link. The PC is detected again, but the same three-dot loading screen appears.

I cannot properly test Air Link or Steam Link because I don't currently have access to a Wi-Fi network. My main concern is getting wired USB Link working.

What I have already checked

Windows detects the Quest 3 correctly.
The headset appears as a USB device with VID/PID 2833:0186.
Both Reality Labs USB interfaces are present and report Status: OK:
- Reality Labs Composite XRSP Interface
- Reality Labs Composite ADB Interface
Both interfaces use the WINUSB service.
The USB device is connected through an AMD USB 3.10 xHCI controller.
The connection is reported as SuperSpeed in the Meta log.
The active Reality Labs driver is oem25.inf, version 1.4.0.0, dated 15 May 2025.
The OVRService is running.
OVRServer_x64.exe responds normally according to Windows. Its CPU usage does not meaningfully increase while the headset is stuck on the three dots.
I found no relevant OVRServer application crash events in Windows Event Viewer.
Windows Defender does not show relevant blocking or detection events.
No USB class UpperFilters or LowerFilters entries are configured.
The Windows OpenXR runtime is already set to the Meta runtime.
The Windows OpenCL/OpenGL/Vulkan Compatibility Pack mentioned in another troubleshooting discussion is not installed.
Switching the Windows audio output device did not solve the problem.
Restarting the OVRServer service did not solve it.

Important information from the Meta log

The log contains the following sequence when the headset is connected:

USB hotplug event received, creating connection object...
USB connection initialization started with 1 connection descriptors

connectionDesc[0]: winusb,2833,ff,8A

usb speed: SuperSpeed

Connected participant on transport winusb,2833,ff,8A

ActiveSession::addConnectedHeadset

This suggests that the headset is detected and the XRSP USB transport is successfully created.

However, immediately afterwards, the log reports:

WinUsb_Initialize(0x...) failed: (8)

ovrError_XRStreamingUSBIssue (-6102)

There is also another message shortly afterwards:

CreateFile(...) failed after 14 attempt(s): (0)

Failed to construct channel for winusb,2833,ff,89

The latter appears to refer to a different USB interface/channel (ff,89), whereas the XRSP interface (ff,8A) was successfully detected. I'm not sure whether this second error is relevant or just a secondary probe.

Another notable sequence in the log is:

session terminated. type=1, reason='session ended by peer'

XRS Device Thread USB: Connection run returned forced termination

USB hotplug event received, creating connection object...

The USB connection is then initialized again, but the headset remains stuck on the loading screen.

What I would like to know

Has anyone encountered this exact combination of symptoms on Quest 3: three white dots, WinUsb_Initialize failed: (8) and ovrError_XRStreamingUSBIssue (-6102)?
Could this be a known issue with a particular Quest 3 Horizon OS firmware or Meta Horizon Link PC software version?
Does WinUsb_Initialize failed: (8) indicate a USB driver/interface problem, or can it also occur when the Link runtime fails to initialize the PCVR session?
Is there a way to reset or reinitialize the Quest Link USB transport without factory-resetting the headset or reinstalling Windows?
Are there any known conflicts involving AMD B450 chipsets or AMD USB 3.10 xHCI controllers and Quest 3 Link?
Has anyone found a reliable workaround for this issue?

___

All I gotta add is:
- This windows installation is absolutely fresh - no legacy at all. Same as Meta Horizon Link app.
- this thread offers a kind of “fix” but it never worked through the issue is the same