When a computer function works in another app, user account or port, keep the repair inside the failing context. For Windows USB-C or Thunderbolt dock, first use the original upstream cable and power supply, then add one function at a time.
What this covers
- Windows USB-C or Thunderbolt dock with this exact failure state
- Diagnosis across laptop port capability versus cable, dock firmware, power budget and peripheral
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleName the failing app, user account, port or peripheral and one that still works. Expected behavior: provide the supported combination of power, display, USB and network through one upstream link.
Isolate the component boundary
ReversibleUse the original upstream cable and power supply, then add one function at a time. Swap only the app, account, cable, port or user profile while keeping the computer unchanged. Boundary to separate: laptop port capability versus cable, dock firmware, power budget and peripheral.
Correct only the proven cause
ReversibleUpdate dock/laptop firmware or replace the limiting cable, adapter or dock. Repair the isolated app, user profile, driver binding or physical path.
Verify and stop safely
ReversibleRetest both contexts after sign-in and one cold restart. Stop for heat, buzzing, melted connectors, liquid or charging instability.
Evidence ledger
Sources behind this answer
Exact questions