Why is my network adapter missing on Windows?

What this covers

A missing network adapter is one of the few Windows problems that looks like dead hardware but almost never is. Windows can lose sight of a perfectly working NIC after a driver update, a Windows update, a sleep cycle, or a corrupted Winsock catalog. The commands below are ordered so each one narrows the cause instead of guessing: first find out whether Windows can see the device, then force it to re-detect, then rebuild the software layer that talks to it, and finally confirm the link is actually up.

Symptom

Check whether Windows sees the adapter at all

Open PowerShell as administrator and list every network adapter with its status, link speed and description. This is the fork in the road: an adapter that appears with a status of Disabled or Not Present means the hardware is fine and this is a software problem; a list that is empty or missing your adapter means Windows never enumerated the device, so you move on to forcing a re-detect. You know it worked when you get a clean table back instead of a red error.

$ Get-NetAdapter | Format-Table Name, Status, LinkSpeed, InterfaceDescription -AutoSize

Cross-check with the adapter's physical address

This is a second, independent look at what Windows actually sees, and it is worth doing because an adapter can exist in the OS yet fail to report a hardware address — which points at a driver or binding problem rather than a missing device. If your adapter's MAC shows up here but not in the status list, you are dealing with a driver fault, not dead hardware. An empty or truncated result confirms the device really is absent.

$ getmac /v

Make Windows re-detect the hardware

This is the command-line equivalent of “Scan for hardware changes” in Device Manager, and it is the single most effective fix when an adapter vanishes after a driver update, a Windows update or a hot-plug event. Run it, then look at the adapter list again. If the adapter reappears, the driver simply was not bound to the device — no reboot needed. If it stays missing, the driver itself is broken and you continue to the next step.

$ pnputil /scan-devices

Stop Windows powering the adapter down

Some adapters — Wi-Fi chips and USB Ethernet dongles in particular — disappear when Windows suspends them to save power, and never come back until the next restart. Disabling power management on the adapter keeps it enumerated across sleep cycles. Only do this if the adapter returns after a reboot but drops out again hours later; the setting is fully reversible, so you can put it back if it changes nothing.

$ Disable-NetAdapterPowerManagement -Name "Wi-Fi"

$ Enable-NetAdapterPowerManagement -Name "Wi-Fi"

Rebuild the network stack

If Windows still has nothing usable to talk to, a corrupted Winsock catalog or TCP/IP stack can make a perfectly present adapter invisible to the networking layer. This resets both to their defaults. A restart is required, and the command affects every adapter on the machine, so expect saved VPN profiles, proxy settings and custom DNS entries to be cleared. Success looks like the adapter appearing with a normal status after the reboot.

$ netsh winsock reset && netsh int ip reset

Confirm the adapter is back and actually linked

List your adapters one last time and check that the one you care about shows a status of Up alongside a non-zero link speed. That number is the proof you want: not only did Windows re-detect the hardware, but the link itself came up. A status of Disabled means you still need to enable the adapter; a status of Not Present means the fix did not take and you should go back a step.

$ Get-NetAdapter | Format-Table Name, Status, LinkSpeed, MacAddress -AutoSize

How to confirm it worked

Get-NetAdapter lists the adapter with Status “Up” and a non-zero LinkSpeed, and the taskbar network icon goes back to normal.

Undo everything

Every command above can be reverted. Run these in order to undo all of it.

$ Enable-NetAdapterPowerManagement -Name "Wi-Fi"

Review before running — some steps may not be independent.

Sources

• Netsh - Network Shell - Windows CMD
  SS64 · technical · 2026-09-17
  Evidence: SS64 lists netsh commands including 'netsh winsock reset' and 'netsh interface ip reset' for restoring TCP/IP and Winsock defaults.
• Get-NetAdapter
  Microsoft Learn · vendor-doc · 2026-09-17
  Evidence: Returns adapter objects with Status, LinkSpeed and MacAddress properties.
• Get-NetIPInterface
  Microsoft Learn · vendor-doc · 2026-09-17
  Evidence: Returns IP interface properties such as ConnectionState and Dhcp per address family.
• netsh
  Microsoft Learn · vendor-doc · 2026-09-17
  Evidence: Documents netsh WLAN commands including `netsh wlan show profile name=... key=clear` and `netsh wlan delete profile name=...`.
• PnPUtil - Plug and Play Utility
  SS64 · community · 2026-09-17
  Evidence: Documents pnputil /scan-devices to trigger a rescan for plug and play device changes.
• pnputil command syntax | Microsoft Learn
  Microsoft · vendor-doc · 2026-09-17
  Evidence: pnputil /scan-devices scans the computer for any device changes.
• Disable-NetAdapterPowerManagement
  Microsoft Learn · vendor-doc · 2026-09-17
  Evidence: Documents disabling power management features (selective suspend, wake patterns, offloads) on a named network adapter.
• Netsh contexts and commands | Microsoft Learn
  Microsoft · vendor-doc · 2026-09-17
  Evidence: Microsoft documents the netsh winsock and netsh interface contexts, including reset commands that restore their default configurations.

Last verified: 2026-09-22

Related guides