Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Devices & drivers · reviewed troubleshooting

Network adapter missing in Windows 11: prove device detection before TCP/IP repair

If Windows cannot enumerate the Wi-Fi/Ethernet adapter, DNS flushes and browser resets are the wrong layer; focus on Device Manager, hardware detection and the correct driver.

Applies to: Windows 11Change risk: Low to mediumReviewed: 2026-09-17
Do this first
  1. Restart Windows once and reopen Device Manager.
  2. Use View > Show hidden devices only as an inventory aid; do not assume a hidden stale entry is active hardware.
  3. Use Scan for hardware changes or pnputil /scan-devices.
  4. Confirm the PC model and obtain the exact network driver from the manufacturer if Windows does not supply one.

What this problem usually means

Network-stack commands operate on adapters Windows already knows about. If the physical adapter is missing from Device Manager, the more relevant branch is detection, power/firmware state and driver installation rather than DNS or Winsock resets.

Ordered repair path

Work from the narrowest fix to the broader one.

1

Scan for hardware changes

Low risk

Why this belongs here: PnP rescan can rediscover hardware that was reconnected or not enumerated after a state change.

  1. Open Device Manager and choose Action > Scan for hardware changes, or use pnputil /scan-devices.
  2. Check Network adapters again.
  3. If the adapter appears with an error code, branch to that code.
pnputil /scan-devices
2

Install the correct model-specific network driver

Medium risk

Why this belongs here: A missing/incompatible driver can prevent a detected device from becoming a usable network adapter.

  1. Download the exact driver on another device if this PC has no Internet.
  2. Transfer it locally.
  3. Install the manufacturer-supported Windows 11 driver.
  4. Restart and recheck Device Manager.
Stop condition

When this guide stops being the right path

If firmware/UEFI or vendor diagnostics cannot detect an internal adapter, or an external adapter is not detected on another known-good port/system, leave the Windows-only repair path.

If the problem is still not fixed

Once the adapter is visible and enabled, use the Wi-Fi/Ethernet/IP/DNS guides based on the remaining symptom rather than continuing device-detection repair.

Evidence

Sources reviewed for this page

Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

ErrorCode 22 — Device Manager Code 22: the device is disabled

Code 22 means Windows sees the device but it has been disabled; enable the device before reinstalling drivers.

ErrorCode 10 — Device Manager Code 10: “This device cannot start”

Code 10 means the device could not start; Microsoft’s primary resolution begins with the device driver.

ErrorCode 12 — Device Manager Code 12: Windows cannot find enough free resources for the device

Code 12 is a resource-allocation problem; confirm the exact device before changing other hardware or firmware settings.

ErrorCode 28 — Device Manager Code 28: drivers are not installed

Code 28 means Windows does not have the driver installed for the device; reinstall the device driver rather than applying unrelated fixes.

ErrorCode 31 — Device Manager Code 31: Windows cannot load the required drivers

Code 31 is a device-driver loading failure; keep the troubleshooting scoped to the affected hardware.

ErrorCode 43 — Device Manager Code 43: Windows stopped a device after it reported a problem

Code 43 means a driver controlling the device told Windows that the device failed in some way; driver and hardware context both matter.