A computer feature or peripheral that has completely stopped should be separated into driver, permission and physical-connection layers before assuming component failure. 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
ReversibleCheck Device Manager or System Information for whether the hardware is even detected, and whether an error code is shown. 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. Test the peripheral on a different port or user account, and test a different peripheral on the same port. 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. Reinstall or roll back the driver, or grant the missing app permission.
Verify and stop safely
ReversibleConfirm the feature works after a full restart in at least two different applications. Stop for heat, buzzing, melted connectors, liquid or charging instability.
Evidence ledger
Sources behind this answer
Exact questions