Quest 3 USB 3.x SuperSpeed Intermittent Disconnects — Detailed Bug Report
SUBJECT Quest 3: intermittent USB 3.x SuperSpeed link loss during wired PC streaming; stable when the link is forced to USB 2.0 DEVICE Meta Quest 3 (eureka), Horizon OS build 52433670048800520, firmware 2026-09-24. PC: Windows 11 25H2 build 10.0.26200.9711, Intel Alder Lake-HX xHCI (PCI\VEN_8086&DEV_7A60), Microsoft xHCI driver 10.0.26100.9711. Cable: AMVR 5 m A-to-C active cable with an in-line VIA Labs hub (VID_2109 PID_0210 SuperSpeed half / PID_2210 USB 2.0 half) and a charge port. Streaming: Virtual Desktop Streamer 1.34.25 USB mode; Meta Horizon Link 1.115.0 also tested. PROBLEM During wired PC VR streaming the USB link drops intermittently. Windows logs Kernel-PnP Event ID 1010 "surprise removal" for VID_2833, the headset re-enumerates within 1-3 seconds, and any active streaming session ends. In some runs the link comes back at USB 2.0 and then runs for a long time without further events. The behaviour is intermittent: on the same hardware, 15 Quest PID_5018 PnP records occur in a 300-second audit window (17:46:25-17:51:25 on Nov 7), while another 1101-second period has zero such records, including a 300 MB ADB transfer at 112.5 MB/s. The audit window is a retrospectively selected raw-log interval, not the original monitoring start/stop. KEY A/B DATA (same headset, same cable, same host, no software change) USB 3.x, audit window 300 s -> 15 PnP records (PID_5018) USB 3.x, after reboot 28 s -> 5 USB 3.x, dense raw-log window 30 s -> 22 PnP records USB 3.x, desktop + 2 songs 550 s -> 0 USB 3.x, idle + 300 MB push 1101 s -> 0 USB 2.0 (passive adapter), idle 300 s -> 0 USB 2.0, saturated bulk transfer 2.7 s -> 0 USB 2.0 + VD streaming @~200 Mbps 900 s -> 0 (three Beat Saber songs) USB 2.0 + multi-hour gameplay full battery discharge: zero noticeable unexpected disconnects (user report, no continuous PnP log) The USB 2.0 runs are a true control: the device tree shows the in-line hub's SuperSpeed half (PID_0210) is completely absent and only its USB 2.0 companion (PID_2210) enumerates, so the SuperSpeed differential pairs were not part of the active link. TO REPRODUCE 1. Connect the headset to a PC USB 3.x port using a long active cable that has an in-line hub. 2. Start a wired streaming session (or leave it idle) and watch Windows Kernel-PnP Event ID 1010 for VID_2833. 3. Repeat with a passive USB 2.0 adapter in the path. In our case the removals stop completely. WHAT WE ARE ASKING 1. Any known Horizon OS issue or regression affecting USB 3.x SuperSpeed link stability for sustained high-bandwidth links? 2. Can Quest 3 USB PHY firmware or high-speed link power management cause intermittent disconnects of this kind? 3. Any known compatibility issue with Intel xHCI (Alder Lake-HX) or VIA Labs VID_2109 hub silicon in the cable path? 4. Can headset-side diagnostics distinguish a PHY link error, a host controller reset, and an application-initiated USB reconfiguration? If yes, what should a user capture? 5. Any released or planned firmware fix, and safe mitigations besides forcing USB 2.0? This reports **two distinct evidence levels**: a 900-second monitored USB 2.0 run and an additional several-hour, full-battery gameplay run described by the owner without synchronized event logging. The earlier May 2026 event cluster had 218 records, including 14 hub events; its negotiated USB speed is unknown. We do not claim the cable, headset, host controller or Horizon OS is defective.