Windows 10 Network Adapter Driver Missing After Update

Start by identifying the failure state: a truly missing adapter needs an offline driver reinstall, a hidden adapter usually needs Device Manager and a reboot, and an unknown device needs the correct network driver. Fixing the wrong case wastes time and can leave Wi-Fi or Ethernet unusable. This guide shows the shortest recovery path for each state after a Windows 10 update.

Missing adapter triage

Use this table before you try driver downloads. The symptom tells you where to look next, which saves time when the PC has no internet.

That split matters. A hidden adapter is not the same as a missing driver, and an Ethernet Controller under Other devices is not the same as a dead NIC. Treating all three the same leads to the wrong fix path.

📊 Windows 10 support ended on October 14, 2025. Source: Microsoft.

Why the adapter disappeared

After a Windows 10 update, the failure usually falls into one of four buckets: driver corruption, a hidden or disabled device state, firmware-level LAN disablement, or power management after sleep. Windows 10 support ended on October 14, 2025, so many systems now sit on older driver stacks that can be fragile after a feature update or a cleanup pass.

Driver corruption after update

An update can replace a working driver with one that fails to start, or it can leave a stale entry in the driver store. In that case, Windows may show the adapter in Device Manager, may hide it, or may move it to Other devices with a warning icon.

A common first-timer mistake is assuming the adapter vanished from hardware when it only moved categories. If the device still appears under Network adapters or Other devices, the chipset is usually still detectable.

Hidden or disabled device state

Windows can hide an adapter after a bad start, a sleep resume failure, or a settings change. The device may be present but greyed out. That is why Show hidden devices matters before any deeper repair.

Firmware-level LAN disabled

If the machine never shows the NIC in Windows or BIOS/UEFI, the onboard LAN controller may have been disabled in firmware. This is common after a BIOS reset or CMOS change. For some desktops and many laptops, Windows cannot repair that state until firmware turns the controller back on.

Power management after sleep

Some adapters are disabled by power-saving settings after sleep or resume. In Device Manager, the Power Management tab can include Allow the computer to turn off this device to save power. If the problem starts after sleep, check that setting on the adapter and on any related USB wireless device.

How do you check Device Manager?

Open Device Manager first, then check the Network adapters section, the View menu, and the Other devices area. The fastest path is to reveal hidden devices, inspect the current status, and force a hardware rescan before you decide whether the driver is missing or the device is disabled.

1. Open Device Manager from Start or search.
2. Open View and select Show hidden devices.
3. Expand Network adapters and look for a greyed-out entry.
4. Check Other devices or Unknown devices for Ethernet Controller or Network Controller.
5. Select Action and choose Scan for hardware changes.
6. Open the device properties and read the status code.

Windows repair guides often advise Show hidden devices in Device Manager for a reason: it reveals devices that are present but not active. Scan for hardware changes can also pull in a device that was not enumerated correctly after the update.

What do Code 10, 28, and 31 mean?

These codes separate a missing driver from a broken one. Code 28 usually means Windows has no usable driver package for that hardware. Code 10 and Code 31 mean Windows found something, but the adapter still will not start cleanly.

Code 10

Code 10 generally means the device cannot start. That often points to a driver that loads badly, a wrong package for the chipset, or a firmware setting that blocks the controller. If you see Code 10 on a Wi-Fi or Ethernet adapter, do not assume a generic update will fix it.

Code 28

Code 28 means Windows has no driver for that device. This is the clearest sign that you need the exact chipset driver, often found by reading Hardware Ids first. If the adapter is under Other devices and shows Code 28, the hardware is being seen but not matched.

Code 31

Code 31 means Windows cannot load the required drivers. That often happens after a partial update, a damaged driver store, or a bad rollback. A clean reinstall of the right package usually works better than repeated update clicks.

For recovery, Code 28 usually goes straight to driver identification. Code 10 and Code 31 often need a driver removal, reboot, and reinstall of the exact chipset package. If the device is gone entirely, the code will not help until the hardware appears again.

Can Windows Repair it first?

Yes, but only for the right failure state. The built-in Network Adapter troubleshooter and Windows network reset are worth trying when Windows still sees the adapter or when the stack is damaged. They are not the best first step for a BIOS-disabled LAN controller or a device with no driver at all.

Network adapter troubleshooter

The built-in Network Adapter troubleshooter is available under additional troubleshooters in Settings. It can detect common adapter and stack problems, and it often pairs well with driver checks. If Windows still shows the device, this is a low-risk first repair before deeper changes.

Windows network reset

Windows network reset is accessed from Network & Internet status settings. It restores default network settings and reinstalls network adapter drivers. That makes it useful when the network stack is tangled, but it does not guarantee that a missing adapter will return if the driver package itself is absent.

Windows update issues can be fixed by using Network Reset and scanning for hidden devices, but the order matters. Try reset when Windows still recognizes some part of the adapter or when multiple network components are broken at once.

When reset helps and when it does not

Reset can help if Wi-Fi or Ethernet disappears after a bad configuration change, VPN cleanup, or update side effect. It usually does not help if Device Manager shows Code 28 with no driver, or if BIOS/UEFI has the onboard LAN controller turned off.

How do I reinstall a missing Wi-Fi or Ethernet driver without internet?

Use the hardware IDs to identify the exact chipset, then move the driver on USB from another PC. If Windows cannot auto-find the driver, the PCI\VEN and DEV strings tell you what the adapter really is, which matters more than the label Windows shows.

Get the chipset from Hardware Ids

Open the adapter or unknown device in Device Manager, then look at Properties and the Details tab. Hardware Ids usually include strings such as PCI\VEN and DEV for internal network chips, or USB\VID and PID for USB Wi-Fi adapters. Those values identify the exact controller family.

DriverGuide identifies PCI\VEN_14E4&DEV_1692 as a NetLink BCM57780 Gigabit Ethernet PCIe device, and USB\VID_0BDA&PID_8176 as an RTL8188CUS 802.11n WLAN Adapter. Those examples show why the ID matters more than the device name.

Choose OEM, Microsoft Update, or generic driver

For laptops, start with the manufacturer support page. Dell, HP, Lenovo, and ASUS are the preferred source because they usually package the correct Wi-Fi or Ethernet driver for that exact model. If the maker provides a model-specific package, use that before anything else.

Use Microsoft Update only when Windows offers a clearly matching network driver and the device is already identified correctly. Use a generic driver only when the OEM package is unavailable and the hardware ID points to a common chipset family. For example, a RealTek RTL8188FTV Wireless LAN 802.11n Driver is a generic chipset package, not a model-specific laptop fix.

Move the driver with USB

Download the driver on another PC, copy it to a USB flash drive, and transfer it to the affected machine. If the package is an installer, run it locally. If the package is an INF-based folder, use Device Manager and the manual driver picker.

That option can expose a compatible driver already present on the system, which helps when the exact package is close but not auto-matched.

How do I find the right driver when the adapter is gone?

Start with the hardware ID, not the marketing name. A missing adapter may still have a PCI\VEN and DEV string or a USB VID and PID string, and those values point to the chipset family you need. That is the cleanest offline method when there is no internet.

Use the hardware ID, not the device label

Labels like Ethernet Controller, Network Controller, or Unknown device do not tell you enough. Hardware Ids do. Once you have the vendor and device values, search the OEM support page or the chipset vendor package list for the matching driver.

Know when to use a generic package

Use a generic package when the exact model package is missing but the hardware ID maps to a common chipset that Windows still supports. DriverGuide says network drivers are for Windows 11, 10, 8, and 7, but that does not mean any old driver will fit your device. Match the hardware ID first.

Suppose a laptop loses Ethernet after a cleanup update, but Wi-Fi still works. The Ethernet Controller under Other devices shows Code 28. In that case, the shortest fix is usually the OEM Ethernet package, not a full network reset.

Should I use the laptop maker’s driver or a generic driver?

Use the laptop maker’s package first when the system is a laptop, especially for Wi-Fi and Ethernet chips that were shipped with that model. Generic drivers are fallback options. They can work, but they are a second choice when the OEM has a precise package for the same hardware ID.

Manufacturer pages are usually the safest source because they match board revisions, power settings, and bundled firmware behavior. That matters after a Windows 10 update, when a driver that was stable before may not behave the same way after a reinstall or rollback.

Can a Windows network reset bring back a missing adapter?

Sometimes, but not always. Network reset is strongest when the network stack is broken, settings are tangled, or the adapter is still visible to Windows. It is weaker when the adapter has no driver, when Code 28 is present, or when firmware has disabled the onboard LAN controller.

Use it after you have checked hidden devices and confirmed the adapter is not simply greyed out. If the device is still present, reset can clear stale network settings and reinstall network adapter drivers. If the device is absent from Device Manager entirely, look at firmware and offline driver recovery first.

Use BIOS and recovery media

If Windows cannot see the NIC and BIOS/UEFI does not list it either, check the onboard LAN controller setting before you chase drivers. If the controller is enabled and the adapter is still missing, move to recovery media or a clean reinstall path.

Check onboard LAN in BIOS/UEFI

Look for onboard LAN, integrated NIC, network controller, or similar wording in firmware setup. After a BIOS reset or CMOS change, that setting can flip off. Until it is enabled, Windows repair tools will not bring the adapter back.

Use Windows 10 installation media

Windows 10 installation media can be created as a USB flash drive or an ISO file. Microsoft recommends a blank USB flash drive with at least 8 GB for installation media, and MediaCreationTool.exe is the tool used to create it. That media can help with repair, reinstall, or offline recovery cases. (Microsoft Support)

If the machine has no network and the driver store is damaged, installation media can also provide recovery access when the local OS will not repair cleanly. Keep the media on hand before you need it.

Bring the driver in from another PC

Download the correct driver on a second computer, copy it to USB, and install it on the problem machine. That is the safest path when the adapter is gone and there is no network path left inside Windows. It also avoids guessing at a wrong package from a random download site.

Frequently asked questions

Why did my network adapter disappear after a Windows 10 update?

A Windows 10 update can replace a driver, hide a device, or expose a firmware setting problem. The adapter may still exist under Network adapters, may move to Other devices with Code 28 or Code 31, or may stop appearing if power management or BIOS/UEFI disabled the controller.

How do I find a missing network adapter in Device Manager?

Open Device Manager, choose View, then Show hidden devices. Check Network adapters first, then Other devices or Unknown devices. If the device is present but greyed out, enable it. If it is not listed, use Scan for hardware changes and read the status code before you move on.

What should I do if my Ethernet controller is under Other devices?

Read the Hardware Ids and install the exact Ethernet driver for that chipset. An Ethernet Controller under Other devices usually means Windows sees the hardware but lacks the right driver. Code 28 is the clearest sign that you need the proper package from the laptop maker or chipset source.

What does Code 28 mean for a missing network adapter?

Code 28 means no driver is installed for that device. Windows sees the hardware, but it cannot match it to a usable network driver. The next step is to read the Hardware Ids, identify the exact chipset, and install the correct OEM or chipset package from a USB drive.