1
Diagnostic step 1
Reproduce the failure while collecting Windows kernel logs (use Windows Performance Recorder / Windows Event Tracing for Windows) and capture USB/Thunderbolt device enumeration traces to correlate timestamps with resume.
FULL AI ANALYSIS
USB‑C dock stops enumerating devices after laptop lid close (S3) following vendor firmware update
Generated Oct 3, 2026, 12:35:03 AM
Analysis summary
The timing (started after dock firmware update) strongly implicates a firmware regression in the dock's handling of USB/Thunderbolt re-enumeration after host S3 sleep. Event log kernel messages about resource allocation and device migration suggest the host detects devices but cannot allocate required resources or driver stack fails to rebind. Reproducing on another host with same dock firmware increases likelihood of dock-side issue, but host Thunderbolt driver and BIOS interplay can also matter. Reversible diagnostics and controlled rollbacks are the safest path before formal escalation.
Possible causes
Dock firmware regressed and fails to properly enumerate or re-negotiate Thunderbolt/USB-C alternate modes after host enters/exits S3.
90%Host Thunderbolt driver or Windows power management interactions changed (driver/Windows update) causing devices not to be reattached after sleep.
60%Thunderbolt security policy or device authorization issue preventing re-attestation after resume (some docks require re-authorizing).
30%Cable/port negotiation edge case exposed by firmware update causing partial enumeration and kernel PnP resource allocation failures.
20%Suggested fixes
2
Diagnostic step 2
Temporarily roll back the dock firmware to the previous known-good version (if vendor provides rollback and instructions) on one unit to confirm regression; do not perform firmware changes on production-critical units without a recovery plan.
3
Diagnostic step 3
Test with a different certified USB‑C/Thunderbolt cable and an alternate Thunderbolt-capable host to see if reproduction is host- or dock-specific.
4
Diagnostic step 4
Enable Thunderbolt device debugging where available or gather the Thunderbolt Control Center and system BIOS logs; then open a vendor support ticket including captured traces and reproduction steps. Escalate to vendor if rollback confirms firmware regression or if logs show dock failing to respond to host enumeration requests.
5
Diagnostic step 5
As a temporary mitigation, avoid closing the lid (use external display mode) or prefer disconnect/reconnect of the cable after resume rather than rebooting the host; document workaround for end users until vendor fixes firmware.