When a computer function works in another app, user account or port, keep the repair inside the failing context. 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
ReversibleName the failing app, user account, port or peripheral and one that still works. 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. Swap only the app, account, cable, port or user profile while keeping the computer unchanged. 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. 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. Preserve managed VPN/security policy and stop for damaged Ethernet hardware.
Evidence ledger
Sources behind this answer
Exact questions