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 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
ReversibleCheck Device Manager or System Information for whether the hardware is even detected, and whether an error code is shown. 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 peripheral on a different port or user account, and test a different peripheral on the same 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. 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. Preserve managed VPN/security policy and stop for damaged Ethernet hardware.
Evidence ledger
Sources behind this answer
Exact questions