A peripheral or feature that disconnects and reconnects on a computer is usually a power-management or driver-timeout setting, not failing hardware. For Windows network adapter, first compare another device and another network, then inspect adapter status and automatic IP.
What this covers
- Windows network adapter with this exact failure state
- Diagnosis across adapter/driver versus router, cable, radio and VPN/filter
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleNote whether the drop correlates with sleep/wake, a specific USB hub, or sustained heavy use. Expected behavior: obtain a valid link, IP route and DNS path over Wi-Fi or Ethernet.
Isolate the component boundary
ReversibleCompare another device and another network, then inspect adapter status and automatic IP. Test the device on a direct port with no hub, and disable USB selective suspend for that port. Boundary to separate: adapter/driver versus router, cable, radio and VPN/filter.
Correct only the proven cause
ReversibleUpdate/roll back the adapter driver or correct the one failed network profile. Disable the power-management setting that turns the device off to save power, or update the controller driver.
Verify and stop safely
ReversibleRun the device under the same load that triggered the drop for at least 30 minutes. Preserve managed VPN/security policy and stop for damaged Ethernet hardware.
Evidence ledger
Sources behind this answer
Exact questions